The SMS Aggregation service is made up of several different components. Each of these components is configured for High Availability (HA) using either active/active pairs or active/hot-standby pairs. All client-facing components are made available in an active/active configuration. Any components not configured as active/active have a designated failover policy that is applied in case a component fails. In addition, each component is provisioned with enough capacity to handle the complete system load at any time.
To avoid any interruptions to service during maintenance or outages, follow the recommendations below:
The HTTP APIs are available for use at any site where the SMS Aggregation service is located. Details of the URLs are discussed in HTTP API URLs.
The architecture of the SMS Aggregation service is the same for each site and is shown in the following figure.
The flow of a client's request is as follows:
- The client's request is received at the datacenter firewall.
- The request is forwarded to load-balancing cluster.
- The load balancer selects the HTTP node using round-robin balancing.
The SMSC component provides HA by supporting multiple client connections to each node within the SMSC cluster. The complete list of available URIs are listed here. To take full advantage of the HA SMSC service, a client should comply with the following recommendations:
- Create one SMPP connection per SMSC node (as shown in the figure below).
- If the SMSC node becomes unavailable, attempt to rebind in 30 second intervals.
- Clients should expect MOs and DRs to be sent to ANY active SMPP connection.