SMPP Gateway
Enterprise-grade SMPP v3.4 connectivity for high-volume SMS sending. Direct carrier routes with guaranteed throughput and 99.9% uptime.
What is SMPP?
SMPP (Short Message Peer-to-Peer) is the industry-standard protocol used by telecom operators and SMS aggregators worldwide for high-volume message exchange. Unlike HTTP-based APIs, SMPP uses persistent TCP connections — eliminating the overhead of establishing a new connection for each message.
SMPP is the backbone of the SMS industry. It's used by carriers, aggregators, and enterprises that need maximum throughput, minimal latency, and native delivery receipt support.
Technical Specifications
| Protocol | SMPP v3.4 (transceiver, transmitter, receiver) |
| Plain port | 2775 |
| TLS port | 2776 (TLS 1.2+ required) |
| Throughput | Up to 1,000 msg/s per bind |
| Max binds | 10 concurrent transceiver binds |
| Encoding | GSM 03.38, UCS-2, Latin-1, ASCII |
| DLR support | Full delivery receipt support (data_sm and deliver_sm) |
| Window size | Configurable, default 10 |
| Enquire link | 30-second interval recommended |
| TLS | TLS 1.2+ supported and recommended |
| IP whitelisting | Required for all connections |
| Uptime SLA | 99.9% guaranteed |
Key Features
Persistent connections
No HTTP overhead. Maintain always-on connections for instant message submission.
TLS encryption
Secure your SMPP traffic with TLS 1.2+ encryption. Required for compliance in regulated industries.
High throughput
1,000 msg/s per bind × 10 binds = 10,000 messages per second. Perfect for time-critical campaigns.
Native DLR
Receive delivery receipts natively via deliver_sm PDUs — no webhook configuration needed.
Multi-bind support
Use multiple transceiver binds for parallel sending and receiving across different use cases.
Smart routing
Automatic carrier selection based on destination, cost, and quality metrics.
SMPP Setup Guide
1. Request SMPP access
Contact our sales team or upgrade to an enterprise plan. We'll provision your system_id and password.
2. Whitelist your IPs
Provide the static IP addresses of your SMPP client. We'll add them to the firewall whitelist.
3. Configure your client
Connect to smpp.bulksmsrates.com on port 2775 (plain) or 2776 (TLS). Bind as transceiver for send + receive.
4. Send a test message
Submit a submit_sm PDU with your test number. Verify you receive a deliver_sm DLR confirming delivery.
5. Go live
Once testing is complete, increase your window size and bind count to match your throughput requirements.
# Example connection settings Host: smpp.bulksmsrates.com Port: 2776 (TLS) System ID: your_system_id Password: your_password Bind type: Transceiver TON: 1 (International) NPI: 1 (ISDN/E.164) Enquire: 30 seconds
SMPP vs REST API
| Feature | SMPP | REST API |
|---|---|---|
| Protocol | TCP (persistent) | HTTP/HTTPS |
| Connection | Always-on | Per-request |
| Max throughput | 10,000 msg/s | 100 req/s (10k msg/batch) |
| Latency | ~5ms | ~50ms |
| TLS | ✓ Port 2776 | ✓ HTTPS |
| Delivery reports | Native (deliver_sm) | Webhook (HTTP POST) |
| Setup complexity | Medium (client library) | Low (HTTP request) |
| Best for | High volume, low latency | Integration, ad-hoc sending |
| Language support | Java, C, Python, Node | Any (HTTP) |
| Batch sending | Sequential PDUs | 10k per request |
| Billing | Per message | Per message |
| Authentication | system_id + password | Bearer token |