Reference section - SMPP


SMPP deliver_sm

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.

4.3.1 deliver_sm Operation

The deliver_sm is issued by the MC to send a message to an ESME. Using this command, the MC may route a short message to the ESME for delivery. deliver_sm Syntax

Field NameSize octetsTypeDescriptionRef.
command_length4IntegerSet to overall length of PDU.4.7.4
sequence_number4IntegerSet to a Unique sequence number. The associated deliver_sm_resp PDU will echo this sequence number.4.7.24
service_typeVar. max 6C-Octet StringThe service_type parameter can be used to indicate the SMS Application service associated with the message. Specifying the service_type allows the ESME to avail of enhanced messaging services such as “replace by service_type” or control the teleservice used on the air interface.

Set to NULL if not known by MC
source_addr_ton 1 IntegerType of Number for source address.4.7.1
source_addr_npi 1 Integer Numbering Plan Indicator for source address.4.7.2
source_addrVar. max 21C-Octet StringAddress of SME which originated this message.4.7.29
dest_addr_ton 1 IntegerType of Number for destination4.7.1
dest_addr_npi 1 IntegerNumbering Plan Indicator for destination4.7.2
destination_addrVar. max 21C-Octet StringDestination address of this short message For mobile terminated messages, this is the directory number of the recipient MS4.7.8
esm_class1IntegerIndicates Message Mode and Message Type4.7.12
protocol_id1IntegerProtocol Identifier. Network specific field.4.7.20
priority_flag1IntegerDesignates the priority level of the message4.7.19
schedule_delivery_time1 or 17C-Octet StringThe short message is to be scheduled by the receiving MC or ESME for delivery.

This field is only applicable if the short message is being forwarded to another MC. In this case it is the time at which the receiving MC should schedule the short message.

Set to NULL if not scheduled.
validity_period1 or 17C-Octet StringThe validity period of this message.

This field is only applicable if this short message is being forwarded to another MC. In this case it specifies how long the receiving MC should retain the SM and continue trying to deliver it.

Set to NULL if the current validity period is unavailable.
registered_delivery1IntegerIndicator to signify if a MC delivery receipt or an SME acknowledgement is required.4.7.21
replace_if_present_flag 1IntegerFlag indicating if delivered message should replace an existing message.4.7.22
data_coding 1IntegerDefines the encoding scheme of the short message user data.4.7.7
sm_default_msg_id1IntegerIndicates the short message to send from a list of pre- defined (‘canned’) short messages stored on the receiving MC.

This field is only applicable if this message is being forwarded to another MC.

Set to NULL. If not known or applicable
sm_length1IntegerLength in octets of the short_message user data.4.7.28
short_messageVar. 0-255Octet StringUp to 255 octets of short message user data.

The exact physical limit for short_message size may vary according to the underlying network

Note: this field is superceded by the message_payload TLV if specified. Ref.

Applications which need to send messages longer than 255 octets should use the message_payload TLV. In this case the sm_length field should be set to zero
Message Delivery Request TLVsVar.TLV4.3.3 deliver_sm_resp Syntax

Field NameSize octetsTypeDescriptionRef.
command_length4IntegerSet to overall length of PDU.4.7.4
command_status4IntegerIndicates outcome of deliver_sm request.4.7.6
sequence_number4IntegerSet to sequence number of original deliver_sm PDU.4.7.24
message_idVar. Max 65C-Octet StringThis field is unused and should be set to NULL4.7.14
Message Delivery Response TLVsVar.TLV4.3.4

SMPP Tools and Services

Services from Melrose Labs (e.g. Tyr SMS Gateway and SMPP SMS Gateway ) support SMPP v5 and the earlier versions, v3.3 and v3.4.

SMSC Simulator

Looking to test your SMS application or SMS-enabled application before connecting to a live SMS gateway or SMSC? SMSC Simulator enables you to test using SMPP v3.3, v3.4 and v5.
Read more about SMSC Simulator >

SMPP Clients

Send and receive SMS using an SMPP account and browser-based SMPP client.

* SMPP session between web browser and provider.

SMS Code Bench

SMS messaging code sample and development playground. Collection of editable and runnable code samples in a variety of languages for different SMS interactions.
SMS Code Bench >

Send SMS programmatically with SMPP

Send SMS programmatically with SMPP using Python, Java, Go, Perl, C++, C#, Node.js, Ruby and PHP.

SMPP Load Test

Perform an SMS load test using SMPP from your web browser and view the results in realtime. SMPP Load Test tool submits SMS messages using SMPP at the specified rate. Messages are sent to one or more mobile numbers in a range from a single source address or range of source addresses.
Use the online SMPP Load Test tool >

SMPP Analyser

The SMPP Analyser acts as an SMPP proxy, with the client application binding to the service and the service onward binding to the SMSC or SMS Gateway. Packet captures can be viewed in your browser or exported into Wireshark.
Use the online SMPP Analyser >

Message Hub

Message routing between applications (uses SMPP protocol). For use in IoT, chat applications, asyncronous notification in web applications, and other applications.
Message Hub documentation >


Find out more...

Please provide your name.
Please provide a valid company name.
Please type your message.
Please provide a valid email address.