SMPP Protocol Documentation


The Short Message Peer-to-Peer (SMPP) protocol is a widely-used industry standard for sending and receiving SMS messages between Short Message Service Centers (SMSCs) and External Short Messaging Entities (ESMEs). SMPP (Short Message Peer-to-Peer) is an open, industry standard protocol designed to provide a flexible data communications interface for the transfer of short message data between External Short Message Entities (ESME), Routing Entities (RE) and Message Centres (MC). The SMPP protocol is a means by which applications can send SMS messages to mobile devices and receive SMS from mobile devices. This documentation provides information on how to use the SMPP protocol for sending bulk SMS to Sozuri.

SMPP Protocol Overview

The SMPP protocol consists of a set of commands and parameters that can be used to submit messages for delivery, receive delivery reports, and manage the state of the connection between the SMSC and the ESME. The protocol supports both ASCII and Unicode character sets, and supports a wide range of messaging applications, including bulk SMS, two-way SMS, and Premium Rate SMS services.

Getting Started with SMPP

To get started with the SMPP protocol, you will need an SMPP account in your Sozuri project. Sozuri will provide you with the necessary credentials, such as the system ID, password, and Sozuri SMPP server address, to connect. You will also need an SMPP client or library to send and receive messages via the SMPP protocol.

101: MT is referred to Mobile Terminated, a SMS-MT is an SMS sent to mobile MO is referred to Mobile Originated, a SMS-MO is an SMS sent from mobile

SMPP Command Reference

The following is a list of the most commonly used SMPP commands:

  • bind_transciever: Used to establish a bidirectional connection between the ESME and the SMSC in transmission mode.
  • submit_sm: Used to submit a message for delivery to a mobile subscriber.
  • deliver_sm: Used by the SMSC to deliver a message to the ESME.
  • unbind: Used to terminate a connection between the ESME and the SMSC.
  • enquire_link: Used to check the status of the connection between the ESME and the SMSC.

SMPP Parameter Reference

Using a proper SMPP Client application, the following parameters must be considered:

Binding to SMPP Server

  1. host:
  2. port: 2775 (Non-TLS)
  3. system_id: The system ID provided by Sozuri, used to identify the ESME.
  4. password: The password provided by Sozuri, used to authenticate the ESME.

Sending Messages via SMPP
  1. source_address: The source address of the message; a shortcode or alphanumeric sender Id. Sozuri will provide you with one. For testing use Sozuri"
  2. destination_address: The destination address of the message, typically the recipient's phone number.
  3. short_message: The text of the message, limited to a maximum length of 160 characters for GSM-7 character sets and 70 characters for Unicode character sets.