Introduction
This document provides a reference for all features available to you via the SMPP interface for sending SMS.
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).
Movider implement the most standard version v3.4 which add transceiver support.
Features
The SMPP Server enables the transmission and reception of SMS messages as well as delivery receipts (DLR). It also facilitates the exchange of extended SMS (exceeding 160 characters) and supports unicode/binary content for enhanced communication.
Server Details
| Element | Value | Description |
|---|---|---|
| IP / Domain | 0.0.0.0 | The SMPP Server listener will only bind to this specified address. |
| PORT | 2775 | The binding TCP port. |
| SessionInitTimer | 30s | The timeout for a bind request. |
| EnquireLinkTimerSecs | 30s | The timeout for an enquire_link request. |
| InactivityTimerSecs | 300s | The inactivity timeout. |
Binding to the server
When employing a suitable SMPP Client application, it is essential to take into account the following parameters:
| Element | Value | Description |
|---|---|---|
| system_id | movider | Username uses for authentication. If you would like to use it, please feel free to contact https://movider.co/en/contact/. |
| password | 1111 | Password used for authentication. If you would like to use it, please feel free to contact https://movider.co/en/contact/. |
For Send SMS Payload, Movider support SMPP v.3.4 PDU, you can check the detail at https://smpp.org/#smppexample
Delivery Receipts
Optional delivery receipts can be transmitted through an RX / TRX (Receiver and Transceiver) bind back to the user. To activate delivery receipts.
We used standard delivery receipt that provided in https://smpp.org/smpp-delivery-receipt.html.
Supported SMPP PDUs
SMPP Server is supporting the following PDUs:
- bind_transmitter (TX)
- bind_transceiver (TRX)
- bind_receiver (RX)
- unbind
- submit_sm / submit_sm_resp
- deliver_sm
- enquire_link
Common Errors
| SMPP Status | Description |
|---|---|
| ESME_ROK | No error |
| ESME_RINVMSGLEN | Message Length is invalid |
| ESME_RINVCMDLEN | Command Length is invalid |
| ESME_RINVCMDID | Invalid Command ID |
| ESME_RINVBNDSTS | Invalid BIND Status for given command |
| ESME_RALYBND | ESME Already in Bound State |
| ESME_RINVPRTFLG | Invalid Priority Flag |
| ESME_RINVREGDLVFLG | Invalid Registered Delivery Flag |
| ESME_RSYSERR | System Error |
| ESME_RINVBCASTAREAFMT | Broadcast Area Format is invalid |
| ESME_RINVSRCADR | Invalid Source Address |
| ESME_RINVDSTADR | Invalid Dest Addr |
| ESME_RINVMSGID | Message ID is invalid |
| ESME_RBINDFAIL | Bind Failed |
| ESME_RINVPASWD | Invalid Password |
| ESME_RINVSYSID | Invalid System ID |
| ESME_RINVBCAST_REP | Number of Repeated Broadcasts is invalid |
| ESME_RCANCELFAIL | Cancel SM Failed |
| ESME_RINVBCASTCHANIND | Broadcast Channel Indicator is invalid |
| ESME_RREPLACEFAIL | Replace SM Failed |
| ESME_RINVBCASTCHANIND | Broadcast Channel Indicator is invalid |
| ESME_RINVSRCADDRSUBUNIT | Source Address Sub unit is Invalid |
| ESME_RINVDSTADDRSUBUNIT | Destination Address Sub unit is Invalid |
| ESME_RINVNUMDESTS | Invalid number of destinations |
| ESME_RINVSRCTON | Invalid Source address TON |
| ESME_RINVSRCNPI | Invalid Source address NPI |
| ESME_RINVDSTTON | Invalid Destination address TON |
| ESME_RINVDSTNPI | Invalid Destination address NPI |
| ESME_RUNKNOWNERR | Unknown Error |
| ESME_RDELIVERYFAILURE | Delivery Failure (used for data_sm_resp) |