Send an SMS
The SMPP specification defines several parameters, which relate to the source and destination addresses of a message.
The following table specifies the values that should be used when issuing submit_sm requests to the SMPP Server.
|Source_addr_ton||It is recommended that the address be always expressed in international format, i.e. prefixed with country code. In this case, the TON value is also ignored.However, if a longcode address is expressed in national format, the TON value should be set to 2.|
|Source_addr_npi||This value is not used by the SMPP Server|
|Dest_addr_ton||It is recommended that destination addresses be always expressed in international format, i.e. prefixed with a country code. Where this is the case, the SMPP Server will ignore the TON parameter.However, if the address is expressed in national format, the TON value should be set to 2.|
|Dest_addr_npi||This value is not used by the SMPP Server|
The encoding used with message data is specified with the SMPP parameter data_coding, also called DCS (data coding scheme). The SMPP Server will use this value to decode the data so that it can then be encoded with the encoding scheme required by the carrier.
The SMPP Server supports the following DCS values.
|0||Default value. With the SMPP Server this is GSM 03.38.|
|3||Latin 1 (ISO-8859-1)|
|4||Octet (8 bit binary). To be used for binary content.|
The SMPP Server does support the sending of binary messages, such as WAP Push and concatenated SMS. This capability is subject to destination carriers also supporting these message types.
Binary messages should be encoded with data_coding DCS value of 4 (Octet encoding).
Concatenated SMS must be implemented by the encoding of a user data header stored along with the message data. For such messages, esm_class must have the User Data Header indicator set, i.e. the bit represented by the hex value 0x40.