PE Parameters Being Passed On SMPP Protocol

DLT – Specification for SMPP Interface

Model one.1

Adjust History
This table reveals a file of sizeable changes to the document.
Version Day Description of Improve
one.0 26.08.2020 Preliminary SMPP document released with added TLV

parameters

1.one 12.10.2020 Further DLT error codes added with description

2 | P a g e
Desk of Contents:

1. Introduction ...............................................................................................................................3
2. Assumptions .............................................................................................................................three
three. Link Configuration......................................................................................................3
four. Hosts............................................................................................................................................three
5. Encoding Formats....................................................................................................................4
six. Bind Operations........................................................................................................................4
7. Session States ..........................................................................................................................4
8. Bind Parameters.......................................................................................................................five
9. Bind lifetime...............................................................................................................................5
ten. Submit_sm Parameters..........................................................................................................five
eleven. SMPP TLV parameters:...........................................................................................................6
twelve. SMPP Commands ....................................................................................................................six
13. Command Point out........................................................................................................................seven
14. Submitting Messages .............................................................................................................8
14.one Submitting Message................................................................................................................eight
fourteen.two Submit Responses ..................................................................................................................eight
fourteen.3 Message ID................................................................................................................................eight
fifteen. Supply Receipts .....................................................................................................................nine
16. Information Position ........................................................................................................................9
17. Terminology ............................................................................................................................ten
18. Transactional Error Codes(NACK Errors in Decimal structure).....................................eleven
19. DLT Mistake codes .....................................................................................................................12
twenty. Reference Documents ..........................................................................................................twelve

3 | P a g e
one. Introduction
As per TRAI TCCCPR Regulation 2018, Lively participation from Company/
Businesses associated with the Professional Conversation is essential so as to suppress
spam. To fulfill the compliance specifications, some alterations are
integrated from the A2P SMS setup with respect to additional parameters in SMPP
interface.

The SMPP V3.four requirements are being used with relevant added TLV
parameters required to meet the TRAI advice for DLT eco technique.

2. Assumptions
It is actually assumed that readers of this doc Use a standard knowledge of SMPP
Protocol specifications v3.4

three. Link Configuration

SMPP Version 3.four
Bind Variety Transmitter, Receiver or Transceiver
Support Type, auth TON and auth NPI All values are overlooked and can be blank
Utmost allowed classes Account certain configuration

four. Hosts
You could join present SMPP account by incorporating added parameters mentioned in stage
range eleven.

four | P a g e
five. Encoding Formats
You should make sure you end up picking the proper facts coding scheme According to the down below
Concept Kind DCS UDH
Regular Textual content Message – GSM 0 0
Very long SMS – GSM 0 1
Typical Textual content Concept - Latin one (ISO-8859-1) three 0
Extensive SMS - Latin 1 (ISO-8859-1) 3 1
Unicode Messages eight 0
Flash Messages 16 0

six. Bind Operations
There are 3 ways to open up a connection applying SMPP. You can hook up as:
ï‚· Transmitter: Deliver quick messages to SMSC and receive responses from
SMSC.
ï‚· Receiver: get supply receipts within the SMSC and return the
corresponding responses.
ï‚· Transceiver: deliver and get messages to and through the SMSC around a
one SMPP session.

7. Session States
Your relationship to our server throughout an SMPP website link can be in a single of five states:
ï‚· Open up: related and bind pending
ï‚· BOUND_TX: linked and asked for to bind as a Transmitter
ï‚· BOUND_RX: connected and asked for to bind as a Receiver
ï‚· BOUND_TRX: related and asked for to bind as a Transceiver
ï‚· Shut: unbound and disconnected

five | P a g e
8. Bind Parameters
The syntax for initiating a bind_transmitter, bind_receiver or bind_transceiver
occasion utilizes the subsequent parameters:
ï‚· system_id: identifies the person requesting to bind (username)
ï‚· password: password to permit obtain
ï‚· system_type: identifies the system sort (dismissed, established to blank)
ï‚· interface_version: signifies SMPP version supported by person
ï‚· addr_ton: identifies user style of variety (dismissed, set to blank)
ï‚· addr_npi: numbering strategy indicator for user (ignored, established to blank)
ï‚· address_range: The person address (overlooked, set to blank)

nine. Bind life span
We endorse enquire link For each moment (fewer than sixty seconds) to keep the
bind alive with the server finish, failing to do this may well result in the bind get disconnected.
10. Submit_SM Parameters
The parameters demanded for that SUBMIT_SM request (accustomed to ship an SMS) are:
ï‚· service_type: suggests SMS application provider
ï‚· source_addr_ton: kind of variety for supply tackle
ï‚· source_addr_npi: numbering program indicator for supply deal with
ï‚· source_addr: source tackle
ï‚· dest_addr_ton: form of range for spot
ï‚· dest_addr_npi: numbering strategy indicator for desired destination
ï‚· destination_addr: vacation spot address of your limited information
ï‚· esm_class: concept mode and sort
ï‚· protocol_id: protocol identifier (network particular)
ï‚· priority_flag: sets the precedence on the message (This can be dismissed)
ï‚· schedule_delivery_time: established to NULL for speedy delivery (This is certainly
overlooked)
ï‚· validity_period: validity period of concept
ï‚· registered_delivery: indicator to signify if an SMSC supply receipt or
acknowledgment is required

six | P a g e
ï‚· replace_if_present_flag: flag indicating if submitted concept ought to
substitute an present concept (This really is dismissed)
ï‚· data_coding: defines the encoding plan of your SMS message
ï‚· sm_default_msg_id: signifies quick concept to ship from the predefined
list of messages stored on SMSC (This is certainly dismissed)
ï‚· sm_length: size in octets on the short_message consumer data
ï‚· short_message: nearly 254 octets of quick concept person info.
ï‚· user_message_reference: consumer assigned reference quantity (This is often
dismissed)

11. SMPP TLV parameters:
For sending messages in Submit_SM utilizing SMPP , there'll be Two mandatory parameters
introduced in SMPP PDU.
These new tags are launched during the optional parameter record. On the other hand, the TLV values will
be checked by our DLT scrubber :

Optional Parameter Tag price in
Hex

Tag Value in
Decimal
PE_ID 1400 5120
Template_ID 1401 5121

12. SMPP Commands
The SMS Gateway supports the website following SMPP instructions:
1. Supported customer-to-server commands
ï‚· BIND_TRASMITTER ï‚· SUMIT_SM
ï‚· BIND_RECEIVER ï‚· ENQUERY_LINK
ï‚· BIND_TRANSCEIVER ï‚· DELIVERY_SM_RESP
ï‚· UNBIND
two. Unsupported shopper-to-server commands
ï‚· SUBMIT_MULTI ï‚· REPLACE_SM
ï‚· DATA_SM ï‚· ALERT_NOTIFICATION
ï‚· QUERY_SM

7 | P a g e
3. Supported server-to-consumer instructions
ï‚· BIND_TRANSMITTER_RESP ï‚· SUBMIT_SM_RESP
ï‚· BIND_RECEIVER_RESP ï‚· UNBIND_RESP
ï‚· BIND_TRANSCEIVER_RESP ï‚· ENQUIRE_LINK_RESP
ï‚· GENERIC_NACK ï‚· DELIVER_SM

13. Command State
SMPP supports the following instructions through the subsequent SMPP session states:

Command Expected point out
bind_transmitter Open up
bind_transmitter_resp Open up
bind_receiver OPEN
bind_receiver_resp OPEN
bind_transceiver OPEN
bind_transceiver_resp Open up
Unbind

BOUND_TX, BOUND_RX,
BOUND_TRX

unbind_resp

BOUND_TX, BOUND_RX,
BOUND_TRX

submit_sm BOUND_TX, BOUND_TRX
submit_sm_resp BOUND_TX, BOUND_TRX
deliver_sm BOUND_RX, BOUND_TRX
deliver_sm_resp BOUND_RX, BOUND_TRX
enquire_link

BOUND_TX, BOUND_RX,
BOUND_TRX

enquire_link_resp

BOUND_TX, BOUND_RX,
BOUND_TRX

generic_nack

BOUND_TX, BOUND_RX,
BOUND_TRX

eight | P a g e
fourteen. Submitting Messages
14.1 Publishing Information
Originators, Called source_addr. For billed information the originator must be
the quick code if it is not established into the quick code System will not accept the message.

Vacation spot - (called dest_addr). Destination deal with styles are usually not
supported. You might set these to anything, However they will almost always be interpreted as one,one.
Spot addresses (MSISDN) should really constantly be submitted in Intercontinental structure
without the need of top 00 or + e.g. (917751123456). MSISDN length Must be twelve digits in
submission packet

Information & Unicode (UTF16) information body types - established data_coding properly as
per the applicable seller specification for the kind of Data or Unicode information you’re
sending, and the type of handset you’re sending it to.
Character Encoding - By default messages has to be submitted utilizing the GSM
encoding character established.
Message Expiry (validity_period) – Is supported by System Until You can find
restriction with the supplier. This element is about at account stage and maximum
validity is restricted to 6 hrs
14.2 Post Responses
A constructive reaction to the post will consist of an mistake code of zero and also a non-null
concept reference. The concept reference will probably be provided in decimal. A adverse
response will most certainly have seller distinct error code or SMPP v3.4 mistake
codes plus a null message reference.
fourteen.3 Information ID
At this time the concept reference provided is 19 digits, it may improve in potential
(Most forty).

9 | P a g e
15. Supply Receipts
SMPP supply receipts just take the subsequent format:
id:IIIIIIIIII sub:SSS dlvrd:DDD submit date:YYMMDDhhmmss performed day:YYMMDDhhmmss
stat:DDDDDDD err:E Text .........

Where by:
ï‚· id: the message ID allotted to the information with the server
ï‚· sub: the amount of quick messages initially submitted (This is often overlooked)
ï‚· dlvrd: the amount of shorter messages sent (That is overlooked)
ï‚· post day: the day and time at which the quick information was submitted
ï‚· carried out day: the day and time at which the small information achieved its
final point out
ï‚· stat: the ultimate status of the concept. Make sure you see part Message Status for
more details.
ï‚· err: in which proper this could hold a network particular error code or an
SMSC mistake code
ï‚· textual content: the primary twenty characters on the shorter message (This is often ignored)
Be aware: To empower enable/disable seconds parameter in “post date” & “completed day” remember to
contact help crew
16. Concept Position
The shipping and delivery report standing implies if the SMS message click here was sent
productively via the SMSC. If your SMS wasn't properly sent, then the
supply report will provide a explanation in the shape of an [mistake code].

SMPP information states more info as well as their meanings are outlined right here to your ease:

CODE DESCRIPTION
DELIVRD Concept sent to desired destination
Unsuccessful Message is undelivered
EXPIRED Information validity interval has expired
REJECTD Information is in turned down point out

10 | P a g e
17. Terminology

ï‚· SMPP: Small Information Peer to look Protocol
ï‚· ACK: Acknowledgement
ï‚· DLR: Shipping and delivery Report
ï‚· DND: Tend not to Disturb
ï‚· ESME: External Limited Information Entity
ï‚· MSISDN: Mobile Subscriber Integrated Products and services Digital Network: the cell
number in international structure.
ï‚· MSC: Cellular Switching Centre: the spot community machines that gets
an SMS (through ahead-SM operation) in a desired destination cell community.
ï‚· HLR: House Location Sign-up: the location community gear that returns
standing and routing details about an MSISDN to the SMSC (by using SRI-SM
Procedure).
ï‚· SMSC: Shorter Message Service Centre: the devices belonging to CLX or 1
of its carriers that transmits SMS for the destination network by way of SS7.
ï‚· SS7: Signalling Process seven: the transport protocol that interconnects international GSM
networks.
ï‚· MNP: Cellular Quantity Portability: the process of a subscriber shifting from just one
mobile community to another but retaining the identical MSISDN.
ï‚· IMSI: Intercontinental Mobile Subscriber Identity: a novel identification number
which identifies the location place, genuine network, and network subscriber
ID.
ï‚· Subscriber: The cell person that has a SIM card.

eleven | P a g e
18. Transactional Error Codes (NACK Glitches in Decimal structure)
That may help you discover what may very well be creating an issue with all your SMPP transaction,
Here's a summary of error codes with a little description:
Error Code Description
0 No mistake
3 Invalid command ID
four Invalid bind position for provided command
five ESME currently in sure condition
10 Invalid resource handle
12 Information ID is invalid
thirteen Bind failed
fourteen Invalid password
fifteen Invalid process ID
20 Concept queue full
21 Invalid method form
97 Invalid scheduled shipping and delivery time
98 Invalid message shipping and delivery period

twelve | P a g e
19. DLT Error codes
We will probably be providing high quality and reliable reporting coupled with DLT error codes in
scrubbing mechanism as per new TLV parameters. Should website your information is just not scrubbed
properly and fails, an error code will likely be returned inside the deliver_sm with a
explanation.

Mistake codes could well be returned during the supply report (in the event that shipping and delivery reports are
enabled because of the consumer) as:

stat: err:

The value in the Status and the Error Code could well be as per the under table: In
long term, the extra error code can even be shared with descriptions.

Mistake Identify Description Mistake Code
BLOCKED_BY_DLT Concept blocked by DLT

Scrubbing

4106/5101/5102/5103/5104/5105/51
06/5107/5108

DLT_SCRUBBING_TIMEOUT Timeout although carrying out

DLT Scrubbing 4107/4001/5000/5001

SENDER_BLOCKED_BY_DLT Blocked by DLT mainly because

sender failed to pass scrubbing 4108/5201/5202/5203/5204/5205

TEMPLATE_ERROR Articles Template will not be
Matching/Sign up

5301/5302/5303/5304/5304/5305/fifty three
06/5307/5401/5402/5403/5404/5405
/5406/5407
ENTITY_ID_ERROR Entity not matching 7001/7002/7003

twenty. Reference Documents

ï‚· SMPP Protocol Specification v3.4

Leave a Reply

Your email address will not be published. Required fields are marked *