AWS connect documentation change
Summary
Removed section about Japanese carrier requirements and updated content structure
Security assessment
Content removal focuses on carrier-specific technical requirements rather than security controls
Diff
diff --git a/connect/latest/adminguide/queues-callerid.md b/connect/latest/adminguide/queues-callerid.md index fffde3175..c9e3b9a05 100644 --- a//connect/latest/adminguide/queues-callerid.md +++ b//connect/latest/adminguide/queues-callerid.md @@ -5 +5 @@ -Outbound parameters: Set in queueHow outbound parameters are selectedHow to set the caller ID number dynamicallyUse E.164 format for international phone numbersHow to specify a custom caller ID number using a blockCNAMJapanese carrier requirementsAvoid labels like "spam" +Outbound parameters: Set in queueHow outbound parameters are selectedHow to set the caller ID number dynamicallyUse E.164 format for international phone numbersHow to specify a custom caller ID number using a blockCNAMAvoid labels like "spam" @@ -25,2 +24,0 @@ This topic explains how to set up your outbound caller ID name and number. - * Japanese carrier requirements - @@ -220,26 +217,0 @@ All existing CNAM configurations set up before March 2023, are still in place. W -## Japanese carrier requirements for outbound calls - -Japanese telecom carriers only allow outbound caller ID for phone numbers that they issued. This means: - - 1. If you use a Custom Caller ID as your outbound caller ID, the Japanese carrier's Session Border Controller (SBC) will reject the call. - - 2. When a call is rejected: - - * The Voice SBC automatically retries the call using our backup carrier (referred to here as Carrier B). - - * Carrier B uses its own designated number (03-4520-9200) for the outbound call. - - - - -This same failover process occurs if there are other issues, such as: - - * Trunk failures - - * Other carrier-side problems that cause call rejection - - - - -In these cases, Carrier B also uses its designated number (03-4520-9200) for outbound calls. -