If the HTTP status code in the response within the 2xx range, the request is considered successful and any returned content will be parsed (based on the returned content-type) into an SMS reply. In all other cases (including network timeouts) the request is considered un-successful and will be re-tried after 1 minute. The returned content is read cased on content-type according to the following table:
Content-Type
|
Description
|
text/plain; [charset="xxx"]
|
The reply is read according to the specified encoding (optional, default is latin-1) and trimmed (leading and trailing whitespace is removed) and routed back as an SMS message.
|
text/html
|
Same as above, but all tags within the content are removed.
|
application/octet-stream
|
The content is read as 8-bit binary data and formed into a binary SMS message
|
| application/vnd.wap.mms-message |
If the account is set up for MMS messaging, the returned message is routed back to the original recipient as a MMS message
|
application/vnd.wap.si
|
The returned content is interpreted as a WAP Service Indidication document as defined in WAP-167-ServiceInd-20010731-a. This is an XML document that will be transformed into its binary equivalent (WBXML) and sent back the recipient as an SMS WAP-SI message |
The attributes of the reply message can further be altered using the following HTTP headers. These headers are all optional.
Header
|
Description
|
X-Tambur-UDH
|
An (optional) field that specifies the UDH part of the reply message. This should be encoded as two-character hex integers for each byte.
|
X-Tambur-Success
|
Set to "false" if the operation can be (billing wise) considered unsuccessful.
|
X-Tambur-Charge
|
Amount to be billed from the end-user, in cents and including tax. I.e. a 2 eur service should be signaled as 200.
|
X-Tambur-From
|
Set this if the sender in the reply message should be changed.
|
| X-Tambur-TransactionId |
When set, DLR's are enabled for the reply message, and given transaction id is returned back in the DLR request.
|
 | Not all of these attributes are compatible with all billing scenarios. Please check with Roottori support that your choice of message attributes is valid. |