Messaging & Entitlement SMSC

A cloud-native short message service centre: MAP and SMPP for the network you have, SMSF and SMSoIP for the one you are building, and horizontal scaling instead of a forklift upgrade. It is the least glamorous component we sell and the one most often load-bearing.

MAP (MO-ForwardSM, MT-ForwardSM, SRI-for-SM) over SS7/SIGTRAN, and SMPP 3.4 / 5.0
5G SMSF and SMSoIP for IMS and service-based-architecture cores
Store-and-forward with per-destination retry policy and first-delivery-attempt optimisation
Multi-tenant: routing, number ranges, quotas and CDRs isolated per brand
Anti-spam, anti-faking, SMS home routing and grey-route detection

Scope a replacement

Messaging & Entitlement

MAP / SS7 / SIGTRAN

SMPP 3.4 & 5.0

5G SMSF

SMSoIP / IMS

Home routing

Anti-faking

Multi-tenant

Kubernetes

Zero-downtime cutover

PX instrumented

An honest positioning

SMSC is a mature, crowded market and we are not going to pretend otherwise. If you are a Tier-1 running a competitive replacement programme with five incumbents bidding, we are probably not your answer.

Where we do win is specific: operators and MVNEs who need a modern SMSC quickly, who are adding SMSF for 5G without wanting to reopen a Tier-1 contract, who need genuine multi-tenancy, or who are replacing something end-of-life and value a cutover method over a feature matrix.

It is also the foundation the rest of this pillar sits on. Fallback from RBM lands here. Entitlement and RCS provisioning assume it works. Buying it with the components around it is where it makes the most sense.

Capabilities

Interworking

MAP over SIGTRAN with SRI-for-SM, MT/MO forward and status reporting
SMPP 3.4 and 5.0 for aggregators and enterprise platforms
5G SMSF with SMSoIP toward IMS and the service-based core
IPSM-GW interworking for IMS-attached subscribers

Delivery engine

Store-and-forward with per-destination, per-error retry schedules
First-delivery-attempt optimisation and alert-SC handling
Configurable validity, priority classes and expiry behaviour
Throughput scaled by adding pods, not by replacing hardware

Protection

SMS home routing so foreign networks never see your HLR
Anti-faking, anti-spoofing and origin validation
Grey-route and A2P-over-P2P detection with evidence capture
Per-aggregator quotas, throttles and allow-lists

Operations

Per-tenant CDRs, rating hooks and reconciliation exports
Web console and full REST provisioning API for BSS-driven onboarding
ProBee instrumentation on every interface as standard
Blue/green and canary deployment supported by design

Logical architecture

Signalling front ends. SIGTRAN/MAP, SMPP and SMSF/SMSoIP terminations, each scaled independently.

Routing and policy core. Per-tenant routing tables, screening, home routing and anti-abuse policy.

Store-and-forward. Replicated message store with retry scheduling and durable delivery state.

Management plane. Web console, REST provisioning API, CDR export and configuration as code.

Assurance plane. ProBee probes on each interface, PX per route and per peer.

MMS Suite

RBM Gateway

Replacing an end-of-life SMSC?

Ask us about the shadow-and-canary cutover method before you ask us about the feature list. It is the part that decides whether the project goes well.

Contact us

How replacements run