SMPP Load Balancer

Scenario #1 - Multiplex

Customer-facing endpoint that multiplexes traffic onto fixed set of connections to your platforms

Customer SMPP credentials and connection details for your platforms are configured in the SMPP Load Balancer service. Your customers connect to the service instead of your platforms. The service connects to your platforms, and messages submitted by your customers are load-balanced across your platforms. Traffic from multiple customers is multiplexed onto the connections with your platforms. Delivery receipts are routed back from your platforms via the service to the customer SMPP connection that submitted the corresponding outbound message.

Scenario #2 - Proxy

Customer-facing endpoint that proxies traffic onto your platforms using customer credentials

The service proxies SMPP submit_sm requests to your platforms. SMPP binds are made from the service to your platforms using the customer's SMPP credentials, and only SMS traffic sent by that customer is routed to your platforms using their credentials. Delivery receipts and MO SMS are routed back to the customer as though they had directly connected to your platforms. No customer accounts are configured in the service. Only the host and port for each of your platforms are configured in the SMPP Load Balancer service.

Scenario #3

Customer-facing endpoint that routes messages to supplier platforms

Customer SMPP credentials and connection details for your supplier platforms are configured in the SMPP Load Balancer service. Your customers connect to the service. The service connects to your suppliers, and messages submitted by your customers are load-balanced across those supplier connections. Traffic from multiple customers is multiplexed onto the connections with your suppliers. Delivery receipts are routed back from your suppliers via the service to the customer SMPP connection that submitted the corresponding outbound message.

This is ideal for when you don't need to operate your own platform, and are using the SMPP Load Balancer as a simple SMS gateway.

Scenario #4

Upstream endpoint for your platform or application

Use the service upstream of your platform to handle message submission to your suppliers. Your platform could be a messaging application, or an application with messaging capability, but you need more control and accounting of messaging. The SMPP Load Balancer service enables you to achieve this.

Connect an application to multiple upstream platform by using the SMPP Load Balancer service to manage the upstream connections. Application needs only to make a single connection the service to be connected to multiple upstream platforms.

Scenario #5

SMPP concentrator

Aggregate customer SMPP connections to a single SMPP supplier connection or other messaging platform.

Customer SMPP credentials and connection details for a supplier platform are configured in the SMPP Load Balancer service. Your customers connect to the service. The service connects to your supplier, and messages submitted by your customers are sent to the supplier connection. Traffic from multiple customers is multiplexed onto the connection with your supplier. Delivery receipts are routed back from your supplier via the service to the customer SMPP connection that submitted the corresponding outbound message.