Reference section - SMPP
alert_notification
SMPP alert_notification
4.1.3 Alert Notification Operation
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 | |
SMSC Simulator
Looking to test your SMS application or SMS-enabled application before connecting to a live SMS gateway or SMSC? Our SMSC Simulator service allows you to test using the SMPP protocol v3.3, v3.4 and v5. Read more about SMSC Simulator >