It runs over TCP\/IP networks, meaning over the internet or private networks. And it is designed to move large volumes of messages quickly and reliably.<\/p>\n\n
To understand it better, think of email. The SMTP<\/a> protocol is the standard for sending emails between servers. SMPP plays a similar role in the world of SMS.<\/p>\n\n The protocol was created in the 1990s by the Irish company Aldiscon. It was later taken over by a developer forum, which eventually became the SMS Forum.<\/p>\n\n These are the main versions:<\/p>\n\n Although 5.0 is the most recent, 3.4 is still the one most used by carriers and providers.<\/p>\n\n SMPP follows a client-server model. Two components are involved:<\/p>\n\n The ESME<\/strong> (External Short Messaging Entity<\/em>) is the application that sends or receives messages. For example, a company’s SMS platform or a bank’s alert system.<\/p>\n\n The SMSC<\/strong> (Short Message Service Center<\/em>) is the carrier’s message center. It receives the SMS messages, stores them and delivers them to the recipients’ phones.<\/p>\n\n The ESME opens a connection with the SMSC and keeps it active for the entire session. Unlike other systems, it doesn’t connect and disconnect for each message. That’s why it can send hundreds of messages per second with very low latency.<\/p>\n\n There are three session types, depending on what the application needs: send only (transmitter<\/em>), receive only (receiver<\/em>) or both at once (transceiver<\/em>).<\/p>\n\n Communication is based on structured messages called PDUs. Each one has a specific function. These are the most important ones:<\/p>\n\n Every command gets a response. That way, both sides know at all times whether a message has been accepted or has failed.<\/p>\n\n One of SMPP’s most useful features is delivery reports, known as DLRs (delivery reports<\/em>). When the message reaches the phone, or when it fails, the SMSC sends a notification to the application.<\/p>\n\n Thanks to them, you know whether each SMS was delivered, whether the number doesn’t exist or whether the phone was switched off. This information is key to measuring your campaigns and keeping your database clean.<\/p>\n\n Today, many providers also offer an HTTP API<\/a> for sending SMS. Which one should you use?<\/p>\n\n SMPP is the preferred option for very high volumes and sends where every second counts, such as verification codes. Its persistent connection makes it faster and more efficient. But it requires more technical knowledge to set up and maintain.<\/p>\n\n An HTTP API is much easier to integrate. All it takes is one web request per message or per batch, and most developers already know how to work with it. For most small and medium-sized businesses, it’s more than enough.<\/p>\n\n And there’s a third option: using a platform that takes care of everything. In that case, you send your campaigns from a dashboard and the provider manages the connection with the carriers.<\/p>\n\n It’s behind a large share of professional SMS traffic. Some common uses:<\/p>\n\n Transactional SMS<\/a>, such as order confirmations, delivery notifications or one-time codes.<\/p>\n\n Mass sends or bulk SMS<\/a>, where a company sends the same campaign to thousands of contacts.<\/p>\n\n Integration with internal systems, such as a CRM<\/a> or a booking tool, that send notifications automatically.<\/p>\n\n It also lets you receive messages. That way, a company can handle replies from its customers, such as an appointment confirmation.<\/p>\n\n The original version of SMPP doesn’t encrypt data. That’s why reputable providers protect the connection with encrypted channels, such as TLS or a VPN, and restrict access to authorized IP addresses.<\/p>\n\n This matters because your recipients’<\/a> personal data travels through this channel. And its processing must comply with the LOPD<\/a>. It’s always a good idea to ask your provider how they protect information.<\/p>\n\n If you want to send SMS without worrying about protocols or carrier connections, Mailrelay makes it easy. With our SMS sending service<\/a>, you create and schedule your campaigns from the same dashboard you use for email marketing.<\/p>\n\n You can check the SMS pricing<\/a> and combine it with your free account, which includes up to 80,000 emails per month and 20,000 contacts. If you want to try it, you can create your Mailrelay account<\/a> today.<\/p>\n\n Is SMPP the same as SMS?<\/strong> No. SMS is the text message; SMPP is one of the protocols used to send it from an application to the carrier’s network.<\/p>\n\n Which port does SMPP use?<\/strong> The officially assigned port is 2775, although many providers use others.<\/p>\n\n Do I need SMPP to do SMS marketing?<\/strong> Not necessarily. If you send from a platform like Mailrelay, the provider handles the technical connection for you.<\/p>\n\n SMPP is the standard that allows companies and carriers to exchange SMS quickly and at scale. Its persistent connection and delivery reports have made it the foundation of SMS marketing<\/a> and transactional messaging.<\/p>\n\n Even so, you don’t need to master it to send your campaigns. What matters is choosing a reliable provider with good connectivity and clear handling of your customers’ data.<\/p>\n\nOrigin and versions<\/h2>\n\n
\n
How it works<\/h2>\n\n
![\"Diagram](\"https:\/\/mailrelay.com\/wp-content\/uploads\/2023\/10\/como-funciona-smpp-esme-smsc-1024x576.png\")
<\/figure>\n\nThe main commands<\/h2>\n\n
\n
Delivery reports<\/h2>\n\n
SMPP vs. an HTTP API<\/h2>\n\n
What SMPP is used for<\/h2>\n\n
Security<\/h2>\n\n
How we help you at Mailrelay<\/h2>\n\n
Frequently asked questions about SMPP<\/h2>\n\n
In conclusion<\/h2>\n\n
Related entries<\/h2>\n\n