Sending SMS using the SMPP protocol

To start an integration with sending via the SMPP protocol, the following requirements are essential:

• A LabsMobile account associated with a username (registration email). Create an account here.
• It is necessary to have a user (system_id) and an SMPP password for authentication.
• The account must have available balance to allow message sending.

Activation of the SMPP Service

To activate this service, it is necessary to send an email to the support area support@labsmobile.com. The email must specify:

• Email associated with the account
• Estimated monthly volume of messages
• IP address of the server that will make the SMPP connections

With the information described above, the user (system_id) and the password that will be used for authentication will be established.

PDU SMPP compatible

The SMPP server supports the following PDU, fundamental for establishing and maintaining communication between the client and the server. Below are detailed their main functions and how they intervene in the transmission and reception of SMS messages.

• Expand all

  Types of PDU

  The SMPP server supports the following PDU

• bind_transmitter

  It is a request to establish an SMPP session as a transmitter. The client sends this command to the SMSC (server) to authenticate and send outgoing SMS messages.

• unbind

  It is used to close an SMPP session correctly. Indicating that it no longer needs to keep the connection active.

• submit_sm

  It is responsible for sending an SMS message through an active session.

• deliver_sm

  It is the command that the SMSC uses to confirm the delivery status of the message (DLR).

• enquire_link

  It serves as a ping maintenance to check that the connection TCP is still active between the client and the server.

Examples of PDU

Below are the different types of response PDU and delivery (DLR) that the LabsMobile platform can return via SMPP connection.

Response Successful - ESME_ROK

This PDU is returned after the successful sending of an SMS. And returns the status ESME_ROK

{
  "params": { "message_id": "68090a534e551" },
  "tlvs": {},
  "cmdLength": 30,
  "cmdId": 2147483652,
  "cmdStatus": "ESME_ROK",
  "seqNr": 2,
  "cmdName": "submit_sm_resp"
}               

Error Unknown - ESME_RUNKNOWNERR

In case of failure, a generic status such as ESME_RUNKNOWNERR can be returned.

{
  "params": { "message_id": "" },
  "tlvs": {},
  "cmdLength": 16,
  "cmdId": 2147483652,
  "cmdStatus": "ESME_RUNKNOWNERR",
  "seqNr": 2,
  "cmdName": "submit_sm_resp"
}               

Response Successful - DELIVERED

Indicates that the message was delivered correctly to the end-user device. The platform can return two types of response: a DLR with the status of the message or a PDU object with the corresponding information.

DLR indicating the status of the message

{
  "statusMsg": "DELIVERED",
  "statusId": 2,
  "smsId": "68090a534e551"
}
              

PDU object with information on the status of the message

{
  "params": {
    "source_addr": "573137464378",
    "destination_addr": "SENDER",
    "esm_class": 4,
    "short_message": "id:68090a534e551 submit date:2504231542 done date:2504231543 stat:DELIVRD err:000"
  },
  "tlvs": {
    "message_state": { "tagId": 1063, "tagName": "message_state", "tagValue": 2 },
    "receipted_message_id": { "tagId": 30, "tagName": "receipted_message_id", "tagValue": "68090a534e551" }
  },
  "cmdName": "deliver_sm",
  "cmdStatus": "ESME_ROK"
}
              

Error in delivery - UNDELIVERABLE

Indicates that the message could not be delivered to the end-user device. The platform can return two types of response: a DLR with the status of the message or a PDU object with detailed information about the error.

DLR indicating failure in message delivery

{
  "statusMsg": "UNDELIVERABLE",
  "statusId": 5,
  "smsId": "6809168bddf6b"
}
              

PDU object with information on the delivery failure

{
  "params": {
    "source_addr": "573137464378",
    "destination_addr": "SENDER",
    "esm_class": 4,
    "short_message": "id:6809168bddf6b submit date:2504231634 done date:2504231635 stat:UNDELIV err:001"
  },
  "tlvs": {
    "message_state": { "tagId": 1063, "tagName": "message_state", "tagValue": 5 },
    "receipted_message_id": { "tagId": 30, "tagName": "receipted_message_id", "tagValue": "6809168bddf6b" }
  },
  "cmdName": "deliver_sm",
  "cmdStatus": "ESME_ROK"
}