SWI-2146 Add New Messaging Error Codes (#985)

* SWI-2146 Add New Messaging Error Codes * update 4772 explanation
Bandwidth · Mar 23, 2023 · ab524d7 · ab524d7
1 parent 94de564
commit ab524d7
Showing 1 changed file with 3 additions and 0 deletions.
diff --git a/site/docs/messaging/errors.mdx b/site/docs/messaging/errors.mdx
@@ -305,6 +305,9 @@ A 4xx code indicates that Bandwidth or the downstream carrier has identified som
 | 4752 | destination-rejected-malformed | Message is malformed for the carrier. | Carrier is rejecting the message malformed; this could be because of a blank message, unacceptable data value, the receiving SMSC or SME does not accept messages with more than 160 characters, syntax error, content is invalid, message ID is invalid, invalid parameter length, expected TLV missing, invalid TLV value, invalid data coding scheme, invalid number of destinations, error in the optional part of the PDU body, TLV not allowed, or XML validation error. | YES |
 | 4770 | destination-spam-detected | Carrier Rejected as SPAM | The Carrier is reporting this message as blocked for SPAM. Spam blocks could be a result of content, SHAFT violations (including specific keywords), originating address has been flagged for repeated spam content | YES |
 | 4771 | rejected-shortened-url | Rejected due to shortened url | There was an error with the shortened URL used. Bandwidth recommends customers obtain their own dedicated domain if shortened links are needed for their messaging campaign. | YES |
+| 4772 | rejected-tn-blocked | Blocked sender or receiver | This error indicates a blocked Sender or Receiver on the downstream platform. Please reach out to Bandwidth support so we can engage our vendor to determine which telephone number is blocked and why. | YES |
+| 4773 | inactive-campaign | Campaign inactive for destination | The campaign this TN is assigned to is not active for the destination. Please check the status with TCR (The Campaign Registry). You will receive this error if the campaign is pending or rejected by the DCA or suspended by an MNO but the TN is still assigned to the campaign. | YES |
+| 4774 | provisioning-issue | Issue with TN provisioning in industry database | There is an issue with how the number is provisioned in the industry's database. There may be some components of 10DLC provisioning that are incorrect or missing. Please reach out to Bandwidth support to investigate and correct this issue. | YES |
 | 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 |
 | 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 |
 | 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 |