SMPP Load Balancer

SMPP load balancer for high availability, reliability and capacity.


Use the Melrose Labs SMPP Load Balancer cloud and on-premises platform with your messaging platform, SMS gateway or SMSCs to provide a high availability endpoint for your customers, insulate your platforms from the Internet, and optimise SMS traffic loading.

The SMPP Load Balancer service provides an endpoint to which your customers connect using the SMPP protocol to submit messages for delivery to mobiles and receive messages from mobiles. SMPP connections over TCP, with or without TLS, can be load-balanced at the transport layer (layer 4) onto our SMPP Load Balancer nodes. Messages submitted via those customer connections are load-balanced (layer 7) across the target platforms you define.

Benefits

The use of the SMPP Load Balancer service can bring the following benefits:

  • Manage customer traffic load.
  • Reduce exposure of platforms to the Internet.
  • Improved availability.
  • Reduced customer impact from upstream platform failures.
  • Enables platform maintenance without service impact.
  • Improved utilisation of resources.

Usage Scenarios

Load balancer scenario 1 - multiplex

Scenario #1 - Multiplex

SLB Platform - 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.

Load balancer scenario 2 - proxy

Scenario #2 - Proxy

SMPP Load Balancer 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.

Load balancer scenario 3

Scenario #3

SLB Platform - Multiplex

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.

Load balancer scenario 4

Scenario #4

SLB Platform - Multiplex or SMPP Load Balancer Proxy

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.

Load balancer scenario 5

Scenario #5

SLB Platform - Multiplex

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.

Melrose Labs SMPP Load Balancer Summary
Client (ESME) Control
  • Authorisation offload (local DB) or passthru
  • Authorisation integration (REST, DIAMETER or RADIUS)
  • Bind count limit
  • Bind region control
  • Rate limiting
  • Source address restriction
  • Destination address restriction
  • Destination address whitelist/blacklist (MSISDN)
  • Validity period (VP) enforcement
  • Message parameter control
Features Supported
  • Delivery receipts (DLRs)
  • Concatenated SMS
  • SMPP v3.3, v3.4, v5
  • SMPP over TLS (ESME and SMSC connections)
  • Harmonized DLR error codes (mapping)
    Routing
    • Proxy or multiplex mode for upstream SMPP bind traffic
    • SMSC pools
    • SMSC maintenance schedules
    • Manual SMSC suspension
    • Automatic SMSC suspension on traffic issues
    • Failover SMSC pools
    • SMS cost-based routing
    • Degraded platform detection
    Worldwide Nodes
    • Europe (UK)
    • Europe (Germany)
    • Europe (Sweden)
    • Africa (South Africa)
    • Middle East (Bahrain)
    • North America (US)
    • South America (Brazil)
    • Asia Pacific (Singapore)
    • Asia Pacific (Australia)
    Portal
    • Account configuration
    • Client (ESME) and SMSC traffic levels
    • SMSC connection state
    • CDRs
    • Client (ESME) traffic reporting
    • SMSC traffic reporting
    Reliability and Availability
    • SLA of 100% uptime across multiple worldwide nodes
    • Unparalleled reliability
    Live  Coming Soon  Planned     Features vary by type and level of SMPP Load Balancer required.

    Platforms, Services and Pricing

    The SMPP Load Balancer platform is available in a number of different on-premises and cloud configurations.

    On-premises platforms

    Melrose Labs will supply you with the necessary binaries and technical support to fulfil your required configuration. You provide the host on which the binaries are installed. Support will be provided by Melrose Labs to assist you with the installation of the platform.

    When ordering, select a RedHat (suitable for Centos, SuSE Linux, etc) or Debian (suitable for Ubuntu, Mint, etc) build.

    TypePrice (one-off)Limits
    SMPP Load Balancer ProxyDocumentation
    SMPP Load Balancer Proxy
    Low level
    • Perpetual software license
    • Binaries delivered
    • Year 1 maintenance included
    GBP 1995.00 per instance 200 SMS/sec
    25 upstream SMPP servers
    TLS supported
    Find out more
    SMPP Load Balancer Proxy
    High level
    • Perpetual software license
    • Binaries delivered
    • Year 1 maintenance included
    GBP 4995.00 per instance 2000 SMS/sec
    50 upstream SMPP servers
    TLS supported
    Find out more

    GBP 525 annual maintenance from year 2 (covers all instances)

    Cloud platforms

    TypePrice (per month)Limits
    SMPP Load Balancer Proxy (Shared)
    SMPP Load Balancer Proxy (Shared)
    Free level
    USD 0.00 per system ID5 SMS/sec
    2 upstream SMPP servers
    Non-TLS
    Find out more
    SMPP Load Balancer Proxy (Shared)
    Low level
    USD 25.00 per system ID200 SMS/sec
    25 upstream SMPP servers
    Non-TLS
    Find out more

    Shared SLBP is available at host smpplb.melroselabs.com:32775 (SMPP)

    Configure system ID and upstream target SMPP servers at https://melroselabs.com/tools/slbp/shared/ .

    TypePrice (per month)Limits
    SMPP Load Balancer Proxy (Dedicated)Documentation
    SMPP Load Balancer Proxy
    Low level
    GBP 195.00 per instance200 SMS/sec
    25 upstream SMPP servers
    Non-TLS
    Find out more
    SMPP Load Balancer Proxy
    Medium level
    GBP 295.00 per instance1000 SMS/sec
    50 upstream SMPP servers
    TLS supported
    Find out more
    SMPP Load Balancer Proxy
    High level
    GBP 395.00 per instance5000 SMS/sec
    100 upstream SMPP servers
    TLS supported
    Find out more
    TypePrice (per month)Limits
    SLB Platform - Multiplex
    SMPP Load Balancer (SLB) Platform
    Standard
    • Manage customer SMPP accounts
    • Create multiple load balancers
    • Define target groups representing groups of SMSCs and SMS gateways
    • Firewall: content and MSISDN blocking
    • Rules for message control and manipulation
    • Message lookup
    • Monitoring and alerting
    • Global sites (EU, NA, SA, AP)
    US$0.0001/SMS
    500 SMS/sec
    200 upstream SMPP servers
    TLS supported
    Find out more

    Service snapshot

    • Load balance across multiple SMS gateways and SMSCs
    • Bind authorisation on load balancer (SLB platform) or passthru (Proxy)
    • Up to 5000 SMS/sec throughput
    • Concatenated SMS support
    • A2P SMS
    • P2A SMS

    Find out more...

    Please provide your name.
    Please provide a valid company name.
    Please type your message.
    Please provide a valid email address.