# SMSC vs SMS gateway — what's the difference?

> An SMSC and an SMS gateway sit at different layers of the delivery path. An SMSC (Short Message Service Centre) is the store-and-forward node inside a mobile operator's core network that queues and delivers SMS to handsets; an SMS gateway is the application-facing platform that accepts messages over HTTP or SMPP and routes them to the correct operator's SMSC. Every SMS passes through an SMSC; a gateway is how an application reaches one.

- Canonical URL: https://www.broadnet.me/answers/smsc-vs-sms-gateway
- Language: en
- Last reviewed: 2026-09-24
- Publisher: BroadNet (https://www.broadnet.me)

## What the SMSC does

The SMSC is a mandatory node in the mobile core, specified in 3GPP TS 23.040. It implements store-and-forward: when a message can't be delivered immediately (handset off, out of coverage), the SMSC holds it and retries until it succeeds or the validity period expires. It handles both mobile-originated (MO) and mobile-terminated (MT) messages and returns the delivery receipt. Operators own and operate their SMSCs; you never connect to one directly.

- Sits inside the operator's core network (3GPP TS 23.040).
- Store-and-forward: queues and retries within the validity period.
- Handles MO and MT messages and issues delivery receipts.
- Owned by operators; not directly reachable by applications.

## What an SMS gateway does

An SMS gateway is the platform that sits between applications and the many operator SMSCs. It exposes a developer-facing interface — an HTTP/REST API or an SMPP bind — accepts your submission, applies sender-ID handling, encoding, and routing logic, and forwards the message to the right destination operator's SMSC. It also normalises the delivery receipts coming back. BroadNet's gateway is exactly this: you call https://api.broadnet.me (for example /sms/sendSms or the /sms/sendbulk REST endpoints), and it reaches operator SMSCs across its network.

- Application-facing: HTTP/REST API or SMPP bind.
- Adds routing, sender-ID, encoding, and DLR normalisation.
- Fans your traffic out to the correct operator SMSCs.
- BroadNet gateway: api.broadnet.me — /sms/sendSms, /sms/sendbulk.

## How they connect

The gateway talks to operator SMSCs over SMPP or SS7 interconnects; the SMSC then delivers to the handset over the radio network. Think of it as a chain: your application → SMS gateway → operator SMSC → handset, with the delivery receipt flowing back the same way. The gateway is the part you integrate against and control; the SMSC is the operator-owned node that performs the final delivery. You need both, but you only ever code against the gateway.

- Chain: application → gateway → operator SMSC → handset.
- Gateway ↔ SMSC over SMPP or SS7 interconnect.
- You integrate and control the gateway, not the SMSC.
- Delivery receipts flow back along the same path.

## SMSC vs SMS gateway at a glance

|  | SMSC | SMS gateway |
|---|---|---|
| Sits where | Inside the operator's core network | Between applications and operators |
| Main job | Store-and-forward delivery to handsets | Accept, route, and forward to the right SMSC |
| Interface | Internal MAP / SMPP | HTTP/REST or SMPP to applications |
| Owned by | The mobile operator | An aggregator / CPaaS (e.g. BroadNet) |
| You talk to it | Indirectly, via a gateway | Directly, via API or SMPP bind |

## Frequently asked questions

### Can I connect my application directly to an SMSC?

In practice, no. SMSCs are operator-owned core-network nodes. Applications reach them through an SMS gateway, which provides the HTTP/REST or SMPP interface and handles routing to the correct operator.

### Is an SMS gateway the same as an SMSC?

No. The SMSC performs the actual store-and-forward delivery inside the operator network; the gateway is the application-facing platform that routes your traffic to the right SMSC and normalises delivery receipts. They are different layers.

### How does BroadNet's gateway relate to operator SMSCs?

You submit to https://api.broadnet.me over HTTP or SMPP, and the gateway forwards each message to the destination operator's SMSC over its interconnects, then returns a delivery receipt. You integrate only against the gateway.

## Related

- [What is an SMSC?](https://www.broadnet.me/answers/what-is-smsc)
- [What is SMPP?](https://www.broadnet.me/answers/what-is-smpp)
- [What is an SMS API?](https://www.broadnet.me/answers/what-is-sms-api)
- [All answers](https://www.broadnet.me/answers)
- [What is an SMSC?](https://www.broadnet.me/answers/what-is-smsc)
- [What is SMPP?](https://www.broadnet.me/answers/what-is-smpp)
- [What is an SMS API?](https://www.broadnet.me/answers/what-is-sms-api)
- [What is an ESME?](https://www.broadnet.me/answers/what-is-esme)
- [SMS API](https://www.broadnet.me/products/sms-api)
- [SMSC gateway](https://www.broadnet.me/operators/smsc-gateway)