Supported PDUs
The SMSC supports the following SMPP Protocol PDUs:
ESME to SMSC |
SMSC to ESME |
|||
---|---|---|---|---|
PDU name |
command_id |
PDU name |
command_id |
Notes |
bind_transmitter |
0x00000002 |
bind_transmitter_resp |
0x80000002 |
|
bind_receiver |
0x00000001 |
bind_receiver_resp |
0x80000001 |
|
bind_transceiver |
0x00000009 |
bind_transceiver_resp |
0x80000009 |
1 |
submit_sm |
0x00000004 |
submit_sm_resp |
0x80000004 |
|
deliver_sm_resp |
0x80000005 |
deliver_sm |
0x00000005 |
|
data_sm |
0x00000103 |
data_sm_resp |
0x80000103 |
2 |
enquire_link |
0x00000015 |
enquire_link_resp |
0x80000015 |
3 |
unbind |
0x00000006 |
unbind_resp |
0x80000006 |
4 |
unbind_resp |
0x80000006 |
unbind |
0x00000006 |
4 |
generic_nack |
0x80000000 |
generic_nack |
0x80000000 |
Notes:
- Only supported in SMPP version 3.4
- The data_sm PDU can be used to send messages from the ESME and from the SMSC, however, the Clickatell SMSC will always use the deliver_sm PDU to send delivery receipts and MO messages to the ESME.
- The enquire_link PDU can be used to test the connection from the ESME and from the SMSC, however, the Clickatell SMSC will never send an enquire_link PDU to the ESME.
- The ESME or the SMSC can disconnect the connection at any time by sending an unbind PDU.
Submit a Comment
Other Resources
Ask the Community
Visit Stack Overflow to join our community of developers and find the answer you need
Contact Support
Contact our support team and one of our agents will be in touch with you to answer any questions you have