A mobile_originated is sent when TMS3 receives a mobile-originated SMS (premium rated) from the mobile network. The SMS is then passed onto you via the URL that you have provided, in order for you to process the SMS and respond to it.

NB: You need respond to this request with a text string, which will then be sent back to the mobile user.

HTTP Method: GET or POST (user selectable)

Data sent

destination

The short code (or number) the mobile-originated (MO) SMS was sent to.

message

The message contained in the SMS.

network_id

The ID of the network which the SMS was sent from.

source

The MSISDN (mobile number) of the mobile phone that sent the SMS.

tms_session_id

The unique TMS3 session assigned to the MO SMS. This ID will be same for the reply SMS, and can be used to track the delivery report for the reply SMS.

Example callback

GET - Parameters

?message=Test+message&network_id=1&source=27820011223&tms_session_id=297643932&destination=33050

POST - XML

<mobile_originated>
  <source>27820011223</source>
  <destination>33050</destination>
  <message>Test message</message>
  <tms_session_id>297643932</tms_session_id>
  <network_id>1</network_id>
</mobile_originated>

Expected response

This callback expects your application to respond with a simple text string that will be sent back as-is to the mobile user as a reply SMS message.

If you do not want to send a reply SMS message, you may either omit the reply completely (i.e. just send back the HTTP 200 OK response code with no response body) or respond with a text string containing only the word END.

Example response

This is a reply to your SMS!

The response above will cause TMS to send back an SMS message containing the text "This is a reply to your SMS!" to the the mobile user's phone.