SMPP: what it is, how it works and how to choose a provider
The protocol that carries your SMS to the carrier in seconds, and when you should use it or leave it to a platform
When your bank sends you a verification code, the SMS arrives in two or three seconds. Behind that speed there is usually a direct connection between the sending platform and the carrier’s network. And that connection almost always speaks the same language: SMPP.
What is SMPP?
SMPP stands for Short Message Peer-to-Peer. It is the open protocol that businesses and SMS providers use to exchange text messages with carriers’ message centers.
It runs over TCP/IP, so it travels over the internet or private networks. And it is designed to move many messages per second with very little waiting.
If you know email, the comparison is simple. SMTP is the protocol servers use to pass emails to each other. SMPP plays that same role in the world of SMS.
Origin and versions
It was created in the early nineties by Aldiscon, an Irish company that made software for carriers. It was later managed by the SMS Forum, an industry association that shut down in 2007, and the specification has not changed since.
| Version | Year | What it brought |
|---|---|---|
| SMPP 3.3 | 1990s | First public specification, send-only or receive-only |
| SMPP 3.4 | 1999 | Sessions that send and receive at the same time. The most widely used today |
| SMPP 5.0 | 2003 | Improvements for high volumes and broadcasting to areas, with little adoption |
How does SMPP work?
SMPP follows a client-server model with two parts.
The ESME (External Short Messaging Entity) is the application that sends or receives the SMS. It can be a provider’s platform or a bank’s alert system.
The SMSC (Short Message Service Center) is the carrier’s message center. It receives each SMS, stores it if the phone is unavailable and delivers it as soon as it can.
The ESME opens a connection with the SMSC and keeps it open. It does not connect and disconnect for each message, as a regular website would. That is why it can send hundreds of SMS per second.
The session can be one of three types: send only (transmitter), receive only (receiver) or both at once (transceiver).

Send SMS without setting up connections
Create your free Mailrelay account and send your SMS from the dashboard, with no SMPP sessions or agreements with carriers.
The main commands
The two sides talk to each other with messages called PDUs. Each one has its response, so you always know whether an SMS was accepted or failed.
| Command | What it’s for |
|---|---|
| bind | Opens the session with a username (system_id) and a password |
| submit_sm | Sends an SMS to the SMSC for delivery |
| deliver_sm | The SMSC delivers an incoming SMS or a delivery report |
| enquire_link | Checks every few seconds that the connection is still alive |
| unbind | Closes the session cleanly |
Delivery reports
When the SMS reaches the phone, or when it fails, the SMSC notifies the application with a delivery report (DLR). That way you know whether the number does not exist, the phone was switched off or the message expired.
With that data you measure your sends and clean out numbers that no longer work.
Characters and long messages
An SMS holds 160 characters with the GSM alphabet. If you use emojis or other symbols, the message switches to Unicode and the limit drops to 70.
Longer messages are split into segments of 153 characters (or 67 in Unicode) that the phone puts back together. Each segment is charged as one SMS, so it pays to count your SMS characters before sending.
What is an SMPP server?
An SMPP server is the side that accepts connections: a carrier’s SMSC or the gateway of a provider acting as an intermediary. The client is the application that connects to send.
There are open-source gateways, such as Kannel or Jasmin, that let you set up your own SMPP server. But you still need agreements with carriers or with an aggregator that gives you access to the network.
The officially assigned port is 2775, although each provider uses whichever one it wants.
SMPP vs. an HTTP API
Many providers also offer an HTTP API for sending SMS. Both reach the same place, but they are not meant for the same thing.
| SMPP | HTTP API | Platform with a dashboard | |
|---|---|---|---|
| Who it’s for | Providers and high-volume businesses | Developers integrating SMS into their website or app | Marketing teams and SMBs |
| Speed | Very high, permanent connection | High, one request per message or batch | High, the connection belongs to the provider |
| Difficulty | High: sessions, windows, reconnections | Medium: regular web requests | Low: no code |
| Delivery reports | Via deliver_sm | Via webhook or query | In the dashboard statistics |
For most SMBs, it is more than they need. It fits when you send millions of SMS a month or when every second counts, as with one-time codes.

How do you choose an SMPP provider?
If you really need this connection, these are the questions to ask before signing:
- Does it have a direct connection with the carriers? The fewer intermediaries, the fewer delays and lost messages.
- How many messages per second does it support? This is called TPS. Ask about your account’s limit, not the whole platform’s.
- Does it return real delivery reports? Some mark everything that leaves their system as delivered.
- Does it encrypt the connection? SMPP does not encrypt on its own. Ask for TLS or a VPN and access restricted to your IP addresses.
- Does it handle alphanumeric sender IDs? In Spain, since September 15, 2026, the sender ID must be listed in the CNMC registry.
- How does it handle data? Your customers’ phone numbers go through this connection, and their processing must comply with the GDPR.
What SMPP is used for
It is behind a large share of professional SMS traffic:
- Transactional SMS: order confirmations, delivery notices and verification codes.
- Mass sends or bulk SMS: the same campaign to thousands of contacts.
- Integrations with a CRM or a booking system that sends notices automatically.
- Receiving replies, such as an appointment confirmation.
How Mailrelay helps you
To send SMS you don’t need to open sessions with carriers. With Mailrelay’s SMS service we handle the connection with the carriers, and you create and schedule your campaigns from the same dashboard you use for email.
You send to more than 50 countries with prepaid packages and no commitment, register your CNMC sender ID right from the dashboard and can add SMS to your automations alongside your emails. If you prefer to integrate it into your website or app, you can also send via API.
SMS and email from the same dashboard
Combine your SMS campaigns with up to 80,000 free emails a month, with human support on every plan.
Frequently asked questions about SMPP
Is SMPP the same as SMS? No. SMS is the text message. SMPP is one of the protocols that carry that message from an application to the carrier’s network.
Do I need SMPP to do SMS marketing? No. If you send from an SMS marketing platform, the provider takes care of the technical connection and you only prepare the message.