Skip to content
This repository was archived by the owner on Nov 29, 2023. It is now read-only.

Commit 7d08d73

Browse files
authored
DX-2853 Update Messaging Errors (#723)
* DX-2853 Update Messaging Errors * remove 4320
1 parent 6f50ed4 commit 7d08d73

File tree

1 file changed

+3
-1
lines changed

1 file changed

+3
-1
lines changed

site/docs/messaging/errors.mdx

Lines changed: 3 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -295,7 +295,7 @@ A 4xx code indicates that Bandwidth or the downstream carrier has identified som
295295
| 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.  | YES |
296296
| 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. | YES |
297297
| 4711 | rejected-message-size-limit-exceeded | Media size too large | Downstream vendor cannot retrieve the media as the MMS attachment is too large | YES |
298-
| 4712 | media-invalid | Invalid media | The end user’s handset cannot download the MMS or the media is not formatted in a way the end user can open on their handset. | YES |
298+
| 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](https://support.bandwidth.com/hc/en-us/articles/360014128994-What-MMS-file-types-are-supported-). | YES |
299299
| 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 | YES |
300300
| 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. | YES |
301301
| 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 | YES |
@@ -308,10 +308,12 @@ A 4xx code indicates that Bandwidth or the downstream carrier has identified som
308308
| 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. | YES |
309309
| 4780 | volume-violation-tmo | T-Mobile rejected due to volumetric violation | [T-Mobile](https://support.bandwidth.com/hc/en-us/articles/1500004766182-T-Mobile-10DLC-) 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](https://support.bandwidth.com/hc/en-us/articles/5829369841047-Brand-vetting). | YES |
310310
| 4781 | volume-violation-att | AT&T rejected due to 10DLC volumetric violation or throttling | [AT&T](https://support.bandwidth.com/hc/en-us/articles/360061793113-AT-T-10DLC) 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. | YES |
311+
| 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. | YES |
311312
| 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. | YES |
312313
| 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 | YES |
313314
| 4792 | destination-rejected-sc-not-provisioned | Carrier Rejected Short Code Not Provisioned | Short Code not provisioned on mobile operator's network. | YES |
314315
| 4793 | destination-rejected-sc-expired | Carrier Rejected Short Code Expired | Short Code expired with the mobile operator | YES |
316+
| 4795 | tfn-not-verified | Toll Free number is not verified | The message was blocked due to the toll free number not being verified. Please review [unverified sending limits](https://support.bandwidth.com/hc/en-us/articles/1500006962542-Bandwidth-toll-free-verification-handbook-) and submit TFN for verification as soon as possible. | YES |
315317

316318

317319
### Bandwidth Service Failures

0 commit comments

Comments
 (0)