Last Updated: Wednesday, September 19, 2018
Connecting to the Service
The customer will provide an External Short Message Entity (ESME) implementation and will establish binds to the Vibes Short Message Service Center (SMSC) end points. Vibes provides two active data centers for messaging capabilities, with multiple SMSCs in each data center to provide the maximum in redundancy and availability. For maximum resiliency, the customer should plan on establishing a minimum of four bind pairs (MO + MT) to take maximum advantage of the Platform.
Specific host IP addresses and Ports will be assigned as part of the onboarding process, as well as System_ID and password credentials.
Bind Options & Supported Operations
The Vibes Connect Platform supports Transmitter, Receiver and Transceiver binds. As part of the onboarding process, either a VPN tunnel should be established between the client and Vibes, or the client should utilize SMPP/SSL. Additionally, the client IP addresses need to be specified for whitelisting for the connections.
Currently, the Vibes Connect Platform supports the following Short Message Peer-to-Peer (SMPP) Operations:
Default Timer Settings
The following are the default Timers values on the SMSC. We suggest that the ESMEs use the same timer values.
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 the client preference. The number of binds and throughput limits will be determined as part of the initial setup process. Client ESME applications should ensure that the application can throttle, that the limit is not exceeded for optimal performance, and to avoid throttle_limit_exceeded errors.
ESMEs should limit the number of unacknowledged messages to the Window Size allowed for a Bind. The default is 20.
Heartbeat Keep Alives
Vibes recommends the client should establish an Enquire-Link at a 30 second interval to keep the connection alive.