Reference section - SMPP
data_sm
SMPP data_sm
4.2.2 data_sm Operation
The data_sm operation is similar to the submit_sm in that it provides a means to submit a mobile-terminated message. However, data_sm is intended for packet-based applications such as WAP in that it features a reduced PDU body containing fields relevant to WAP or packet-based applications.
4.2.2.1 data_sm Syntax
| Field Name | Size octets | Type | Description | Ref. |
|---|---|---|---|---|
| command_length | 4 | Integer | Set to overall length of PDU. | 4.7.4 |
| command_id | 4 | Integer | 0x00000103 | 4.7.5 |
| command_status | 4 | Integer | 0x00000000 | 4.7.6 |
| sequence_number | 4 | Integer | Set to a Unique sequence number. The associated data_sm_resp PDU will echo this sequence number. | 4.7.24 |
| service_type | Var. max 6 | C-Octet String | The service_type parameter can be used to indicate the SMS Application service associated with the message. Specifying the service_type allows the ESME to avail of enhanced messaging services such as “replace by service_type” or control the teleservice used on the air interface. Set to NULL for default MC settings | 4.7.25 |
| source_addr_ton | 1 | Integer | Type of Number for source address. If not known, set to NULL (Unknown). | 4.7.1 |
| source_addr_npi | 1 | Integer | Numbering Plan Indicator for source address. If not known, set to NULL (Unknown). | 4.7.2 |
| source_addr | Var. max 65 | C-Octet String | Address of SME which originated this message. If not known, set to NULL (Unknown). | 4.7.29 |
| dest_addr_ton | 1 | Integer | Type of Number for destination. | 4.7.1 |
| dest_addr_npi | 1 | Integer | Numbering Plan Indicator for destination. | 4.7.2 |
| destination_addr | Var. max 65 | C-Octet String | Destination address of this short message For mobile terminated messages, this is the directory number of the recipient MS. | 4.7.8 |
| esm_class | 1 | Integer | Indicates Message Mode and Message Type | 4.7.12 |
| registered_delivery | 1 | Integer | Indicator to signify if a MC delivery receipt or an SME acknowledgement is required. | 4.7.21 |
| data_coding | 1 | Integer | Defines the encoding scheme of the short message user data. | 4.7.7 |
| Message Submission TLVs or Message Delivery TLVs | Var. | TLV | 4.2.4 |
4.2.2.2 data_sm_resp Syntax
| Field Name | Size octets | Type | Description | Ref. |
|---|---|---|---|---|
| command_length | 4 | Integer | Set to overall length of PDU. | 4.7.4 |
| command_id | 4 | Integer | 0x80000103 | 4.7.5 |
| command_status | 4 | Integer | Indicates outcome of data_sm request. | 4.7.6 |
| sequence_number | 4 | Integer | Set to sequence number of original data_sm PDU. | 4.7.24 |
| message_id | Var. max 65 | C-Octet String | This field contains the MC message ID of the submitted message. It may be used at a later stage to query the status of a message, cancel or replace the message. | 4.7.14 |
| Message Submission Response TLVs or Message Delivery Response TLVs | Var. | TLV | 4.2.5 |
SMSC Simulator
Looking to test your SMS application or SMS-enabled application before connecting to a live SMS gateway or SMSC? Our SMSC Simulator service allows you to test using the SMPP protocol v3.3, v3.4 and v5. Read more about SMSC Simulator >
SMPP Client
Test an SMPP account and service using the Melrose Labs SMPP Client . Use from your web browser. No software installation necessary.