SMPP SMS API
Carrier Grade SMPP SMS via API
Introduction
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 ▲
| Parameter | Description |
|---|---|
| IP/DOMAIN | smpp.smsglobal.com |
| PORT | 1775 |
| SYSTEM ID | [ Username ] |
| PASSWORD | [ Password ] |
| TLS Connection: Use port 1776 instead. |
Options Scroll to Top ▲
| Parameter |
|---|
| 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 Code | Error Type. | Description |
|---|---|---|
| 1 | Error | ESME_RINVMSGLEN Message Length is invalid |
| 2 | Error | ESME_RINVCMDLEN Command Length is invalid |
| 3 | Error | ESME_RINVCMDID Invalid Command ID |
| 4 | Error | ESME_RINVBNDSTS Incorrect BIND |
| 5 | Error | ESME_RALYBND ESME Already in Bound State |
| 10 | Error | ESME_RINVSRCADR Invalid Source Address |
| 11 | Error | ESME_RINVDSTADR Invalid Dest Addr |
| 12 | Error | ESME_RINVMSGID Message ID is invalid |
| 13 | Error | ESME_RBINDFAIL Bind Failed |
| 14 | Error | ESME_RINVPASWD Invalid Password |
| 69 | Error | ESME_RSUBMITFAIL Submit SM failed |
| 88 | Error | ESME_RTHROTTLED Exceeded allowed message limits |
| 102 | Error | Destination not covered or Unknown prefix |
| 400 | Timeout | Send message timed-out. |
| 401 | System Error | System temporarily disabled |
| 402 | No Response | No response from SMSGlobal SMSC |