All errors on the SMPP connection received in submit_sm_resp are described in the SMPP Protocol Specification v3.4 Issue 1.2 chapter 5.1.3 command_status.
A message will always be in one of the following states:
| Message state | Value | Description |
|---|---|---|
| ENROUTE | 1 | Message is in the process of being sent to the destination |
| Delivered | 2 | Message has been delivered to destination |
| EXPIRED | 3 | Message validity period has expired |
| DELETED | 4 | Message has been deleted |
| UNDELIVERABLE | 5 | Message is undeliverable |
| UNKNOWN | 7 | Message is in invalid state |
The states are described in the SMPP Protocol Specification v3.4 Issue 1.2 chapter 5.2.28 message_state. The message state value is also attached in a SMPP Optional Parameter message_state value 0x0427 described in the SMPP Protocol Specification v3.4 Issue 1.2 chapter 5.3.2.35.
The error codes are provided in status reports according to the SMPP Protocol Specification v3.4 Issue 1.2, Appendix B. Error codes come in two types: permanent means that the send message failure will continue, regardless of how many times the user tries the same operations (for example, if the destination phone number is incorrect). Temporary means that the send message operation may succeed if circumstances change (for example, system congestion clears up). The following table displays the error codes Sinch networks will be sending.
US customers--just looking for 10DLC or toll-free number SMPP errors? Find those here.
| Error | Error Type | Description | Possible Causes | Possible Solutions | Treated as |
|---|---|---|---|---|---|
| 0 | NO ERROR | No error | Message has been successfully delivered to the recipient's handset. | None | Permanent |
| 1 | ROUTING ERROR | Invalid or Missing Source Address | Your message could not be sent because the Source Address is invalid or missing. This can happen if:
|
| Permanent |
| 2 | ROUTING ERROR | Message is unable to be routed by Sinch. Internal routing error. |
| Ensure the phone number is in the correct E-164 format. It should start with the country code and be followed by the phone number, like “11234567890”, without including the '+' sign. Learn more. Phone Number Format If you continue to experience this issue, submit a support ticket here: Sinch Support Portal | Permanent |
| 3 | ROUTING ERROR | Message is unable to be routed by Sinch. Internal routing error. |
| Ensure the phone number is in the correct E-164 format. It should start with the country code and be followed by the phone number, like “11234567890”, without including the '+' sign. Learn more. Phone Number Format If you continue to experience this issue, submit a support ticket here: Sinch Support Portal | Permanent |
| 4 | ROUTING ERROR | Traffic limit exceeded. Internal routing error. | Temporary throttling on internal servers | If you continue to experience this issue, submit a support ticket here: Sinch Support Portal | Temporary |
| 5 | ROUTING ERROR | Location not found. Internal routing error. | No location found for routing number | If you continue to experience this issue, submit a support ticket here: Sinch Support Portal | Permanent |
| 6 | ROUTING ERROR | Location blocked. Internal routing error. | Location blocked for routing number to | If you continue to experience this issue, submit a support ticket here: Sinch Support Portal | Permanent |
| 7 | ROUTING ERROR | Reply path not found. Internal routing error. | This error occurs very rarely and the exact trigger is unknown. It could be due to a temporary network glitch, a downstream carrier issue, or an unrecognized element in your message. | If you continue to experience this issue, submit a support ticket here: Sinch Support Portal | Permanent |
| 8 | ROUTING ERROR | Message not submitted. Internal routing error. | There was an issue with routing the number internally and the message has failed | If you continue to experience this issue, submit a support ticket here: Sinch Support Portal | Permanent |
| 9 | ROUTING ERROR | Unsupported number plan. | Invalid Numbering Plan Indicator (NPI) for destination address in the dest_addr_npi parameter | Check the value for the dest_addr_npi parameter is set to a 1. Learn more: SMPP 3.4 Specification Page 118 | Permanent |
| 10 | ROUTING ERROR | Unsupported type of number. | Possible invalid Type of Number (TON) in submit_sm SMPP message | Check the value for the source_addr_ton and dest_addr_ton parameters is set to a 1. Learn more: SMPP 3.4 Specification Page 59 | Permanent |
| 11 | ROUTING ERROR | Message not delivered. | An infrequent, uncategorized error. Because the exact cause (internal, external, or message-specific) is unknown, we recommend retrying the message before escalating. | If you continue to experience this issue, submit a support ticket here: Sinch Support Portal | Temporary |
| 12 | ROUTING ERROR | Dialing zone not found. | This error occurs very rarely and the exact trigger is unknown. It could be due to a temporary network glitch, a downstream carrier issue, or an unrecognized element in your message. | If you continue to experience this issue, submit a support ticket here: Sinch Support Portal | Permanent |
| 13 | ROUTING ERROR | Home zone and IMSI not allowed. | This error occurs very rarely and the exact trigger is unknown. It could be due to a temporary network glitch, a downstream carrier issue, or an unrecognized element in your message. | If you continue to experience this issue, submit a support ticket here: Sinch Support Portal | Permanent |
| 14 | ROUTING ERROR | Home zone and IMSI fetch failed. | This error occurs very rarely and the exact trigger is unknown. It could be due to a temporary network glitch, a downstream carrier issue, or an unrecognized element in your message. | If you continue to experience this issue, submit a support ticket here: Sinch Support Portal | Permanent |
| 15 | SCREENING ERROR | Screening blocked the message for possible SPAM | This message was blocked by the carrier due to spam filtering. Carriers may block messages for several reasons, including, containing certain restricted words or phrases, restricted content, or violations of SHAFT guidelines |
| Permanent |
| 16 | SCREENING ERROR | Terminating IMSI blocked. | This error occurs very rarely and the exact trigger is unknown. It could be due to a temporary network glitch, a downstream carrier issue, or an unrecognized element in your message. | If you continue to experience this issue, submit a support ticket here: Sinch Support Portal | Permanent |
| 17 | ROUTING ERROR | Destination network type unknown. | The dest_network_type parameter is not supported | Ensure the dest_network_type is set to a valid type. A value of 0x0006 (Generic) is valid for all networks. | Permanent |
| 18 | ESME ERROR | Carrier error | The carrier is experiencing a temporary error that is preventing the message from being processed. | Retry recommended after 30 seconds (up to 3 attempts). If still failing, open a support ticket. | Temporary |
| 19 | SCREENING ERROR | Originating location mismatch. | This error occurs very rarely and the exact trigger is unknown. It could be due to a temporary network glitch, a downstream carrier issue, or an unrecognized element in your message. | If you continue to experience this issue, submit a support ticket here: Sinch Support Portal | Permanent |
| 20 | ESME ERROR | Originating reservation failed. | This error occurs very rarely and is due to the carrier experiencing a temporary error that is preventing the message from being processed. | Retry recommended after 30 seconds (up to 3 attempts). | Temporary |
| 21 | ESME ERROR | Originating reservation denied. Subscription not found. | Multiple destinations in one PDU: The submit_sm message contained more that one destination in the dest_addr field | Ensure you are not putting multiple destination numbers in a single submit_sm PDU. | Permanent |
| 22 | ESME ERROR | Originating reservation denied. Subscription state illegal. | This error occurs very rarely and the exact trigger is unknown. It could be due to a temporary network glitch, a downstream carrier issue, or an unrecognized element in your message. | If you continue to experience this issue, submit a support ticket here: Sinch Support Portal | Permanent |
| 23 | ESME ERROR | Originating reservation denied. Call case blocked for subscription. | This error occurs very rarely and is due to originating number not allowed to send the type of message being sent. Originating number not allowed to originate messages. The message type (e.g., SMS, MMS, 10DLC, TFN) not permitted under the current subscription. | If you continue to experience this issue, submit a support ticket here: Sinch Support Portal | Permanent |
| 24 | ESME ERROR | Originating reservation denied. Call case blocked for subscription type. | This error occurs very rarely and the exact trigger is unknown. It could be due to a temporary network glitch, a downstream carrier issue, or an unrecognized element in your message. | If you continue to experience this issue, submit a support ticket here: Sinch Support Portal | Permanent |
| 25 | ESME ERROR | Originating reservation denied. Low balance. Internal Error. | This error occurs very rarely and the exact trigger is unknown. It could be due to a temporary network glitch, a downstream carrier issue, or an unrecognized element in your message. | If you continue to experience this issue, submit a support ticket here: Sinch Support Portal | Permanent |
| 30 | ESME ERROR | Terminating reservation failed. | An infrequent, uncategorized error. Because the exact cause (internal, external, or message-specific) is unknown, we recommend retrying the message before escalating. | If you continue to experience this issue, submit a support ticket here: Sinch Support Portal | Temporary |
| 31 | ESME ERROR | Terminating reservation denied subscription not found. | This error occurs very rarely and the exact trigger is unknown. It could be due to a temporary network glitch, a downstream carrier issue, or an unrecognized element in your message. | If you continue to experience this issue, submit a support ticket here: Sinch Support Portal | Permanent |
| 32 | ESME ERROR | Terminating reservation denied subscription state illegal. | Usually caused by sending a cancel_sm or replace_sm message on a message that is not in a state that allows for cancellation/replace. | Verify subscription state: If you are reserving a subscription, ensure it is active and in the state allowed for the command. | Permanent |
| 33 | ESME ERROR | Terminating reservation denied call case blocked for subscription. | This error occurs very rarely and the exact trigger is unknown. It could be due to a temporary network glitch, a downstream carrier issue, or an unrecognized element in your message. | If you continue to experience this issue, submit a support ticket here: Sinch Support Portal | Permanent |
| 34 | ESME ERROR | Terminating reservation denied call case blocked for subscription type. | This error occurs very rarely and the exact trigger is unknown. It could be due to a temporary network glitch, a downstream carrier issue, or an unrecognized element in your message. | If you continue to experience this issue, submit a support ticket here: Sinch Support Portal | Permanent |
| 35 | SCREENING ERROR | Terminating reservation denied due to low balance. Internal error. | This error occurs very rarely and the exact trigger is unknown. It could be due to a temporary network glitch, a downstream carrier issue, or an unrecognized element in your message. | If you continue to experience this issue, submit a support ticket here: Sinch Support Portal | Permanent |
| 40 | INTERNAL ERROR | System Congestion. Internal error. | Network congestion or messaging queue full | If you continue to experience this issue, submit a support ticket here: Sinch Support Portal | Temporary |
| 41 | ESME ERROR | Originating IMSI mismatch. | This error occurs very rarely and the exact trigger is unknown. It could be due to a temporary network glitch, a downstream carrier issue, or an unrecognized element in your message. | If you continue to experience this issue, submit a support ticket here: Sinch Support Portal | Permanent |
| 45 | ESME ERROR | Quarantine add. | This error occurs very rarely and the exact trigger is unknown. It could be due to a temporary network glitch, a downstream carrier issue, or an unrecognized element in your message. | If you continue to experience this issue, submit a support ticket here: Sinch Support Portal | Permanent |
| 46 | ESME ERROR | Quarantine remove. | An infrequent, uncategorized error. Because the exact cause (internal, external, or message-specific) is unknown, we recommend retrying the message before escalating. | If you continue to experience this issue, submit a support ticket here: Sinch Support Portal | Temporary |
| 50 | INTERNAL ERROR | Error from Store. Internal error. | An infrequent, uncategorized error. Because the exact cause (internal, external, or message-specific) is unknown, we recommend retrying the message before escalating. | If you continue to experience this issue, submit a support ticket here: Sinch Support Portal | Temporary |
| 51 | INTERNAL ERROR | Direct delivery disabled from Store. Internal error. | An infrequent, uncategorized error. Because the exact cause (internal, external, or message-specific) is unknown, we recommend retrying the message before escalating. | If you continue to experience this issue, submit a support ticket here: Sinch Support Portal | Temporary |
| 52 | INTERNAL ERROR | Error from Store: internal exception. Internal error. | An infrequent, uncategorized error. Because the exact cause (internal, external, or message-specific) is unknown, we recommend retrying the message before escalating. | If you continue to experience this issue, submit a support ticket here: Sinch Support Portal | Temporary |
| 53 | INTERNAL ERROR | Error from Store: number of stored messages exceeded. Internal error. | This error occurs very rarely and the exact trigger is unknown. It could be due to a temporary network glitch, a downstream carrier issue, or an unrecognized element in your message. | If you continue to experience this issue, submit a support ticket here: Sinch Support Portal | Permanent |
| 54 | INTERNAL ERROR | Error from Store: retry scheme ended. Internal error. | This error occurs very rarely and the exact trigger is unknown. It could be due to a temporary network glitch, a downstream carrier issue, or an unrecognized element in your message. | If you continue to experience this issue, submit a support ticket here: Sinch Support Portal | Permanent |
| 55 | INTERNAL ERROR | Error from store: invalid destination. Internal error. | This error occurs very rarely and the exact trigger is unknown. It could be due to a temporary network glitch, a downstream carrier issue, or an unrecognized element in your message. | If you continue to experience this issue, submit a support ticket here: Sinch Support Portal | Permanent |
| 56 | INTERNAL ERROR | Error from store: direct delivery disabled from carrier cache. Internal error | An infrequent, uncategorized error. Because the exact cause (internal, external, or message-specific) is unknown, we recommend retrying the message before escalating. | If you continue to experience this issue, submit a support ticket here: Sinch Support Portal | Temporary |
| 57 | None | Error from store: ESME cache limit exceeded. Internal Error | An infrequent, uncategorized error. Because the exact cause (internal, external, or message-specific) is unknown, we recommend retrying the message before escalating. | If you continue to experience this issue, submit a support ticket here: Sinch Support Portal | Temporary |
| 58 | None | Error from store: scheduled delivery time limit exceeded | The schedule_delivery_time value has exceeded the allowed time permitted | Learn more: SMPP 3.4 Specification Page 124 | Permanent |
| 60 | SCREENING ERROR | Originator blocked. | Campaign is not in a valid active state with carrier. This means the campaign is in a state that doesn't allow messages to be sent (suspended, expired, etc.) or not setup properly. Originating number not approved to be used over account. Invalid or missing Campaign ID / Program ID or A2P context flag. | Verify that the correct Campaign ID is being used. Check whether your phone number is associated with a Campaign ID and has the appropriate A2P context flag enabled. If either is missing, ensure the number is properly configured for 10DLC messaging. If the issue persists, please contact your Account Manager for assistance in resolving your campaign status. Contact Account Manager | Permanent |
| 61 | SCREENING ERROR | Destination blocked. | Account not permitted to reach the destination address. |
| Permanent |
| 62 | SCREENING ERROR | Keyword blocked. | A word or phase in the body of the message has triggered a SPAM or SHAFT filter. |
| Permanent |
| 63 | SCREENING ERROR | SC (short code) address blocked | This error occurs very rarely and the exact trigger is unknown. It could be due to a temporary network glitch, a downstream carrier issue, or an unrecognized element in your message. | If you continue to experience this issue, submit a support ticket here: Sinch Support Portal | Permanent |
| 64 | SCREENING ERROR | Blocked due to exceeded quota. | Throttling Limit Reached: The campaign has exceeded its messaging limit and is being throttled until volume decreases. | 10DLC & Short Code: Keep TPS within your configured account limit. If exceeded, traffic is throttled and will automatically resume once the rate is reduced. Carrier Limits: Toll-Free (Unverified): T-Mobile: Daily limits reset at midnight Pacific Time. Wait for the next day if exceeded. Messages may be blocked if the toll-free number is not verified. Other Carriers: Typically enforce per-minute limits. Keep TPM within your configured threshold. Requesting Higher Throughput: To increase throughput, see: How to Vet Your Brand for Higher Throughput TFN: Learn more about Toll-free Number sender verification here: Toll-Free Verified Sender Form | Permanent |
| 65 | SCREENING ERROR | Loop detected. | This message appears to be auto-generated. Replying programmatically may cause infinite loops. | If you continue to experience this issue, submit a support ticket here: Sinch Support Portal | Permanent |
| 66 | SCREENING ERROR | Data coding scheme blocked. | Invalid Data Coding Scheme. | Learn more: SMPP 3.4 Specification Page 126 | Permanent |
| 67 | SCREENING ERROR | Information element identifier blocked. | This error occurs very rarely and the exact trigger is unknown. It could be due to a temporary network glitch, a downstream carrier issue, or an unrecognized element in your message. | If you continue to experience this issue, submit a support ticket here: Sinch Support Portal | Permanent |
| 68 | None | Country code validation blocked | This error occurs very rarely and the exact trigger is unknown. It could be due to a temporary network glitch, a downstream carrier issue, or an unrecognized element in your message. | If you continue to experience this issue, submit a support ticket here: Sinch Support Portal | Permanent |
| 70 | ESME ERROR | No carrier provider available. Internal error. | An infrequent, uncategorized error. Because the exact cause (internal, external, or message-specific) is unknown, we recommend retrying the message before escalating. | If you continue to experience this issue, submit a support ticket here: Sinch Support Portal | Temporary |
| 71 | ESME ERROR | Carrier account not connected. Internal error. | An infrequent, uncategorized error. Because the exact cause (internal, external, or message-specific) is unknown, we recommend retrying the message before escalating. | If you continue to experience this issue, submit a support ticket here: Sinch Support Portal | Temporary |
| 72 | ESME ERROR | Carrier account routing issue. Internal error. | This error occurs very rarely and the exact trigger is unknown. It could be due to a temporary network glitch, a downstream carrier issue, or an unrecognized element in your message. | If you continue to experience this issue, submit a support ticket here: Sinch Support Portal | Permanent |
| 73 | ESME ERROR | Carrier account blocked. Internal error. | An infrequent, uncategorized error. Because the exact cause (internal, external, or message-specific) is unknown, we recommend retrying the message before escalating. | If you continue to experience this issue, submit a support ticket here: Sinch Support Portal | Temporary |
| 74 | ESME ERROR | Carrier local TX throttling. Internal error. | An infrequent, uncategorized error. Because the exact cause (internal, external, or message-specific) is unknown, we recommend retrying the message before escalating. | If you continue to experience this issue, submit a support ticket here: Sinch Support Portal | Temporary |
| 75 | ESME ERROR | Outstanding requests exceeded to Carrier. Internal error. | An infrequent, uncategorized error. Because the exact cause (internal, external, or message-specific) is unknown, we recommend retrying the message before escalating. | If you continue to experience this issue, submit a support ticket here: Sinch Support Portal | Temporary |
| 76 | ESME ERROR | Carrier router route not found. Internal error. | An infrequent, uncategorized error. Because the exact cause (internal, external, or message-specific) is unknown, we recommend retrying the message before escalating. | If you continue to experience this issue, submit a support ticket here: Sinch Support Portal | Temporary |
| 77 | ESME ERROR | Carrier router IMSI lookup failed. | This error occurs very rarely and the exact trigger is unknown. It could be due to a temporary network glitch, a downstream carrier issue, or an unrecognized element in your message. | If you continue to experience this issue, submit a support ticket here: Sinch Support Portal | Permanent |
| 78 | None | Error from Carrier router, route suspended | This error occurs very rarely and the exact trigger is unknown. It could be due to a temporary network glitch, a downstream carrier issue, or an unrecognized element in your message. | If you continue to experience this issue, submit a support ticket here: Sinch Support Portal | Permanent |
| 80 | None | Error from Carrier source, home routing sender GT mismatch | This error occurs very rarely and the exact trigger is unknown. It could be due to a temporary network glitch, a downstream carrier issue, or an unrecognized element in your message. | If you continue to experience this issue, submit a support ticket here: Sinch Support Portal | Permanent |
| 81 | None | Error from MO source, location mismatch between provided location and location known to HLR. | This error occurs very rarely and the exact trigger is unknown. It could be due to a temporary network glitch, a downstream carrier issue, or an unrecognized element in your message. | If you continue to experience this issue, submit a support ticket here: Sinch Support Portal | Permanent |
| 82 | None | Error from MO source, IMSI mismatch between provided IMSI (MAP v3) and IMSI known to HLR. | This error occurs very rarely and the exact trigger is unknown. It could be due to a temporary network glitch, a downstream carrier issue, or an unrecognized element in your message. | If you continue to experience this issue, submit a support ticket here: Sinch Support Portal | Permanent |
| 83 | None | Error from MS and SMSC sink, local throttling by the sink. | An infrequent, uncategorized error. Because the exact cause (internal, external, or message-specific) is unknown, we recommend retrying the message before escalating. | If you continue to experience this issue, submit a support ticket here: Sinch Support Portal | Temporary |
| 84 | None | IMSI could not be retrieved from HSS. | This error occurs very rarely and the exact trigger is unknown. It could be due to a temporary network glitch, a downstream carrier issue, or an unrecognized element in your message. | If you continue to experience this issue, submit a support ticket here: Sinch Support Portal | Permanent |
| 85 | None | IMEI of the UE is unknown. | This error occurs very rarely and the exact trigger is unknown. It could be due to a temporary network glitch, a downstream carrier issue, or an unrecognized element in your message. | If you continue to experience this issue, submit a support ticket here: Sinch Support Portal | Permanent |
| 86 | None | User location is unknown. | This error occurs very rarely and the exact trigger is unknown. It could be due to a temporary network glitch, a downstream carrier issue, or an unrecognized element in your message. | If you continue to experience this issue, submit a support ticket here: Sinch Support Portal | Permanent |
| 88 | ESME_RTHROTTLED | Throttling error (Exceeded allowed message limits) | Message blocked because the account has exceeded its allowed TPS message limit and is being throttled. | Ensure your system’s sending TPS rate stays within the configured account TPS limit; throttling clears automatically once the rate is reduced. | Temporary |
| 100 | SMSC ERROR | Unidentified Subscriber. | This error occurs very rarely and the exact trigger is unknown. It could be due to a temporary network glitch, a downstream carrier issue, or an unrecognized element in your message. | If you continue to experience this issue, submit a support ticket here: Sinch Support Portal | Permanent |
| 101 | SMSC ERROR | Facility not supported. | An infrequent, uncategorized error. Because the exact cause (internal, external, or message-specific) is unknown, we recommend retrying the message before escalating. | If you continue to experience this issue, submit a support ticket here: Sinch Support Portal | Temporary |
| 102 | SMSC ERROR | System failure. | An infrequent, uncategorized error. Because the exact cause (internal, external, or message-specific) is unknown, we recommend retrying the message before escalating. | If you continue to experience this issue, submit a support ticket here: Sinch Support Portal | Temporary |
| 103 | SMSC ERROR | Unexpected data value . | This error occurs very rarely and the exact trigger is unknown. It could be due to a temporary network glitch, a downstream carrier issue, or an unrecognized element in your message. | If you continue to experience this issue, submit a support ticket here: Sinch Support Portal | Permanent |
| 104 | SMSC ERROR | Data missing. | This error occurs very rarely and the exact trigger is unknown. It could be due to a temporary network glitch, a downstream carrier issue, or an unrecognized element in your message. | If you continue to experience this issue, submit a support ticket here: Sinch Support Portal | Permanent |
| 105 | SMSC ERROR | Equipment protocol error. | This error occurs very rarely and the exact trigger is unknown. It could be due to a temporary network glitch, a downstream carrier issue, or an unrecognized element in your message. | If you continue to experience this issue, submit a support ticket here: Sinch Support Portal | Permanent |
| 106 | SMSC ERROR | Unknown service center address. | An infrequent, uncategorized error. Because the exact cause (internal, external, or message-specific) is unknown, we recommend retrying the message before escalating. | Retry recommended after 30 seconds (up to 3 attempts). If still failing, open a support ticket here: Sinch Support Portal | Temporary |
| 107 | SMSC ERROR | Service center congestion. | An infrequent, uncategorized error. Because the exact cause (internal, external, or message-specific) is unknown, we recommend retrying the message before escalating. | Retry recommended after 30 seconds (up to 3 attempts). If still failing, open a support ticket here: Sinch Support Portal | Temporary |
| 108 | SMSC ERROR | Invalid short message entity address. | This error occurs very rarely and the exact trigger is unknown. It could be due to a temporary network glitch, a downstream carrier issue, or an unrecognized element in your message. | If you continue to experience this issue, submit a support ticket here: Sinch Support Portal | Permanent |
| 109 | SMSC ERROR | Subscriber not service center subscriber. | This error occurs very rarely and the exact trigger is unknown. It could be due to a temporary network glitch, a downstream carrier issue, or an unrecognized element in your message. | If you continue to experience this issue, submit a support ticket here: Sinch Support Portal | Permanent |
| 110 | SMSC ERROR | Reject. | This error occurs very rarely and the exact trigger is unknown. It could be due to a temporary network glitch, a downstream carrier issue, or an unrecognized element in your message. | If you continue to experience this issue, submit a support ticket here: Sinch Support Portal | Permanent |
| 111 | SMSC ERROR | Local cancel. | An infrequent, uncategorized error. Because the exact cause (internal, external, or message-specific) is unknown, we recommend retrying the message before escalating. | If you continue to experience this issue, submit a support ticket here: Sinch Support Portal | Temporary |
| 112 | SMSC ERROR | Abort. | An infrequent, uncategorized error. Because the exact cause (internal, external, or message-specific) is unknown, we recommend retrying the message before escalating. | If you continue to experience this issue, submit a support ticket here: Sinch Support Portal | Temporary |
| 113 | SMSC ERROR | Exception (internal). | This error occurs very rarely and the exact trigger is unknown. It could be due to a temporary network glitch, a downstream carrier issue, or an unrecognized element in your message. | If you continue to experience this issue, submit a support ticket here: Sinch Support Portal | Permanent |
| 114 | SMSC ERROR | Unknown error. | An infrequent, uncategorized error. Because the exact cause (internal, external, or message-specific) is unknown, we recommend retrying the message before escalating. | Retry recommended after 30 seconds (up to 3 attempts). If still failing, open a support ticket here: Sinch Support Portal | Temporary |
| 150 | HLR ERROR | Unknown subscriber. | Message is rejected because the MSISDN is not active with the carrier. |
| Permanent |
| 151 | HLR ERROR | Call barred. | Message rejected due to active barring by the end-user. | The person receiving the message needs to call their mobile service provider to fix any blocks on their account. It might be best to stop sending messages to this number for now. | Permanent |
| 152 | HLR ERROR | Teleservice not provisioned. | Message is rejected because the recipient mobile subscriber has no SMS subscription. This could be that the destination number is not active, not enabled for messaging, or is an invalid number. |
| Permanent |
| 153 | HLR ERROR | Absent subscriber. | Subscriber handset not connected to the network. Likely turned off or outside the area of coverage. |
| Temporary |
| 154 | HLR ERROR | Facility not supported. | The message is rejected due to no provision of the SMS in the VPLMN. | If you continue to experience this issue, submit a support ticket here: Sinch Support Portal | Permanent |
| 155 | HLR ERROR | System failure. | Message rejected due to network or protocol failure. | Retry recommended after 30 seconds (up to 3 attempts). If still failing, open a support ticket. | Temporary |
| 156 | HLR ERROR | Unexpected data value. | Message rejected due to network or protocol failure. | If you continue to experience this issue, submit a support ticket here: Sinch Support Portal | Permanent |
| 157 | HLR ERROR | Data missing. | Message rejected due to network or protocol failure. | If you continue to experience this issue, submit a support ticket here: Sinch Support Portal | Permanent |
| 158 | HLR ERROR | Memory capacity exceeded. | The handset does not have sufficient free memory to accept the SMS. | Recipient may need to make sure the phone has enough space for new messages. Delete old texts if necessary. | Temporary |
| 159 | HLR ERROR | Mobile subscriber not reachable. | The destination number cannot be reached because it is either turned off, out of network coverage, or has been in a low-coverage area for an extended period. |
| Temporary |
| 160 | HLR ERROR | Reject. | Indicates temporary problem or lost reach. | If you continue to experience this issue, submit a support ticket here: Sinch Support Portal | Permanent |
| 161 | HLR ERROR | Local Cancel. | An infrequent, uncategorized error. Because the exact cause (internal, external, or message-specific) is unknown, we recommend retrying the message before escalating. | Retry recommended after 30 seconds (up to 3 attempts). If still failing, open a support ticket. | Temporary |
| 162 | HLR ERROR | Abort. | An infrequent, uncategorized error. Because the exact cause (internal, external, or message-specific) is unknown, we recommend retrying the message before escalating. | If you continue to experience this issue, submit a support ticket here: Sinch Support Portal | Temporary |
| 163 | HLR ERROR | Exception (internal). | This error occurs very rarely and the exact trigger is unknown. It could be due to a temporary network glitch, a downstream carrier issue, or an unrecognized element in your message. | If you continue to experience this issue, submit a support ticket here: Sinch Support Portal | Permanent |
| 164 | HLR ERROR | Unknown error. | An infrequent, uncategorized error. Because the exact cause (internal, external, or message-specific) is unknown, we recommend retrying the message before escalating. | Retry recommended after 30 seconds (up to 3 attempts). If still failing, open a support ticket. | Temporary |
| 200 | MSC ERROR | Unidentified subscriber. | Message is rejected because the MSISDN could not be found with the carrier. |
| Temporary |
| 201 | MSC ERROR | Absent subscriber, IMSI detached. | The destination number cannot be reached because it is either turned off, out of network coverage, or has been in a low-coverage area for an extended period. |
| Temporary |
| 202 | MSC ERROR | Absent subscriber, no page response. | The message is rejected because there was no paging response. |
| Temporary |
| 203 | MSC ERROR | Subscriber busy for MT SMS. | The message is rejected because of congestion encountered at the visited MSC. |
| Temporary |
| 204 | MSC ERROR | Facility not supported. | The message is rejected due to no provision of the SMS in the destination SIM. | If you continue to experience this issue, submit a support ticket here: Sinch Support Portal | Permanent |
| 205 | MSC ERROR | Illegal subscriber. | Message rejected because of failed authentication. | If you continue to experience this issue, submit a support ticket here: Sinch Support Portal | Permanent |
| 206 | MSC ERROR | Illegal equipment. | Message rejected because the mobile subscriber was blacklisted. | If you continue to experience this issue, submit a support ticket here: Sinch Support Portal | Permanent |
| 207 | MSC ERROR | System failure. | Message rejected due to network or protocol failure. | Retry recommended after 30 seconds (up to 3 attempts). If still failing, open a support ticket. | Temporary |
| 208 | MSC ERROR | Unexpected data value. | This error occurs very rarely and the exact trigger is unknown. It could be due to a temporary network glitch, a downstream carrier issue, or an unrecognized element in your message. | If you continue to experience this issue, submit a support ticket here: Sinch Support Portal | Permanent |
| 209 | MSC ERROR | Data missing. | This error occurs very rarely and the exact trigger is unknown. It could be due to a temporary network glitch, a downstream carrier issue, or an unrecognized element in your message. | If you continue to experience this issue, submit a support ticket here: Sinch Support Portal | Permanent |
| 210 | MSC ERROR | Memory capacity exceeded. | Message rejected because the mobile subscriber doesn’t have enough memory. |
| Temporary |
| 211 | MSC ERROR | Equipment protocol error. | An infrequent, uncategorized error. Because the exact cause (internal, external, or message-specific) is unknown, we recommend retrying the message before escalating. | Retry recommended after 30 seconds (up to 3 attempts). If still failing, open a support ticket. | Temporary |
| 212 | MSC ERROR | Device not short message equipped. | The number cannot receive text messages, for example Data-SIMs. | Check Number Type: Recipient may need to ensure the number can receive texts. It shouldn't be a data-only SIM card, landline, VoIP, or any special service number that can't get text messages. | Temporary |
| 213 | MSC ERROR | Reject. | Indicates temporary problem or lost reach. | If you continue to experience this issue, submit a support ticket here: Sinch Support Portal | Permanent |
| 214 | MSC ERROR | Local Cancel. | Indicates temporary problem or lost reach. | If you continue to experience this issue, submit a support ticket here: Sinch Support Portal | Temporary |
| 215 | MSC ERROR | Abort. | Indicates temporary problem or lost reach. | Retry recommended after 30 seconds (up to 3 attempts). If still failing, open a support ticket. | Temporary |
| 216 | MSC ERROR | Exception (internal). | This error occurs very rarely and the exact trigger is unknown. It could be due to a temporary network glitch, a downstream carrier issue, or an unrecognized element in your message. | If you continue to experience this issue, submit a support ticket here: Sinch Support Portal | Permanent |
| 217 | MSC ERROR | Unknown error. | An infrequent, uncategorized error. Because the exact cause (internal, external, or message-specific) is unknown, we recommend retrying the message before escalating. | Retry recommended after 30 seconds (up to 3 attempts). If still failing, open a support ticket. | Temporary |
| 250 | SCREENING ERROR | Personal service barring, MO Personal. | Determined Barring White List. |
| Permanent |
| 251 | SCREENING ERROR | Personal service barring, MO Personal. | Determined Barring Black List. |
| Permanent |
| 252 | SCREENING ERROR | Personal service barring, MO Operator. | Determined Barring White List. |
| Permanent |
| 253 | SCREENING ERROR | Personal service barring, MO Operator. | Determined Barring Black List. |
| Permanent |
| 254 | SCREENING ERROR | Personal service barring, MT Personal. | Determined Barring White List. |
| Permanent |
| 255 | SCREENING ERROR | Personal service barring, MT Personal. Determined Barring Black List. | The end-user has opted out from receiving messages. Either all A2P messages or sender ID specific. TFN: This message was blocked by the carrier due to spam filtering. Carriers may block messages for several reasons, including, containing certain restricted words or phrases, restricted content, or violations of SHAFT guidelines |
| Permanent |
| 256 | SCREENING ERROR | Personal service barring, MT Operator. | Determined Barring White List. | If you continue to experience this issue, submit a support ticket here: Sinch Support Portal | Permanent |
| 257 | SCREENING ERROR | Personal service barring, MT Operator. | Determined Barring Black List. The end-user has opted out from receiving messages. Either all A2P messages or sender ID specific. |
| Permanent |
| 280 | None | SM external control. | Indicates internal network problem. | If you continue to experience this issue, submit a support ticket here: Sinch Support Portal | Temporary |
| 281 | None | Secondary UE delivery failure | An infrequent, uncategorized error. Because the exact cause (internal, external, or message-specific) is unknown, we recommend retrying the message before escalating. | If you continue to experience this issue, submit a support ticket here: Sinch Support Portal | Temporary |
| 300 | ESME EXTERNAL ERROR | Invalid destination address. | Message blocked because the destination number is invalid, deactivated, disconnected, or does not support messaging. This can happen if the number doesn’t exist, is a landline, or isn’t enabled for text messages. TFN: For toll-free messages it may also mean the recipient has blocked all toll-free and short code traffic. |
| Permanent |
| 301 | ESME EXTERNAL ERROR | Invalid destination numbering plan. | Invalid Numbering Plan Indicator for destination address in the dest_addr_npi parameter | Check the value for the dest_addr_npi parameter is set to a 1. Learn more: SMPP 3.4 Specification Page 118 | Permanent |
| 302 | ESME EXTERNAL ERROR | Invalid destination type of number. | Invalid Type of Number (TON) for the destination address in the dest_addr_ton parameter | Check the value for the dest_addr_ton parameter is set to a 1. Learn more: SMPP 3.4 Specification Page 117 | Permanent |
| 303 | ESME EXTERNAL ERROR | Invalid destination flag. | The dest_flag parameter which will identify whether destination address is a Distribution List (DL) name or SME address is invalid. | Learn more: SMPP 3.4 Specification Page 75 | Permanent |
| 304 | ESME EXTERNAL ERROR | Invalid number of destinations. | The number_of_dests field in the submit_multi PDU is invalid. | submit_multi IS NOT SUPPORTED | Permanent |
| 310 | ESME EXTERNAL ERROR | Invalid source address. | Message blocked because the sending number is invalid or not authorized. This can happen if the number doesn’t exist, the source carrier is disabled, the sender isn’t authorized, or the number type isn’t supported for messaging. |
| Permanent |
| 311 | ESME EXTERNAL ERROR | Invalid source numbering plan. | Invalid Numbering Plan Indicator (NPI) for source address in the source_addr_npi parameter | Check the value for the source_addr_npi parameter is set to a 1. Learn more: SMPP 3.4 Specification Page 118 | Permanent |
| 312 | ESME EXTERNAL ERROR | Invalid source type of number. | Invalid Type of Number (TON) for the source address in the source_addr_ton parameter | Check the value for the source_addr_ton parameter is set to a 1. Learn More: SMPP 3.4 Specification Page 117 | Permanent |
| 320 | ESME EXTERNAL ERROR | ESME Receiver permanent error. | Access to the specified service_type is denied due to lack of authorization, prohibited operations, service unavailability, or inappropriate message content. Broadcast operation failed. | Check the value for the service_type parameter is set to the proper value. Default is set to NULL. Learn more: SMPP 3.4 Specification Page 120 If the issue persist open a support ticket: Sinch Support Portal | Permanent |
| 321 | ESME EXTERNAL ERROR | ESME Receiver reject error. | This error occurs very rarely and the exact trigger is unknown. It could be due to a temporary network glitch, a downstream carrier issue, or an unrecognized element in your message. | If you continue to experience this issue, submit a support ticket here: Sinch Support Portal | Permanent |
| 322 | ESME EXTERNAL ERROR | ESME Receiver temporary error. | The ESME is experiencing a temporary error that is preventing the message from being processed. | Retry recommended after 30 seconds (up to 3 attempts). If still failing, open a support ticket. | Temporary |
| 330 | ESME EXTERNAL ERROR | Invalid command length. | The command being sent is too long or too short for the given PDU. | Check that the correct command syntax and parameters are being used. Learn More: SMPP 3.4 Specification Page 41 | Permanent |
| 331 | ESME EXTERNAL ERROR | Invalid service type. | The Service Type for the service_type parameter is either not recognised or its length is not within the defined range. | Check the value for the service_type parameter is set to the proper value. Default is set to NULL. Learn more: SMPP 3.4 Specification Page 120 | Permanent |
| 332 | ESME EXTERNAL ERROR | Invalid operation. | This error occurs very rarely and the exact trigger is unknown. It could be due to a temporary network glitch, a downstream carrier issue, or an unrecognized element in your message. | If you continue to experience this issue, submit a support ticket here: Sinch Support Portal | Permanent |
| 333 | ESME EXTERNAL ERROR | Operation not allowed. | This error occurs very rarely and the exact trigger is unknown. It could be due to a temporary network glitch, a downstream carrier issue, or an unrecognized element in your message. | If you continue to experience this issue, submit a support ticket here: Sinch Support Portal | Permanent |
| 334 | ESME EXTERNAL ERROR | Invalid parameter. | A parameter in the submit_sm message is invalid | Learn more: SMPP 3.4 Specification Page 59 If you continue to experience this issue, submit a support ticket here: Sinch Support Portal | Permanent |
| 335 | ESME EXTERNAL ERROR | Parameter not allowed. | This error occurs very rarely and the exact trigger is unknown. It could be due to a temporary network glitch, a downstream carrier issue, or an unrecognized element in your message. | If you continue to experience this issue, submit a support ticket here: Sinch Support Portal | Permanent |
| 336 | ESME EXTERNAL ERROR | Invalid parameter length. | A parameter in the submit_sm message has an invalid length | Learn more: SMPP 3.4 Specification Page 59 If the issue persist open a support ticket: Sinch Support Portal | Permanent |
| 337 | ESME EXTERNAL ERROR | Invalid optional parameter. | An Optional parameter in the submit_sm message has an invalid value | Learn more: SMPP 3.4 Specification Page 62 If the issue persist open a support ticket: Sinch Support Portal | Permanent |
| 338 | ESME EXTERNAL ERROR | Optional parameter missing. | An Optional Parameter in the submit_sm message has is missing | Learn more: SMPP 3.4 Specification Page 62 If the issue persist open a support ticket: Sinch Support Portal | Permanent |
| 339 | ESME EXTERNAL ERROR | Invalid validity parameter. | The validity_period parameter is invalid. | Learn more: SMPP 3.4 Specification Page 70 | Permanent |
| 340 | ESME EXTERNAL ERROR | Invalid scheduled delivery parameter. | The schedule_delivery_time parameter in the submit_sm message is invalid | Learn more: SMPP 3.4 Specification Page 70 | Permanent |
| 341 | ESME EXTERNAL ERROR | Invalid distribution list. | The Distribution List dl_name parameter is not supported | Do not use the dl_name parameter | Permanent |
| 342 | ESME EXTERNAL ERROR | Invalid message class. | Invalid GSM message class in the data_coding parameter | Learn more: SMPP 3.4 Specification Page 126 | Permanent |
| 343 | ESME EXTERNAL ERROR | Invalid message length. | The carrier rejected the message because its length was invalid or exceeded the allowed limit. Messages containing 10 or more segments will be rejected by some carriers. The message may include excessive characters, special symbols, or unsupported encoding that increases segment count. |
| Permanent |
| 344 | ESME EXTERNAL ERROR | Invalid message reference. | This error occurs very rarely and the exact trigger is unknown. It could be due to a temporary network glitch, a downstream carrier issue, or an unrecognized element in your message. | If you continue to experience this issue, submit a support ticket here: Sinch Support Portal | Permanent |
| 345 | ESME EXTERNAL ERROR | Invalid number of messages. | The destination ESME has exceeded the allowed message limits | If you continue to experience this issue, submit a support ticket here: Sinch Support Portal | Temporary |
| 346 | ESME EXTERNAL ERROR | Invalid predefined message. | This error occurs very rarely and the exact trigger is unknown. It could be due to a temporary network glitch, a downstream carrier issue, or an unrecognized element in your message. | If you continue to experience this issue, submit a support ticket here: Sinch Support Portal | Permanent |
| 347 | ESME EXTERNAL ERROR | Invalid priority flag. | priority_flag parameter contains an illegal or unsupported value. | Check that the priority_flag parameter has priority level of 0, 1, 2, or 3 | Permanent |
| 348 | ESME EXTERNAL ERROR | Invalid replace flag. | Invalid replace_if_present_flag parameter | Check that the replace_if_present_flag parameter is set to 0 or 1 | Permanent |
| 349 | ESME EXTERNAL ERROR | Request failed. | Message could not be delivered because the recipient’s carrier reported a service issue or the message expired before delivery. |
| Permanent |
| 350 | ESME EXTERNAL ERROR | Invalid delivery report request. | An infrequent, uncategorized error. Because the exact cause (internal, external, or message-specific) is unknown, we recommend retrying the message before escalating. | If you continue to experience this issue, submit a support ticket here: Sinch Support Portal | Temporary |
| 360 | ESME EXTERNAL ERROR | Message queue full. | Indicates a resource error within the destination Message Center. This may be caused by the maximum number of messages addressed to a single destination or a global maximum of undelivered messages within the Message Center. | If you continue to experience this issue, submit a support ticket here: Sinch Support Portal | Temporary |
| 361 | ESME EXTERNAL ERROR | External error. | An infrequent, uncategorized error. Because the exact cause (internal, external, or message-specific) is unknown, we recommend retrying the message before escalating. | If you continue to experience this issue, submit a support ticket here: Sinch Support Portal | Temporary |
| 362 | ESME EXTERNAL ERROR | External error. | An error has occurred outside of Sinch, either with the Supplier or the Carrier Network. This could be caused by simple congestion, high messages volumes during peak sending times, supplier/network intermittent issues, supplier/network internal issues, emergency maintenance, etc. | Retry recommended after 30 seconds (up to 3 attempts). If still failing, open a support ticket. | Temporary |
| 370 | ESME EXTERNAL ERROR | Can't find information. | An infrequent, uncategorized error. Because the exact cause (internal, external, or message-specific) is unknown, we recommend retrying the message before escalating. | If you continue to experience this issue, submit a support ticket here: Sinch Support Portal | Temporary |
| 399 | ESME EXTERNAL ERROR | Unknown. | The carrier is experiencing a temporary error that is preventing the message from being processed. | Retry recommended after 30 seconds (up to 3 attempts). If still failing, open a support ticket. | Temporary |
- SMPP Connectivity
- Prefer a REST API? Get started with the REST SMS API.