Carrier Grade SMPP SMS via API


This document provides a reference for all features available to you via the SMPP interface for sending SMS. SMPP is considered the industry standard for sending SMS to Network providers and is our native protocol.

The Short Message Peer-to-Peer (SMPP) is a protocol used by the telecommunications industry for exchanging SMS messages between Short Message Service Centers (SMSC) and/or External Short Messaging Entities (ESME).

The protocol is a level-7 TCP/IP protocol, which allows fast delivery of SMS messages.

The most commonly used versions of SMPP are v3.3, the most widely supported standard, and v3.4, which adds transceiver support (single connections that can send and receive messages). Data exchange may be synchronous, where each peer must wait for a response for each PDU being sent, and asynchronous, where multiple requests can be issued in one go and acknowledged in a skew order by the other peer.

SMSGlobal supports the industry standard SMPP V3.4 protocol.

SMPP Features Scroll to Top ▲

  • SMPP is a direct connection to carriers and provides instant delivery
  • High throughput (up to 200 msgs/second)
  • Usage of Short Code
  • SMPP offers status delivery reports
  • 24/7 support via our support system

Server Details Scroll to Top ▲

SYSTEM ID[ Username ]
PASSWORD[ Password ]
TLS Connection: Use port 1776 instead.

Options Scroll to Top ▲

Transmitter bind (TX)
Receiver bind (RX)
Transceiver bind (TRX)
Submit command
TON: 1
NPI: 1
Delivery receipts note: Please contact us to enable this for you.

Are your messages over 160 characters?

Please note you will need to split your SMS into 153 characters per part and include the headers.

Do you wish to use Unicode in your SMS?

Please ensure you set your DCS value to 8 to ensure Unicode is encrypted properly. If you wish to send over 70 characters using Unicode you will need to split your SMS into parts of 67 characters and include the headers.

Delivery Receipts Scroll to Top ▲

Delivery receipts are optional. They can be pushed through an RX / TRX bind back to the user. To enable delivery receipts, login to MXT and update your delivery receipt settings to enable a push over SMPP in Tools.

Common Errors Scroll to Top ▲

Error CodeError Type.Description
1ErrorESME_RINVMSGLEN Message Length is invalid
2ErrorESME_RINVCMDLEN Command Length is invalid
3ErrorESME_RINVCMDID Invalid Command ID
5ErrorESME_RALYBND ESME Already in Bound State
10ErrorESME_RINVSRCADR Invalid Source Address
11ErrorESME_RINVDSTADR Invalid Dest Addr
12ErrorESME_RINVMSGID Message ID is invalid
13ErrorESME_RBINDFAIL Bind Failed
14ErrorESME_RINVPASWD Invalid Password
69ErrorESME_RSUBMITFAIL Submit SM failed
88ErrorESME_RTHROTTLED Exceeded allowed message limits
102ErrorDestination not covered or Unknown prefix
400TimeoutSend message timed-out.
401System ErrorSystem temporarily disabled
402No ResponseNo response from SMSGlobal SMSC
Loading Form