The 2sms SMPP SMSC allows customers to send SMS messages to mobile destination using the SMPP v3.4 protocol. The SMPP SMSC accepts valid SMPP PDUs from authenticated users, allowing customers to send messages to domestic and international mobile phones, and collect delivery receipts.
Getting Started
Contact 2sms to generate a system ID and password required for the SMPP SMSC connection.
Binding to 2sms SMPP
You can bind to the 2sms SMPP SMSC via:
- As a Transmitter/Receiver (Transceiver) pair
- As a single Transceiver
Connection credentials
You will need a unique system ID and password for each bind connection. Please contact support for assistance.
Typical SMPP Setup Specifications
| SMPP HOST | smpp.2sms.us |
| SMSC PORT | 2775 |
| SMSC_USER | System ID generated by 2sms |
| SMSC_PASSWD | SMPP Password generated by 2sms |
| SMSC_ADDR | Shortcode number issued by 2sms |
| SMSC_ADDR_SOURCE | International number issues by 2sms for international destinations |
| CONN_TYPE | tx or rx |
| SOURCE_ADDR_TON | 3 (for US and Canada mobile numbers) |
| SOURCE_ADDR_NPI | 0 |
| DEST_ADDR_TON | 5 (for international mobile numbers) |
| DEST_ADDR_NPI | 0 |
| SOURCE TYPE OF NUMBER (TON) | 3 |
| SOURCE NETWORK PLAN INDICATOR (NPI) | 1 |
| REGISTERED_DELIVERY | 1 |
| SUBMIT_TIMEOUT | 30 |
| MAX_PENDING | 10 |
| WAIT_FOR_RECEIVER | 1 |
| SMSC_PINGTIME | 60 |
| ENQUIRELINK | 60 |
| ENQUIRE WAIT | 30 |
Delivery Receipts
Delivery receipt fields conform to the example in the SMPP specification. The values that may be returned in the stat field are described below:
| Status | Description |
| DELIVRD | The message has been delivered to the subscriber’s handset |
| ACKED | The message has been submitted to a deliverer |
| BUFFRED | The message was not delivered, but will be retried |
| FAILED | The message was not delivered and will not be retried |
| UNKNOWN | The message status is unknown, but no further retries will be attempted |