Jio Platforms

TrueConnect (DLT) BASED SMPP FAQ

Version 2.6

2 | TrueConnect (DLT) BASED SMPP

COPYRIGHT INFORMATION

3 | TrueConnect (DLT) BASED SMPP

1. No part of this document may be copied, reproduced,
stored in any retrieval system, or transmitted in any form or
by any means, either electronically, mechanically, or
otherwise without prior written permission.

© Copyright Jio Platforms

All rights reserved

Jio Platforms,
Reliance Corporate Park Thane Belapur Road,
Ghansoli-400 701

TRADEMARKS

All the brand names and other products or services mentioned in this document are
identified by the trademarks or service marks of their respective owners.

DISCLAIMER

The information in this document is subject to change without notice and should not be
construed as commitment by Jio Platforms. Jio Platforms assumes no responsibility or
makes no warranties for any errors that may appear in this document and disclaims any
implied warranty of merchantability or fitness for a particular purpose.

4 | TrueConnect (DLT) BASED SMPP

Version History:
The Document Author is authorized to make the following types of changes to the
document without requiring that the document be re-approved:
a) Editorial, formatting, and spelling

b) Clarification

To request a change to this document, contact the Document Author or Owner. Changes to
this document are summarized in the following table in reverse chronological order (latest
version first)

Revision Date Created By Short Description

2.0 03-May-2021 Harshada Deore Initial Draft
Tejendra Singhadiya
2.1 18-May-2021 Sumeet Pol  Error Code 602 (PEID Inactive) removed
Risabh Sharma from Scrubbing Error list, replaced with
Error Code 601
 Eliminated Error Code 605, 610, 611,
612, 635, 636
2.2 27-May-2021 Sumeet Pol  Description’s provided for Bind &
Risabh Sharma Submit Errors
 Eliminated Error Code 604
2.3 21-Jul-2021 Sumeet Pol  Updated Error Code “600” to “609”
2.4 31-Aug-2021 Tejendra Singhadiya,  Replaced 652 error code to 21.
Parth Kashikar  Added JIO SMSC error codes.
 Added TON NPI info for JIO SMSC.
 Added consent related scrubbing error
codes.
2.5 04-Oct-2021 Tejendra Singhadiya,  Added Error Codes “671” and “672” for
Parth Kashikar submit loss
 Updated Allowed Sessions info. & NPI
TON for Jio SMSC
2.6 15-Dec-2021 Tejendra Singhadiya,  Added Error Codes “646” for
Parth Kashikar, unsupported Data Coding
Yuvraj Chavan  Added list of supported Data Coding
schemes.
2.7 20-Jan-2022 Sumeet Pol  Added Error code 673
 Added Error code 635
 Updated Error code 633

5 | TrueConnect (DLT) BASED SMPP

 Title Owner Location
TCCCPR 2018 Regulation TRAI https://trai.gov.in/notifications/press-release/trai-releases-
telecom-commercial-communication-customer-preference

6 | TrueConnect (DLT) BASED SMPP

Contents
Overview.................................................................................................................................. 8
Scrubbing Logic......................................................................................................................... 8
SMPP Specifications.................................................................................................................. 8
Connection............................................................................................................................... 9
Encoding Format....................................................................................................................... 9
Bind Operations........................................................................................................................ 9
Bind Duration ........................................................................................................................... 9
Additional Mandatory TLV ....................................................................................................... 10
Additional Optional TLV........................................................................................................... 10
Guidelines for Content Template Scrubbing:............................................................................. 11
Scrubbing Related Error Codes (PEID, Header/CLI, Template ID) –.............................................. 12
DLT is using two SMSCs ........................................................................................................... 14
1. COMVIVA SMSC Error Code (Permanent / Temporary) ................................................... 14
2. JIO SMSC Error Code (Permanent / Temporary) ............................................................. 21
Not Supported PDUs ............................................................................................................... 25
FAQs ...................................................................................................................................... 26

7 | TrueConnect (DLT) BASED SMPP

 Overview
This document provides guidance for using TrueConnect DLT based SMPP Platform for sending SMS
using SMPP Interface.

SMS Preference Scrubbing applicable to promotional messages

The SMPP (Short Message Peer-to-Peer) protocol 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). It is a
means by which applications can send SMS messages to mobile devices and receive SMS from
mobile devices.

Scrubbing Logic
Terms Definition and Remark

Transaction Check for Sender registration, header registration and template

Service Check for Sender registration, header registration and template

Implicit/Inferred

Service Explicit Check for Sender registration, header registration, check for consent
and template
If the consent scrub fails then preferences will be checked w.r.t Fully
Block.
If preference scrub passes (i.e. Customer is not on FULLY BLOCK)
then the message will be delivered. If both of these fail (i.e.
Customer is on FULLY BLOCK), message will not be delivered.

Promotional Check for Sender registration, header registration, check for consent
and template
If the consent scrub fails then preferences will be checked.
If preference scrub passes then the message will be delivered. If
both of these fails, message will not be delivered.

SMPP Specifications
SMPP 3.4: Short Message Peer to Peer Protocol Specification v3.4, 12-Oct-1999, Issue 1.2

8 | TrueConnect (DLT) BASED SMPP

 Connection
We recommended to create minimum of 8 session per account while binding.

SMPP Version 3.4

Bind Type Transmitter, Receiver and Transceiver
Allowed Bind Sessions Min.: 4
Max.: 8

On SMSC Max. up to 30 Session’s are

permitted. Ensure that all the Session’s are
equally distributed.

Encoding Format
Please ensure that you choose the correct data coding scheme as per the below

Message Type DCS

Normal Text Message – GSM 0
Long SMS – GSM 0
Normal Text Message - Latin 1 (ISO-8859-1) 3
Long SMS - Latin 1 (ISO-8859-1) 3
Unicode Messages 8
Flash Messages (Default encoding) 240
GSM Flash Messages 16
Unicode Flash Messages 24

Bind Operations
There are three ways to open a connection using SMPP. You can connect as:
 Transmitter (TX): Send short messages to SMSC and receive responses from SMSC.

 Receiver (RX): receive delivery receipts from the SMSC and return the corresponding
responses.

 Transceiver (TRX): send and receive messages to and from the SMSC over a single SMPP
session.

Preferred Mode TRX

Bind Duration
We recommend enquire link for every 90 seconds to keep the bind alive at the server end,
failing to do this may cause the bind getting disconnected.

TON & NPI Recommendations

Type TON NPI
Src_Addr Alphanumeric 5 - Alphanumeric 0 - Unknown
Blank/Null 0 - Unknown 0 - Unknown
Shortcode & Longcode 0-Unknown 2 -National 3- N/W 1 - ISDN(E164/E163) 0 - Unknown
specific
Dest_Addr National Format 2 - National 0 - Unknown 1 - ISDN(E164/E163) 0 - Unknown
International Format 1 - International 0 - Unknown 1 - ISDN(E164/E163) 0 - Unknown

9 | TrueConnect (DLT) BASED SMPP

 Additional Mandatory TLV
Mandatory TLV Tag value Decimal Tag value Hex
PE_ID 5120 1400
Template_ID 5121 1401

Additional Optional TLV

Mandatory TLV Tag value Decimal Tag value Hex
Telemarketer_ID (TM_ID) 5122 1402

Screenshot for passing TLV

If Image is not visible, please use WireShark for inspecting sample pcap file

10 | TrueConnect (DLT) BASED SMPP

 Guidelines for Content Template Scrubbing:

1. Case insensitive scrubbing.

E.g.:
Content Template: “WELCOME TO JIO.” Message: “Welcome to Jio.”

2. Ignoring space.
E.g.:
Content Template: “WELCOME TO JIO.” Message: “WELCOME TO JIO.”

3. Ignoring New Line

E.g.:
Content Template: “WELCOME TO JIO “ Message: “WELCOME\nTO \n JIO ”

4. Dynamic variable range is 0 to 30.

E.g.:
1. Content Template:” WELCOME TO JIO {#var#}” Message: “WELCOME TO JIO ”(Min-0)
2. Content Template:” WELCOME TO JIO {#var#}”
Message: “WELCOME TO JIO 123456789012345678901234567890”(Max-30)

5. List of Ignored Special Characters.

`£ $ ¥ è é ù ì ò Ç Ø ø Å å Δ Φ Γ Λ Ω Π Ψ Σ Θ Ξ € Æ æ ß É # ¤ % ¡ Ä Ö Ñ Ü § ¿ ä
ö ñü à_ ~`!@ #$% ^ &*() – - +={}[]| /:; "' <>, .? — “” ‘ ’ ½ ¾®
™`; \

Note: For all these scenarios message will get pass.

11 | TrueConnect (DLT) BASED SMPP

 Scrubbing Related Error Codes (PEID, Header/CLI, Template ID) –
These Errors would be shared as part of “deliver-sm” PDU, under Delivery Report –

Delivery Status – REJECTD

Error Code – xxx

Error
Sr. No. Status Description
Code
1. 601 ENTITY_INACTIVE Entity is inactive on Jio's platform
Entity is blacklisted on all
2. 603 ENTITY_BLACKLISTED
platforms
No record found with PEID as
3. 609 ENTITY_NOT_FOUND
primary key
602,
4. 604 – ENTITY_RESERVED Reserved for Entity
608
610 – Revered for Telemarketer
5. TELEMARKETER_RESERVED
619 validations
No record found with header (case
6. 620 HEADER_NOT_FOUND
sensitive) as primary key
7. 621 HEADER_INACTIVE Header is inactive on the platform
Header is blacklisted on all
8. 622 HEADER_BLACKLISTED
platforms
Principle Entity Id is not matched
9. 623 PEID_NOT_MATCHED_WITH_HEADER
with Header Id
624-
10. HEADER_RESERVED Reserved for Header
627
Header type is not matching with
11. 628 HEADER_AND_ACCO UNTTYPE_MISMATCH
account type
12. 629 HEADER_IN_FREEPOOL Header in free pool
No record found with Template Id
13. 630 TEMPLATE_NOT_FOUND
as primary key/no template found
Template is inactive on the
14. 631 TEMPLATE_INACTIVE
platform
Template is blacklisted on all
15. 632 TEMPLATE_BLACKLISTED
platforms
Template not matched for given
Template ID
16. 633 TEMPLATE_NOT_MATCHED
Or failed due to content violation
in static part
Header is not registered for the
17. 634 HEADER_NOT_REGISTERED_FOR_TEMPLATE
template
Template scrubbing failed due to
18. 635 TEMPLATE_FAILED_O N_DYNAMIC_PART constraints violation in dynamic
part
19. 646 UNSUPPORTED_DCS Data coding not supported
20. 647 TEMPLATE_NOT_REGISTERED_TO_ENTITY Template does not belong to PE
Promotional Template used on
21. 648 PROMOTIONAL_TEMPLATE_USED_ON_OTHERS_HEADER
other/transaction header
22. 649 INVALID_TEMPLATE_TYPE Invalid template type
Blocked in preferences with
23. 650 PREFERENCE_NOT_MATCHED
MSISDN as PK.
635-
24. TEMPLATE_RESERVED Reserved for Template
645
25. 651 INVALID_PROMO_TIME Block promo hours (9PM to 10AM)

12 | TrueConnect (DLT) BASED SMPP

 Error
Sr. No. Status Description
Code
SE category blocking on fully DND,
26. 21 SE_CATEGORY_BLOCK
if consent not available or expired
652-
27. PREFERENCE_RESERVED Reserved for Preference
659
Blocked in preference and consent
28. 660 CONSENT_NOT_FOUND
not found
Blocked in preference and consent
29. 661 CONSENT_EXPIRED
expired
662-
30. CONSENT_RESERVED Reserved for Consent
669
General error code in case of any
31. 670 SCRUBBING_FAILED
exceptions.
Failed to assemble pdu as all parts
32. 671 FAILED_TO_ASSEMBLE_PDUS
not received
Rejected as pdu with same udh
33. 672 UDH_HEADER_REUSED header is already being process on
TrueConnect
DLT failed to received
34. 673 SMSC_SUBMIT_TIMEOUT acknowledgment from SMSC for
submits.
674-
35. SCRUBBING_RESERVED Reserved for scrubbing
699
36. 698 TLV_PEID_NOT_FOUND TLV PEID missing/empty/null
37. 699 TLV_TMPID_NOT_FOUND TLV TMPID missing/empty/null

13 | TrueConnect (DLT) BASED SMPP

 DLT is using two SMSCs
1. COMVIVA SMSC
2. JIO SMSC

1. COMVIVA SMSC Error Code (Permanent / Temporary)

Please refer to below sheet & table for additional information on error code while delivery report.
Bind Errors
Sr. No. Error code that is sent in Command Status Description
SMPP bind-resp Name
1. 12 ESME_RINVMSGID Message ID is invalid
2. 13 ESME_RBINFFAIL Bind Failed
3. 14 ESME_RINVPASWD Invalid Password
4. 15 ESME_RINVSYSID Invalid System ID

Submit-Resp provided by TrueConnect

Sr. No. Error code that is sent in Command Status Description
SMPP deliver-sm PDU Name
(Decimal)
1. 0 ESME_ROK No Error

Submit-Resp Errors that would be provided as part of deliver-sm PDU

Error code that is sent in SMPP
Command Status
Sr. No. deliver-sm PDU (Decimal) Description
Name
Message length is
1. 1 ESME_RINVMSGLEN
invalid
Command length is
2. 2 ESME_RINVCMDLEN
invalid
3. 3 ESME_RINVCMDID Invalid Command ID
Incorrect BIND Status
4. 4 ESME_RINVBNDSTS
for given command
ESME Already in Bound
5. 5 ESME_RALYBND
State
6. 6 ESME_RINVPRTFLG Invalid Priority Flag
Invalid Registered
7. 7 ESME_RINVREGDLVFLG
Delivery Flag
8. 8 ESME_RSYSERR System Error
9. 10 ESME_RINVSRCADR Invalid Source Address
10. 11 ESME_RINVDSTADR Invalid Dest Addr
11. 17 ESME_RCANCELFAIL Cancel SM Failed
12. 19 ESME_RREPLACEFAIL Replace SM Failed
13. 20 ESME_RMSGQFUL Message Queue Full
14. 21 ESME_RINVSERTYP Invalid Service Type
Destination flag is
15. 64 ESME_RINVDESTFLAG
invalid (submit_multi)
Cannot Submit to
16. 68 ESME_RCNTSUBDL
Distribution List
Invalid esm_class field
17. 67 ESME_RINVESMCLASS
data
submit_sm or
18. 69 ESME_RSUBMITFAIL
submit_multi failed

14 | TrueConnect (DLT) BASED SMPP

 Error code that is sent in SMPP
Command Status
Sr. No. deliver-sm PDU (Decimal) Description
Name
Invalid Source address
19. 72 ESME_RINVSRCTON
TON
Invalid Source address
20. 73 ESME_RINVSRCNPI
NPI
Invalid Destination
21. 80 ESME_RINVDSTTON
address TON
Invalid Destination
22. 81 ESME_RINVDSTNPI
address NPI
Invalid system_type
23. 83 ESME_RINVSYSTYP
field
Throttling error; ESME
24. 88 ESME_RTHROTTLED has exceeded allowed
message limits.
Invalid Scheduled
25. 97 ESME_RINVSCHED
Delivery Time
Invalid message validity
26. 98 ESME_RINVEXPIRY
period (Expiry time).
Predefined Message
27. 99 ESME_RINVDFTMSGID
Invalid or Not Found
28. 103 ESME_RQUERYFAIL query_sm request failed
29. 255 ESME_RUNKNOWNERR Unknown Error
Error in the optional
30. 192 ESME_RINVOPTPARSTREAM
part of the PDU Body
Optional Parameter not
31. 193 ESME_ROPTPARNOTALLWD
allowed
Expected Optional
32. 195 ESME_RMISSINGOPTPARAM
Parameter missing.
Invalid number of
33. 51 ESME_RINVNUMDESTS
destinations
ESME not authorised to
34. 256 ESME_RSERTYPUNAUTH use specified
servicetype
ESME prohibited from
35. 257 ESME_RPROHIBITED using specified
operation
Specified servicetype is
36. 258 ESME_RSERTYPUNAVAIL
unavailable
Specified servicetype is
37. 259 ESME_RSERTYPDENIED
denied
Invalid data coding
38. 260 ESME_RINVDCS
scheme
Invalid source address
39. 261 ESME_RINVSRCADDRSUBUNIT
subunit
Invalid destination
40. 262 ESME_RINVDSTADDRSUBUNIT
address subunit
Broadcast Frequency
Interval is invalid.
41. 263 ESME_RINVBCASTFREQINT Specified value is either
invalid or not
supported.
Broadcast Alias Name is
42. 264 ESME_RINVBCASTALIAS_NAME invalid. Specified value
has an incorrect length

15 | TrueConnect (DLT) BASED SMPP

 Error code that is sent in SMPP
Command Status
Sr. No. deliver-sm PDU (Decimal) Description
Name
or contains
invalid/unsupported
characters
Broadcast Area Format
is invalid. Specified
43. 265 ESME_RINVBCASTAREAFMT
value violates protocol
or is unsupported.
Number of Broadcast
Areas is invalid.
44. 266 ESME_RINVNUMBCAST_AREAS Specified value violates
protocol or is
unsupported.
Broadcast Content Type
is invalid. Specified
45. 267 ESME_RINVBCASTCNTTYPE
value violates protocol
or is unsupported.
Broadcast Message
Class is invalid. Specified
46. 268 ESME_RINVBCASTMSGCLASS
value violates protocol
or is unsupported.
broadcast_sm operation
47. 269 ESME_RBCASTFAIL
failed
query_broadcast_sm
48. 270 ESME_RBCASTQUERYFAIL
operation failed
cancel_broadcast_sm
49. 271 ESME_RBCASTCANCELFAIL
operation failed.
Number of Repeated
Broadcasts is invalid.
50. 272 ESME_RINVBCAST_REP Specified value violates
protocol or is
unsupported.
Broadcast Service
Group is invalid.
51. 273 ESME_RINVBCASTSRVGRP Specified value violates
protocol or is
unsupported.
Broadcast Channel
Indicator is invalid.
52. 274 ESME_RINVBCASTCHANIND Specified value violates
protocol or is
unsupported.

SMSC Delivery Report Error Code for SMPP interface

Error code that is sent
Sr. No. in SMPP deliver-sm Error Description Error Type
PDU
1 0 Successfully delivered the message NO ERROR
2 60 Request timeout Temporary Error
3 105 SMPP - ESME Already in Bound State Permanent Error
4 106 SMPP - Invalid Priority Flag Permanent Error
5 107 SMPP - Invalid Registered Delivery Flag Permanent Error
6 108 SMPP - System Error Permanent Error

16 | TrueConnect (DLT) BASED SMPP

 Error code that is sent
Sr. No. in SMPP deliver-sm Error Description Error Type
PDU
7 201 Unknown Subscriber Temporary Error
8 202 Unknown Base Station Temporary Error
9 203 Unknown MSC Temporary Error
10 205 Unidentified Subscriber Temporary Error
11 206 Absent Subscriber for SM Temporary Error
12 207 Unknown Equipment Temporary Error
13 208 Roaming Not Allowed Temporary Error
14 209 Illegal Subscriber Temporary Error
15 210 Illegal SS Operation Temporary Error
16 211 SS Error Status Temporary Error
17 212 SS Not Available Temporary Error
18 213 SS Subscription Violation Temporary Error
19 214 SS Incompatible Temporary Error
20 215 Facility Not Supported Temporary Error
21 219 No Handover Number Available Temporary Error
22 220 SM Delivery Fail Permanent Error
23 221 Message List Full Temporary Error
24 222 Network System Failure Temporary Error
25 223 Data Missing Temporary Error
26 224 Unexpected Data Temporary Error
27 225 PW Registration Failure Temporary Error
28 226 Negative PW Check Temporary Error
29 227 No Roaming Number Available Temporary Error
30 228 Tracing Buffer Full Temporary Error
31 230 Not Allowed Temporary Error
32 231 ATI Not Allowed Temporary Error
33 232 No Group Call Number Available Temporary Error
34 233 Resource Limitation Temporary Error
35 234 Unauthorized Requesting Network Temporary Error
36 235 Unathorized LCS Client Temporary Error
37 236 Position Method Failure Temporary Error
38 247 Unknown Alphabet Temporary Error
39 248 USSD Busy Temporary Error
40 275 Error Gateway Temporary Error
41 300 Provider Error Duplicate Invoke ID Permanent Error
42 301 Provider Error Service Not Supported Permanent Error
43 302 Provider Error Mistyped Paramter Permanent Error
44 303 Provider Error Resource Limitation Permanent Error
45 304 Provider Error Initiating Release Permanent Error
46 305 Provider Error Unexpected Response Permanent Error
47 306 Provider Error Service Completion Failure Permanent Error
48 307 Provider No Response from Peer Permanent Error
49 308 Provider Error Invalid Response Permanent Error
50 400 MAP P Abort Temporary Error
51 401 Stack/Sig Error Map User specific Reason Permanent Error
52 402 Stack/Sig Error Map User Resource Limitation Permanent Error
53 403 Stack/Sig Error Map Resource Unavailable Permanent Error
Stack/Sig Error Map Application Procedure
54 404 Permanent Error
Cancellation
55 407 HLR/MSC Timeout Temporary Error
Stack/Sig Error Abnormal Event Detected by
56 414 Permanent Error
Peer

17 | TrueConnect (DLT) BASED SMPP

 Error code that is sent
Sr. No. in SMPP deliver-sm Error Description Error Type
PDU
57 415 Stack/Sig Response Rejected By Peer Permanent Error
58 416 Stack/Sig Abnormal Event Recieved From Peer Permanent Error
59 417 Sig Error Map Invalid Response from peer Permanent Error
60 418 Sig Error Map Dialogue Does not Exist Permanent Error
61 419 Sig Error Map Max evoke reached Temporary Error
62 420 Stack/Sig Invalid Origination Reference Permanent Error
63 421 Stack/Sig No Reson Temporary Error
64 422 Stack/Sig Remote Node Not Reachable Permanent Error
65 423 Stack/Sig Map Potential Version Incompatibility Permanent Error
66 424 Stack/Sig Secured Transport Not Possible Permanent Error
67 425 Stack/Sig Usr Transport Protection Not Adequate Permanent Error
68 428 Sig Error MAP Subsystem congested Temporary Error
69 429 Sig Error MAP Subsystem failure Temporary Error
70 430 Sig Error MAP Error in local processing CCIT92 Permanent Error
71 431 Sig Error MAP Re assembly failure Permanent Error
72 432 Sig Error MAP SCCP failure Permanent Error
73 433 Sig Error MAP HOP counter violation ITU Permanent Error
74 434 Sig Error MAP segmentation not supported Permanent Error
75 435 Sig Error MAP Segmentation failure Permanent Error
76 436 Stack Error - Notice indication/Pabort/Uabort Permanent Error
77 501 Sig Error Internal resource not available Permanent Error
78 502 Sig Error MAF create pdu failed Permanent Error
79 503 Sig Error SEncode function fails Permanent Error
80 504 Sig Error maf get pdu param for error info failed Permanent Error
81 507 Sig Error Internal Timeout Permanent Error
82 514 Sig Error Open Request failued from Maf to ccpu Permanent Error
83 602 Unknown Error Permanent Error
84 801 AS Send Fail Permanent Error
85 802 AS iError Resp Permanent Error
86 803 AS NO Response Permanent Error
87 864 As Subscriber Not Found Permanent Error
88 901 SMSC Not Connected Permanent Error
89 914 Queue Full Or Throttle Error Permanent Error
90 1001 SMPP - Message Length is invalid Permanent Error
91 1002 SMPP - Command Length is invalid Permanent Error
92 1003 SMPP - Invalid Command ID Permanent Error
93 1004 SMPP - Incorrect BIND Status Permanent Error
94 1011 SMPP - Cancel SM Failed Permanent Error
95 1013 SMPP - Replace SM Failed Permanent Error
96 1014 SMPP - Message Queue Full Permanent Error
97 1015 SMPP - Invalid Service Type Permanent Error
98 1033 SMPP - Invalid number of destinations Permanent Error
99 1034 SMPP - Invalid Distribution List name Permanent Error
100 1040 SMPP - Destination flag is invalid Permanent Error
101 1042 SMPP - Invalid submit with replace request Permanent Error
102 1043 SMPP - Invalid esm_class field data Permanent Error
103 1044 SMPP - Cannot Submit to Distribution List Permanent Error
104 1045 SMPP - submit_sm or submit_multi failed Permanent Error
105 1048 SMPP - Invalid Source address TON Permanent Error
106 1049 SMPP - Invalid Source address NPI Permanent Error
107 1050 SMPP - Invalid Destination address TON Permanent Error

18 | TrueConnect (DLT) BASED SMPP

 Error code that is sent
Sr. No. in SMPP deliver-sm Error Description Error Type
PDU
108 1051 SMPP - Invalid Destination address NPI Permanent Error
109 1053 SMPP - Invalid system_type field Permanent Error
110 1054 SMPP - Invalid replace_if_present flag Permanent Error
111 1055 SMPP - Invalid number of messages Permanent Error
112 1058 SMPP - Throttling error Permanent Error
113 1061 SMPP - Invalid Scheduled Delivery Time Permanent Error
114 1062 SMPP - Invalid message validity period Permanent Error
115 1063 SMPP - Predefined Message Invalid or Not Found Permanent Error
SMPP - ESME Receiver Temporary App Error
116 1064 Permanent Error
Code
SMPP - ESME Receiver Permanent App Error
117 1065 Permanent Error
code
SMPP - ESME Receiver Reject Message Error
118 1066 Permanent Error
code
119 1067 SMPP - query_sm request failed Permanent Error
120 1300 MAP_APPLICATION_CONTEXT_NOT_SUPPORTED Permanent Error
121 1304 MAP_REMOTE_NODE_NOT_REACHABLE Permanent Error
122 2100 Invalid Short Code Permanent Error
Destination Short Code Rejected with
123 2108 Permanent Error
International TON
124 2111 MO DBILL Failure Permanent Error
125 2112 MO DBILL Timeout Permanent Error
126 2113 MO DBILL Internal Error Permanent Error
127 2114 Account not Bound on SMSP Permanent Error
128 2115 Account not Bound on MSDP Permanent Error
129 2166 Source MSISDN Barring Permanent Error
130 2172 Alpha Numeric Sender Id Barring Permanent Error
131 100a SMPP - Invalid Source Address Permanent Error
132 100b SMPP - Invalid Dest Addr Permanent Error
133 100c SMPP - Message ID is invalid Permanent Error
134 100d SMPP - Bind Failed Permanent Error
135 100e SMPP - Invalid Password Permanent Error
136 100f SMPP - Invalid System ID Permanent Error
137 103c SMPP - Account not connected Permanent Error
138 103d SMPP - Account Based List Full Permanent Error
SMPP - Error in the optional part of the PDU
139 10c0 Permanent Error
body
140 10c1 SMPP - Optional Parameter not allowed Permanent Error
141 10c2 SMPP - Invalid Parameter Length Permanent Error
142 10c3 SMPP - Expected Optional Parameter missing Permanent Error
143 10c4 SMPP - Invalid Optional Parameter Value Permanent Error
144 10fe SMPP - Delivery Failure Permanent Error
145 10ff SMPP - Unknown Error Permanent Error
146 20a Bearer Service Not Supported Temporary Error
147 20b Tele Service Not Provisioned Temporary Error
148 20c Error Equipment Temporary Error
149 20d Call Barred Temporary Error
150 20e Error Forward Violation Temporary Error
151 20f Error CUG Reject Temporary Error
152 21a Subsequent Handover Failure Temporary Error
153 21b Absent Subscriber for MT/SRI Temporary Error
154 21c Incompatible Terminal Temporary Error

19 | TrueConnect (DLT) BASED SMPP

 Error code that is sent
Sr. No. in SMPP deliver-sm Error Description Error Type
PDU
155 21c7 Anti Spoofing Permanent Error
156 21d Short Term Denial Temporary Error
157 21e Long Term Denial Temporary Error
158 21f Subscriber Busy for MT Temporary Error
159 22c Number of PW attempts Violation Temporary Error
160 22d Busy Subscriber Temporary Error
161 22e No Subscriber Reply Temporary Error
162 22f Forwarding Failed Temporary Error
163 23a Unknown or Unreachable LCS Client Permanent Error
164 40a Stack/Sig Error Map Provider Malfunction Permanent Error
Stack/Sig Error Map Unrecognised Transaction
165 40b Permanent Error
ID
166 40c Stack/Sig Error Dialog Resource Limitation Permanent Error
167 40d Stack/Sig Error Map Maintenance Activity Permanent Error
168 40e Stack/Sig Error Map Version Incompatibility Permanent Error
169 40f Stack/Sig Error Abnormal Map Dialogue Permanent Error
170 41a Sig Error Map guard Timer Expired Permanent Error
171 41b Sig Error Map SPCAUSE mask Permanent Error
172 41c Sig Error MAP No Translation Basd Address Permanent Error
173 41d Sig Error MAP No Translation specific address Permanent Error
174 41e Stack/Sig Application Context Not Supported Permanent Error
175 41f Stack/Sig Dlg Invalid Destination Reference Permanent Error
176 42a Sig Error MAP Un Equipped User Permanent Error
177 42b Sig Error MAP Network Failure Permanent Error
178 42c Sig Error MAP Network Conjestion Permanent Error
179 42d Sig Error MAP un Qualified Permanent Error
180 42e Sig Error MAP HOP Counter violaion ANS92 Permanent Error
181 42f Sig Error MAP Error in message transport CCIT92 Permanent Error
182 2175 Destination Cell ID Barring Permanent Error
183 216a Destination IMSI Barring Permanent Error
184 216b Destination MSISDN Barring Permanent Error
185 216e Destination ShortCode Barring Permanent Error
186 216d Destination VMSC Barring Permanent Error
187 2174 Source Cell ID Barring Permanent Error
188 2165 Source IMSI Barring Permanent Error
189 2169 Source ShortCode Barring Permanent Error
190 2168 Source VMSC Barring Permanent Error
191 2173 System ID Barring Permanent Error
192 160 Timeout at SRI/MT Temporary Error

20 | TrueConnect (DLT) BASED SMPP

 2. JIO SMSC Error Code (Permanent / Temporary)
Please refer to below sheet & table for additional information on error code while delivery report

Bind Errors
Sr. No. Error code that is sent in Command Status Description
SMPP bind-resp Name
1. 8 ESME_RSYSERR System Error
2. 13 ESME_RBINFFAIL Bind Failed
3. 14 ESME_RINVPASWD Invalid Password
4. 15 ESME_RINVSYSID Invalid System ID

Submit-Resp provided by TrueConnect

Sr. No. Error code that is sent in Command Status Description
SMPP deliver-sm PDU Name
(Decimal)
1. 0 ESME_ROK No Error

Submit-Resp Errors that would be provided as part of deliver-sm PDU

Error code that is sent in SMPP
Command Status
Sr. No. deliver-sm PDU (Decimal) Description
Name
Message Length is
1. 1 ESME_RINVMSGLEN
invalid
Command Length is
2. 2 ESME_RINVCMDLEN
invalid
3. 3 ESME_RINVCMDID Invalid Command ID
Incorrect BIND Status
4. 4 ESME_RINVBNDSTS
for given command
ESME Already in Bound
5. 5 ESME_RALYBND
State
Invalid Registered
6. 7 ESME_RINVREGDLVFLG
Delivery Flag
7. 8 ESME_RSYSERR System Error
8. 10 ESME_RINVSRCADR Invalid Source Address
9. 11 ESME_RINVDSTADR Invalid Dest Addr
Invalid esm_class field
10. 67 ESME_RINVESMCLASS
data
Invalid Source address
11. 72 ESME_RINVSRCTON
TON
Invalid Source address
12. 73 ESME_RINVSRCNPI
NPI
Invalid Destination
13. 80 ESME_RINVDSTTON
address TON
Invalid Destination
14. 81 ESME_RINVDSTNPI
address NPI
15. 88 ESME_RTHROTTLED Throttling
Invalid Scheduled
16. 97 ESME_RINVSCHED
Delivery Time
Invalid message validity
17. 98 ESME_RINVEXPIRY
period (Expiry time)
Error in the optional
18. 192 ESME_RINVOPTPARSTREAM
part of the PDU Body.

21 | TrueConnect (DLT) BASED SMPP

SMSC Delivery Report Error Code for SMPP interface
JIO SMSC error codes are formed by 3 digit positive integer value. Following are the cases when JIO
SMSC will send negative delivery report and their error code value series:
a. MAP Message Failures - 0xx
b. Message Acknowledgment Failures (RP-error) - 1xx
c. Other Failures - 2xx
d. SIP Failures (For MNP and Message Delivery) - 3xx-6xx
e. Diameter Failures (For SH) - 7xx-9xx

1.MAP Message Failures

DR error code for MAP message failure shall be formed by using series 0xx. A configurable MAP to
DR error code map is used for sending different error code in case of different MAP message failure.
If no mapping is found for MAP error code to DR error code then a default error code 099 shall be
send in the DR error code field. This MAP to DR error code map can be configure using EMS from tab
“IPSMGW_MAP_To_DR_Code” and from CLI using command “addToa2pmapToDrErrorCodeMap”.
In this case delivery state shall be either STATE_REJECTED if message fail with permanent error code
or retry and store & forward feature is FASLE for submitting ESME, or STATE_EXPIRED if validity
period of message got expired.

MAP Error Delivery Receipt Error Code Status

Unknown Subscriber 001 Rejected
Unidentified Subscriber 005 Expired
AbsentSubscriberSM 006 Expired
Illegal Subscriber 009 Rejected
Tele-Service not provisioned 011 Rejected
Illegal Equipment 012 Rejected
Call Barred 013 Rejected
Facility Not Supported 021 Rejected
AbsentSubscriber 027 Expired
SubscriberBusyForMT 031 Expired
SMDeliveryFail 032 Expired
MessageListFull 033 Expired
NetworkSystemFailure 034 Expired
DataMissing 035 Expired
UnexpectedData 036 Expired
GlobalFailure 097 Expired
Timeout 098 Expired
Default error code 099 Expired

2.Message Acknowledgment Failures

DR error code for message acknowledgement failures shall be formed by using series 1xx. A
configurable RP to DR error code map is used for sending different error code in case of different rp -

22 | TrueConnect (DLT) BASED SMPP

error. If no mapping is found for RP error code to DR error code then a default error code 199 shall
be send in the DR error code field. This RP to DR error code map can be configure using EMS from
tab “IPSMGW_RP_To_DR_Code” and from CLI using command “addToa2prpToDrErrorCodeMap”.
In this case delivery state shall be STATE_UNDELIVERABLE.

RP-Error Name Delivery Receipt Error Code Status

RP-ACK not received (Error 702) 102 Undeliverable
Protocol error, unspecified 111 Undeliverable
Memory capacity exceed 122 Undeliverable
Invalid short message transfer reference value 181 Undeliverable
Semantically incorrect message 195 Undeliverable
Invalid mandatory information 196 Undeliverable
Message type non-existent or not implemented 197 Undeliverable
Message not compatible with short message
198
protocol state Undeliverable
Default error code 199 Undeliverable

For e.g. if message failed with RP error code 22 and message not going to try in MAP then A2P-
IPSMGW will send its corresponding Delivery Receipt error code value as 122. RP error codes can
also be retrieve from CDRs.

3.Other Failures
DR error code for other failures shall be formed using series 2xx. In these cases following scenarios
can occur:
a. for M2M user if trigger UDR is false or if all SH peers are down then A2P-IPSMGW will send DR
with delivery state as STATE_REJECTED and error code as 202.
b. for M2M user if the sender address is not allowed to send the message (M2M-Blocking) then
A2P-IPSMGW will send DR with delivery state as STATE_REJECTED and error code as 203.
c. if user’s PLMN is blocked then A2P-IPSMGW will send DR with delivery state as
STATE_REJECTED and DR error code as 205.
d. if user’s Cell-Id is blocked then A2P-IPSMGW will send DR with delivery state as
STATE_REJECTED and DR error code as 206.

Other Error Delivery Receipt Error Code Status

M2M-User with No sh-UDR trigger 202 Rejected
M2M-Blocking 203 Rejected
PLMN Blocking 205 Rejected
Cell-Id Blocking 206 Rejected
4.SIP Failures
DR error code for MNP failures and message delivery failures shall be formed by using series 3xx-
6xx. A configurable SIP to DR error code map is used for sending different error code in case of
different MNP failure and message delivery failure. If no mapping is found for SIP error code to DR
error code then a default error code 699 shall be send in the DR error code field. This SIP to DR error
code map can be configure using EMS from tab “IPSMGW_SIP_To_DR_Code” and from CLI using
command “addToa2psipToDrErrorCodeMap”. In case of MNP failure delivery state shall be

23 | TrueConnect (DLT) BASED SMPP

STATE_UNKNOWN and in case of message delivery failure delivery state shall be
STATE_UNDELIVERABLE.

SIP Error Delivery Receipt Error Code Status

Moved Temporarily 302 Undeliverable
Unauthorized 401 Undeliverable
Forbidden 403 Undeliverable
Not Found 404 Unknown
Method Not Allowed 405 Undeliverable
Request Timeout 408 Undeliverable
Unsupported Media Type 415 Undeliverable
Address Incomplete 484 Undeliverable
Busy Here 486 Undeliverable
Server Internal Error 500 Undeliverable
Version Not Supported 505 Undeliverable
Busy Everywhere 600 Undeliverable
Decline 603 Undeliverable
Does Not Exist Anywhere 604 Undeliverable
Default error code 699 Undeliverable

For e.g. if message failed with SIP error code 486 and message not going to try in MAP then A2P-
IPSMGW will send its corresponding Delivery Receipt error code value as 486. SIP error codes can
also be retrieve from CDRs.

5.Diameter Failures
DR error code for Diameter (SH interface) failures shall be formed by using series 7xx-9xx. A
configurable Diameter to DR error code map is used for sending different error code in case of
different Sh failure. If no mapping is found for Diameter error code to DR error code then a default
error code 999 shall be send in the DR error code field. This Diameter to DR error code map can be
configure using EMS from tab “IPSMGW_DIA_To_DR_Code” and from CLI using command
“addToa2pdiaToDrErrorCodeMap”. In this case delivery state shall be STATE_UNDELIVERABLE.

Diameter Error Name Error Code DR Error Code Status

3xxx-Protocol Error 3000-3020 700-720 Undeliverable
4xxx-Transient Failure 4000-4020 800-820 Undeliverable
5xxx-Permanent Failure 5000-5031 900-931 Undeliverable
Default error code 999 Undeliverable

For e.g. if message failed with Diameter error code 5012 and message not going to try in MAP then
A2P-IPSMGW will send its corresponding Delivery Receipt error code value as 912. Since Diameter
error codes are of 4 digit and Delivery Receipt error codes are of 3 digit so we have provided
mappings like 3xxx mapped with 7xx, 4xxx mapped with 8xx and 5xxx mapped with 9xx. Diameter
error codes can also be retrieve from CDRs.

24 | TrueConnect (DLT) BASED SMPP

 Not Supported PDUs
1. Submit Multi
2. Outbind

25 | TrueConnect (DLT) BASED SMPP

 FAQs

Sr. No. Question Solution

1. Not Able to receive delivery Receipt Ensure there are minimum of 8 session per
For Transactional Messages account active.
2. Not able to send special character Please provide data coding in pdu as per
requirement & if data coding is not provide
default will be assumed as per SMPP
standards

3. Received SMPP Error 650 Submit_sm rejected due as per user’s

preferences
4. Not Able to receive Delivery Receipt Delivery receipts are available for
for Promotional Messages transactional messages
5. Received SMPP Error 651 Invalid Promo Time (Temporary until the full
24 hr promotional window is declared by
TRAI)
6. Maximum how many characters we 30 Characters
can use in one variable parameter?
7. Special characters will consider one One Character
character or two characters?
8. In variable parameters can we use Yes
space & new lines?
9. The variable parameter can be Yes
registered in the beginning of the
content?
10. If the content is registered with the No. Content template scrubbing ignores
newline the same format we have to control characters (\n, \r, \r\n etc.) and
use? spaces.
11. If the variable character is Yes
alphanumeric will it accept?
12. How to handle the long URL which is Maximum Character Limit for variable
more than 30 characters? template is 30.
So if your character length is x then minimum
variables required is ceil(x/30).
For e.g.:
1.variable length = 30 then number of
variables = ceil(30/30)=1
2.variable length = 31 then number of
variables = ceil(31/30)=2
3.variable length = 29then number of
variables = ceil(29/30)=1
4.variable length = 150 then number of
variables = ceil(150/30)=5

13. The content should match 100% No.

with the DLT registered content? Static Template: Control characters and
spaces are ignored while scrubbing rest it
should match with DLT registered content.

26 | TrueConnect (DLT) BASED SMPP

 Variable Template: Allowed characters are
accepted in the place of variable (#var#).
Control characters and spaces are ignored
while scrubbing rest it should match with DLT
registered content.

27 | TrueConnect (DLT) BASED SMPP