Model one.one
Adjust History
This table demonstrates a history of substantial modifications on the document.
Variation Day Description of Improve
1.0 26.08.2020 Original SMPP doc released with more TLV
parameters
one.one 12.10.2020 More DLT error codes added with description
2 | P a g e
Desk of Contents:
1. Introduction ...............................................................................................................................three
two. Assumptions .............................................................................................................................3
3. Connection Configuration......................................................................................................3
four. Hosts............................................................................................................................................three
five. Encoding Formats....................................................................................................................4
six. Bind Functions........................................................................................................................4
seven. Session States ..........................................................................................................................four
8. Bind Parameters.......................................................................................................................five
9. Bind life span...............................................................................................................................five
ten. Submit_sm Parameters..........................................................................................................5
eleven. SMPP TLV parameters:...........................................................................................................six
twelve. SMPP Commands ....................................................................................................................6
13. Command State........................................................................................................................7
14. Submitting Messages .............................................................................................................eight
fourteen.1 Publishing Information................................................................................................................8
fourteen.2 Submit Responses ..................................................................................................................eight
14.three Message ID................................................................................................................................eight
15. Delivery Receipts .....................................................................................................................9
16. Information Position ........................................................................................................................9
seventeen. Terminology ............................................................................................................................ten
eighteen. Transactional Mistake Codes(NACK Errors in Decimal format).....................................eleven
19. DLT Error codes .....................................................................................................................twelve
20. Reference Paperwork ..........................................................................................................12
3 | P a g e
one. Introduction
According to TRAI TCCCPR Regulation 2018, active participation from Small business/
Providers associated with the Business Communication is necessary so that you can suppress
spam. To satisfy the compliance demands, some changes have been
included within the A2P SMS setup with respect to added parameters in SMPP
interface.
The SMPP V3.four specifications are being used with applicable further TLV
parameters required to meet the TRAI suggestion for DLT eco program.
2. Assumptions
It can be assumed that readers of this doc Have got a simple knowledge of SMPP
Protocol specs v3.4
3. Connection Configuration
SMPP Model three.four
Bind Variety Transmitter, Receiver or Transceiver
Support Variety, auth TON and auth NPI All values are overlooked and may be blank
Utmost authorized classes Account specific configuration
4. Hosts
You'll be able to join current SMPP account by including more parameters talked about in issue
range eleven.
4 | P a g e
five. Encoding Formats
Be sure to be certain that you select the right facts coding scheme According to the beneath
Message Sort DCS UDH
Normal Text Concept – GSM 0 0
Very long SMS – GSM 0 one
Typical Text Message - Latin 1 (ISO-8859-1) three 0
Long SMS - Latin 1 (ISO-8859-1) 3 1
Unicode Messages 8 0
Flash Messages sixteen 0
six. Bind Functions
There are actually 3 ways to open a relationship employing SMPP. It is possible to link as:
ï‚· Transmitter: Deliver brief messages to SMSC and receive responses from
SMSC.
ï‚· Receiver: acquire shipping and delivery receipts from your SMSC and return the
corresponding responses.
ï‚· Transceiver: ship and obtain messages to and through the SMSC around a
solitary SMPP session.
7. Session States
Your relationship to our server throughout an SMPP connection is usually in a single of five states:
ï‚· Open up: related and bind pending
ï‚· BOUND_TX: linked and asked for to bind as being a Transmitter
ï‚· BOUND_RX: connected and requested to bind as a Receiver
ï‚· BOUND_TRX: linked and asked for to bind as being a Transceiver
ï‚· Shut: unbound and disconnected
5 | P a g e
8. Bind Parameters
The syntax for initiating a bind_transmitter, bind_receiver or bind_transceiver
occasion works by using the next parameters:
ï‚· system_id: identifies the person requesting to bind (username)
ï‚· password: password to allow accessibility
ï‚· system_type: identifies the procedure sort (disregarded, established to blank)
ï‚· interface_version: signifies SMPP Edition supported by consumer
ï‚· addr_ton: identifies consumer style of number (ignored, set to blank)
ï‚· addr_npi: numbering approach indicator for person (overlooked, established to blank)
ï‚· address_range: The person tackle (overlooked, set to blank)
nine. Bind life span
We recommend enquire url For each minute (below 60 seconds) to help keep the
bind alive for the server close, failing to do this may possibly result in the bind get disconnected.
10. Submit_SM Parameters
The parameters necessary for the SUBMIT_SM request (utilized to ship an SMS) are:
ï‚· service_type: suggests SMS software provider
ï‚· source_addr_ton: type of number for source address
ï‚· source_addr_npi: numbering plan indicator for resource handle
ï‚· source_addr: resource handle
ï‚· dest_addr_ton: style of amount for destination
ï‚· dest_addr_npi: numbering prepare indicator for destination
ï‚· destination_addr: destination tackle of the brief concept
ï‚· esm_class: concept manner and sort
ï‚· protocol_id: protocol identifier (community specific)
ï‚· priority_flag: sets the precedence from the concept (This can be dismissed)
ï‚· schedule_delivery_time: set to NULL for instant shipping and delivery (This is often
ignored)
ï‚· validity_period: validity duration of concept
ï‚· registered_delivery: indicator to signify if an SMSC supply receipt or
acknowledgment is required
6 | P a g e
ï‚· replace_if_present_flag: flag indicating if submitted information need to
exchange an existing information (That is ignored)
ï‚· data_coding: defines the encoding scheme of the SMS message
ï‚· sm_default_msg_id: signifies limited information to send from a predefined
list of messages stored on SMSC (That is overlooked)
ï‚· sm_length: size in octets from the short_message person information
ï‚· short_message: up to 254 octets of quick concept user knowledge.
ï‚· user_message_reference: person assigned reference number (That is
disregarded)
eleven. SMPP TLV parameters:
For sending messages in Submit_SM utilizing SMPP , there will be Two necessary parameters
introduced in SMPP PDU.
These new tags are launched inside the optional parameter record. However, the TLV values will
be checked by our DLT scrubber :
Optional Parameter Tag worth in
Hex
Tag Value in
Decimal
PE_ID 1400 5120
Template_ID 1401 5121
12. SMPP Commands
The SMS Gateway supports the following SMPP commands:
1. Supported customer-to-server commands
ï‚· BIND_TRASMITTER ï‚· SUMIT_SM
ï‚· BIND_RECEIVER ï‚· ENQUERY_LINK
ï‚· BIND_TRANSCEIVER ï‚· DELIVERY_SM_RESP
ï‚· UNBIND
2. Unsupported customer-to-server commands
ï‚· SUBMIT_MULTI ï‚· REPLACE_SM
ï‚· DATA_SM ï‚· ALERT_NOTIFICATION
ï‚· QUERY_SM
7 | P a g e
three. Supported server-to-client instructions
ï‚· BIND_TRANSMITTER_RESP ï‚· SUBMIT_SM_RESP
ï‚· BIND_RECEIVER_RESP ï‚· UNBIND_RESP
ï‚· BIND_TRANSCEIVER_RESP ï‚· ENQUIRE_LINK_RESP
ï‚· GENERIC_NACK ï‚· DELIVER_SM
13. Command Point out
SMPP supports the following commands by means of the next SMPP session states:
Command Demanded condition
bind_transmitter Open up
bind_transmitter_resp OPEN
bind_receiver OPEN
bind_receiver_resp Open up
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
14. Distributing Messages
fourteen.1 Submitting Concept
Originators, Called source_addr. For billed message the originator needs to be
the quick code if It is far from established to your shorter code System won't accept the information.
Destination - (known as dest_addr). Desired destination handle types aren't
supported. You could possibly set these to everything, However they will almost always be interpreted as 1,one.
Place addresses (MSISDN) must often be submitted in Global structure
with Free Bulk SMS on Signup out foremost 00 or + e.g. (917751123456). MSISDN size Should be 12 digits in
submission packet
Details & Unicode (UTF16) message human body forms - set data_coding appropriately as
per the appropriate vendor specification for the sort of Information or Unicode concept you’re
sending, and the type of handset you’re sending it to.
Character Encoding - By default messages have to be submitted utilizing the GSM
encoding character established.
Message Expiry (validity_period) – Is supported by platform Until There's
restriction with the provider. This characteristic is ready at account degree and utmost
validity is limited to six hrs
14.2 Submit Responses
A constructive response to your post will consist of an error code of zero and a non-null
concept reference. The message reference might be provided in decimal. A adverse
response will probably consist of vendor certain mistake code or SMPP v3.four mistake
codes along with a null message reference.
fourteen.3 Information ID
At present the concept reference supplied is 19 digits, it may well transform in long run
(Maximum 40).
9 | P a g e
fifteen. Supply Receipts
SMPP supply receipts just take the subsequent format:
id:IIIIIIIIII sub:SSS dlvrd:DDD post day:YYMMDDhhmmss done date:YYMMDDhhmmss
stat:DDDDDDD err:E Textual content .........
The place:
ï‚· id: the concept ID allocated for the concept with the server
ï‚· sub: the volume of quick messages at first submitted (this is disregarded)
ï‚· dlvrd: the amount of small messages sent (this is dismissed)
ï‚· post date: the date and time at which the shorter information was submitted
ï‚· accomplished date: the date and time at which the shorter concept attained its
ultimate state
ï‚· stat: the final position of the information. Make sure you see area Information read more Status for
more info.
ï‚· err: where by suitable this will hold a community unique error code or an
SMSC mistake code
ï‚· text: the very first twenty characters in the short concept (this is ignored)
Notice: To permit help/disable seconds parameter in “submit day†& “done day†you should
Make contact with guidance workforce
sixteen. Concept Position
The supply report standing indicates whether the SMS information was sent
productively by the SMSC. If the SMS was not properly sent, then the
supply report will provide a cause in the form of the [mistake code].
SMPP information states as well as their meanings are shown right here to your advantage:
CODE DESCRIPTION
DELIVRD Message delivered to place
FAILED Concept is undelivered
EXPIRED Information validity period has expired
REJECTD Concept is in rejected condition
ten | P a g e
17. Terminology
ï‚· SMPP: Small Message Peer to look Protocol
ï‚· ACK: Acknowledgement
ï‚· DLR: Shipping and delivery Report
ï‚· DND: Usually do not Disturb
ï‚· ESME: Exterior Shorter Information Entity
ï‚· MSISDN: Mobile Subscriber Built-in Expert services Digital Network: the mobile
quantity in Worldwide format.
ï‚· MSC: Mobile Switching Centre: the vacation spot network products that gets
an SMS (by using forward-SM operation) in a very location cellular community.
ï‚· HLR: Residence Locale Sign-up: the destination network devices that returns
status and routing information regarding an MSISDN towards the SMSC (through SRI-SM
Procedure).
ï‚· SMSC: Quick Information Service Centre: the tools belonging to CLX or one
of its carriers that transmits SMS towards the spot network by means of SS7.
ï‚· SS7: Signalling Process seven: the transportation protocol that interconnects world wide GSM
networks.
ï‚· MNP: Cellular Number Portability: the process of a subscriber moving from 1
mobile community to another but retaining precisely the same MSISDN.
ï‚· IMSI: Global Mobile Subscriber Id: a singular identification amount
which identifies the location nation, real network, and community subscriber
ID.
ï‚· Subscriber: The cellular consumer who has a SIM card.
eleven | P a g e
eighteen. Transactional Mistake Codes (NACK Problems in Decimal format)
That will help you discover what may be causing a difficulty with your SMPP transaction,
here is a listing of mistake codes with a small description:
Mistake Code Description
0 No error
three Invalid command ID
4 Invalid bind status for supplied command
5 ESME currently in bound condition
ten more info Invalid resource handle
12 Message ID is invalid
13 Bind failed
14 Invalid password
15 Invalid technique ID
twenty Information queue total
21 Invalid procedure variety
ninety seven Invalid scheduled delivery time
ninety eight Invalid information shipping and delivery interval
12 | P a g e
19. DLT Mistake codes
We is going to be offering top quality and dependable reporting coupled with DLT error codes in
scrubbing system According to new TLV parameters. In case your concept is not scrubbed
productively and fails, an mistake code will be returned while in the deliver_sm with a
cause.
Mistake codes might be returned from the shipping here report (in the event that delivery reviews are
enabled with the consumer) as:
stat:
The value from the Status and the Mistake Code could well be According to the under table: In
long term, the additional mistake code will likely be shared with descriptions.
Mistake Title Description Error Code
BLOCKED_BY_DLT Information blocked by DLT
Scrubbing
4106/5101/5102/5103/5104/5105/fifty one
06/5107/5108
DLT_SCRUBBING_TIMEOUT Timeout though accomplishing
DLT Scrubbing 4107/4001/5000/5001
SENDER_BLOCKED_BY_DLT Blocked by DLT because
sender failed to go scrubbing 4108/5201/5202/5203/5204/5205
TEMPLATE_ERROR Content Template is not really
Matching/Sign up
5301/5302/5303/5304/5304/5305/53
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.four