Reference section - SMPP
alert_notification
SMPP alert_notification
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.
4.1.3 Alert Notification Operation
SMPP v5 Alert Notification reference
The alert_notification PDU is sent by the MC to the ESME across a Receiver or Transceiver session. It is sent when the MC has detected that a particular mobile subscriber has become available and a delivery pending flag had been previously set for that subscriber by means of the set_dpf TLV (ref. 4.8.4.52).
A typical use of this operation is to trigger a data content "Push" to the subscriber from a WAP Proxy Server.
Note: There is no associated alert_notification_resp PDU.
4.1.3.1 alert_notification Syntax
Following is the format of the SMPP alert_notification PDU.
| Field Name | Size Octets | Type | Description | Ref. |
| command_length | 4 | Integer | Defines the overall length of the PDU. | 4.7.4 |
| command_id | 4 | Integer | 0x00000102 | 4.7.5 |
| command_status | 4 | Integer | 0x00000000 | 4.7.6 |
| sequence_number | 4 | Integer | Set to a unique sequence number. | 4.7.24 |
| source_addr_ton | 1 | Integer | Type of Number for alert SME. | 4.7.1 |
| source_addr_npi | 1 | Integer | Numbering Plan Indicator for alert SME. | 4.7.2 |
| source_addr | Var. max 65 | C-Octet String | Address of alert SME. | 4.7.29 |
| esme_addr_ton | 1 | Integer | Type of Number for ESME address which requested the alert. | 4.7.1 |
| esme_addr_npi | 1 | Integer | Numbering Plan Indicator for ESME address which requested the alert. | 4.7.2 |
| esme_addr | Var. max 65 | C-Octet String | Address for ESME which requested the alert. | 4.7.11 |
| Optional TLVs: | ||||
| TLV Name | Type | Description | ||
| ms_availability_status | TLV | The status of the mobile station | 4.8.4.39 | |
SMPP Tools and Services
Services from Melrose Labs (e.g. Tyr SMS Gateway and SMPP SMS Gateway ) support SMPP v5 and the earlier versions, v3.3 and v3.4.
SMSC Simulator
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 >
SMPP Clients
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
Send SMS programmatically with SMPP using Python, Java, Go, Perl, C++, C#, Node.js, Ruby and PHP.
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 >
SMPP Analyser
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 Hub
Message routing between applications (uses SMPP protocol). For use in IoT, chat applications, asyncronous notification in web applications, and other applications.
Message Hub documentation >