PE Parameters To become Handed On SMPP Protocol

DLT – Specification for SMPP Interface

Version 1.one

Alter Record
This table demonstrates a file of sizeable improvements on the doc.
Model Day Description of Alter
one.0 26.08.2020 First SMPP document published with more TLV

parameters

one.one 12.10.2020 Added DLT mistake codes included with description

2 | P a g e
Table of Contents:

1. Introduction ...............................................................................................................................three
2. Assumptions .............................................................................................................................3
3. Connection Configuration......................................................................................................3
four. Hosts............................................................................................................................................3
5. Encoding Formats....................................................................................................................4
6. Bind Functions........................................................................................................................4
7. Session States ..........................................................................................................................4
eight. Bind Parameters.......................................................................................................................5
nine. Bind lifetime...............................................................................................................................5
ten. Submit_sm Parameters..........................................................................................................five
eleven. SMPP TLV parameters:...........................................................................................................six
twelve. SMPP Commands ....................................................................................................................6
13. Command Point out........................................................................................................................seven
14. Distributing Messages .............................................................................................................eight
14.1 Publishing Concept................................................................................................................eight
14.2 Post Responses ..................................................................................................................eight
14.three Message ID................................................................................................................................8
fifteen. Supply Receipts .....................................................................................................................nine
16. Concept Status ........................................................................................................................nine
seventeen. Terminology ............................................................................................................................ten
eighteen. Transactional Mistake Codes(NACK Faults in Decimal structure).....................................11
19. DLT Mistake codes .....................................................................................................................twelve
20. Reference Paperwork ..........................................................................................................12

three | P a g e
one. Introduction
According to TRAI TCCCPR Regulation 2018, Energetic participation from Organization/
Corporations involved in the Professional Conversation is necessary in an effort to suppress
spam. To meet the compliance specifications, some modifications have already been
included within the A2P SMS setup with respect to supplemental parameters in SMPP
interface.

The SMPP V3.four specifications are getting used with applicable supplemental TLV
parameters needed to satisfy the TRAI suggestion for DLT eco system.

2. Assumptions
It can be assumed that viewers of the document have a essential idea of SMPP
Protocol requirements v3.4

three. Relationship Configuration

SMPP Edition 3.four
Bind Sort Transmitter, Receiver or Transceiver
Company Style, auth TON and auth NPI All values are overlooked and will be blank
Maximum permitted sessions Account unique configuration

4. Hosts
You'll be able to link present SMPP account by adding more parameters outlined in issue
range eleven.

4 | P a g e
five. Encoding Formats
Be sure to be certain that you end up picking the right info coding plan According to the under
Concept Variety DCS UDH
Typical Text Concept – GSM 0 0
Very long SMS – GSM 0 1
Ordinary Text Information - Latin one (ISO-8859-1) three 0
Extensive SMS - Latin one (ISO-8859-1) 3 1
Unicode Messages 8 0
Flash Messages sixteen 0

six. Bind Operations
You can find 3 ways to open a connection working with SMPP. You could join as:
ï‚· Transmitter: Mail brief messages to SMSC and obtain responses from
SMSC.
ï‚· Receiver: get delivery receipts from your SMSC and return the
corresponding responses.
ï‚· Transceiver: mail and receive messages to and with the SMSC more than a
single SMPP session.

seven. Session States
Your relationship to our server across an SMPP url may be in a single of five states:
ï‚· Open up: linked and bind pending
ï‚· BOUND_TX: connected and requested to bind as a Transmitter
ï‚· BOUND_RX: related and requested to bind being a Receiver
ï‚· BOUND_TRX: related and asked for to bind for a Transceiver
ï‚· CLOSED: unbound and disconnected

five | P a g e
eight. Bind Parameters
The syntax for initiating a bind_transmitter, bind_receiver or bind_transceiver
instance takes advantage of the next parameters:
ï‚· system_id: identifies the consumer requesting to bind (username)
ï‚· password: password to allow access
ï‚· system_type: identifies the method sort (dismissed, set to blank)
ï‚· interface_version: suggests SMPP Model supported by user
ï‚· addr_ton: identifies person variety of number (overlooked, established to blank)
ï‚· addr_npi: numbering plan indicator for person (disregarded, set to blank)
ï‚· address_range: The consumer handle (overlooked, set to blank)

9. Bind lifetime
We advocate enquire hyperlink For each minute (below 60 seconds) to maintain the
bind alive for the server stop, failing to do this may perhaps result in the bind get disconnected.
ten. Submit_SM Parameters
The parameters demanded for your SUBMIT_SM request (used to mail an SMS) are:
ï‚· service_type: indicates SMS application assistance
ï‚· source_addr_ton: type of variety for resource address
ï‚· source_addr_npi: numbering prepare indicator for supply handle
ï‚· source_addr: supply handle
ï‚· dest_addr_ton: type of quantity for destination
ï‚· dest_addr_npi: numbering plan indicator for location
ï‚· destination_addr: vacation spot address on the short concept
ï‚· esm_class: concept mode and kind
ï‚· protocol_id: protocol identifier (community certain)
ï‚· priority_flag: sets the priority on the concept (This can be overlooked)
ï‚· schedule_delivery_time: established to NULL for fast shipping and delivery (This can be
dismissed)
ï‚· validity_period: validity period of concept
ï‚· registered_delivery: indicator to signify if an SMSC delivery receipt or
acknowledgment is needed

six | P a g e
ï‚· replace_if_present_flag: flag indicating if submitted concept should
swap an existing concept (This is often dismissed)
ï‚· data_coding: defines the encoding scheme of your SMS concept
ï‚· sm_default_msg_id: indicates shorter information to ship from a predefined
listing of messages saved on SMSC (This really is dismissed)
ï‚· sm_length: duration in octets in the short_message person information
ï‚· short_message: around 254 octets of brief concept consumer information.
ï‚· user_message_reference: person assigned reference quantity (That is
disregarded)

11. SMPP TLV parameters:
For sending messages in Submit_SM making use of SMPP , there'll be Two necessary parameters
introduced in SMPP PDU.
These new tags are launched within the optional parameter listing. Even so, the TLV values will
be checked by our DLT scrubber :

Optional Parameter Tag price in
Hex

Tag Worth in
Decimal
PE_ID 1400 5120
Template_ID 1401 5121

twelve. SMPP Commands
The SMS Gateway supports the subsequent SMPP instructions:
1. check here Supported consumer-to-server instructions
ï‚· BIND_TRASMITTER ï‚· SUMIT_SM
ï‚· BIND_RECEIVER ï‚· ENQUERY_LINK
ï‚· BIND_TRANSCEIVER ï‚· DELIVERY_SM_RESP
ï‚· UNBIND
2. Unsupported client-to-server instructions
ï‚· SUBMIT_MULTI ï‚· REPLACE_SM
ï‚· DATA_SM ï‚· ALERT_NOTIFICATION
ï‚· QUERY_SM

seven | P a g e
3. Supported server-to-shopper commands
ï‚· BIND_TRANSMITTER_RESP ï‚· SUBMIT_SM_RESP
ï‚· BIND_RECEIVER_RESP ï‚· UNBIND_RESP
ï‚· BIND_TRANSCEIVER_RESP ï‚· ENQUIRE_LINK_RESP
ï‚· GENERIC_NACK ï‚· DELIVER_SM

thirteen. Command Condition
SMPP supports the next commands by way of the next SMPP session states:

Command Demanded state
bind_transmitter Open up
bind_transmitter_resp OPEN
bind_receiver OPEN
bind_receiver_resp OPEN
bind_transceiver Open up
bind_transceiver_resp OPEN
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

8 | P a g e
fourteen. Submitting Messages
14.1 Submitting Concept
Originators, Referred get more info to as source_addr. For billed message the originator has to be
the short code if It is far from established to the shorter code platform won't take the read more information.

Destination - (often called dest_addr). Spot deal with sorts will not be
supported. It's possible you'll established these to something, but they will always be interpreted as 1,one.
Location addresses (MSISDN) must normally be submitted in international format
without foremost 00 or + e.g. (917751123456). MSISDN duration Has to be 12 digits in
submission packet

Data & Unicode (UTF16) message body varieties - set data_coding appropriately as
for each the appropriate vendor specification for the type of Facts or Unicode message you’re
sending, and the type of handset you’re sending it to.
Character Encoding - By default messages need to be submitted utilizing the GSM
encoding character established.
Message Expiry (validity_period) – Is supported by System unless There's
restriction from the supplier. This attribute is set at account amount and most
validity is restricted to six hours
14.two Submit Responses
A positive response to your submit will contain an mistake code of zero plus a non-null
message reference. The concept reference will probably be offered in decimal. A detrimental
reaction will almost certainly consist of seller particular mistake code or SMPP v3.4 mistake
codes and a null concept reference.
14.three Message ID
At present the concept reference delivered is 19 digits, it may adjust in long term
(Highest forty).

9 | P a g e
15. Supply Receipts
SMPP delivery receipts take the following structure:
id:IIIIIIIIII sub:SSS dlvrd:DDD submit date:YYMMDDhhmmss performed date:YYMMDDhhmmss
stat:DDDDDDD err:E Text .........

Wherever:
ï‚· id: the information ID allocated on the information because of the server
ï‚· sub: the number of short messages originally submitted (this is ignored)
ï‚· dlvrd: the quantity of shorter messages sent (This really is ignored)
ï‚· post day: the day and time at which the quick concept was submitted
ï‚· performed date: the day and time at which the shorter information reached its
closing point out
ï‚· stat: the ultimate status from the message. Be sure to see part Information Standing for
more details.
ï‚· err: in which suitable this could hold a network unique error code or an
SMSC error code
ï‚· textual content: the very first 20 people from the brief concept (this is disregarded)
Note: To help enable/disable seconds parameter in “submit date” & “performed day” please
Call guidance crew
16. Message Position
The shipping report position suggests whether the SMS message was sent
successfully from the SMSC. In case the website SMS was not effectively delivered, then the
shipping and delivery report will give a explanation in the form of an [error code].

SMPP information states as well as their meanings are shown below to your advantage:

CODE DESCRIPTION
DELIVRD Message delivered to place
FAILED Message is undelivered
EXPIRED Information validity period of time has expired
REJECTD Concept is in turned down condition

10 | P a g e
17. Terminology

ï‚· SMPP: Limited Concept Peer to see Protocol
ï‚· ACK: Acknowledgement
ï‚· DLR: Supply Report
ï‚· DND: Tend not to Disturb
ï‚· ESME: External Limited Message Entity
ï‚· MSISDN: Cell Subscriber Built-in Products and services Digital Community: the cell
range in Global format.
ï‚· MSC: Cell Switching Centre: the destination network products that gets
an SMS (through ahead-SM operation) in a very location cell community.
ï‚· HLR: Property Location Sign-up: the spot network gear that returns
status and routing specifics of an MSISDN for the SMSC (by way of SRI-SM
operation).
ï‚· SMSC: Short Message Support Centre: the gear belonging to CLX or a single
of its carriers that transmits SMS to the destination community by way of SS7.
ï‚· SS7: Signalling Procedure 7: the transport protocol that interconnects international GSM
networks.
ï‚· MNP: Cellular Range Portability: the process of a subscriber shifting from one
cellular network to another but retaining the identical MSISDN.
ï‚· IMSI: Worldwide Cellular Subscriber Id: a novel identification number
which identifies the location region, actual network, and community subscriber
ID.
ï‚· Subscriber: The mobile user who has a SIM card.

11 | P a g e
eighteen. Transactional Error Codes (NACK Mistakes in Decimal structure)
That can assist you discover what could possibly be triggering a problem with your SMPP transaction,
Here's a listing of error codes with a small description:
Error Code Description
0 No mistake
three Invalid command ID
4 Invalid bind standing for given command
5 ESME currently in sure condition
ten Invalid resource tackle
twelve Message ID is invalid
13 Bind unsuccessful
fourteen Invalid password
15 Invalid technique ID
twenty Information queue whole
21 Invalid program kind
97 Invalid scheduled supply time
ninety eight Invalid information shipping and delivery period of time

twelve | P a here g e
19. DLT Error codes
We is going to be giving top quality and trusted reporting as well as DLT error codes in
scrubbing system According to new TLV parameters. When your message is just not scrubbed
efficiently and fails, an mistake code are going to be returned during the deliver_sm which has a
explanation.

Error codes will be returned within the supply report (in case shipping and delivery studies are
enabled with the user) as:

stat: err:

The value from the Standing as well as Mistake Code would be According to the under desk: In
long run, the extra mistake code will likely be shared with descriptions.

Mistake Identify Description Mistake Code
BLOCKED_BY_DLT Message blocked by DLT

Scrubbing

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

DLT_SCRUBBING_TIMEOUT Timeout though executing

DLT Scrubbing 4107/4001/5000/5001

SENDER_BLOCKED_BY_DLT Blocked by DLT since

sender did not go scrubbing 4108/5201/5202/5203/5204/5205

TEMPLATE_ERROR Information Template will not be
Matching/Register

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

20. Reference Documents

ï‚· SMPP Protocol Specification v3.4

Leave a Reply

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