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.
SMS successfully delivered
Telecom services have not been commissioned
SMS is prohibited
MS does not support SMS
MS receiving error
Facility not supported.
Handset memory full
SMSC system failure
Gateway mobile switching error
Mobile handset switched off
SMS undelivered due to roaming limitation
Subscriber is busy.
Resource cannot be used at GMSC level
Submission error or invalid input data
The template does not match the template registered on the DLT platform
The senderID used along with the template ID do not match as per the registration in DLT portal
The message content sent was not found in the DLT platform as a registered template.
The variable content sent exceeds the allowed limit
The message template pushed has been blacklisted at the DLT platform level.
The message template sent is in inactive status at the DLT platform level.
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.
Failed due to network errors
Invalid template id has been processed.
Hex – 0x00000400
Dec – 1024
Series has been temporary / permanently blocked.
Hex – 0x00000401
Dec – 1025
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
Hex – 0x00000481
Dec – 1153
Hex – 0x00000500
Dec – 1280
Not an Opt - In data
Hex – 0x00000555
Dec – 1365
Time out for promotional message.
Hex – 0x00000777
Dec – 1911
Hex – 0x00000407
Dec – 1031
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.
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.
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.).
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 [email protected]