SMS Gateway Explained: How Business Messaging Is Routed
An SMS gateway connects a business application to mobile telecommunications networks. It accepts messages from systems such as banking platforms, customer relationship management software and authentication services, then routes those messages towards the recipient’s mobile network.
That simple description hides a substantial amount of network activity. A message may pass through an application platform, an SMS gateway, one or more carrier connections, a Short Message Service Centre and the recipient’s serving network before appearing on a handset. Routing decisions, number portability, sender identification, traffic filtering and delivery reporting can all affect the outcome.
Understanding this path helps businesses assess route quality, investigate delivery problems and choose an appropriate messaging provider. It has also become more important from a compliance perspective. On 15 July 2026, Ofcom finalised new protections intended to help mobile providers block, limit and disrupt scam messages. These measures raise the operational expectations placed on participants in the UK messaging chain.
What Does an SMS Gateway Do?
An SMS gateway provides the technical interface between a business application and the mobile messaging ecosystem.
A business system generally does not connect directly to every mobile operator it needs to reach. Establishing and managing individual interconnects would require specialist infrastructure, commercial agreements, technical testing, security controls and continuous route management.
Instead, the application submits messages to an SMS gateway provider. The provider authenticates the connection, validates the message, selects an available route and passes the traffic towards the appropriate destination network.
Common business use cases include:
One time passwords and account verification
Transaction and payment notifications
Appointment reminders
Delivery and logistics updates
Service alerts
Customer support conversations
Marketing messages sent with the appropriate consent
For low volume applications, a business might connect through an HTTP API. Larger messaging platforms and carriers often use SMPP interconnect because it supports persistent sessions, higher throughput and detailed messaging controls.
SMPP, or Short Message Peer-to-Peer, is an open industry protocol for transferring short message data between applications, routing entities and message centres. It allows external applications to submit messages to an SMSC or SMS gateway and receive inbound messages and delivery receipts.
How Business Messaging Is Routed
The precise route varies by provider and destination, but a typical application-to-person message follows this sequence.
1. The business application creates the message
A banking platform, SaaS product or communications platform generates a message for a recipient.
The message request usually contains:
The destination mobile number
The message body
A sender ID or originating number
Character encoding information
A client message reference
A request for a delivery receipt
Optional validity and scheduling settings
The destination should normally use the international E.164 format, such as +447... for a UK mobile number. Normalised numbering reduces ambiguity when messages cross national networks.
2. The application submits the message
The application sends the message to the SMS gateway through an API or SMPP session.
With SMPP, the client application is commonly described as an External Short Message Entity. It binds to the gateway using credentials and submits a submit_sm protocol data unit. The gateway responds with a submit_sm_resp, normally containing a message identifier if it accepts the submission.
Acceptance does not mean the handset has received the message.
It means the gateway has accepted responsibility for further processing. Final delivery remains dependent on downstream routing, network availability, subscriber status and filtering.
3. The gateway validates the traffic
Before routing begins, the SMS gateway may perform several checks:
Is the client authenticated?
Is the destination correctly formatted?
Is the sender ID permitted for this customer and destination?
Does the account have sufficient credit or commercial authorisation?
Is the content within permitted policy limits?
Does the traffic resemble an expected customer pattern?
Is the message duplicated or malformed?
Does the request comply with rate and throughput limits?
Modern gateways also apply fraud and abuse controls. A sudden increase in traffic, a new destination pattern or suspicious URLs may trigger additional checks, throttling or blocking.
4. The gateway identifies the destination network
The number prefix alone may not show which operator currently serves a subscriber because mobile numbers can be ported.
A number originally allocated to one operator may now be active on another. Effective A2P SMS routing therefore requires access to current portability or network routing information.
The gateway or downstream carrier determines the serving network and chooses a route based on factors such as:
Destination country and operator
Number portability data
Route availability
Commercial agreements
Traffic type
Sender ID restrictions
Quality history
Latency and congestion
Regulatory requirements
A gateway may have several technically valid routes to the same country. They are not necessarily equal.
5. The message enters an SMSC
The message is passed to a Short Message Service Centre, usually abbreviated to SMSC.
An SMSC acts as a store and forward system. It receives the message, attempts delivery and retains it for another attempt when immediate delivery is not possible and the validity period permits retrying.
For example, a handset might be switched off, temporarily out of coverage or unable to receive messages. Rather than failing at once, the SMSC may keep the message and try again later.
The SMSC also creates or relays status information that can become a delivery receipt.
6. The network locates the subscriber
Within traditional GSM and UMTS architectures, signalling systems are used to determine where the subscriber is registered and where the message should be sent.
SS7, or Signalling System No. 7, provides a signalling framework used across telecommunications networks. The Mobile Application Part within SS7 supports mobile services including SMS routing.
The sending network can query subscriber routing information and pass the message towards the appropriate serving network element. In newer network environments, parts of this process may use LTE or IP based signalling, but SMS interworking remains essential because businesses must reach subscribers across different generations of mobile network technology.
7. The serving network attempts handset delivery
The recipient’s mobile network sends the message towards the device.
Several outcomes are possible:
The handset accepts the message
The handset is unavailable and the SMSC retries
The number is invalid or disconnected
The subscriber is roaming and additional routing is needed
The message is blocked by network policy
The validity period expires before delivery
The network returns an error
Once the destination network has a final or interim result, status information can travel back through the routing chain.
SMPP, SMSC and SS7: Different Parts of the Route
SMPP, the SMSC and SS7 are sometimes discussed as though they perform the same function. They do not.
SMPP connects applications and messaging platforms
SMPP is mainly an application and messaging interconnect protocol. It carries message submissions, responses, inbound messages and delivery receipts across an IP connection.
It is widely used between:
CPaaS providers and mobile operators
Enterprise messaging platforms and gateways
Aggregators and carriers
SMS gateways and SMSCs
Messaging hubs and downstream providers
An SMPP connection can be configured as transmitter, receiver or transceiver. A transceiver session supports sending and receiving traffic through the same bind.
The SMSC stores and forwards messages
The SMSC is the messaging service centre.
Its responsibilities can include:
Receiving message submissions
Queuing traffic
Attempting delivery
Applying retry rules
Managing validity periods
Creating message status records
Routing mobile originated messages
Interworking with other networks
The SMSC is where the store and forward behaviour associated with SMS normally takes place.
SS7 supports signalling inside and between networks
SS7 is a wider telecommunications signalling system. It is not an enterprise messaging API.
In an SMS context, SS7 based signalling can help networks locate subscribers, exchange routing information and deliver messages across mobile infrastructure. A business platform will usually interact with SMPP or an HTTP API rather than issuing SS7 messages itself.
Stour supports full SMPP and SS7 interconnectivity to its SMSC platform, as well as inbound and outbound SMS on mobile and fixed line numbers. This gives wholesale customers access to messaging infrastructure at the network level rather than treating SMS solely as a software API transaction.
How Routing Decisions Affect SMS Delivery
An accepted message can still be delayed, blocked or misreported. Route design plays a large part in the outcome.
Direct routes and indirect routes
A direct route usually involves a commercial and technical relationship that brings the message into the destination operator or an authorised network partner with limited intermediary handling.
An indirect route may pass through additional aggregators or carriers.
Indirect routing is not automatically poor. International messaging depends on a broad ecosystem, and reputable providers use indirect relationships where appropriate. Problems arise when a buyer cannot see how traffic is being routed or when a low price depends on unstable, unauthorised or heavily filtered paths.
Every additional intermediary can introduce:
Another queue
Another policy layer
Another point of failure
Another message identifier
Another delivery receipt conversion
Less direct fault visibility
More complex commercial reconciliation
For authentication or urgent operational alerts, those differences matter.
Least cost routing versus quality routing
Least cost routing selects the lowest priced available path that meets the provider’s rules. Quality based routing gives greater weight to delivery performance, latency, stability and error behaviour.
A sensible routing policy considers more than price. It may use:
Historical delivery rates
Time to first delivery attempt
Delivery receipt quality
Destination specific restrictions
Route capacity
Current network incidents
Sender ID support
Complaint and blocking trends
The lowest unit cost can become expensive when messages arrive late, customers request repeat codes or support teams must investigate inconsistent delivery.
Sender IDs affect route selection
A sender ID tells the recipient who sent the message. It may be:
An alphanumeric name
A dedicated long number
A short code
A virtual mobile number
A shared service number
Countries and operators apply different rules to sender IDs. Some allow dynamic alphanumeric senders. Others require preregistration, substitute the sender, restrict generic names or prohibit certain formats.
The route must support the sender type being used. Otherwise, the message may fail, arrive with a modified sender or be blocked as suspicious.
Concatenation and character encoding
A standard GSM encoded SMS segment can carry up to 160 characters. Messages containing characters outside the GSM character set may use Unicode, which reduces the number of characters available in each segment.
Long messages are split into concatenated segments. Each segment consumes network capacity and is normally charged separately.
This matters operationally. A small change such as using a Unicode quotation mark can turn one message into several billable segments.
A competent SMS gateway should expose segment counts, encoding and message length before submission or through reporting.
What Do Delivery Receipts Actually Mean?
A delivery receipt, commonly called a DLR, reports the status of a message.
Possible statuses include:
Accepted
Submitted
Delivered
Undeliverable
Expired
Rejected
Deleted
Unknown
The exact terminology and meaning depend on the provider and network.
A DELIVRD status generally indicates that the destination network reported successful delivery to the handset or subscriber device. It does not prove that the recipient read the message, understood it or acted on it.
A submitted status is weaker. It might only confirm that a downstream platform accepted the message.
This distinction is important when comparing providers. A reported delivery rate is only useful when the underlying status definitions are clear.
Technical teams should ask:
Does the receipt come from the destination network?
Are intermediate statuses presented as delivered?
How are provider specific error codes normalised?
How long are receipts retained?
Can reports be reconciled using the original client reference?
Are receipts available in real time through SMPP and API callbacks?
Delivery receipts also have limitations. Some international networks provide incomplete, delayed or inconsistent status data. Honest reporting should preserve that uncertainty instead of turning every ambiguous result into a success.
Security, Filtering and UK Compliance
An SMS gateway is part of the security boundary for business messaging.
Gateways process recipient numbers, message content, sender information, routing metadata and delivery records. Providers therefore need appropriate access control, logging, incident management and data protection measures.
Security controls commonly include:
Encrypted API or SMPP transport
IP allowlisting
Credential rotation
Account and role separation
Traffic rate limits
Audit logs
Content and URL analysis
Sender ID controls
Customer due diligence
Continuous traffic monitoring
Incident response procedures
Ofcom’s 2026 mobile messaging measures
Ofcom finalised a new package of protections on 15 July 2026 aimed at reducing scam text messages. Ofcom said fraud represented an estimated 45 per cent of reported crime incidents in England and Wales, with £1.28 billion lost to criminals during 2025. It also reported that four in ten UK mobile users had received at least one suspicious mobile message during the preceding three months.
The earlier consultation set out measures covering both person-to-person and application-to-person messaging. For A2P services, the proposals included effective Know Your Customer checks, controls around alphanumeric sender IDs, ongoing Know Your Traffic monitoring, incident management and the blocking of scam messages in transit.
These requirements change how businesses should assess an SMS gateway provider. Compliance cannot be reduced to a clause stating that the customer must not send spam.
Providers need practical processes for onboarding, sender validation, traffic monitoring, investigation and blocking. They must also minimise the risk of legitimate business messages being caught by fraud controls.
For customers, this means onboarding may require more evidence about the organisation, intended use case, sender IDs and expected traffic. That additional scrutiny protects the wider messaging ecosystem and reduces the chance of trusted routes being exploited.
Choosing an SMS Gateway Provider
The right provider depends on traffic profile, destinations, technical resources and risk tolerance. A retailer sending occasional promotions has different requirements from a bank sending time sensitive login codes across several countries.
A useful assessment should cover the following areas.
Network and route quality
Ask where the provider sits in the delivery chain.
Is it an MNO, carrier, aggregator or software reseller?
Which destinations use direct operator relationships?
How many intermediaries may handle the traffic?
How is number portability resolved?
Can routes be changed automatically during an incident?
Are premium and economy route classes clearly separated?
The purpose is not to insist that every destination must use a single direct connection. It is to understand who controls the route and who can investigate when something goes wrong.
SMPP and API capabilities
Technical teams should review:
Supported SMPP version
Transceiver session support
Maximum binds
Throughput limits
Window size
Enquire link behaviour
Delivery receipt format
Error code documentation
HTTP API availability
Webhook retry behaviour
IP security options
Test environment access
A headline throughput figure is not enough. Confirm whether the limit applies per bind, per account, per destination or across the whole service.
Reporting and operational visibility
Useful reporting should include:
Submission timestamps
Network response timestamps
Final delivery timestamps
Message IDs
Client references
Route or supplier identifiers
Error codes
Segment counts
Sender IDs
Destination network
Cost records
Without this information, diagnosing delayed or failed messages becomes guesswork.
Compliance and security
Review how the provider handles:
Customer due diligence
Sender ID authorisation
Consent and opt out requirements
Suspicious traffic
Data retention
Access management
Security incidents
Regulatory changes
Subcontractors and downstream providers
Stour operates as an independent Ofcom regulated UK MNO established in 2006. Its SMS services include SMPP and SS7 interconnectivity to its SMSC platform, global operator relationships and support for inbound and outbound messaging. Its positioning is based on direct network expertise rather than consumer messaging software.
Frequently Asked Questions
-
An SMS gateway connects business applications to mobile networks. An SMSC receives, stores, forwards and retries SMS messages. A gateway may connect directly to one or more SMSCs.
-
SMPP is a protocol used to submit messages, receive inbound SMS and collect delivery receipts. It is widely used by carriers, CPaaS providers and businesses sending higher message volumes.
-
No. A delivery receipt usually confirms that the destination network reported delivery to the handset. It does not confirm that the recipient opened or read the message.
-
Acceptance only confirms that the gateway received the message. Delivery can still fail because of an invalid number, sender ID restrictions, network filtering, handset availability or message expiry.
-
A2P SMS routing is the process of sending application generated messages, such as authentication codes, alerts and reminders, to mobile subscribers through gateways, carriers and mobile operators.
Key Takeaways
An SMS gateway is the connection point between a business application and the mobile network ecosystem. It accepts messages, validates traffic, selects routes and passes each message towards an SMSC and the recipient’s serving network.
SMPP usually handles the application or platform interconnect. The SMSC stores, forwards and retries messages. SS7 and other network signalling technologies support subscriber location and delivery within mobile networks.
Route quality depends on far more than whether a provider offers an API. Number portability, sender ID rules, carrier relationships, filtering, delivery receipt quality and operational support all affect real performance.
The UK regulatory direction is also clear. Effective customer checks, sender controls, traffic monitoring and scam blocking are becoming central requirements for business messaging providers, not optional service features.
Businesses evaluating an SMS gateway should therefore examine the whole delivery chain. Price matters, but so do route visibility, technical accountability, security and the ability to resolve faults quickly.
To discuss SMPP connectivity, UK messaging routes or network level SMS requirements, contact Stour’s technical team to review your interconnect and routing needs.
