SMPP Documentation

Text messaging at advanced speeds!

This page provides instructions and examples how to use SMPP communication interface for sending sms. The Short Message Peer-to-Peer SMPP is an open, industry standard protocol used by the telecommunication industry for exchanging SMS messages between Short Message Service Centres and a SMS application systems. The protocol is a level-7 TCP/IP protocol, which allows fast delivery of SMS messages. The connection between the application and the SMPP server is SMPP version 3.4. Version 3.3 is not supported.

SMPP Paramenters




 Required. Provided for each client.


Required. Provided for each client. Maximum password length is 8 characters.

 IP address

 Required. Connection point:


 Required. 8888 (primary and secondary) / 8887 (ssl)

 timeout (keep alive or msg)

 Required. 30 sec


 Optional. <r:route_code>

Important: You are allowed to bind as transmitter, receiver or transceiver. In order to receive delivery reports, you must bind as transceiver or receiver.

You’ll receive delivery reports only if your route provides delivery reporting. Delivery reports will be sent equally over all of your currently available sessions capable of receiving them (transceiver or receiver). By default, you are allowed to bind with 4 sessions.

PDUs supported

  • bind_transmitter
  • bind_receiver
  • bind_transceiver
  • unbind
  • submit_sm
  • deliver_sm
  • enquire_link

Delivery Report Format

  id:{message_id} sub:{message_sub} dlvrd:{message_dlvrd} submit date:{message_submit_date} done date:{message_done_date} stat:{message_stat} err:{message_err}

Delivery Statuses



If you set DCS 0 or DCS 1 when sending messages, we will treat that as default GSM7 encoding (SMSC Default Alphabet or IA5).

For Latin1 (ISO-8859-1) please use DCS 3 and DCS 8 for sending messages as Unicode (ISO/IEC-10646).

If needed, the content of messages can be processed in Latin1 (ISO-8859-1) even with DCS  0,  and in that case a simple adjustment is needed on account level.

Command Status and GSM Error Codes

Each request sent to our system is to receive an acknowledgement in submit_sm resp PDU and it is fully compliant with SMPP v 3.4 standard. A few proprietary platform command statuses with platform specific delivery report error code are described in the SMPP Command Status & GSM Error Codes section.

Command status is received as an response for Submit_SM, on special events, illustrated in the table below.




 Invalid credentials, only returned in bind_resp

 0x00000022 / 34

Network not covered.

 0x000000FF / 255

 Account has insufficient balance


 Invalid source address


 Invalid destination address


 Duplicate messageID


 System error or channel disabled


 Invalid optional parameter length

Scheduled Delivery

Scheduled delivery is supported over SMPP protocol using the relative time format.

“070605040302100R” – this would mean that the message will be delivered in 7 years, 6 months, 5 days, 4 hours, 3 minutes, 2 seconds and 1 tenth of a second from now.