This section covers key concepts for integrating with the Twilio SMPP API, essential for secure and efficient messaging. Each concept will be explained in detail below.
The SMPP API doesn't support connection via Internet Protocol Security (IPSec), Virtual Private Network (VPN), and it doesn't offer static IP's to connect to.
Connecting to the Twilio SMPP API integration requires Transport Layer Security (TLS) version 1.2 or higher, using the Fully Qualified Domain Name (FQDN) of Twilio's integration's host and designated port.
Twilio will only accept connections and traffic from a specific and predetermined set of IP addresses that you provide when you set up your account. If you want to change your IP addresses for sending traffic, inform your Twilio Account Manager so they can update your profile's IP allowlist.
With the Twilio SMPP API, your system should send enquire_link Protocol Data Unit (PDUs) every 60 seconds if your application isn't actively submitting messages. Twilio's SMSC will also be sending enquire_link PDU. Note that unresponsive connections will be dropped.
SMPP credentials allow you to control who can use the platform and help monitor messaging activities.
The Twilio SMPP credentials consist of:
system_id is an alphanumeric string that includes letters and numbers, and it can be up to 16 characters long, as specified by the SMPP v3.4 documentation. It acts as your "username" for authentication.You can request that Twilio generate additional SMPP Credentials for your account SID to support an integration that needs more than one system ID. Upon request, Twilio can also replace a credential by removing an old credential(s), and generating new credential(s) as a replacement.
A bind is a command used to establish a persistent connection between an SMPP client and an SMPP server. You must maintain an active bind between your SMPP client and the Twilio SMPP server to send outbound messages or receive inbound messages or delivery receipts.
There is an account-level limit to the total number of simultaneous SMPP sessions allowed. This limit will be included in a secure email when you receive your SMPP credentials. It is customized to your account, based on your use cases and agreements with Twilio.
A bind type specifies the type of connection you want to establish, whether for sending messages, receiving messages, or both.
The Twilio SMPP integration allows you to connect using the following bind types:
bind_transmitter: send outbound messages from your ESME client to Twilio.bind_receiver: receive inbound messages and delivery receipts from Twilio to your ESME client.bind_transceiver: send outbound messages and receive inbound messages and delivery receipts.Throughput refers to the maximum number of message submissions you can send per second. This value is customized to your account, based on your use case and agreement with Twilio.
The capacity configured by Twilio during the SMPP API onboarding only corresponds to its ingress capacity and doesn't guarantee the ability of the network providers or carriers to handle message volume. If you need more capacity to handle your message volume, please contact your account manager or solution engineer.
Set up your SMPP API integration by following the initial setup and connection guide.