This documentation should be use in conjunction with our complete protocol PDF.
The first step to using the SMPP API is to connect to our services. To do so, you’ll need to provide us with an External Short Message Entity (ESME) implementation and establish binds to the Vibes Short Message Service Center (SMSC) end points. For maximum resiliency, you should plan on establishing a minimum of four bind pairs.
Specific host IP addresses and Ports will be assigned as part of the onboarding process, as well as
System_ID and password credentials.
The Vibes Connect platform supports Transmitter, Receiver and Transceiver binds. As part of the onboarding process, either a VPN tunnel should be established between your endpoint and ours, or you should utilize SMPP/SSL.
Additionally, you’ll need to provide us with IP addresses to be added to our list of trusted connections.
Currently, the Vibes Connect platform supports the following Short Message Peer-to-Peer (SMPP) Operations:
The following are the default Timers values on the SMSC. We suggest that the ESMEs use the same timer values.
|Session Init||50 seconds|
|Enquire Link||30 seconds|
|Inactivity Period||150 seconds|
|Response Timer||10 seconds|
Each SMPP connection will have a maximum rate limit in messages per second. These limits can either be per bind or per SMSC, based on your preference. The number of binds and throughput limits will be determined as part of the initial setup process.
Your ESME applications should ensure that the application can throttle, that the limit is not exceeded for optimal performance, and to avoid
ESMEs should limit the number of unacknowledged messages to the window size allowed for a bind. The default is 20.
We recommend establishing an Enquire-Link at a 30 second interval to keep the connection alive.