SMSC and SMS Gateway Platforms

What is the difference between an SMSC and an SMPP gateway?

An SMSC (short message service centre) is the network element that stores and forwards SMS to handsets. An operator SMSC speaks the mobile network's signaling, MAP over SS7 or SIGTRAN, and in IMS networks SIP. An SMPP gateway sits outside that layer: it accepts SMS from business applications and aggregators over SMPP or HTTP, applies account, routing and security rules, and hands each message to an SMSC that delivers it.

Two platforms, two jobs

	Operator SMSC	Enterprise SMPP Gateway
Main job	Store and deliver SMS to subscribers of a mobile network	Accept, police and route A2P traffic from many business customers
Buyers	Mobile operators, MVNOs, MVNEs, IoT and private network operators	SMS aggregators, banks, resellers, MVNO enterprise units
Network side	MAP over SS7/SIGTRAN, SIP (IMS), HLR integration	SMPP and HTTP to upstream SMSCs and suppliers
Customer side	SMPP and HTTP for applications	SMPP and HTTP for many tenants, with resellers
Built-in protection	Account and access controls; optional inline SMS firewall	Embedded ESME firewall on every submission

How they fit together

The gateway can deliver through the operator SMSC for on-network traffic, or through upstream SMSCs and suppliers for other destinations.

Built in-house

Both platforms are software that runs on standard Linux servers or virtual machines, with no proprietary signaling hardware. Our engineers develop, maintain and support them, so protocol variants, billing exports and integrations can be adapted to each network.

Security built around them

Messaging platforms are where abuse arrives. The gateway includes an ESME firewall on every submission; the SMSC can run with our SMS firewall inline, and operators can protect SMPP connections to any SMSC with our SMPP firewall.

Frequently asked questions

Do I need both products?

Not necessarily. A mobile operator or MVNO that delivers SMS to its own subscribers needs an SMSC. An aggregator, bank or reseller that sends A2P traffic through other networks needs a gateway. Operators that also sell A2P access to enterprises often run the gateway in front of the SMSC.

Are these platforms built by Wise Network?

Yes. Both are designed, built and supported by our engineering team, which means protocol adaptations and customer-specific integrations are handled by the people who wrote the code.

How is capacity sized?

Throughput and latency depend on traffic mix, message classes, redundancy and hardware. We size each deployment from your expected traffic and confirm it in a written sizing document rather than quoting a generic figure.