Delivery Report Availability by Network
Overview
The delivery report reason codes which may be returned for a given MT message will vary depending on the destination network. The tables below give a summary of which reason codes may be returned.
The Billing nibble and Network byte are independent of the report type and reason bytes, and these are therefore left unspecified in the tables below. They are represented by the character ‘.’.
Contents
- Delivery report reason codes available for MT messages to main US networks
- Delivery report reason codes available for MT messages to TIER3US networks
- Delivery report reason codes available for MT messages to Canadian networks
- Delivery report reason codes available for premium MT messages to Australian networks
- Delivery report reason codes available for premium and bulk MT messages to other networks
Delivery report reason codes available for MT messages to main US networks
 |
May be returned for any MT message |
 |
Returned only for premium MT messages |
REASON_
An unexpected error occurred during delivery, where we cannot differentiate between a system failure (some part of system not functioning correctly) and an expected failure (unknown subscriber, etc).
REASON_
The message exceeded its validity period before a delivery attempt could be made.
REASON_
An unexpected error occurred during billing, where we cannot differentiate between a system failure (some part of system not functioning correctly) and an expected failure (subscriber out of credit, etc).
REASON_
Billing of prepay subscribers is not supported on this network.
REASON_
Charges to this subscriber have been barred - no further information available from network.
REASON_
This charge has been rejected by the network. Used where none of the reasons below apply, but we believe that the subscriber is still billable (unlike REASON_REJECTED_BILLING_PSMSBARRED).
REASON_
On networks where the network controls an opt-in process (eg, AT&T USA OPPC), this reason code is returned if no positive opt-in is received within the timelimit allowed by the network.
REASON_
A previously-active subscription billing mandate has now terminated. No further billing should be performed under this subscription.
REASON_
This charge exceeds the terms (eg, monthly limit) of a subscription billing mandate.
REASON_
On networks where the network controls an opt-in process (eg, AT&T USA OPPC), this reason code is returned if there is already a pending opt-in process for this subscription.
REASON_
Subscriber has reached a spending limit, or is out of credit. Used when we cannot distinguish which.
REASON_
Subscriber has reached a spending limit (eg, monthly spend cap).
REASON_
Subscriber has exceeded their credit limit. This is specific to limits which can be resolved by the subscriber adding credit to their account. Note that this may apply to either pre or postpay subscribers.
REASON_
Attempt to bill against a closed account. This subscriber should not be billed further.
REASON_
Attempt to bill against a locked/suspended account.
REASON_
Subscriber obtains connectivity via a reseller; billing of this subscriber is therefore barred.
REASON_
Adult settings on subscriber account prevent billing of subscriber.
REASON_
Originator on this message was invalid.
REASON_
Shortcode has not been provisioned. Contact MX Telecom support.
REASON_
An attempt was made to send a message to an unwhitelisted subscriber from a shortcode which has only been provisioned for testing.
REASON_
Temporary delivery problem to the destination.
REASON_
Temporary bar on delivery of this content to the destination.
REASON_
Message could not be delivered as handset message memory is full.
REASON_
Message could not be delivered as handset is absent from the network.
REASON_
Temporary delivery problem to the destination.
REASON_
Delivery to this subscriber has failed for an unknown reason. It may be due to a premium-rate bar, so it may still be possible to deliver standard-rate messages to this subscriber after failure of a premium message.
REASON_
Delivery to this subscriber has been barred.
REASON_
This subscriber cannot receive bulk or premium SMS messages from any sender
REASON_
The destination of this message does not represent a known subscriber. For billing traffic, or traffic within the USA, this may be network specific - i.e. the subscriber may be known by another network. For non-USA bulk messages it means the number is invalid.
REASON_
This subscriber is known to have ported off-net; delivery through this network is no longer possible.
REASON_
Subscriber obtains connectivity via a reseller; messaging to this subscriber is therefore barred.
REASON_
Subscriber obtains connectivity via a virtual network (MVNO); messaging to this subscriber is therefore barred.
REASON_
Some part of MX Telecom or network systems not functioning correctly. Contact MX Telecom support for more details.
REASON_
As per REASON_REJECTED_SYSFAIL, for errors occuring during billing phase.
REASON_
Network rejected message contents. Used where we have no further information as to the problem with the contents.
REASON_
Unicode (UCS2) messages are not supported on this network/shortcode.
REASON_
Binary (8-bit) messages are not supported on this network/shortcode.
REASON_
Message could not be submitted to network due to invalid opt-in details
REASON_
This reason code is returned when we receive a notification from the network that they have been unable to deliver the message, but are continuing to retry.
REASON_
REASON_
The message is being held whilst the network performs an opt-in process (eg, AT&T USA OPPC).
REASON_
Message could not be delivered as handset message memory is full.
REASON_
Message could not be delivered as handset is absent from the network.
REASON_
Temporary delivery problem to the destination.
REASON_
Sent when we have received a successful handset delivery report from the network, but billing is still pending.
REASON_
Sent when we have received a failed handset delivery report from the network, but billing is still pending. The final delivery report will usually contain more information on why the message failed.
REASON_
Indicates that the message was successfully billed. Note that the Billing nibble will always be set to 1 with this reason code.
REASON_
An unexpected error occurred during delivery, where we cannot differentiate between a system failure (some part of system not functioning correctly) and an expected failure (unknown subscriber, etc).
REASON_
The message exceeded its validity period before a delivery attempt could be made.
REASON_
Special reason code for Cricket credit-checking: indicates that the credit check was successful.
REASON_
An unexpected error occurred during billing, where we cannot differentiate between a system failure (some part of system not functioning correctly) and an expected failure (subscriber out of credit, etc).
REASON_
Billing of prepay subscribers is not supported on this network.
REASON_
Charges to this subscriber have been barred - no further information available from network.
REASON_
This charge has been rejected by the network. Used where none of the reasons below apply, but we believe that the subscriber is still billable (unlike REASON_REJECTED_BILLING_PSMSBARRED).
REASON_
On networks where the network controls an opt-in process (eg, AT&T USA OPPC), this reason code is returned if no positive opt-in is received within the timelimit allowed by the network.
REASON_
A previously-active subscription billing mandate has now terminated. No further billing should be performed under this subscription.
REASON_
This charge exceeds the terms (eg, monthly limit) of a subscription billing mandate.
REASON_
On networks where the network controls an opt-in process (eg, AT&T USA OPPC), this reason code is returned if there is already a pending opt-in process for this subscription.
REASON_
Subscriber has reached a spending limit, or is out of credit. Used when we cannot distinguish which.
REASON_
Subscriber has reached a spending limit (eg, monthly spend cap).
REASON_
Subscriber has exceeded their credit limit. This is specific to limits which can be resolved by the subscriber adding credit to their account. Note that this may apply to either pre or postpay subscribers.
REASON_
Attempt to bill against a closed account. This subscriber should not be billed further.
REASON_
Attempt to bill against a locked/suspended account.
REASON_
Subscriber obtains connectivity via a reseller; billing of this subscriber is therefore barred.
REASON_
Adult settings on subscriber account prevent billing of subscriber.
REASON_
Originator on this message was invalid.
REASON_
Shortcode has not been provisioned. Contact MX Telecom support.
REASON_
An attempt was made to send a message to an unwhitelisted subscriber from a shortcode which has only been provisioned for testing.
REASON_
Temporary delivery problem to the destination.
REASON_
Temporary bar on delivery of this content to the destination.
REASON_
Message could not be delivered as handset message memory is full.
REASON_
Message could not be delivered as handset is absent from the network.
REASON_
Temporary delivery problem to the destination.
REASON_
Delivery to this subscriber has failed for an unknown reason. It may be due to a premium-rate bar, so it may still be possible to deliver standard-rate messages to this subscriber after failure of a premium message.
REASON_
Delivery to this subscriber has been barred.
REASON_
This subscriber cannot receive bulk or premium SMS messages from any sender
REASON_
The destination of this message does not represent a known subscriber. For billing traffic, or traffic within the USA, this may be network specific - i.e. the subscriber may be known by another network. For non-USA bulk messages it means the number is invalid.
REASON_
This subscriber is known to have ported off-net; delivery through this network is no longer possible.
REASON_
Subscriber obtains connectivity via a reseller; messaging to this subscriber is therefore barred.
REASON_
Subscriber obtains connectivity via a virtual network (MVNO); messaging to this subscriber is therefore barred.
REASON_
Some part of MX Telecom or network systems not functioning correctly. Contact MX Telecom support for more details.
REASON_
As per REASON_REJECTED_SYSFAIL, for errors occuring during billing phase.
REASON_
Network rejected message contents. Used where we have no further information as to the problem with the contents.
REASON_
Unicode (UCS2) messages are not supported on this network/shortcode.
REASON_
Binary (8-bit) messages are not supported on this network/shortcode.
REASON_
Message could not be submitted to network due to invalid opt-in details
REASON_
Message delivered to handset.
REASON_
Control message (eg, STOP MT for subscription termination) has been processed.
REASON_
Message delivered to handset. As part of the billing process, a new carrier-managed subscription billing mandate was created with the user's network.
Delivery report reason codes available for MT messages to TIER3US networks
The TIER3US networks are those which can be reached via "ust3" SMS Gateway accounts. The reports supported depend on the network of the destination number.
|
May be returned for any MT message |
|
Returned only for premium MT messages |
|
||||||||||||||||||||
| Symbolic Name | Hexadecimal Reason Code | |||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Symbolic name | Hexadecimal Reason Code |
|
||||||||||||||||||
| REASON_ |
0x1.0000.. | |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| REASON_ |
0x1.0100.. | |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
||
| REASON_ |
0x1.0110.. | |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
||
| REASON_ |
0x1.0201.. | |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
||
| REASON_ |
0x1.0405.. | |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
||
| REASON_ |
0x1.0500.. | |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| REASON_ |
0x1.0501.. | |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
||
| REASON_ |
0x5.0000.. | |
|
|
|
|
|
|
|
|
|
|||||||||
| REASON_ |
0x5.0004.. | |
|
|
||||||||||||||||
| REASON_ |
0x6.0000.. | |
|
|
|
|
|
|
|
|
|
|
|
|
||||||
| REASON_ |
0x6.0002.. | |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
REASON_
An unexpected error occurred during delivery, where we cannot differentiate between a system failure (some part of system not functioning correctly) and an expected failure (unknown subscriber, etc).
REASON_
The message exceeded its validity period before a delivery attempt could be made.
REASON_
An unexpected error occurred during billing, where we cannot differentiate between a system failure (some part of system not functioning correctly) and an expected failure (subscriber out of credit, etc).
REASON_
Billing of prepay subscribers is not supported on this network.
REASON_
Charges to this subscriber have been barred - no further information available from network.
REASON_
This charge has been rejected by the network. Used where none of the reasons below apply, but we believe that the subscriber is still billable (unlike REASON_REJECTED_BILLING_PSMSBARRED).
REASON_
On networks where the network controls an opt-in process (eg, AT&T USA OPPC), this reason code is returned if no positive opt-in is received within the timelimit allowed by the network.
REASON_
A previously-active subscription billing mandate has now terminated. No further billing should be performed under this subscription.
REASON_
This charge exceeds the terms (eg, monthly limit) of a subscription billing mandate.
REASON_
On networks where the network controls an opt-in process (eg, AT&T USA OPPC), this reason code is returned if there is already a pending opt-in process for this subscription.
REASON_
Subscriber has reached a spending limit, or is out of credit. Used when we cannot distinguish which.
REASON_
Subscriber has reached a spending limit (eg, monthly spend cap).
REASON_
Subscriber has exceeded their credit limit. This is specific to limits which can be resolved by the subscriber adding credit to their account. Note that this may apply to either pre or postpay subscribers.
REASON_
Attempt to bill against a closed account. This subscriber should not be billed further.
REASON_
Attempt to bill against a locked/suspended account.
REASON_
Subscriber obtains connectivity via a reseller; billing of this subscriber is therefore barred.
REASON_
Adult settings on subscriber account prevent billing of subscriber.
REASON_
Originator on this message was invalid.
REASON_
Shortcode has not been provisioned. Contact MX Telecom support.
REASON_
An attempt was made to send a message to an unwhitelisted subscriber from a shortcode which has only been provisioned for testing.
REASON_
Temporary delivery problem to the destination.
REASON_
Temporary bar on delivery of this content to the destination.
REASON_
Message could not be delivered as handset message memory is full.
REASON_
Message could not be delivered as handset is absent from the network.
REASON_
Temporary delivery problem to the destination.
REASON_
Delivery to this subscriber has failed for an unknown reason. It may be due to a premium-rate bar, so it may still be possible to deliver standard-rate messages to this subscriber after failure of a premium message.
REASON_
Delivery to this subscriber has been barred.
REASON_
This subscriber cannot receive bulk or premium SMS messages from any sender
REASON_
The destination of this message does not represent a known subscriber. For billing traffic, or traffic within the USA, this may be network specific - i.e. the subscriber may be known by another network. For non-USA bulk messages it means the number is invalid.
REASON_
This subscriber is known to have ported off-net; delivery through this network is no longer possible.
REASON_
Subscriber obtains connectivity via a reseller; messaging to this subscriber is therefore barred.
REASON_
Subscriber obtains connectivity via a virtual network (MVNO); messaging to this subscriber is therefore barred.
REASON_
Some part of MX Telecom or network systems not functioning correctly. Contact MX Telecom support for more details.
REASON_
As per REASON_REJECTED_SYSFAIL, for errors occuring during billing phase.
REASON_
Network rejected message contents. Used where we have no further information as to the problem with the contents.
REASON_
Unicode (UCS2) messages are not supported on this network/shortcode.
REASON_
Binary (8-bit) messages are not supported on this network/shortcode.
REASON_
Message could not be submitted to network due to invalid opt-in details
REASON_
This reason code is returned when we receive a notification from the network that they have been unable to deliver the message, but are continuing to retry.
REASON_
REASON_
The message is being held whilst the network performs an opt-in process (eg, AT&T USA OPPC).
REASON_
Message could not be delivered as handset message memory is full.
REASON_
Message could not be delivered as handset is absent from the network.
REASON_
Temporary delivery problem to the destination.
REASON_
Sent when we have received a successful handset delivery report from the network, but billing is still pending.
REASON_
Sent when we have received a failed handset delivery report from the network, but billing is still pending. The final delivery report will usually contain more information on why the message failed.
REASON_
Indicates that the message was successfully billed. Note that the Billing nibble will always be set to 1 with this reason code.
REASON_
An unexpected error occurred during delivery, where we cannot differentiate between a system failure (some part of system not functioning correctly) and an expected failure (unknown subscriber, etc).
REASON_
The message exceeded its validity period before a delivery attempt could be made.
REASON_
Special reason code for Cricket credit-checking: indicates that the credit check was successful.
REASON_
An unexpected error occurred during billing, where we cannot differentiate between a system failure (some part of system not functioning correctly) and an expected failure (subscriber out of credit, etc).
REASON_
Billing of prepay subscribers is not supported on this network.
REASON_
Charges to this subscriber have been barred - no further information available from network.
REASON_
This charge has been rejected by the network. Used where none of the reasons below apply, but we believe that the subscriber is still billable (unlike REASON_REJECTED_BILLING_PSMSBARRED).
REASON_
On networks where the network controls an opt-in process (eg, AT&T USA OPPC), this reason code is returned if no positive opt-in is received within the timelimit allowed by the network.
REASON_
A previously-active subscription billing mandate has now terminated. No further billing should be performed under this subscription.
REASON_
This charge exceeds the terms (eg, monthly limit) of a subscription billing mandate.
REASON_
On networks where the network controls an opt-in process (eg, AT&T USA OPPC), this reason code is returned if there is already a pending opt-in process for this subscription.
REASON_
Subscriber has reached a spending limit, or is out of credit. Used when we cannot distinguish which.
REASON_
Subscriber has reached a spending limit (eg, monthly spend cap).
REASON_
Subscriber has exceeded their credit limit. This is specific to limits which can be resolved by the subscriber adding credit to their account. Note that this may apply to either pre or postpay subscribers.
REASON_
Attempt to bill against a closed account. This subscriber should not be billed further.
REASON_
Attempt to bill against a locked/suspended account.
REASON_
Subscriber obtains connectivity via a reseller; billing of this subscriber is therefore barred.
REASON_
Adult settings on subscriber account prevent billing of subscriber.
REASON_
Originator on this message was invalid.
REASON_
Shortcode has not been provisioned. Contact MX Telecom support.
REASON_
An attempt was made to send a message to an unwhitelisted subscriber from a shortcode which has only been provisioned for testing.
REASON_
Temporary delivery problem to the destination.
REASON_
Temporary bar on delivery of this content to the destination.
REASON_
Message could not be delivered as handset message memory is full.
REASON_
Message could not be delivered as handset is absent from the network.
REASON_
Temporary delivery problem to the destination.
REASON_
Delivery to this subscriber has failed for an unknown reason. It may be due to a premium-rate bar, so it may still be possible to deliver standard-rate messages to this subscriber after failure of a premium message.
REASON_
Delivery to this subscriber has been barred.
REASON_
This subscriber cannot receive bulk or premium SMS messages from any sender
REASON_
The destination of this message does not represent a known subscriber. For billing traffic, or traffic within the USA, this may be network specific - i.e. the subscriber may be known by another network. For non-USA bulk messages it means the number is invalid.
REASON_
This subscriber is known to have ported off-net; delivery through this network is no longer possible.
REASON_
Subscriber obtains connectivity via a reseller; messaging to this subscriber is therefore barred.
REASON_
Subscriber obtains connectivity via a virtual network (MVNO); messaging to this subscriber is therefore barred.
REASON_
Some part of MX Telecom or network systems not functioning correctly. Contact MX Telecom support for more details.
REASON_
As per REASON_REJECTED_SYSFAIL, for errors occuring during billing phase.
REASON_
Network rejected message contents. Used where we have no further information as to the problem with the contents.
REASON_
Unicode (UCS2) messages are not supported on this network/shortcode.
REASON_
Binary (8-bit) messages are not supported on this network/shortcode.
REASON_
Message could not be submitted to network due to invalid opt-in details
REASON_
Message delivered to handset.
REASON_
Control message (eg, STOP MT for subscription termination) has been processed.
REASON_
Message delivered to handset. As part of the billing process, a new carrier-managed subscription billing mandate was created with the user's network.
Delivery report reason codes available for MT messages to Canadian networks
|
May be returned for any MT message |
|
||||||||||
| Symbolic Name | Hexadecimal Reason Code | |||||||||
|---|---|---|---|---|---|---|---|---|---|---|
| Symbolic name | Hexadecimal Reason Code |
|
||||||||
| REASON_ |
0x1.0000.. | |
|
|
|
|
|
|
|
|
| REASON_ |
0x1.0500.. | |
|
|
|
|
|
|
|
|
| REASON_ |
0x5.0000.. | |
|
|
|
|
|
|
||
| REASON_ |
0x5.0004.. | |
|
|
||||||
| REASON_ |
0x6.0000.. | |
|
|
|
|
|
|||
| REASON_ |
0x6.0002.. | |
|
|
|
|
|
|
|
|
REASON_
An unexpected error occurred during delivery, where we cannot differentiate between a system failure (some part of system not functioning correctly) and an expected failure (unknown subscriber, etc).
REASON_
The message exceeded its validity period before a delivery attempt could be made.
REASON_
An unexpected error occurred during billing, where we cannot differentiate between a system failure (some part of system not functioning correctly) and an expected failure (subscriber out of credit, etc).
REASON_
Billing of prepay subscribers is not supported on this network.
REASON_
Charges to this subscriber have been barred - no further information available from network.
REASON_
This charge has been rejected by the network. Used where none of the reasons below apply, but we believe that the subscriber is still billable (unlike REASON_REJECTED_BILLING_PSMSBARRED).
REASON_
On networks where the network controls an opt-in process (eg, AT&T USA OPPC), this reason code is returned if no positive opt-in is received within the timelimit allowed by the network.
REASON_
A previously-active subscription billing mandate has now terminated. No further billing should be performed under this subscription.
REASON_
This charge exceeds the terms (eg, monthly limit) of a subscription billing mandate.
REASON_
On networks where the network controls an opt-in process (eg, AT&T USA OPPC), this reason code is returned if there is already a pending opt-in process for this subscription.
REASON_
Subscriber has reached a spending limit, or is out of credit. Used when we cannot distinguish which.
REASON_
Subscriber has reached a spending limit (eg, monthly spend cap).
REASON_
Subscriber has exceeded their credit limit. This is specific to limits which can be resolved by the subscriber adding credit to their account. Note that this may apply to either pre or postpay subscribers.
REASON_
Attempt to bill against a closed account. This subscriber should not be billed further.
REASON_
Attempt to bill against a locked/suspended account.
REASON_
Subscriber obtains connectivity via a reseller; billing of this subscriber is therefore barred.
REASON_
Adult settings on subscriber account prevent billing of subscriber.
REASON_
Originator on this message was invalid.
REASON_
Shortcode has not been provisioned. Contact MX Telecom support.
REASON_
An attempt was made to send a message to an unwhitelisted subscriber from a shortcode which has only been provisioned for testing.
REASON_
Temporary delivery problem to the destination.
REASON_
Temporary bar on delivery of this content to the destination.
REASON_
Message could not be delivered as handset message memory is full.
REASON_
Message could not be delivered as handset is absent from the network.
REASON_
Temporary delivery problem to the destination.
REASON_
Delivery to this subscriber has failed for an unknown reason. It may be due to a premium-rate bar, so it may still be possible to deliver standard-rate messages to this subscriber after failure of a premium message.
REASON_
Delivery to this subscriber has been barred.
REASON_
This subscriber cannot receive bulk or premium SMS messages from any sender
REASON_
The destination of this message does not represent a known subscriber. For billing traffic, or traffic within the USA, this may be network specific - i.e. the subscriber may be known by another network. For non-USA bulk messages it means the number is invalid.
REASON_
This subscriber is known to have ported off-net; delivery through this network is no longer possible.
REASON_
Subscriber obtains connectivity via a reseller; messaging to this subscriber is therefore barred.
REASON_
Subscriber obtains connectivity via a virtual network (MVNO); messaging to this subscriber is therefore barred.
REASON_
Some part of MX Telecom or network systems not functioning correctly. Contact MX Telecom support for more details.
REASON_
As per REASON_REJECTED_SYSFAIL, for errors occuring during billing phase.
REASON_
Network rejected message contents. Used where we have no further information as to the problem with the contents.
REASON_
Unicode (UCS2) messages are not supported on this network/shortcode.
REASON_
Binary (8-bit) messages are not supported on this network/shortcode.
REASON_
Message could not be submitted to network due to invalid opt-in details
REASON_
This reason code is returned when we receive a notification from the network that they have been unable to deliver the message, but are continuing to retry.
REASON_
REASON_
The message is being held whilst the network performs an opt-in process (eg, AT&T USA OPPC).
REASON_
Message could not be delivered as handset message memory is full.
REASON_
Message could not be delivered as handset is absent from the network.
REASON_
Temporary delivery problem to the destination.
REASON_
Sent when we have received a successful handset delivery report from the network, but billing is still pending.
REASON_
Sent when we have received a failed handset delivery report from the network, but billing is still pending. The final delivery report will usually contain more information on why the message failed.
REASON_
Indicates that the message was successfully billed. Note that the Billing nibble will always be set to 1 with this reason code.
REASON_
An unexpected error occurred during delivery, where we cannot differentiate between a system failure (some part of system not functioning correctly) and an expected failure (unknown subscriber, etc).
REASON_
The message exceeded its validity period before a delivery attempt could be made.
REASON_
Special reason code for Cricket credit-checking: indicates that the credit check was successful.
REASON_
An unexpected error occurred during billing, where we cannot differentiate between a system failure (some part of system not functioning correctly) and an expected failure (subscriber out of credit, etc).
REASON_
Billing of prepay subscribers is not supported on this network.
REASON_
Charges to this subscriber have been barred - no further information available from network.
REASON_
This charge has been rejected by the network. Used where none of the reasons below apply, but we believe that the subscriber is still billable (unlike REASON_REJECTED_BILLING_PSMSBARRED).
REASON_
On networks where the network controls an opt-in process (eg, AT&T USA OPPC), this reason code is returned if no positive opt-in is received within the timelimit allowed by the network.
REASON_
A previously-active subscription billing mandate has now terminated. No further billing should be performed under this subscription.
REASON_
This charge exceeds the terms (eg, monthly limit) of a subscription billing mandate.
REASON_
On networks where the network controls an opt-in process (eg, AT&T USA OPPC), this reason code is returned if there is already a pending opt-in process for this subscription.
REASON_
Subscriber has reached a spending limit, or is out of credit. Used when we cannot distinguish which.
REASON_
Subscriber has reached a spending limit (eg, monthly spend cap).
REASON_
Subscriber has exceeded their credit limit. This is specific to limits which can be resolved by the subscriber adding credit to their account. Note that this may apply to either pre or postpay subscribers.
REASON_
Attempt to bill against a closed account. This subscriber should not be billed further.
REASON_
Attempt to bill against a locked/suspended account.
REASON_
Subscriber obtains connectivity via a reseller; billing of this subscriber is therefore barred.
REASON_
Adult settings on subscriber account prevent billing of subscriber.
REASON_
Originator on this message was invalid.
REASON_
Shortcode has not been provisioned. Contact MX Telecom support.
REASON_
An attempt was made to send a message to an unwhitelisted subscriber from a shortcode which has only been provisioned for testing.
REASON_
Temporary delivery problem to the destination.
REASON_
Temporary bar on delivery of this content to the destination.
REASON_
Message could not be delivered as handset message memory is full.
REASON_
Message could not be delivered as handset is absent from the network.
REASON_
Temporary delivery problem to the destination.
REASON_
Delivery to this subscriber has failed for an unknown reason. It may be due to a premium-rate bar, so it may still be possible to deliver standard-rate messages to this subscriber after failure of a premium message.
REASON_
Delivery to this subscriber has been barred.
REASON_
This subscriber cannot receive bulk or premium SMS messages from any sender
REASON_
The destination of this message does not represent a known subscriber. For billing traffic, or traffic within the USA, this may be network specific - i.e. the subscriber may be known by another network. For non-USA bulk messages it means the number is invalid.
REASON_
This subscriber is known to have ported off-net; delivery through this network is no longer possible.
REASON_
Subscriber obtains connectivity via a reseller; messaging to this subscriber is therefore barred.
REASON_
Subscriber obtains connectivity via a virtual network (MVNO); messaging to this subscriber is therefore barred.
REASON_
Some part of MX Telecom or network systems not functioning correctly. Contact MX Telecom support for more details.
REASON_
As per REASON_REJECTED_SYSFAIL, for errors occuring during billing phase.
REASON_
Network rejected message contents. Used where we have no further information as to the problem with the contents.
REASON_
Unicode (UCS2) messages are not supported on this network/shortcode.
REASON_
Binary (8-bit) messages are not supported on this network/shortcode.
REASON_
Message could not be submitted to network due to invalid opt-in details
REASON_
Message delivered to handset.
REASON_
Control message (eg, STOP MT for subscription termination) has been processed.
REASON_
Message delivered to handset. As part of the billing process, a new carrier-managed subscription billing mandate was created with the user's network.
Delivery report reason codes available for premium MT messages to Australian networks
|
May be returned for any premium MT message |
|
||||||
| Symbolic Name | Hexadecimal Reason Code | |||||
|---|---|---|---|---|---|---|
| Symbolic name | Hexadecimal Reason Code |
|
||||
| REASON_ |
0x1.0000.. | |
|
|
|
|
| REASON_ |
0x1.0122.. | |
||||
| REASON_ |
0x1.0132.. | |
||||
| REASON_ |
0x1.0201.. | |
||||
| REASON_ |
0x1.0302.. | |
||||
| REASON_ |
0x1.0400.. | |
|
|
||
| REASON_ |
0x1.0401.. | |
||||
| REASON_ |
0x1.0500.. | |
|
|
||
| REASON_ |
0x5.0000.. | |
|
|
||
| REASON_ |
0x5.0004.. | |
||||
| REASON_ |
0x5.0122.. | |
|
|||
| REASON_ |
0x5.0301.. | |
||||
| REASON_ |
0x5.0302.. | |
||||
| REASON_ |
0x5.0303.. | |
||||
| REASON_ |
0x5.0405.. | |
||||
| REASON_ |
0x6.0000.. | |
|
|
|
|
| REASON_ |
0x6.0002.. | |
|
|
||
