Not sure how TextbyChoice can help you? Need support on your subscription?
Email us at support[at]textbychoice[dot]com
The message has been delivered.
| ID | Status | Description |
|---|---|---|
| 0 | DELIVERED | Message has been successfully delivered |
| 000 | DELIVERED | Message has been successfully delivered. |
| 2 | DELIVERED_TO_OPERATOR | Message has been successfully delivered to the operator’s system and awaits further processing or delivery to the recipient’s handset. |
| 5 | DELIVERED_TO_HANDSET | Message has been successfully delivered to the recipient’s handset. |
The message has been processed and sent to the next instance, for example, a mobile operator. Note that this does not mean the message has been delivered to the handset. For the full delivery status, use delivery reports instead.
| ID | Status | Description |
|---|---|---|
| 3 | PENDING_WAITING_DELIVERY | Message has been successfully sent from our platform to the operator’s end, but we are awaiting a delivery report from their end. |
| 7 | PENDING_ENROUTE | Message has been successfully accepted and processed by our platform and forwarded to the next instance, which specifically involves the mobile operator. |
| 26 | PENDING_ACCEPTED | Message is pending after being accepted by the system and waiting for further processing or delivery confirmation from the operator. |
The message has not been delivered.
| ID | Status | Description |
|---|---|---|
| 4 | UNDELIVERABLE_REJECTED_OPERATOR | Message was rejected by the operator and deemed undeliverable, possibly due to a network glitch or restrictions imposed by the operator. Resolution steps include contacting Support for further clarification or resolution. |
| 9 | UNDELIVERABLE_NOT_DELIVERED | Message was not delivered to the intended recipient and considered undeliverable, typically due to factors such as an invalid or unreachable destination number. Resolution steps involve verifying the accuracy of the recipient’s number. If the issue persists, contact Support for assistance. |
| 31 | UNDELIVERABLE_NOT_SENT | The message has not been sent. |
| 96 | NO_ANSWER | The call was successfully delivered to the end user device; however, it was not answered by the end user. |
| 97 | BUSY | The call has been successfully delivered to the end user’s device, but the end user’s device indicates that they are currently busy and unable to answer the incoming call. |
| 98 | CANCELLED | The call was canceled at the origination end before it could be successfully routed to the end user. |
The message has been sent and has either expired due to pending past its validity period (our platform defaults to 48 hours), or the delivery report from the operator has returned EXPIRED as a final status.
| ID | Status | Description |
|---|---|---|
| 15 | EXPIRED_EXPIRED | Message was received and sent to the operator. However, it has been pending until the validity period has expired or the operator returns the EXPIRED status. |
| 29 | EXPIRED_DLR_UNKNOWN | Message has expired, and the delivery status is unknown, indicating that the delivery report or confirmation was not received or could not be determined. |
| 87 | SIGNALS_BLOCKED | Message has been rejected due to an anti-fraud mechanism. The message is charged to the customer. |
The message has been received but has either been rejected by provider or the operator has returned REJECTED as final status.
| ID | Status | Description |
|---|---|---|
| 6 | REJECTED_NETWORK | Message has been received, but the network is either out of our coverage or is not set up on your account. |
| 8 | REJECTED_PREFIX_MISSING | Message has been received but rejected as the number is not recognized due to an incorrect number prefix or length. This information is different for each network and is regularly updated. |
| 10 | REJECTED_DND | Message has been received and rejected because the user is subscribed to DND (Do Not Disturb) services, disabling any service traffic to their number. |
| 11 | REJECTED_SOURCE | Your account is set to accept only registered sender IDs, and the sender ID defined in the request has not been registered on your account. |
| 12 | REJECTED_NOT_ENOUGH_CREDITS | Your account is out of credits for further submission. |
| 13 | REJECTED_SENDER | The sender ID has been blocklisted on your account via the web interface. |
| 14 | REJECTED_DESTINATION_BLOCKLISTED | The destination address has been blocklisted either at the operator’s request or on your account via the web interface. |
| 17 | REJECTED_PREPAID_PACKAGE_EXPIRED | Account credits are past their validity period. |
| 18 | REJECTED_DESTINATION_NOT_REGISTERED | Your account has been set up for submission only to a single number for testing purposes. |
| 19 | REJECTED_ROUTE_NOT_AVAILABLE | Message has been received on the system. However, your account has not been set up to send messages, that is, no routes on your account are available for further submission. |
| 20 | REJECTED_FLOODING_FILTER | Message has been rejected due to an anti-flooding mechanism. By default, a single number can only receive 20 varied and 6 identical messages per hour. |
| 21 | REJECTED_SYSTEM_ERROR | The request has been rejected due to an expected system error. |
| 23 | REJECTED_DUPLICATE_MESSAGE_ID | The request has been rejected due to a duplicate message ID specified in the submit request; the message IDs should be a unique value. |
| 24 | REJECTED_INVALID_UDH | Message has been received and our system detected the message was formatted incorrectly because of either an invalid ESM class parameter or an inaccurate amount of characters when using esmclass:64 (UDH). |
| 25 | REJECTED_MESSAGE_TOO_LONG | Message has been received, but the total message length is more than 25 parts, or the message text exceeds 4000 bytes as per our system limitation. |
| 51 | MISSING_TO | The request has been received, but the to parameter has not been set, or it is empty, that is, there must be a valid recipient to send the message to. |
| 52 | REJECTED_DESTINATION | The request has been received, but the destination is invalid—the number prefix is incorrect as it does not match a valid number prefix by any mobile operator. Number length is also taken into consideration when verifying number validity. |
| 87 | SIGNALS_BLOCKED | Message has been rejected due to an anti-fraud mechanism. If the message is deemed fraudulent, it will not be charged. |
| 100 | UNDELIVERABLE_REJECTED_PLATFORM | The request was rejected due to being invalid, malformed, or because the service is temporarily unavailable. Review the request parameters and structure, and try again when the service is accessible. |
MMS status codes
The message has been received but has either been rejected and the operator has reverted to rejected as the final status.
| ID | Status | Description |
|---|---|---|
| 56 | REJECTED_INVALID_NOTIFY_URL | Status is returned when the delivery webhook url is not formatted properly. |
| 77 | REJECTED_MESSAGE_TEXT_TOO_LONG | Message has been received, but due to over 1600 characters it has been rejected. |
The request has not been completed due to handset-related issues.
| ID | Permanent | Error | Description |
|---|---|---|---|
| 1 | true | EC_UNKNOWN_SUBSCRIBER | Typically, this indicates that the subscriber or recipient of the message is unknown or not recognized by the network. |
| 2 | false | EC_UNKNOWN_BASE_STATION | Suggests an error involving an unidentified or unrecognized base station, often in the context of network or communication systems. This could be due to a missing or inaccessible base station. |
| 5 | false | EC_UNIDENTIFIED_SUBSCRIBER | This can occur for reasons such as an invalid or unregistered number, incomplete or incorrect subscriber information, or technical issues.
|
| 6 | false | EC_ABSENT_SUBSCRIBER_SM | Indicates the destination numbers were unreachable, powered off, or in an area with limited coverage. Ensure the subscriber’s device is turned on and has a stable network connection. |
| 7 | false | EC_UNKNOWN_EQUIPMENT | The mobile device has not been recognized by EIR (Equipment Identity Register) during device verification on the MAP protocol level at the operator’s infrastructure. |
| 8 | false | EC_ROAMING_NOT_ALLOWED | The subscriber is roaming in another country or operator’s infrastructure. Delivery is not guaranteed due to a lack of roaming agreements between operators. |
| 9 | true | EC_ILLEGAL_SUBSCRIBER | Indicates the mobile station failed authentication, often due to the subscriber’s number being blocklisted. |
| 11 | true | EC_TELESERVICE_NOT_PROVISIONED | The mobile subscription does not support the requested service (for example, SMS). Contact the service provider or network operator to activate the required teleservice. |
| 12 | true | EC_ILLEGAL_EQUIPMENT | Indicates the IMEI check on the handset failed due to the IMEI being blocklisted or unauthorized. Use authorized equipment to resolve this issue. |
| 13 | false | EC_CALL_BARRED | The operator suspended the subscriber’s service, usually for unpaid invoices. Check the subscriber’s account status and ensure sufficient balance or contact the network operator to resolve. |
| 21 | false | EC_FACILITY_NOT_SUPPORTED | The requested service is not supported by the handset or network. Verify the supported facilities and ensure compatibility. Restart the device and apply the latest software/firmware updates. |
| 27 | false | EC_ABSENT_SUBSCRIBER | Indicates the destination numbers were unreachable, powered off, or in an area with limited coverage. Ensure the subscriber’s device is turned on and has a stable network connection. |
| 31 | false | EC_SUBSCRIBER_BUSY_FOR_MT_SMS | Indicates that the subscriber is busy for MT SMS. |
| 32 | false | EC_SM_DELIVERY_FAILURE | Indicates a failure in delivering an SMS to the recipient, possibly due to unavailability, memory capacity issues, or temporary communication issues.
|
| 33 | false | EC_MESSAGE_WAITING_LIST_FULL | The message waiting list is full. |
| 34 | false | EC_SYSTEM_FAILURE | Indicates a system failure. |
| 35 | false | EC_DATA_MISSING | Indicates that some data is missing. |
| 36 | false | EC_UNEXPECTED_DATA_VALUE | Indicates that an unexpected data value has been entered. |
| 255 | false | EC_UNKNOWN_ERROR | Indicates an unknown error. |
| 256 | false | EC_SM_DF_MEMORYCAPACITYEXCEEDED | Indicates that the message inbox on the recipient’s mobile phone is full, preventing new messages. Delete messages to clear space. |
| 257 | false | EC_SM_DF_EQUIPMENTPROTOCOLERROR | There has been a mobile subscriber equipment error. |
| 258 | false | EC_SM_DF_EQUIPMENTNOTSM_EQUIPPED | There has been a mobile subscriber equipment error. |
| 259 | false | EC_SM_DF_UNKNOWNSERVICECENTRE | There has been a mobile subscriber equipment error. |
| 260 | false | EC_SM_DF_SC_CONGESTION | There has been a mobile subscriber equipment error. |
| 261 | false | EC_SM_DF_INVALIDSME_ADDRESS | There has been a mobile subscriber equipment error. |
| 262 | false | EC_SM_DF_SUBSCRIBERNOTSC_SUBSCRIBER | There has been a mobile subscriber equipment error. |
| 500 | false | EC_PROVIDER_GENERAL_ERROR | General network protocol error caused by incompatible operator network protocol versions or parameters between network components. |
| 502 | false | EC_NO_RESPONSE | The message was processed and forwarded to the operator, but no response was returned. The error may also apply to SS7 network level issues. |
| 503 | false | EC_SERVICE_COMPLETION_FAILURE | General network protocol error caused by incompatible operator network protocol versions or parameters between network components. |
| 504 | false | EC_UNEXPECTED_RESPONSE_FROM_PEER | General network protocol error caused by incompatible operator network protocol versions or parameters between network components. |
| 507 | false | EC_MISTYPED_PARAMETER | General network protocol error caused by incompatible operator network protocol versions or parameters between network components. |
| 508 | false | EC_NOT_SUPPORTED_SERVICE | General network protocol error caused by incompatible operator network protocol versions or parameters between network components. |
| 509 | false | EC_DUPLICATED_INVOKE_ID | General network protocol error caused by incompatible operator network protocol versions or parameters between network components. |
| 565 | true | EC_CANNOT_RECEIVE_SC | End users connected to this MVNO cannot receive short code messages. The mobile operator rejected the message as the end user is connected to their network via an MVNO. This restriction applies to short code messages. |
| 573 | true | EC_SC_BLOCKED_BY_END_USER | The end user has asked their mobile operator to block messages sent from your short code. Additional messages must not be sent unless the end user opts in again. |
| 581 | false | EC_USER_OUT_OF_CREDIT | The end user is out of prepaid credit and cannot receive the message. Retry sending every 24 hours for up to seven days. |
| 628 | true | EC_TEMPORARY_HANDSET_FAILURE | There is a temporary handset failure. |
| 629 | true | EC_DEST_ADDRESS_UNABLE_TO_RECEIVE_SMS | The destination address is unable to receive SMS. |
| 1024 | false | EC_OR_APPCONTEXTNOTSUPPORTED | General network protocol error caused by incompatible operator network protocol versions or parameters between network components. |
| 1025 | false | EC_OR_INVALIDDESTINATIONREFERENCE | General network protocol error caused by incompatible operator network protocol versions or parameters between network components. |
| 1026 | false | EC_OR_INVALIDORIGINATINGREFERENCE | General network protocol error caused by incompatible operator network protocol versions or parameters between network components. |
| 1027 | false | EC_OR_ENCAPSULATEDAC_NOTSUPPORTED | General network protocol error caused by incompatible operator network protocol versions or parameters between network components. |
| 1028 | false | EC_OR_TRANSPORTPROTECTIONNOTADEQUATE | General network protocol error caused by incompatible operator network protocol versions or parameters between network components. |
| 1029 | false | EC_OR_NOREASONGIVEN | General network protocol error caused by incompatible operator network protocol versions or parameters between network components. |
| 1030 | false | EC_OR_POTENTIALVERSIONINCOMPATIBILITY | General network protocol error caused by incompatible operator network protocol versions or parameters between network components. |
| 1031 | false | EC_OR_REMOTENODENOTREACHABLE | The mobile subscriber was not reachable due to a network operator protocol error. |
| 1152 | false | EC_NNR_NOTRANSLATIONFORANADDRESSOFSUCHNATURE | The mobile subscriber was not reachable due to a network operator protocol error. |
| 1153 | false | EC_NNR_NOTRANSLATIONFORTHISSPECIFICADDRESS | No translation for this specific address. |
| 1154 | false | EC_NNR_SUBSYSTEMCONGESTION | The mobile subscriber was not reachable due to a network operator protocol error. |
| 1155 | false | EC_NNR_SUBSYSTEMFAILURE | The mobile subscriber was not reachable due to a network operator protocol error. |
| 1156 | false | EC_NNR_UNEQUIPPEDUSER | The mobile subscriber was not reachable due to a network operator protocol error. |
| 1157 | false | EC_NNR_MTPFAILURE | The mobile subscriber was not reachable due to a network operator protocol error. |
| 1158 | false | EC_NNR_NETWORKCONGESTION | The mobile subscriber was not reachable due to a network operator protocol error. |
| 1159 | false | EC_NNR_UNQUALIFIED | The mobile subscriber was not reachable due to a network operator protocol error. |
| 1160 | false | EC_NNR_ERRORINMESSAGETRANSPORTXUDT | The mobile subscriber was not reachable due to a network operator protocol error. |
| 1161 | false | EC_NNR_ERRORINLOCALPROCESSINGXUDT | The mobile subscriber was not reachable due to a network operator protocol error. |
| 1162 | false | EC_NNR_DESTINATIONCANNOTPERFORMREASSEMBLYXUDT | The mobile subscriber was not reachable due to a network operator protocol error. |
| 1163 | false | EC_NNR_SCCPFAILURE | The mobile subscriber was not reachable due to a network operator protocol error. |
| 1164 | false | EC_NNR_HOPCOUNTERVIOLATION | The mobile subscriber was not reachable due to a network operator protocol error. |
| 1165 | false | EC_NNR_SEGMENTATIONNOTSUPPORTED | The mobile subscriber was not reachable due to a network operator protocol error. |
| 1166 | false | EC_NNR_SEGMENTATIONFAILURE | The mobile subscriber was not reachable due to a network operator protocol error. |
| 1281 | false | EC_UA_USERSPECIFICREASON | Message was aborted by a network peer due to a network protocol error. |
| 1282 | false | EC_UA_USERRESOURCELIMITATION | Message was aborted by a network peer due to a network protocol error. |
| 1283 | false | EC_UA_RESOURCEUNAVAILABLE | Message was aborted by a network peer due to a network protocol error. |
| 1284 | false | EC_UA_APPLICATIONPROCEDURECANCELLATION | Message was aborted by a network peer due to a network protocol error. |
| 1536 | false | EC_PA_PROVIDERMALFUNCTION | Message was aborted due to other network protocol errors. |
| 1537 | false | EC_PA_SUPPORTINGDIALOGORTRANSACTIONREALEASED | Message was aborted due to other network protocol errors. |
| 1538 | false | EC_PA_RESSOURCELIMITATION | Message was aborted due to other network protocol errors. |
| 1539 | false | EC_PA_MAINTENANCEACTIVITY | Message was aborted due to other network protocol errors. |
| 1540 | false | EC_PA_VERSIONINCOMPATIBILITY | Message was aborted due to other network protocol errors. |
| 1541 | false | EC_PA_ABNORMALMAPDIALOG | Message was aborted due to other network protocol errors. |
| 1792 | false | EC_NC_ABNORMALEVENTDETECTEDBYPEER | Message was aborted due to other network protocol errors. |
| 1793 | false | EC_NC_RESPONSEREJECTEDBYPEER | Message was aborted due to other network protocol errors. |
| 1794 | false | EC_NC_ABNORMALEVENTRECEIVEDFROMPEER | Message was aborted due to other network protocol errors. |
| 1795 | false | EC_NC_MESSAGECANNOTBEDELIVEREDTOPEER | Message was aborted due to other network protocol errors. |
| 1796 | false | EC_NC_PROVIDEROUTOFINVOKE | Message was aborted due to other network protocol errors. |
User error occurred.
| ID | Permanent | Error | Description |
|---|---|---|---|
| 323 | true | EC_INVALID_REQUEST_TYPE | The request type was invalid. |
| 351 | false | EC_INVALID_DESTINATION_ADDRESS | Invalid destination address. Possible reasons for receiving this error for the following mobile operators might be: Any operator: T-Mobile and MetroPCS: T-Mobile: AT&T (US): |
| 352 | true | EC_INVALID_REQUEST_DESTINATION | Invalid request – destination address country code is not recognized. |
| 355 | true | EC_MSG_TEXT_TOO_LONG | Message text is too long. |
| 368 | true | EC_INVALID_SOURCE_ADDRESS | Invalid source address value. The mobile operator rejected the message with an invalid MT source address error. |
| 433 | true | EC_ACCOUNT_ACCESS_DENIED | Account access has been denied. |
| 541 | false | EC_LIMIT_REACHED | Carrier sending limit has been reached. The message was blocked by AT&T because the TPS (transactions per second) limit on your messaging campaign has been exceeded. |
| 542 | false | EC_QUOTA_REACHED | Carrier daily quota reached. The message was blocked by T-Mobile because the daily volume limit for your brand has been exceeded. You cannot resend the message until the next day. |
| 572 | true | EC_CAMPAIGNID_NOT_PROVISIONED | Program ID or campaign ID is not provisioned for this mobile operator or is not active. |
| 577 | true | EC_ACC_NOT_PROVISIONED_TO_SMS_DEMO_SC | The account is not provisioned to use the SMS demo short code. |
| 578 | true | EC_EXCEEDED_THE_TIME_LIMIT_OF_SMS_DEMO | Exceeded the time limit for using SMS demo. |
| 579 | true | EC_DEST_ADDRESS_NOT_IN_SMS_DEMO | The destination address is not in the safelist for SMS demo. |
| 580 | true | EC_EXCEEDED_THE_MAX_NUMBER | Exceeded the maximum number of demo requests. |
| 594 | true | EC_INVALID_GLOBAL_CAMPAIGN_ID | Invalid global campaign ID. |
| 597 | true | EC_ACC_HAS_NO_ADRESS_FOR_DESR | Account is not provisioned with an address that can reach the destination. |
| 598 | true | EC_INTERACTION_NOT_SUPPORTED | Interaction is not supported for the message destination. |
| 601 | true | EC_ACC_NOT_2_WAY | Account is not provisioned for global two-way SMS. |
| 603 | true | EC_CONTENT_BLOCKED | Content blocked by user opt-out (MO: STOP). This code can be returned in a delivery receipt for an MT originating from a North American, SMS-enabled toll-free number or an SMS-enabled landline number. Messaging can resume to the end user if the end user opts back into your program. |
| 604 | true | EC_BLOCKED_BY_CAMPAIGN_BLACKLIST | Content blocked by campaign blocklist. |
| 607 | true | EC_REJECTED_SPAM_BY_OPERATOR | This message was identified as spam and cannot be delivered. |
| 608 | false | EC_SIGNALS_BLOCKED | The message has been rejected due to an anti-fraud mechanism. |
| 609 | true | EC_SIGNALS_HARD_LIMIT_REACHED | The daily system-defined limit for sent messages (UTC-based) has been reached. |
| 2049 | true | EC_IMSI_BLACKLISTED | IMSI is blocklisted. |
| 2052 | true | EC_BLACKLISTED_DESTINATIONADDRESS | The destination number has been blocklisted either at the operator`s request or on your account via the web interface. |
| 2053 | true | EC_BLACKLISTED_SENDERADDRESS | The sender number has been blocklisted either at the operator’s request or on your account via the web interface. |
| 3041 | true | EC_DEACTIVATED_LIST | The phone number you provided is listed as deactivated, which means it is no longer active and cannot receive messages. If you included the For more details, see the guidelines on handling deactivated phone numbers. |
| 4096 | true | EC_INVALID_PDU_FORMAT | Invalid PDU format. |
| 4099 | true | EC_MONTHLY_LIMIT_REACHED | Your account monthly credit limit has been reached. For further financial assistance, contact your account manager or contact Support. |
| 4100 | true | EC_MESSAGE_CANCELED | The request was received, but has not been sent to the next instance within its validity period and has expired with the appropriate error code, or the same error code was reverted from the operator. |
| 4101 | true | EC_VALIDITY_EXPIRED | The message was sent to the next instance and has not been delivered within the message validity period, thus it has expired with the appropriate error code, or the error code was reverted from the operator. |
| 4102 | true | EC_NOTSUBMITTEDTOSMPPCHANNEL | Inbound SM cannot be transferred via SMPP due to the lack of SMPP connectivity. |
| 4103 | true | EC_DESTINATION_FLOODING | As per the flooding filter rule, you can send 6 messages with the same content to the same destination in one hour while or you can send up to 20 messages with different content to the same destination in a period of one hour. |
| 4104 | true | EC_DESTINATION_TXT_FLOODING | Related to the The message is rejected due to the number of identical messages sent to a single number. |
| 4202 | true | EC_10DLC_LIMIT_REACHED | Message was not delivered due to 10DLC operator limit. |
The request has not been completed due to operator issues.
| ID | Permanent | Error | Description |
|---|---|---|---|
| 10 | true | EC_BEARER_SERVICE_NOT_PROVISIONED | Suggests that the requested bearer service is not available or activated for the user or device attempting to access it. This can be due to service unavailability in the subscription, lack of network support, or configuration/provisioning issues. Resolving this error typically involves contacting the service provider or network operator to ensure the necessary bearer service is provisioned and activated for the subscriber’s account. |
| 20 | false | EC_SS_INCOMPATIBILITY | Indicates that the SS is not compatible. |
| 51 | true | EC_RESOURCE_LIMITATION | Indicates that invoked MAP operation could not be finished due to the network congestion – this is an SS7 network congestion error on the MAP protocol level. |
| 71 | false | EC_UNKNOWN_ALPHABET | Indicates an unknown alphabet. |
| 345 | true | EC_OPERATOR_NOT_FOUND | Mobile operator not found for the destination address. The service performed a dynamic carrier lookup for the destination address, but it could not be identified; or, the MT source address is not a North American toll-free phone number or landline. |
| 375 | true | EC_SOURCE_ADDRESS_IS_BLOCKED | Source address (recipient) is blocked or is not provisioned. |
| 488 | true | EC_TF_NUMBER_NOT_VERIFIED | Indicates that the number has either gone over the limit or they are trying to send to Canada and the number is not verified. |
| 501 | false | EC_INVALID_RESPONSE_RECEIVED | An invalid response has been received. |
| 560 | true | EC_SC_BLOCKED_FOR_END_USER | The mobile operator blocked the end user from this short code. |
| 561 | true | EC_CONTENT_BLOCKED_BY_OPERATOR | Content blocked by the mobile operator for this end user. |
| 562 | true | EC_SC_NOT_PROVISIONED | Short code not provisioned with mobile operator. |
| 563 | true | EC_SC_EXPIRED | Short code expired with mobile operator. |
| 564 | true | EC_SC_BLOCKED | Short code blocked by mobile operator. The mobile operator rejected the message as the short code is currently blocked from sending messages across their network. |
| 566 | true | EC_DESTINATION_BLOCKED_BY_OPERATOR | The mobile operator is blocking the phone number from receiving messages from short codes. This is likely due to the end user’s account being suspended or barred in some way. |
| 568 | true | EC_DESTINATION_NOT_SMS_PROVISIONED | Destination address not provisioned for SMS. |
| 569 | true | EC_DEST_ADDRESS_SUSPENDED | Destination address suspended by the mobile operator. |
| 571 | false | EC_CAMPAIGN_ID_REJECTED | Program ID or Campaign ID rejected by the mobile operator. This error applies to messages sent to US mobile operators. The error indicates that the program ID or campaign ID in the message request is not provisioned with the mobile operator. |
| 574 | true | EC_BLOCKED_NEW_SUBSCRIPTIONS_FOR_SC | New subscriptions for this short code are blocked by the mobile operator. Indicates that for a given short code, new subscribers are not allowed to receive or send messages. However, existing subscribers are still allowed to receive and send messages. |
| 592 | true | EC_ACCOUNT_NOT_PROVISIONED_FOR_SMS | The end user’s number belongs to a network for which the account is not provisioned, or we do not provide coverage for the specific network. |
| 630 | true | EC_DEST_OVERLOADED | Destination overloaded. |
| 631 | true | EC_MOBILE_OPERATOR_NETWORK_ERROR | Mobile operator network error. |
| 632 | true | EC_SMS_REJECTED_BY_MOBILE_OPERATOR | SMS rejected by the mobile operator for attempted destination address. |
| 633 | true | EC_UNKNOWN_MOBILE_OPERATOR | Message failed due to an unknown mobile operator error. |
| 810 | true | EC_FAILED_MESSAGE_DELIVERY | Failed message delivery. |
| 811 | true | EC_MESSAGE_EXPIRED | Message expired before it reached handset. |
| 815 | true | EC_MESSAGE_SUBMITTED_NOT_ACKED | Message submitted to but not acknowledged by the mobile operator. |
| 2048 | false | EC_TIME_OUT | Time out. |
| 2050 | true | EC_DEST_ADDRESS_BLACKLISTED | The numbers were identified as blocklisted in the operator’s DND (Do Not Disturb) database, provided by the operator, or the operator reverted the same error code. Resolving this error typically involves reviewing the blocklist status of the destination address, checking for any legitimate reasons for blocklisting, and taking appropriate actions to remove it. |
| 2051 | false | EC_INVALIDMSCADDRESS | Text is blocklisted. |
| 4097 | false | EC_NOTSUBMITTEDTOGMSC | Messages not passed to any operator and failed at the platform. |
| 4102 | true | EC_NOTSUBMITTEDTOSMPPCHANNEL | Not submitted to SMPP channel. |
| 5492 | true | EC_DUPLICATE_MESSAGE | The same message has already been sent to this destination address. |
| Code | Description | Friendly Description | Explanation Of Error |
| 4001 | service-not-allowed | Message was rejected for reasons other than those covered by other 4xxx codes | This is a general error that the service you are attempting to use is not allowed; you may have inaccurate permissions, formatting or may not be enable to use that service. |
| 4301 | malformed-invalid-encoding | Malformed message encoding | The message contains invalid characters that are not supported. TextByChoice cannot re-encode message for destination. |
| 4302 | malformed-invalid-from-number | Malformed 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). |
| 4303 | malformed-invalid-to-number | Malformed 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). |
| 4350 | malformed-for-destination | Malformed message encoding | Message passed validation on receive stage, but failed on send. This is likely because the destination number (To) is an invalid number. |
| 4360 | message-not-sent-expiration-date-passed | Message expired | Message was not sent because the specified expiration date passed before the message was able to send |
| 4401 | rejected-routing-error | TBC is unable to route the message | Message is unable to be routed within TextByChoice 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. |
| 4403 | rejected-forbidden-from-number | Messaging forbidden on From number | Messaging on this From number is forbidden most commonly because the number does not belong to TBC or the account. Other reasons include: the TN is not enabled in the TextByChoice Dashboard, 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). |
| 4404 | rejected-forbidden-to-number | Messaging forbidden on To number | Messaging on this To number is forbidden. This could be the number is not active, not enabled for messaging or is an invalid number (i.e. 11111111111) |
| 4405 | rejected-unallocated-from-number | Unallocated from number | The From telephone number is considered unallocated when the number does not exist in our database as an active number. This number is either not enabled for messaging at the industry level, or the number is not yet released in the industry |
| 4406 | rejected-unallocated-to-number | 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. |
| 4407 | rejected-account-not-defined-from-number | From Number is associated with account | Undefined source account id. The From number associated with this message is not associated with this account, is an invalid number or not configured appropriately to send messages. |
| 4408 | rejected-account-not-defined-to-number | To Number not associated with account | Undefined destination account id. The To (destination) number is not associated with an account, is an invalid number or not configured correctly to receive messages. |
| 4409 | rejected-invalid-from-profile | Invalid destination profile | TextByChoice failed to create destination. The destination profile is considered invalid, most often this is because the destination number does not support MMS. |
| 4410 | media-unavailable | Could not download media | There was an error retrieving the media from the media web server. Check the media URL and try to access directly to see if the media can be fetched successfully. |
| 4411 | rejected-message-size-limit-exceeded | Combined size of media too large | The total size of MMS message media/attachments exceeded the max file size supported |
| 4412 | media-content-invalid | Failed to parse Content-Type for media | The media content type is not a supported media content type. |
| 4420 | rejected-carrier-does-not-exist | No Route to Destination Carrier | The upstream carrier associated with the message does not exist in TextByChoice configuration |
| 4421 | rejected-forbidden-no-destination | No Route to Destination Carrier | The message cannot be sent downstream as the account associated with the message does not have permission to send to this destination. You may not be provisioned to send to this destination. |
| 4431 | rejected-forbidden-shortcode | Messaging on shortcode forbidden | The message cannot be sent as the account associated with the message is not provisioned for Short code messaging |
| 4432 | rejected-forbidden-country | Messaging to country forbidden | TextByChoice system indicates the account associated with the message is not enabled for messaging this zone, this country or this country is outside of messaging reach (specifically for MMS). |
| 4433 | rejected-forbidden-tollfree | Messaging on Toll Free Number Forbidden | The account associated with this message is not enabled for toll free messaging |
| 4434 | rejected-forbidden-tollfree-for-recipient | Messaging to Toll Free Number Forbidden | Messaging to this toll free number is not allowed. Number is likely not enabled for messaging or not active. |
| 4435 | forbidden-too-many-recipients | Too Many Recipients | The group message has too many recipients. When sending Group Messages, there’s a maximum of 10 participants in a Group. |
| 4451 | rejected-wrong-user-id | Invalid User Id | The user id is not a valid id. Verify the user ID and retry the message |
| 4452 | rejected-wrong-application-id | Invalid Application ID | The Application ID specified is not a valid Application Id, or the Application ID is not associated with the account |
| 4470 | rejected-spam-detected | Rejected as SPAM | This message has been filtered and blocked by TextByChoice for spam. Messages can be blocked for a variety of reason, including but not limited to volumetric filtering, content blocking, SHAFT violation, etc. |
| 4481 | rejected-from-number-in-blacklist | From Number in black list | The From number has been flagged by TextByChoice as prohibited from sending messages. This is typically because TextByChoice or a downstream carriers has several violations; reports of spam, P2P violations, associated with this number. |
| 4482 | rejected-to-number-in-blacklist | To Number in black list | The number you are attempting to send to is blocked from receiving messages. |
| 4492 | reject-emergency | Message to emergency number forbidden | Messaging to an emergency number is forbidden |
| 4493 | rejected-unauthorized | Unauthorized | TextByChoice service indicates the sender is not authorized to send messages from the account. |
| Code | Description | Friendly Description | Explanation Of Error |
| 4700 | invalid-service-type | Carrier Rejected as 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. |
| 4701 | destination-service-unavailable | Destination is not reachable and SMS service is not available. | Carrier service is reporting the destination is not reachable or the SMS service is not available. |
| 4702 | destination-subscriber-unavailable | Destination subscriber is unavailable. | This error indicates the subscriber is unavailable. There are several reasons for this; the subscriber has turned off 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. |
| 4711 | rejected-message-size-limit-exceeded | Media size too large | Downstream vendor cannot retrieve the media as the MMS attachment is too large |
| 4712 | media-content-invalid | The media content type is not supported | The media content type is not supported. Please review the accepted media types. At present supported media files are jpg, gif, txt, vcf. |
| 4720 | invalid-destination-address | Carrier Rejected as 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 toll free messages to TMobile, this could also mean the user has opted to block all toll free and short code traffic |
| 4721 | destination-tn-deactivated | TN on deactivation list | 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. |
| 4730 | no-route-to-destination-carrier | No route to destination carrier or no roaming route exists. | Carrier is reporting there is no route available for message. This could be because no routing exists to destination, no roaming route is available, the destination handset is roaming on a network that cannot be reached, no SS7 route, or routing was denied |
| 4740 | invalid-source-address-address | Carrier Rejected as Invalid Source Address | Carrier is rejecting the message due to invalid source address – the number does not exist in the numbering plan. Other reasons for this error code is the source carrier is invalid or disabled or source not authorized or the number type is not supported. |
| 4750 | destination-rejected-message | Carrier Rejected Message | The destination carrier has rejected the message but provided no specific reason. 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 |
| 4751 | destination-rejected-message-size-invalid | Message is too long or message length is invalid for the carrier. | Carrier has rejected for message length is invalid or too long. |
| 4752 | destination-rejected-malformed | Message is malformed for the carrier. | Carrier is rejecting the message malformed; this could be because of a blank message, unacceptable data value, the receiving SMSC or SME does not accept messages with more than 160 characters, syntax error, content is invalid, 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. |
| 4770 | destination-spam-detected | Carrier Rejected as SPAM | The Carrier is reporting this message as blocked for SPAM. Spam blocks could be a result of content, SHAFT violations (including specific keywords), originating address has been flagged for repeated spam content |
| 4771 | rejected-shortened-url | Rejected due to shortened url | There was an error with the shortened URL used. TextByChoice recommends customers obtain their own dedicated domain if shortened links are needed for their messaging campaign. |
| 4775 | destination-rejected-due-to-user-opt-out | Carrier Rejected due to user opt out | User has opted out of receiving messages from a particular sender. Remove the destination TN from subscriber list and cease communication with the destination. |
| 4780 | volume-violation-tmo | T-Mobile rejected due to volumetric violation | T-Mobile rejected 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. |
| 4781 | volume-violation-att | AT&T rejected due to 10DLC volumetric violation or throttling | AT&T rejected 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. |
| 4785 | volumetric-violation | Carrier rejected due to 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. |
| 4790 | destination-rejected-sc-not-allowed | Carrier Rejected Due to Short Code Restriction | Carrier Rejected Due to Short Code Restriction. Destination address blocked by mobile operator, destination cannot receive short code messages, or the mobile operator blocked the destination from receiving messages from this short code for some other reason. |
| 4791 | destination-rejected-campaign-not-allowed | Carrier Rejected Short Code Campaign Not Allowed | Carrier Rejected SC Campaign Not Allowed or blocked by the mobile operator |
| 4792 | destination-rejected-sc-not-provisioned | Carrier Rejected Short Code Not Provisioned | Short Code not provisioned on mobile operator’s network. |
| 4793 | destination-rejected-sc-expired | Carrier Rejected Short Code Expired | Short Code expired with the mobile operator |
| 4795 | tfn-not-verified | Toll Free number is 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. |
Not sure how TextbyChoice can help you? Need support on your subscription?
Email us at support[at]textbychoice[dot]com