Delivery Reports
Overview
Delivery reports provide feedback to applications concerning the delivery of MT messages. This information can include:
- Confirmation of successful billing for premium messages
- Confirmation of successful delivery to the handset (where this is supported by the carrier)
- Details of errors which prevented successful delivery
Contents
- Enabling receipt of delivery reports
- Interpreting delivery reports
- Delivery report type
- Detailed reason code
Enabling receipt of delivery reports
In order to receive delivery reports, two steps are necessary. Firstly, delivery reports must be requested when the corresponding MT message is submitted to the MX Telecom SMS Gateway:
- HTTP interface: via the report parameter.
- SMPP interface: via the registered_delivery parameter in the DELIVER_SM PDU.
Secondly, delivery reports must be routed to an HTTP URL of your choosing or via your SMPP connection. This routing is configured on a per-account basis; please contact us to have this routing configured or altered.
Interpreting delivery reports
A delivery report contains the following:
- The SMS ID of the MT message. This is a positive 64 bit integer used to uniquely identify an SMS message as it passes through the SMS Gateway. As well as when sending delivery reports, the SMS Gateway will pass on this ID in the response back to a submitted SMS message and when delivering Mobile Originated SMS messages.
- A date, giving the time at which the delivery event occured.
- A delivery report type code giving an overview of the delivery status of the message.
- A detailed reason code, giving further information on the reason for the delivery report.
Delivery report type
The delivery report type code is one of "DELIVERED", "FAILED", "BUFFERED" or "REJECTED". This will correspond to the Type nibble in the detailed reason code. See here for more details on the meaning of each code.
Detailed reason code
The detailed reason code is a 4-byte integer value. It can be interpreted as explained here.
