000 – DELIVERED
Group ID: 1
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. |
Group ID: 2
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. |
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. |
31 | UNDELIVERABLE_NOT_SENT | The message has not been sent. |
Group ID: 3
The message has been delivered.
ID | Status | Description |
---|---|---|
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. |
Group ID: 4
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. |
Group ID: 5
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. |
Group ID: 6
OTHER ERROR CODES
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 here. |
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
Cookie | Duration | Description |
---|---|---|
cookielawinfo-checkbox-analytics | 11 months | This cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Analytics". |
cookielawinfo-checkbox-functional | 11 months | The cookie is set by GDPR cookie consent to record the user consent for the cookies in the category "Functional". |
cookielawinfo-checkbox-necessary | 11 months | This cookie is set by GDPR Cookie Consent plugin. The cookies is used to store the user consent for the cookies in the category "Necessary". |
cookielawinfo-checkbox-others | 11 months | This cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Other. |
cookielawinfo-checkbox-performance | 11 months | This cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Performance". |
viewed_cookie_policy | 11 months | The cookie is set by the GDPR Cookie Consent plugin and is used to store whether or not user has consented to the use of cookies. It does not store any personal data. |