Messages Outcomes & Errors
Message communications can have the following outcomes:
0 - Delivered - The message has been delivered to the handset
1 - Invalid - This number is permanently invalid
2 - Unavailable - There is an issue with the mobile number or handset
3 - Network error - There is an issue with the network
5 - Expired - The message did not deliver within the validity period
6 - Invalid message structure - The message is expecting a custom value that isn't available.
7 - Invalid contact structure
Invalid contact structure is a code that means it has failed at Webio before the message has been created. This is caused by columns missing from the import file. Invalid message structure is a code that means it has failed after the message has been created but before it has passed to the gateway. This is caused by things like misnamed columns.
9 - Overrun - The message was not sent before the schedule's end time.
10 - Blocklisted - The message was sent as they were on your organisation blocklist
11 - Profanity - The message was blocked from being sent as content within it was identified as being a potential profanity
12 - Rejected - There was an issue with either the message or request
By default, SMS sender IDs are equipped with a flooding protection mechanism designed to prevent clients from overwhelming recipients with excessive messaging.
While you may request its deactivation by emailing us to support@webio.com (this needs your administrator approval), doing so is generally discouraged for most use cases.
Flooding protection thresholds are as follows:
- For varied content: Up to 20 different short messages can be sent within an hour; the 21st message will be rejected.
- For identical content: Only 6 messages with the same text are permitted per hour; the 7th will be rejected.
14 - Unconfirmed - The gateway or network have not confirmed the message has sent or delivered
Error Breakdown
The Network Gateways return numerous error codes, Webio categorises these to make it easier for reporting purposes.
Webio Description Gateway Description
| Busy | MSC is busy handling an exisiting transaction with the handset. The subscriber could be currently receiving an SMS at exactly the same time. |
| Busy | Rejection due to subscriber handset not having the memory capacity to recieve the message. Likely to have been in state for 12 hours or more. |
| Busy | Rejection due to subscriber handset not having the memory capacity to receive the message. Likely to have run out of capacity recently. |
| Busy | Mobile operator blocking the end user from this short code |
| Busy | Short code not provisioned with mobile operator |
| Busy | Program ID rejected by mobile operator |
| Expired | Expired |
| Expired | HLR ERROR - Local Cancel |
| Expired | HLR ERROR - Abort |
| Expired | Message was expired before reaching SMSC. |
| Expired | Message was canceled by user before reaching SMSC. |
| Expired | Message failed due to unknown mobile operator error |
| Expired | Failed message delivery |
| Expired | Message expired before it reached handset |
| Expired | Message submitted to but not acknowledged by mobile operator |
| Expired | Partial message delivery failure |
| Expired | Awaiting complete message delivery status |
| Expired | Temporary system error |
| Expired | Temporary mobile operator system error |
| Expired | Non-retryable mobile operator system error |
| Expired | US standard rate message blocked by the OpenMarket deactivated numbers firewall |
| Invalid number | The outboundChannelAddress is inactive or no longer active. |
| Invalid number | Destination number is not a valid mobile number or its routing cannot be determined. |
| Invalid number | Receiving handset or equipment does not support SMS or an SMS feature. This is temporary because the subscriber could switch to a different device. |
| Invalid number | HLR ERROR - unknown subscriber |
| Invalid number | ESME EXTERNAL ERROR - Invalid source address |
| Invalid number | ESME EXTERNAL ERROR - Request failed |
| Invalid number | Aborted - Unprovisioned region - SMSC rejected the message. The account has not been provisioned for this region. |
| Network error | ROUTING ERROR - Internal routing error |
| Network error | It cannot be determined whether this message has been delivered or has failed due to lack of final delivery state information from the carrier. |
| Network error | ROUTING ERROR - Internal routing error |
| Network error | Rejection due to failed authentication or filtering. |
| Network error | The MSC that the subscriber is currently registered to is experiencing a fault. |
| Network error | Rejection due to SS7 protocol or network failure. |
| Network error | Rejection due to subscriber network decoding error or signalling fault. |
| Network error | Rejection due to subscriber network decoding error or signalling fault. |
| Network error | Rejection due to SS7 protocol or network failure. |
| Network error | Rejection due to subscriber network decoding error or signaling fault. |
| Network error | Rejection due to subscriber network decoding error or signaling fault. |
| Network error | INTERNAL ERROR - Internal error |
| Network error | Generic delivery failure |
| Network error | ESME ERROR - Internal error |
| Network error | Internal SMSC error due to invalid message syntax. |
| Network error | HLR ERROR - System failure |
| Network error | Internal SMSC error caused by SS7 link/dialogue fault. |
| Network error | SMSC cannot decode the response received from destination network due to an encoding or protocol fault. |
| Network error | Subscriber network or signalling partner has terminated the signalling connection |
| Network error | Subscriber network or signalling partner has rejected the signalling connection |
| Network error | Subscriber network not recieving packets from SMSC |
| Network error | Subscriber network or signalling partner has not responded to signalling connection setup or maintenance packets. |
| Network error | Subscriber network refuses signalling connection or message packet. |
| Network error | Signalling with destination network has been prevented by SMSC partner or signalling partner. |
| Network error | SMSC partner or 3rd party signalling partner has prevented messages being sent to this outboundChannelAddress or destination network. |
| Network error | SMSC partner has rejected the message due to an unacceptable message parameter. |
| Network error | SMSC partner could not process this message due to a platform fault |
| Network error | SMSC partner could not process this message due to a platform fault and it will not be retried. |
| Network error | SMSC partner cannot route this message currently |
| Network error | SMSC partner cannot route this message and it will not be retried. |
| Network error | ESME EXTERNAL ERROR - Unknown |
| Network error | An unexpected error caused the message to fail. |
| Network error | Message failed because of temporary delivery failure. Message can be retried. |
| Network error | One or more parameters in the message body has no mapping for this recipient. |
| Network error | SS7 signalling link at destination network |
| Network error | Invalid request type |
| Network error | Carrier ID is not an integer. |
| Network error | Source address is blocked or is not provisioned |
| Network error | Short code expired with mobile operator |
| Network error | Short code blocked by mobile operator |
| Network error | End users connected to this MVNO cannot receive short code messages |
| Network error | Destination address blocked by mobile operator |
| Network error | Destination address not provisioned for SMS |
| Network error | Destination address suspended by mobile operator |
| Network error | Program ID is not provisioned for this mobile operator or is not active |
| Network error | Short code blocked by end user |
| Network error | New subscriptions for this short code are blocked by mobile operator |
| Network error | Account not provisioned to use SMS demo short code |
| Network error | Exceeded the time limit for using SMS demo |
| Network error | Destination address not in whitelist for SMS demo |
| Network error | Exceeded the max number of demo requests |
| Network error | End user out of prepay credit |
| Network error | Exceeded the monthly limit on global MT messaging |
| Network error | SAccount not provisioned for global one- or two-way SMS |
| Network error | Cannot determine which message originator to use |
| Network error | Account has no provisioned address that can reach destination |
| Network error | Interaction not supported for message destination |
| Network error | Your account is not provisioned for global two-way SMS |
| Network error | Content blocked by user opt-out (MO: STOP) |
| Network error | This message was identified as spam and cannot be delivered |
| Network error | Temporary handset failure |
| Network error | Destination overload |
| Network error | Mobile operator network error |
| Network error | SMS rejected by mobile operator for attempted destination address |
| Unavailable | Fault in Number Portability Database or HLR of outboundChannelAddress range holder. Occurs more frequently if number ported more than once in certain countries. |
| Unavailable | Occurs when the MSC that a message has been sent to is not aware of the subscriber IMSI. Suggests HLR has not been updated or MSC malfunction. |
| Unavailable | Rejection due to subscription not supporting SMS. |
| Unavailable | Rejection due to subscription |
| Unavailable | Rejection due to subscription or network not allowing SMS. |
| Unavailable | Rejection due to subscription not supporting SMS. |
| Unavailable | Subscriber handset is not logged onto the network due to it being turned off or out of coverage. Likely to have been unavailable for 12 hours or mor. |
| Unavailable | Subscriber handset is not reachable on the network due to it being turned off or out of coverage. Likely to have very recently become unavailable. |
| Unavailable | Subscriber handset is not reachable on the network due to it being turned off or out of coverage. Likely to have been unavailable for several hours. |
| Unavailable | SCREENING ERROR - Error |
| Unavailable | SCREENING ERROR - Error |
| Unavailable | SCREENING ERROR - Error |
| Unavailable | SCREENING ERROR - Error |
| Unavailable | SCREENING ERROR - Error |
| Unavailable | SMSC ERROR - Reject |
| Unavailable | HLR ERROR - Teleservice not provisioned |
| Unavailable | HLR ERROR - absent subscriber |
| Unavailable | MSC ERROR - Facility not supported |
| Unavailable | MSC ERROR - Equipment protocol error |
| Unavailable | ESME EXTERNAL ERROR - Message queue full |
| Unavailable | SMSC rejected message. Retrying is likely to cause the same error. |
| Unavailable | Invalid request version |
| Unavailable | Invalid request protocol |
| Unavailable | Mobile operator not found for the destination address |
| Unavailable | Unable to determine carrier ID from destination address. |
| Unavailable | Destination address contains non-numeric characters. |
| Unavailable | Invalid destination address |
| Unavailable | Invalid destination address country code |
| Unavailable | Message text is too long |
| Unavailable | Invalid source address |
| Unavailable | Destination address unable to receive SMS |
Related Articles
SMS Length - Message Parts
Quick Trick: A single SMS contains up to 160 standard characters, or 70 characters if any are non-standard. Once you go over then each part of a multi-part message can contain up to 153 (GSM-7) or 67 (USC-2). When you send an SMS the network splits ...Insights
Overview From the Insights screen you can access your insights for every aspect of Webio. Monitor your campaigns, messages, agent activity and more through insightful widgets. Full data export tables are also available. Types of Widgets When ...Webio FAQ
General Why can't I log to my Webio account? If you can't log to your Webio Account, try first to clear your internet browser cache and cookies or to log in from incognito window or a different internet browser (Make sure you are entering your ...Conversations screen elements
Overview When you are on the Conversations screen and you select a queue, the list of conversations stored into it is displayed on the left side of the screen. Selected Conversation Once the queue is selected, clicking on a conversation cards will ...Order and colouring of the conversation's cards
Overview When you select a queue from the conversations screen, you access the list of all conversations stored in that queue. Depending on your permissions, as an agent, you might not be able to see conversations assigned to somebody else - this ...