While reviewing your SMS notice failures, you may run across a number of reasons for the error. The list below covers some of the most common errors we run into.
- 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). - Carrier Application Error
The carrier is reporting a general error associated with their application processing the 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 Additionally, for toll free messages to TMobile, this could also mean the user has opted to block all toll free and short code traffic - 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. - Carrier Violation
Most often related to a content issue in the message. Have you recently changed your notification template? Does your text-message content contain a link shortener (like bit.ly)? Open a ticket with Unique if you have any concerns. - Landline or Unreachable Carrier
Most often this occurs when the phone number provided is a landline or the destination phone line is currently out of service.
- Messaging to Country Forbidden
MessageBee 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). - Timed out waiting for delivery receipt. The reason a delivery receipt was not received is not known.
MessageBee timed out waiting for the delivery receipt, this could be because the downstream provider did not send the requested delivery receipt or they sent after the system timed out at two hours.
- Unknown Error
MessageBee has run into a previously unknown issue in the system. - Unknown Error from Downstream
The destination phone carrier has reported an internal error code unknown to MessageBee.
- Unknown Destination Handset / Unreachable Destination Handset
Most often this error comes up due to the destination phone number being a landline and not a mobile number. - 501
This is a general error message provided when the message is unable to send as no destination is available.
The failure reasons below are generally associated with an error or problem with your organizations configuration within Unique and how Unique has registered your organization with the telecommunication companies through which text-messages flow. Unique is responsible for ensuring that this registration is complete and Unique does monitor proactively for these errors to address them if they do come up. If you see these, don't hesitate to open a ticket with Unique!
- 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. - 30024
The number you are attempting from does not currently have a Numeric Sender ID for the specific carrier.
- 30034
You are sending messages to the US using a US 10DLC number that is not associated with an approved A2P 10DLC Campaign. - 30035
is still in the process of registering your number for US A2P 10DLC.