This error indicates that a message has been blocked by the DLT Provider due to regulatory compliance issues, sender registration, template registration, etc.
Timeout while performing DLT Scrubbing.
The error typically indicates that the sender of a message has been blocked by the DLT Provider. This means that the sender has been restricted from sending messages due to non-compliance with regulations, insufficient registration, or other factors determined by the DLT Provider.
Telemarketer blocked by DLT Scrubbing.
The error typically indicates that the principal entity ID of a message has been blocked by the DLT Provider. This means that the entity has been restricted from sending messages due to non-compliance with regulations, insufficient registration, or other factors determined by the DLT Provider.
The error typically indicates that the template or content of a message has been blocked by the DLT Provider. This means that the message template or content has been restricted from sending messages due to non-compliance with regulations, insufficient registration, or other factors determined by the DLT Provider.
Indicates that the requested principal entity ID could not be found or located. This means that the DLT Provider was unable to locate the specific PE ID being referenced. It could be due to various reasons, such as an incorrect identifier, a non-existent entity, or a misconfiguration.
No entry of entity on the platform.
This error code indicates that the principal entity in question is inactive or disabled. This could be due to various reasons, such as principal entity ID suspension, temporary deactivation, or restrictions. Resolving this error typically check with DLT Provider.
This error code indicates that the requested principal entity has been blocklisted. It means that the entity is restricted or prohibited on DLT Provider, such as violation of policies, non-compliance, or suspicious activity.
This error code suggests that the provided Principal entity ID is an invalid or wrong format or does not exist in the DLT Provider. It means that the principal entity ID is incorrect or unrecognized. Verifying the accuracy of the entity ID or resolving any issues related to the entity's DLT provider can help resolve this error.
Principal entity is not allowed for the TM.
No entry of TMID on the platform.
Telemarketer is inactive on the platform.
Telemarketer is blacklisted on all platforms.
This error code signifies that the requested header/Sender ID information was not found. It means that the DLT Provider could not locate the required header in the given context or request. Review the request structure, and ensure the presence of the necessary headers.
This error code indicates that the requested header is inactive or disabled. It means that the header, typically used to send messages, is currently inactive. Activating the required header or checking for any configuration or permission-related issues on DLT Provider can help resolve this error.
This error code suggests that the requested header has been blocklisted, meaning it is restricted or prohibited from being used. It could be due to policy violations, non-compliance, or suspicious activity.
This error code indicates that the provided PEID (Principal Entity ID) does not match the header/Sender ID information. It means that there is a mismatch between the specified PEID and the associated header in the request. Verifying the accuracy and alignment of the PEID and header on the DLT Provider can help resolve this error.
Header in free pool.
This error code signifies that the requested template could not be found. It means that the DLT Provider was unable to locate the specified template, which is typically used for standardized message formats or content. Verifying the template's existence, and correct identifier, or troubleshooting any issues related to template retrieval can help address this error.
This error code suggests that the requested template is inactive or disabled. It means that the template, which is typically used for predefined message structures, is currently not active on DLT Provider. Activating the required template or addressing any configuration or permission-related issues with DLT Provider can help resolve this error.
This error code indicates that the requested template has been blocklisted, meaning it is restricted or prohibited from being used. It could be due to policy violations, non-compliance, or suspicious activity.
This error code suggests that the requested template does not match the provided content or message. It means that there is a mismatch between the specified template and the actual content being sent. Ensuring the alignment between the registered template and the actual content being sent can help resolve this error.
This error code signifies that the specified header is not registered or associated with the requested template. It means that the header being used does not align with the template requirements or associations. Verifying the registration and linkage between the header and template can help address this error.
This error code indicates that a variable within the template exceeds the maximum allowed length. It means that variables used within the template exceed the defined character limit. Adjusting the character length can help resolve this error.
Error in identifying the template.
This error code suggests that the provided template ID is invalid or does not exist in the system. It means that the template ID/Content ID used to reference a specific template is incorrect or unrecognized. Verifying the accuracy of the template ID or troubleshooting any issues related to the template's existence can help address this error.
This error code signifies that the requested template is not registered or associated with the specified principal entity ID. It means the template being used does not link to the intended principal entity. Verifying the registration and association between the template and principal entity ID can help resolve this error.
Promotional template used on other/transaction header.
Invalid template type.
This error code indicates that the requested preference does not match the specified criteria on the end user number. It means that the preference being used does not align with the end user number.
This error code suggests that the provided promotional time is invalid or outside the allowed range (9 PM to 10 AM). It means that the specified promotional time period does not adhere to the defined constraints or rules.
his error code indicates that the requested category of service entity (SE) has been blocked. It means that the particular category or type of service entity is restricted or prohibited from being used. Resolving this error typically check the category of service entity or DND consent on a specific number.
General error code for Consent.
General error code in case of any exceptions.
This error code suggests that the requested Principal Entity ID (PEID) within the TLV structure was not found. It means that the system or service could not locate the specified PEID within the TLV data. Verifying the correct usage and presence of the PEID within the TLV structure in the SMPP request can help resolve this error.
This error code signifies that the requested Template ID within the TLV structure was not found. It means that the system or service was unable to locate the specified Template ID within the TLV data. Verifying the correct usage and presence of the Template ID within the TLV structure in the SMPP request can help address this error.
Undelivered/expired. If the DLT has not received long SMS parts or if any part is missing, the DLT shows this code.
This error signifies that the header has been suspended due to validity issues concerning DLT compliance. To resolve this, review and ensure that the header information complies with DLT regulations.
This error occurs when the header is suspended due to excessive usage that violates DLT regulations. Evaluate your SMS sending practices, consider reducing the volume of messages sent, and adhere to DLT guidelines.
This error suggests that the header has been suspended due to issues related to the customer's DLT account. Contact your DLT service provider or Support to address and resolve customer-specific DLT compliance concerns.
This error indicates that the template has been suspended due to validity problems concerning DLT compliance. To rectify this, review and correct the template content to ensure it aligns with DLT regulations and standards.
This error arises when the template is suspended due to excessive usage that violates DLT regulations. Optimize your SMS templates or reduce the frequency of template usage to comply with DLT guidelines.
This error implies that the template has been suspended due to issues related to the customer's DLT compliance status. Engage with your DLT service provider or Support to address and resolve customer-specific DLT compliance matters.
This error indicates that the URL in your SMS template has not been safelisted on the DLT platform, a requirement for SMS delivery in accordance with TRAI regulations.
This error indicates that the PE-TM hash was either not received or an empty value was provided in the request.
This error indicates that the submitted PE-TM hash does not match any registered hash for the specified PE.
This error indicates that the status of the PE-TM hash is invalid because one of the telemarketers in the chain is inactive.
This error implies that the status of the PE-TM hash is blocklisted.
This error indicates that the status of the PE-TM hash is suspended by the customer.
Typically, this indicates that the subscriber or recipient of the message is unknown or not recognized by the network.
Verify the subscriber details by dialing the number. If correct, contact Support.
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.
This can occur for reasons such as an invalid or unregistered number, incomplete or incorrect subscriber information, or technical issues.
Verify and correct subscriber information. If correct, contact Support.
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.
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.
The subscriber is roaming in another country or operator’s infrastructure. Delivery is not guaranteed due to a lack of roaming agreements between operators.
Indicates the mobile station failed authentication, often due to the subscriber's number being blacklisted.
Investigate and address the issue with the network operator, or contact Support.
The mobile subscription does not support the requested service (for example, SMS).
Contact the service provider or network operator to activate the required teleservice.
Indicates the IMEI check on the handset failed due to the IMEI being blocklisted or unauthorized.
Use authorized equipment to resolve this issue.
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.
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.
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.
Indicates that the subscriber is busy for MT SMS.
Indicates a failure in delivering an SMS to the recipient, possibly due to unavailability, memory capacity issues, or temporary communication issues.
Verify details or contact Support.
The message waiting list is full.
Indicates a system failure.
Indicates that some data is missing.
Indicates that an unexpected data value has been entered.
Indicates an unknown error.
Indicates that the message inbox on the recipient's mobile phone is full, preventing new messages.
Delete messages to clear space.
There has been a mobile subscriber equipment error.
There has been a mobile subscriber equipment error.
There has been a mobile subscriber equipment error.
There has been a mobile subscriber equipment error.
There has been a mobile subscriber equipment error.
There has been a mobile subscriber equipment error.
General network protocol error caused by incompatible operator network protocol versions or parameters between network components.
The message was processed and forwarded to the operator, but no response was returned.
The error may also apply to SS7 network level issues.
General network protocol error caused by incompatible operator network protocol versions or parameters between network components.
General network protocol error caused by incompatible operator network protocol versions or parameters between network components.
General network protocol error caused by incompatible operator network protocol versions or parameters between network components.
General network protocol error caused by incompatible operator network protocol versions or parameters between network components.
General network protocol error caused by incompatible operator network protocol versions or parameters between network components.
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.
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.
The end user is out of prepaid credit and cannot receive the message.
Retry sending every 24 hours for up to seven days.
There is a temporary handset failure.
The destination address is unable to receive SMS.
General network protocol error caused by incompatible operator network protocol versions or parameters between network components.
General network protocol error caused by incompatible operator network protocol versions or parameters between network components.
General network protocol error caused by incompatible operator network protocol versions or parameters between network components.
General network protocol error caused by incompatible operator network protocol versions or parameters between network components.
General network protocol error caused by incompatible operator network protocol versions or parameters between network components.
General network protocol error caused by incompatible operator network protocol versions or parameters between network components.
General network protocol error caused by incompatible operator network protocol versions or parameters between network components.
The mobile subscriber was not reachable due to a network operator protocol error.
The mobile subscriber was not reachable due to a network operator protocol error.
No translation for this specific address.
The mobile subscriber was not reachable due to a network operator protocol error.
The mobile subscriber was not reachable due to a network operator protocol error.
The mobile subscriber was not reachable due to a network operator protocol error.
The mobile subscriber was not reachable due to a network operator protocol error.
The mobile subscriber was not reachable due to a network operator protocol error.
The mobile subscriber was not reachable due to a network operator protocol error.
The mobile subscriber was not reachable due to a network operator protocol error.
The mobile subscriber was not reachable due to a network operator protocol error.
The mobile subscriber was not reachable due to a network operator protocol error.
The mobile subscriber was not reachable due to a network operator protocol error.
The mobile subscriber was not reachable due to a network operator protocol error.
The mobile subscriber was not reachable due to a network operator protocol error.
The mobile subscriber was not reachable due to a network operator protocol error.
Message was aborted by a network peer due to a network protocol error.
Message was aborted by a network peer due to a network protocol error.
Message was aborted by a network peer due to a network protocol error.
Message was aborted by a network peer due to a network protocol error.
Message was aborted due to other network protocol errors.
Message was aborted due to other network protocol errors.
Message was aborted due to other network protocol errors.
Message was aborted due to other network protocol errors.
Message was aborted due to other network protocol errors.
Message was aborted due to other network protocol errors.
Message was aborted due to other network protocol errors.
Message was aborted due to other network protocol errors.
Message was aborted due to other network protocol errors.
Message was aborted due to other network protocol errors.
Message was aborted due to other network protocol errors.
The request type was invalid.
Invalid destination address.
Possible reasons for receiving this error for the following mobile operators might be:
Any operator:
• The mobile number is not on the mobile operator's network.
• The mobile number has been deactivated.
T-Mobile and MetroPCS:
• The phone number belongs to a prepaid user who does not have enough credit to receive a message.
T-Mobile:
• The end user is not provisioned to receive a message from all short codes (or from specific short codes)
• The end user is on an MVNO connected via T-Mobile.
• T-Mobile does not deliver messages from short codes to end users on MVNOs.
AT&T (US):
• The phone number belongs to a prepaid user who does not have enough credit to receive a message.
• The phone number is not provisioned for any messages.
• The phone number could be blocked due to a spam complaint.
Invalid request - destination address country code is not recognized.
Message text is too long.
Invalid source address value.
The mobile operator rejected the message with an invalid MT source address error. Contact your account manager or reach out to Support to determine if the MT source address should be supported by the end user's mobile operator.
Account access has been denied.
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.
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.
Program ID or campaign ID is not provisioned for this mobile operator or is not active.
The account is not provisioned to use the SMS demo short code.
Exceeded the time limit for using SMS demo.
The destination address is not in the safelist for SMS demo.
Exceeded the maximum number of demo requests.
Invalid global campaign ID.
Account is not provisioned with an address that can reach the destination.
Interaction is not supported for the message destination.
Account is not provisioned for global two-way SMS.
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.
Content blocked by campaign blocklist.
This message was identified as spam and cannot be delivered.
The message has been rejected due to an anti-fraud mechanism.
It means that the risk score of the destination hit the defined threshold and the system blocked the message. In case of a false positive, you can use Signals API(opens in a new tab) to add it to the trusted list.
IMSI is blacklisted.
The destination number has been blacklisted either at the operator`s request or on your account via the web interface.
Go to the web interface(opens in a new tab) to remove the blocklist on your account or contact Support for more information.
The sender number has been blacklisted either at the operator's request or on your account via the web interface.
Go to the web interface(opens in a new tab) to remove the blocklist on your account or contact Support for more information.
The phone number you provided is listed as deactivated, which means it is no longer active and cannot receive messages.
If you included the mobileOperatorId in your request, you can perform an operator lookup to check if the number was ported to a new operator. If you did not include the mobileOperatorId, we have already performed the lookup and confirmed that the number is permanently deactivated. It is crucial to refrain from sending any further messages to this number.
For more details, see the guidelines on handling deactivated phone numbers.
Invalid PDU format.
Your account monthly credit limit has been reached.
For further financial assistance, contact your account manager or contact Support.
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.
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.
Inbound SM cannot be transferred via SMPP due to the lack of SMPP connectivity.
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.
If there is a valid reason for the traffic to bypass the filter, your account manager can assist you with adjusting these limitations, or reach out to Support.
Related to the REJECTED_FLOODING_FILTER status.
The message is rejected due to the number of identical messages sent to a single number.
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.
Indicates that the SS is not compatible.
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.
Indicates an unknown alphabet.
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.
Source address (recipient) is blocked or is not provisioned.
Indicates that the number has either gone over the limit or they are trying to send to Canada and the number is not verified.
Contact your account manager or reach out to Support to get the TFN verified.
An invalid response has been received.
The mobile operator blocked the end user from this short code.
Content blocked by the mobile operator for this end user.
Short code not provisioned with mobile operator.
Contact your dedicated account manager or contact Support if you believe that you are provisioned for the operator or if you want to begin provisioning.
Short code expired with mobile operator.
Contact your dedicated account manager or contact Support if you believe that you are provisioned for the operator or if you want to begin provisioning.
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. Contact your dedicated account manager or reach out to Support if you are unsure why you received this error.
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.
Destination address not provisioned for SMS.
Destination address suspended by the mobile operator.
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. Contact your dedicated account manager or Support if you are unsure why you received this error.
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.
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.
Destination overloaded.
Mobile operator network error.
SMS rejected by the mobile operator for attempted destination address.
Message failed due to an unknown mobile operator error.
Failed message delivery.
Message expired before it reached handset.
Message submitted to but not acknowledged by the mobile operator.
Time out.
The numbers were identified as blacklisted in the operator's DND (Do Not Disturb) database, provided by the operator, or the operator reverted to 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.
Text is blacklisted.
Messages not passed to any operator and failed at the platform.
Not submitted to SMPP channel.
The same message has already been sent to this destination address.
