SMPP error codes

Our mobile phones sometimes inform us that a text message hasn’t been delivered and it will retry later. It can be frustrating, but now imagine the problem for an enterprise sending hundreds, thousands or millions of messages to their customers. A frustration now becomes a significant business challenge.

The following lists the error messages generated by the Local Mail SMPP. These error codes are included in both intermediate and final delivery notifications. For further information about these error codes and vocabulary, please refer to the GSM protocol specification.

Status

Description

Error Code

DELIVRD

SMS successfully delivered

000

INVALID-SUB

Unknown subscriber

001

INVALID-SUB

Illegal subscriber

001

ABSENT-SUB

Telecom services have not been commissioned

003

HANDSET-ERR

Illegal equipment

004

BARRED

SMS is prohibited

005

HANDSET-ERR

MS does not support SMS

006

HANDSET-ERR

MS receiving error

007

NET-ERR

Facility not supported.

008

MEMEXEC

Handset memory full

009

ABSENT-SUB

Absent subscriber

010

FAILED

SMSC system failure

011

NET-ERR

Gateway mobile switching error

012

MOB-OFF

Mobile handset switched off

013

FAILED

SMS undelivered due to roaming limitation

014

INVALID-SUB

Unidentified subscriber

015

HANDSET-BUSY

Subscriber is busy.

016

NET-ERR

Resource cannot be used at GMSC level

017

SERIES-BLK

Series blocked

018

NET-ERR

Submission error or invalid input data

019

BARRED

CUG reject

020

EXPIRED

SMS timeout

021

TL-NT-MTCHD

The template does not match the template registered on the DLT platform

023

SDR-TL-MSMAT

The senderID used along with the template ID do not match as per the registration in DLT portal

024

TL-NT-FOUND

The message content sent was not found in the DLT platform as a registered template.

025

TL-LMT-EXCED

The variable content sent exceeds the allowed limit

026

TL-BLKLST

The message template pushed has been blacklisted at the DLT platform level.

027

TL-INACTIVE

The message template sent is in inactive status at the DLT platform level.

028

PRFT-NT-MTCH

Preference not matched. This error code is received for Service Explicit content only., when the end user is registered under DND. This is completely based on the DND preference selected by the end user.

03

UNDELIV

Failed due to network errors

-

TL-ID-INVLD

Invalid template id has been processed.

-

Hex – 0x00000400

Dec – 1024

Series has been temporary / permanently blocked.

-

Hex – 0x00000401

Dec – 1025

Credit exhausted.

-

Hex – 0x00000404

Dec – 1028

Invalid destination number [ number not in proper format, correct format is 919999999999 without + and with 91 followed by the 10 digit number]

-

Hex – 0x00000405

Dec – 1029

ESME client error

-

Hex – 0x00000444

Dec – 1092

Message rejected as sender id not allotted for ESME

-

Hex – 0x00000454

Dec – 1108

Text template does not match

-

Hex – 0x00000455

Dec – 1109

Sender ID not found

-

Hex – 0x00000453

Dec – 1107

Template not found.

-

Hex – 0x00000450

Dec – 1104

Black-listed number.

-

Hex – 0x00000481

Dec – 1153

DND number.

-

Hex – 0x00000500

Dec – 1280

Not an Opt - In data

-

Hex – 0x00000555

Dec – 1365

Time out for promotional message.

-

Hex – 0x00000777

Dec – 1911

Duplicate Termination

-

Hex – 0x00000407

Dec – 1031

Spam Text

-

Content Restrictions

Many countries enforce different types of content restrictions on network operators. For example, in India, companies must register their Content and Consent Templates on the DLT. Japan does not allow you to add URLs in the message body.

Time restriction on promotional SMS

SMS campaigns are one of the best ways to promote your products. However, there are time restrictions enforced by various countries.

For example, in India, if you run a campaign outside the permitted hours of 9:00 PM to 9:00 AM then, the SMS campaign shows as failed or message undelivered.

Other reasons for SMS message Failure

Below are some of the other reasons:

  • Exception Time Out

  • Message Inbox memory is full on your mobile device (Lack of space in the receiver's Mobile internal memory for new messages).

  • The number is out of reach (not reachable or out of coverage area).

  • Handset failure(The receiver handset is damaged or is not working properly).

  • Network failure (The carrier network is facing some technical difficulties and messages are just not able to be delivered. (Downtime caused by network problems, Security failure, Hardware failure, etc.).

Need More Help?

If you need any further Help During your Integration or questions related to technical know-how, you can reach out to our support team at support@localmail.io

Last updated