SMPP Connectivity
SMPP Connectivity for SMSGatewayCenter APIs
Introduction General
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 Center (SMSC) and 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 SMSGatewayCenter Enterprise Messaging Gateway SMPP Server is SMPP version 3.4.
Purpose
This SMPP Interface document shall help understand the settings and and needs to establish SMS connection between SMSGatewayCenter Enterprise Messaging Gateway and customer.
We assume a level of close acquaintance with SMPP Protocol functionality and required to follow the SMPP 3.4 specification.
If you require further assistance, please do not hesitate to contact your Sales/Project Manager.
Objective
This document is meant to outline the requirements from the service provider/mobile operator technical connectivity of SMS to the SMSGatewayCenter Enterprise Messaging Gateway system. This connectivity is used receiving SMS messages from the client to the SMSGatewayCenter Enterprise Messaging Gateway system.
The connection settings explained here are based on connectivity using the SMPP protocol.
Please note that connectivity using other protocols is possible as well - for further assistance please contact your sales/project manager.
Glossary
| Name | Value |
|---|---|
| SMPP | Short Message Peer to Peer Protocol |
| SMSC | Short Message Service Center |
| ESME | External Short Message Entity |
| PDU | Protocol Data Unit |
Connecting to SGC EMG SMPP Service
SMPP Parameters
| Name | Description |
|---|---|
| system_id | Required. Configured on our platform. |
| password | Required. Configured on our platform. |
| IP address | Will be given by your Sales/Project ManagerWill be given by your Sales/Project Manager |
| Port | Will be given by your Sales/Project Manager |
| Timeout (Keep Alive) | 30 Seconds (Recommended) |
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 5 sessions. There are no other throughput (TPS) limitations besides internet speed.
PDUs Supported
- bind_transmitter
- bind_receiver
- bind_transceiver
- unbind
- submit_sm
- deliver_sm
- enquire_link
Delivery Report Format
id:7563423917286768871 sub:001 dlvrd:001 submit date:1812272114 done date:1812272114 stat:DELIVRD err:000 text:Hello World, this is a test message.
Delivery Statuses (message_stat)
- Delivrd
- Expired
- Undeliv
- Acceptd
- Unknown
- Rejectd
Data Coding Scheme
| Name | Value |
|---|---|
| DCS 01 DCS 02 |
Default GSM7 Encoding (SMSC Default Alphabet or IA5) |
| DCS 08 | Unicode (UCS2 (ISO/IEC-10646)) |
SMPP Command Status and GSM Error Codes
| Name | Description |
|---|---|
| Invalid System ID | 0x0000000F |
| Invalid Password | 0x0000000E |
| Invalid Source Address | 0x0000000A |
| Session Exceeded | 0x00000005 |
| ESME has exceeded allowed message limits | 0x00000058 |
| Error in the optional part of the PDU Body | 0x000000C0 |
GSM Error Codes
The list of GSM Error codes are same as Delivery Error Codes which has mentioned on the API Documentation site here.
Send a Message:
Messages should be sent with submit_sm, using either the short_message or message_payload fields.
The above flow chart illustrates a typical SMPP request/response sequence between an SMSC and an ESME bound as a Transmitter.
Unlock Real-Time Messaging – Integrate Today!
Try Our API in a Sandbox Environment Before Going Live!
Join Thousands of Developers – Try Our API Now!
Get in touchSign upTestimonials
Why do Great Businesses Trust SMS Gateway Center?