SMPP SMS delivery receipts and error codes
Follow
Mara Wallace
The table below lists all possible SMPP error codes. Please note you may see these errors in the submit-sm response as well as the SMPP delivery report. However, when sending over SMPP, full visibility into the status of messages is only possible when a delivery receipt (DLR) is requested. The initial submit_sm response received is only the acknowledgment that Bandwidth’s Short Message Service Center (SMSC) has received the message. Therefore, the delivery report indicates the most accurate status of outbound messages.
Note: With rare exceptions, error codes 0 and 902 generally mean the message was successful. The rest of the error codes mean the message has failed.
| Error Code | Description | Explanation of Error (for information purposes only) | Client/ Service Error | Reported By |
|
0 |
delivered |
The message was delivered to the intended carrier or handset. |
||
|
1 |
service-not-allowed |
This is a general error that the service you are attempting to use is not allowed; you may have inaccurate permissions or formatting, or may not be enabled to use that service. |
Client Error |
Bandwidth Reported |
|
100 |
temporary-app-error |
An application within the Bandwidth service is experiencing a temporary error that is preventing the message from being processed |
Service Error |
Bandwidth Reported |
|
101 |
temporary-app-shutdown |
App going down. Message not received. The sender should send these messages later or to other hosts. |
Service Error |
Bandwidth Reported |
|
106 |
impossible-to-route |
Impossible to route / Attempt to deliver through retries has failed and you will need to reattempt these messages later. |
Service Error |
Bandwidth Reported |
|
111 |
temporary-app-connection-closed |
Received messaged for connection which is already closed - reopen connection and retry messages. |
Service Error |
Bandwidth Reported |
|
201 |
temporary-rout-error-retries-exceeded |
Bandwidth service expired the message after attempts to deliver through retries failed. |
Service Error |
Bandwidth Reported |
|
211 |
temporary-app-error-app-busy |
Bandwidth service application is temporarily busy so it cannot receive messages at this time |
Service Error |
Bandwidth Reported |
|
220 |
temporary-store-error |
Message not received. Cannot save the message to store. |
Service Error |
Bandwidth Reported |
|
231 |
discarded-concatenation-timeout |
Bandwidth did not receive all parts of the message. Message cannot be sent. |
Service Error |
Bandwidth Reported |
|
242 |
discarded-cannot-handle-udh-now |
Bandwidth service failed the message due to an error with the user data header (udh). This could be because total parts in UDH do not match received before, duplicate message part |
Service Error |
Bandwidth Reported |
|
301 |
malformed-invalid-encoding |
The message contains invalid characters that are not supported. Bandwidth cannot re-encode messages for the destination. |
Client Error |
Bandwidth Reported |
|
302 |
malformed-invalid-from-number |
The From number associated with the message is a number not routable to a carrier or valid in the industry (Ex: a 9-digit number). |
Client Error |
Bandwidth Reported |
|
303 |
malformed-invalid-to-number |
The To number associated with the message is a number not routable to a carrier or valid in the industry (Ex: a 9-digit number). |
Client Error |
Bandwidth Reported |
|
304 |
malformed-invalid-udh |
Invalid concatenation User Data Header (udh), Bandwidth cannot process the message. |
Client Error |
Bandwidth Reported |
|
305 |
malformed-invalid-udh |
Malformed UDH length indicator: udh length greater than message length, Bandwidth cannot process the message. |
Client Error |
Bandwidth Reported |
|
306 |
malformed-invalid-dlr-flag |
Bandwidth cannot process the request for a delivery receipt (DLR) as the flag is not set properly. In case of ESME: registered delivery flag not in range [0, 1]. In case of SMSC: registered delivery flag not 0. |
Client Error |
Bandwidth Reported |
|
350 |
malformed-for-destination |
The message passed validation on the receive stage but failed on send. This is likely because the destination number (To) is an invalid number. |
Client Error |
Bandwidth Reported |
|
352 |
too-large-for-dst |
The message size is too large for the destination carrier to support. |
Client Error |
Bandwidth Reported |
|
401 |
rejected-routing-error |
The message is unable to be routed within Bandwidth particularly when the source and destination are the same number. The destination or To number is mis-provisioned or there is a configuration with the message that is causing a situation where a message is being sent repeatedly between the same numbers. |
Client Error |
Bandwidth Reported |
|
402 |
fail-with-code |
data_fail_with_code attribute set in source TN profile. |
Client Error |
Bandwidth Reported |
|
403 |
rejected-forbidden-from-number |
Messaging on this From number is forbidden most commonly because the number does not belong to BW or the account. Other reasons include: the TN is not enabled in the Bandwidth App, the account associated with this number is not enabled for this type of messaging, the TN is disconnected, or it is an invalid number (i.e., 11111111111). |
Client Error |
Bandwidth Reported |
|
405 |
rejected-unallocated-from-number |
The From telephone number is considered unallocated when the number does not exist in our database as an active number or the number is not enabled for messaging. |
Client Error |
Bandwidth Reported |
|
406 |
rejected-unallocated-to-number |
The To number associated with this message, while a valid North American number, is not yet assigned to a carrier and the message cannot be sent downstream. |
Client Error |
Bandwidth Reported |
|
431 |
rejected-forbidden-shortcode |
The message cannot be sent as the account associated with the message is not provisioned for Short code messaging. |
Client Error |
Bandwidth Reported |
|
432 |
rejected-forbidden-country |
Bandwidth system indicates the account associated with the message is not enabled for this messaging zone or country, or this country is outside of the messaging reach (specifically for MMS). |
Client Error |
Bandwidth Reported |
|
433 |
rejected-forbidden-tollfree |
Either the source or destination account is not enabled for toll-free messaging. |
Client Error |
Bandwidth Reported |
|
434 |
rejected-forbidden-tollfree-for-recipient |
Toll-free messaging to this destination number is not allowed. The number is likely not enabled for toll-free messaging or is not active. |
Client Error |
Bandwidth Reported |
|
451 |
rejected-wrong-user-id |
The user id is not valid or permitted to send messages on your account. Verify the user ID associated with your account and retry the message. |
Client Error |
Bandwidth Reported |
|
452 |
rejected-wrong-application-id |
The application id specified is not a valid Application Id or the application id is not associated with the account. |
Client Error |
Bandwidth Reported |
|
470 |
rejected-spam-detected |
This message has been filtered and blocked by Bandwidth for spam. Messages can be blocked for a variety of reasons, including but not limited to volumetric filtering, content blocking, SHAFT violation, etc. |
Client Error |
Bandwidth Reported |
|
481 |
rejected-from-number-in-blacklist |
The From number has been flagged by Bandwidth as prohibited from sending messages. Numbers can be added to a blacklist when they are associated with messages that repeatedly violate spam policies, fraud policies, or messaging AUP. |
Client Error |
Bandwidth Reported |
|
482 |
rejected-to-number-in-blacklist |
The number you are attempting to send to is blocked from receiving messages. |
Client Error |
Bandwidth Reported |
|
492 |
reject-emergency |
Messaging to an emergency number is forbidden. |
Client Error |
Bandwidth Reported |
|
493 |
rejected-unauthorized |
Bandwidth service indicates the sender is not authorized to send messages from the account. |
Client Error |
Bandwidth Reported |
|
500 |
message-send-failed |
There was a failure with sending the message. |
Service Error |
Bandwidth Reported |
|
501 |
message-send-failed |
There was a failure with sending the message. |
Service Error |
Bandwidth Reported |
|
600 |
destination-carrier-queue-full |
The destination application cannot accept new messages at this time. This could result from network congestion, messaging queue full on the vendor side, or throttling error on the vendor side. |
Service Error |
Carrier Reported |
|
610 |
submit* sm-or-submit* multi-failed |
The downstream carrier application is experiencing an error. submitting the message has failed or canceling message has failed. |
Service Error |
Carrier Reported |
|
620 |
destination-app-error |
The carrier is reporting a general error associated with their application processing the message. |
Service Error |
Carrier Reported |
|
630 |
message-not-acknowle |
NACK - no response or acknowledgment received from the carrier |
Service Error |
Carrier Reported |
|
650 |
destination-failed |
Carrier Service is reporting a failure to send to a destination (mobile operator or handset). |
Service Error |
Carrier Reported |
|
700 |
invalid-service-type |
Carrier rejected message for invalid service type. This usually means messaging (SMS or MMS) is not supported by the carrier or handset. |
Client Error |
Carrier Reported |
|
701 |
destination-service-unavailable |
Carrier service is reporting the destination is not reachable or the SMS service is not available. |
Client Error |
Carrier Reported |
|
702 |
destination-subscriber-unavailable |
This error indicates the destination subscriber is unavailable. There are several reasons for this; the subscriber has turned off the handset, the destination is unreachable or barred, the GSM subscriber is busy for outbound SMS, SIM card is full, voicemail is full, or cannot reach the destination handset and has stored the message for retry in its « Store & Forward » function. |
Client Error |
Carrier Reported |
|
720 |
invalid-destination-address |
Carrier Rejected as Invalid Destination Address. This could mean the number is not in the numbering plan (area code does not exist or the number is just invalid) or the number is not enabled for messaging (like a landline). Additionally, for A2P messages to T-Mobile, this could also mean the user has opted to block all A2P traffic (toll-free, short code, and 10DLC). |
Client Error |
Carrier Reported |
|
721 |
destination-tn-deactivated |
The phone number you are attempting to send to is on the deactivation list. It is not associated with a carrier to be able to receive messages or is inactive. |
Client Error |
Carrier Reported |
|
730 |
no-route-to-destination-carrier |
Carrier is reporting there is no route available for messages. This could be because no routing exists to the destination, no roaming route is available, the destination handset is roaming on a network that cannot be reached, or the route is blocked for another reason. |
Client Error |
Carrier Reported |
|
740 |
invalid-source-address-address |
Carrier is rejecting the message due to an invalid source address - the number does not exist in the numbering plan. Other reasons for this error code are the source carrier is invalid/disabled, the source is not authorized or the number type is not supported. |
Client Error |
Carrier Reported |
|
750 |
destination-rejected-message |
The destination carrier has rejected the message but did not provide a specific reason. Specifically for AT&T traffic, this could be a prepaid user whose account is out of money, a subscriber that is provisioned to not receive this type of SMS or it was identified as Spam. |
Client Error |
Carrier Reported |
|
751 |
destination-rejected-message-size-invalid |
Carrier has rejected the message because the message length is invalid or too long. |
Client Error |
Carrier Reported |
|
752 |
destination-rejected-malformed |
Carrier is rejecting the message as malformed; this could be because of a blank message, unacceptable data value, the carrier does not accept messages with more than 160 characters, syntax error, content is invalid, the message ID is invalid, invalid parameter length, expected TLV missing, invalid TLV value, invalid data coding scheme, invalid number of destinations, error in the optional part of the PDU body, TLV not allowed, or XML validation error. |
Client Error |
Carrier Reported |
|
753 |
destination-rejected-handset |
The handset has rejected the message |
Client Error |
Carrier Reported |
|
770 |
destination-spam-detected |
The Carrier is reporting this message as blocked for SPAM. Some examples of common spam blocks: unwanted content, SHAFT violations (including specific keywords), or originating address has been flagged for repeated spam content. |
Client Error |
Carrier Reported |
|
771 |
rejected-shortened-url
|
There was an error with the shortened URL used. Bandwidth recommends customers obtain their own dedicated domain if shortened links are needed for their messaging campaign.
|
Client Error |
Carrier Reported |
|
772 |
rejected-tn-blocked |
This error indicates a blocked Sender or Receiver on the downstream platform. Please reach out to Bandwidth support so we can engage our vendor to determine which telephone number is blocked and why. |
Client Error |
Carrier Reported |
|
773 |
inactive-campaign |
The campaign this TN is assigned to is not active for the destination. Please check the status with TCR (The Campaign Registry). You will receive this error if the campaign is pending or rejected by the DCA or suspended by an MNO but the TN is still assigned to the campaign. |
Client Error |
Carrier Reported |
|
774 |
provisioning-issue |
There is an issue with how the number is provisioned in the industry's database. There may be some components of 10DLC provisioning that are incorrect or missing. Please reach out to Bandwidth support to investigate and correct this issue. |
Client Error |
Carrier Reported |
|
775 |
destination-rejected-due-to-user-opt-out |
The user has opted out of receiving messages from a particular sender. Remove the destination TN from the subscriber list and cease communication with the destination. |
Client Error |
Carrier Reported |
|
780 |
volume-violation-tmo |
Rejected by T-Mobile due to volumetric violation. You have sent over the daily limit for your 10DLC Brand. Please review your Brand daily throughput limit to ensure you are not exceeding the approved volumes. To improve your Brand score, please see our article on external vetting Brand Vetting |
Client Error |
Carrier Reported |
|
781 |
volume-violation-att
|
Rejected by AT&T due to volumetric violation. You have sent over the rate limit for your 10DLC campaign. Please review your campaign throughput limit to ensure you are not exceeding the approved volumes. This error can also indicate throttling by AT&T for other reasons, including high spam rates. |
Client Error |
Carrier Reported |
|
785 |
volumetric-violation |
The carrier rejected the message due to a volumetric violation. You have sent over the allotted limit and need to back off sending. Please retry after some time. |
Client Error |
Carrier Reported |
|
790 |
destination-rejected-sc-not-allowed |
Carrier Rejected Due to Short Code Restriction. Destination address blocked by mobile operator, the destination cannot receive short code messages, or the mobile operator blocked the destination from receiving messages from this short code for some other reason. |
Client Error |
Carrier Reported |
|
791 |
destination-rejected-campaign-not-allowed |
Carrier Rejected SC Campaign Not Allowed or blocked by the mobile operator |
Client Error |
Carrier Reported |
|
792 |
destination-rejected-sc-not-provisioned |
Short Code not provisioned on mobile operator's network. |
Client Error |
Carrier Reported |
|
793 |
destination-rejected-sc-expired |
Short Code expired with the mobile operator. |
Client Error |
Carrier Reported |
|
795 |
tfn-not-verified |
The message was blocked due to the toll-free number not being verified. This can also be because there is SPAM on the unverified TFN. Please review unverified sending limits and submit TFN for verification as soon as possible. |
Client Error |
Carrier Reported |
|
902 |
delivery-receipt-expired |
Bandwidth timed out waiting for the delivery receipt, this could be because the downstream provider did not send the requested delivery receipt or they sent it after the system timed out at two hours. |
Ambiguous Error |
Carrier Reported |
|
999 |
unknown-error |
Bandwidth does not recognize the vendor's error response or does not have the vendor code mapped internally. |
Ambiguous Error |
Carrier Reported |
Article is closed for comments.