A delivery_report is sent when TMS3 receives either a submit response or delivery report from the mobile network. This is then passed onto you via the URL that you have provided. The same format is used for both responses from the network, in order to simplify TMS3 client code.

HTTP Method: GET or POST (user selectable)

Data sent

msisdn

The destination (mobile number) that the message was sent to.

status

The status of the message. The status can be one of the following:

• ENROUTE - message is enroute to its destination (not in a finalised state yet).
• DELIVRD - message is delivered to destination.
• EXPIRED - message validity period has expired.
• DELETED - message has been deleted.
• UNDELIV - message is undeliverable.
• ACCEPTD - message was read by the network on behalf of the mobile user.
• UNKNOWN - message is in an invalid state.
• REJECTD - message was rejected by the network.

network_id

The ID of the mobile network that the message was sent to.

tms_session_id

The unique ID of the message as assigned by TMS3.

delivery_date

The date the message was finalised, i.e. delivered, rejected etc. The format for the delivery date is: yyMMddHHmmss, where:

• yy - year
• MM - month
• dd - day of month
• HH - hour
• mm - minute
• ss - second

batch_id

The batch that the message belongs to.

Example callback

GET - Parameters

?msisdn=27820000004&status=DELIVRD&delivery_date=110819105448& /
    tms_session_id=1082201817&network_id=1&batch_id=1108191254485252556

POST - XML

<delivery_report>
  <msisdn>27820000004</msisdn>
  <status>DELIVRD</status>
  <delivery_date>2011-08-19 10:54:48.274 UTC</delivery_date>
  <tms_session_id>1082201817</tms_session_id>
  <network_id>1</network_id>
  <batch_id>1108191254485252556</batch_id>
</delivery_report>