SMPP (Short Message Peer-to-Peer) is an open, industry standard protocol designed to provide a flexible data communications interface for the transfer of short message data between External Short Message Entities (ESME), Routing Entities (RE) and Message Centres (MC). The SMPP protocol is a means by which applications can send SMS messages to mobile devices and receive SMS from mobile devices.
For the full SMPP v5 specification and further information on the SMPP protocol, see SMPP - Short Message Peer-to-Peer protocol at smpp.org .
Session Management Operations
These operations are used to establish and maintain an SMPP session.
The purpose of the SMPP bind operation is to register an instance of an ESME with the MC system and request a SMPP session over this network connection for the submission or delivery of messages. Thus, the Bind operation may be viewed as a form of MC login request to authenticate the ESME entity wishing to establish a connection.
- bind_transmitter / bind_transmitter_resp
- bind_receiver / bind_receiver_resp
- bind_transceiver / bind_transceiver_resp
- unbind / unbind_resp
Message Submission Operations
Message submission operations provide an ESME with the ability to submit messages for onward delivery to mobile stations.
Message Delivery Operations
Message delivery operations provide the means of delivering short messages from a MC to an ESME. These messages typically originate from mobile stations.
Message Broadcast Operations
Message broadcast operations provide Cell Broadcast services to ESMEs.
- broadcast_sm / broadcast_sm_resp
- Broadcast TLVs
Anciliary Submission Operations
Ancillary submission operations provide additional management of messages submitted by ESMEs. This includes cancellation, querying and replacement of messages.
- cancel_sm / cancel_sm_resp
- query_sm / query_sm_resp
- replace_sm / replace_sm_resp
- Message Replacement TLVs
Anciliary Broadcast Operations
Ancillary broadcast operations provide additional management of messages submitted by ESMEs. This includes cancellation and querying of messages.
- query_broadcast_sm / query_broadcast_sm_resp
- Query Broadcast TLVs
- cancel_broadcast_sm / cancel_broadcast_sm_resp
- Cancel Broadcast TLVs
SMPP PICs statement (based on SMPP PICS at smpp.org ) for Melrose Labs Tyr SMS Gateway and SMPP SMS Gateway.
SMPP Tools and Services
Looking to test your SMS application or SMS-enabled application before connecting to a live SMS gateway or SMSC? SMSC Simulator enables you to test using SMPP v3.3, v3.4 and v5.
Read more about SMSC Simulator >
Send and receive SMS using an SMPP account and browser-based SMPP client.
- SMPP Client * - send/receive SMS and perform other SMPP operations
- SMPP Sender * - basic send SMS client
- SMPP Multi-Sender * - send SMS to multiple numbers from a CSV or spreadsheet
- SMPP Chat * - one or more two-way conversations using SMS and SMPP
- Message Broadcast - text messaging portal for use with any SMPP-capable messaging provider
* SMPP session between web browser and provider.
SMS Code Bench
SMS messaging code sample and development playground. Collection of editable and runnable code samples in a variety of languages for different SMS interactions.
SMS Code Bench >
Send SMS programmatically with SMPP
SMPP Load Test
Perform an SMS load test using SMPP from your web browser and view the results in realtime. SMPP Load Test tool submits SMS messages using SMPP at the specified rate. Messages are sent to one or more mobile numbers in a range from a single source address or range of source addresses.
Use the online SMPP Load Test tool >
The SMPP Analyser acts as an SMPP proxy, with the client application binding to the service and the service onward binding to the SMSC or SMS Gateway. Packet captures can be viewed in your browser or exported into Wireshark.
Use the online SMPP Analyser >
Message routing between applications (uses SMPP protocol). For use in IoT, chat applications, asyncronous notification in web applications, and other applications.
Message Hub documentation >