message database) before forwarding the message for delivery to the recipient SME. The conventional approach to SMS has been to store the message in an SMSC storage area (e.g. When the async operation completes, the event loop returns to the task to execute its callback. It then continues to execute the rest of its program. In contrast, when a Node application needs to perform an I/O operation, it sends an asynchronous task to the event loop, along with a callback function. This old approach consumes a lot of memory and is notoriously difficult to program. Traditionally, I/O operations either run synchronously (blocking) or asynchronously by spawning off parallel threads to perform the work. Node.js will help us to achieve high MPS as it performs all I/O operations asynchronously. The SMPP server also transmits a delivery report back to the client when there is a change of status for an SMS.

The SMPP client takes care of the SMS and delivers them to the SMPP server. There is a continuous exchange of SMPP PDU (Protocol Data Units or Packets) to ensure a proper bind/connection is established. This session is created using an SMPP client that communicates with an SMPP protocol.

unbind request issued by either the server or the client to terminate the SMPP sessionĪn SMPP session must be established between the ESME (External Short Messaging Entities) and the Message Centre or SMPP Routing Entity where appropriate.

enquire_link requests issued by both the server and client to keep the SMPP session alive.

deliver_sm requests issued by the server to forward messages from the mobile phone to the client, including delivery receipts.

submit_sm requests issued by the client to send messages to a mobile phone.

bind request to establish the SMPP session.

We will be using Node.js node-smpp for the implementation. Meaning that requests can be issued without having to wait first for responses to earlier requests to be received.

Requests are processed asynchronously.

Requests can be issued by the SMPP client as well as the SMPP server.

There is not the connection overhead to be found with protocols such as HTTP that use transient connections.

Connections established by the client with the server are persistent and may be kept open indefinitely.

SMPP is particularly suited to high-volume and high-throughput SMS applications. This tutorial will help you to send SMS messages using your own SMSC gateway. ESME is the system that delivers SMS to SMSC. SMSC acts as middleman to store the message and route it. It exchanges SMS messages between (SMSC) and ESME. SMPP (Short Message Peer-to-Peer) is a protocol used by the telecommunications industry.

Nodejs send sms