SMPP Server for A2P smpp Applications Devloper in linux ( SMS Protocol)

What is SMPP?

The SMPP (Short Message Peer-to-Peer) protocol 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). It is a means by which applications (termed ESMEs) can send SMS messages to mobile devices and receive SMS from mobile devices.

Typical Applications of SMPP

The variety of messaging applications, particularly using SMS, for which SMPP can be employed is almost boundless. Mobile Operators, Message Centre vendors, Infrastructure Providers, and application developers are continually developing new applications for SMS. SMPP is ideal as an access protocol for these applications. The following summarises typical applications of SMPP:

Marketing. Businesses send promotions to customers as text messages.

Booking confirmations. Hotels, restaurants, taxis. Confirmations via SMS are better than email when it comes to immediate notification.

Appointment reminders. Used by businesses to remind customers of appointments and avoid the financial impact and/or impact on customer of a missed appointment.

SMPP Sessions

In order to make use of the SMPP Protocol, an SMPP session must be established between the ESME and Message Centre or SMPP Routing Entity where appropriate. The established session is based on an application layer TCP/IP connection between the ESME and MC/RE and is usually initiated by the ESME. The connection is often over the Internet and can use SMPP over TLS or a VPN to secure the connection. SMPP has been assigned TCP port 2775 by IANA, however other port numbers are often used.

There are three forms of ESME-initiated session:

Transmitter (TX) - when authenticated as a transmitter, an ESME may submit short messages to the MC for onward delivery to Mobile Stations (MS). A transmitter session will also allow an ESME cancel, query or replace previously submitted messages. Messages sent in this manner are often called mobile terminated messages.

Receiver (RX) - a receiver session enables an ESME to receive messages from a MC. These messages typically originate from mobile stations and are referred to as mobile originated messages.

Transceiver (TRX) - a TRX session is a combination of TX and RX, such that a single SMPP session can be used to submit mobile terminated messages and receive mobile originated messages.

Linux PHP MySQL

Proje NO: #28505253

Proje hakkında