SMPP command list and required SMPP state
SMPP supports the following commands through the following
SMPP session states:
Please note data_sm, query_sm, cancel_sm, replace_sm and submit_sm_multi are not supported.
| SMPP PDU Name | Required SMPP state |
|---|
| bind_transmitter | OPEN |
| bind_transmitter_resp | OPEN |
| bind_receiver | OPEN |
| bind_receiver_resp | OPEN |
| bind_transceiver | OPEN |
| bind_transceiver_resp | OPEN |
| unbind | BOUND_TX, BOUND_RX, BOUND_TRX |
| unbind_resp | BOUND_TX, BOUND_RX, BOUND_TRX |
| submit_sm | BOUND_TX, BOUND_TRX |
| submit_sm_resp | BOUND_TX, BOUND_TRX |
| deliver_sm | BOUND_RX, BOUND_TRX |
| deliver_sm_resp | BOUND_RX, BOUND_TRX |
| enquire_link | BOUND_TX, BOUND_RX, BOUND_TRX |
| enquire_link_resp | BOUND_TX, BOUND_RX, BOUND_TRX |
| generic_nack | BOUND_TX, BOUND_RX, BOUND_TRX |
submit_sm and resp transactions will include a message identifier and a status which identifies whether the message is valid or invalid. If invalid, an error status will be returned. Please note that the message identifier will be hex encoded on
SMPP 3.3 connections but will be a standard ASCII encoded integer on
SMPP 3.4 connections.
To learn more please consult our article on
SMPP session states.
For more information on
SMPP functions please consult the
SMPP specifications in the
What Are SMPP And UCP-EMI? article or the
SMPP Command Codes article.
