Our platform supports direct SMPP connectivity for high-throughput, low-latency SMS delivery. This document describes the requirements and steps needed to establish a successful SMPP connection to our SMSC.
Overview
Protocol: SMPP v3.4
Use cases: A2P SMS termination, transactional and bulk messaging
Connection type: Persistent TCP bind
Authentication: System ID & Password
IP security: Source IP whitelisting required
Host and port: contact support or your account manager
Before You Connect
Create an SMPP API key in the client dashboard.
Your SMPP clients source IP address must be whitelisted prior to connection.
Supported SMPP Version
Your SMPP client must support SMPP version 3.4 or higher.
Earlier SMPP versions are not supported.
How to Connect
Configure your SMPP client using the bind parameters provided.
Establish a TCP connection to the SMSC host and port. (contact support for host and port values)
Connect in transceiver mode (bind_transceiver) for two way traffic.
Make sure your connection throughput value corresponds to the value in your SMPP API key.
Connection Limits
You can have up to 2 binds, per account.
If you require additional binds or higher throughput, please contact your account manager to discuss scaling options.
Message Submission
Use submit_sm PDUs for outbound messages.
Message encoding must comply with GSM 03.38 or UCS-2 where applicable.
Delivery Receipts (DLRs)
Delivery receipts are supported via deliver_sm PDU.
Ensure your client properly handles and acknowledges DLR PDUs.
DLR behavior and levels (success, failure, intermediate) are configurable.
Connection Management Best Practices
Maintain a persistent connection.
Implement automatic reconnect logic.
Respond promptly to enquire_link PDUs.
Monitor bind status and throttling responses.
Error Handling & Throttling
The SMSC may throttle traffic based on throughput or policy.
Proper handling of SMPP error codes is required.
Repeated protocol violations may result in temporary suspension.