For sending messages,
data_sm can be used.
When sending more data in the message body or data field than can be submitted in a single submission to the carrier, Sinch will split transactions. These are charged as multiple transaction events.
To help ensure successful delivery, we'll review the way Sinch interprets source and destination addresses below.
Any values other than those listed below will be interpreted as TON 0x0 and NPI 0x1.
|Source Address||Arrives on handset|
|Sent to Sinch||Type Of Number(TON)||Number Plan Indicator(NPI)|
The type of source address is defined by the source address TON and NPI parameters.
- Alphanumeric sender is limited to a maximum length of 11 characters.
- MSISDN sender maximum length is 18.
- To enable a handset to respond to a short code, we recommend using TON=0x00 and NPI=0x01.
A sinch destination address should always be sent as the E.164 CC + NDC + subscriber number. This is also referred to as the “MSISDN” of a subscriber. For further information on the MSISDN format, see the ITU-T specification E.164.
|Sent to Sinch||Type Of Number (TON)||Number Plan Indicator (NPI)|
|46123456789||0x01 | International||0x01 | MSISDN|
Sinch follows the delivery receipt formatting outlined in SMPP Protocol Specification v3.4 Issue 1.2, Appendix B. Contact your account manager to add additional information to the delivery receipt by including MCC/MNC information.
In the value field, you will receive the MCC + MNC of the destination operator.
Optional parameter: 0x1403 (0x1403):
- Tag: 0x1403
- Length: 6
- Value (hex): 32 33 34 33 30 00 (Text: 23430n)
Result is MCC=234 and MNC=30
Review the receiving messages SMPP documentation.