# Contact center business continuity

Canonical: https://warmtransfer.net/knowledge/contact-center-business-continuity

Last verified: 2026-09-30

An Amazon Connect instance is created within 1 AWS Region across a minimum of 3 Availability Zones and is propagated across them in an active-active-active configuration[^3]. With a Microsoft Teams Direct Routing Survivable Branch Appliance (SBA), the Teams client automatically switches to the SBA during an internet outage, and ongoing calls continue without interruption[^49].

## Amazon Connect single-region resilience

AWS documents that if 1 Availability Zone fails, that node is taken out of rotation without impacting production for an Amazon Connect instance[^2]. Amazon Connect is integrated with multiple telephony providers that have redundant dedicated network paths to 3 or more Availability Zones in every AWS Region where the service is offered[^30]. A failed component, data center or Availability Zone endpoint is automatically taken out of rotation[^30].

Inbound US toll-free calls and outbound calls are processed through multiple telecom carriers[^31]. Each of these carriers is connected to multiple Availability Zones active-active[^31]. The RespOrg routes US toll-free traffic across multiple carriers in an active-active fashion[^31]. In the single-region architecture, an agent's browser chooses from at least 2 servers across multiple Availability Zones, based on reachability[^1].

## Amazon Connect Global Resiliency

AWS states that Global Resiliency is the only AWS-supported solution for multi-region resiliency in Amazon Connect[^15]. AWS also states that deploying unsupported third-party or custom-built alternatives might result in denied or reduced service limits on the secondary instance and could impact SLA coverage[^15].

### Regions and pairs

Global Resiliency is available only for instances created in these Regions[^20]:

- US East (N. Virginia)[^20]
- US West (Oregon)[^20]
- Asia Pacific (Osaka)[^20]
- Asia Pacific (Tokyo)[^20]
- Europe (Frankfurt)[^20]
- Europe (London)[^20]

Replicas are limited to fixed Region pairs[^16]:

- US East (N. Virginia) and US West (Oregon), in either direction.[^16]
- Europe (Frankfurt) and Europe (London), in either direction.[^16]
- Asia Pacific (Osaka), only as a replica when the source is Asia Pacific (Tokyo).[^16]

For instances in Asia Pacific (Tokyo), only phone numbers explicitly enabled for Global Resiliency get complete replication behaviour to Asia Pacific (Osaka)[^29]. Inbound calls routed through Osaka might take up to 20 seconds to be delivered[^29].

### Prerequisites and access

Access to Global Resiliency is obtained by contacting an AWS Solutions Architect or Technical Account Manager, and the setup page does not describe it as a self-service toggle[^4]. Onboarding requires AWS Enterprise Support or AWS Unified Operations[^28]. Global Resiliency also requires an existing production SAML 2.0-enabled instance in a supported Region[^22].

All phone numbers that are to be enabled as multi-region must first be ported to Amazon Connect[^17]. AWS instructs customers to request, through a service quota increase case, that all service quotas in the replica instance match those of the source instance[^18].

Before onboarding, flows must replace hardcoded Regions with the `$.AwsRegion` parameter[^19]. Lambda functions must also have the same name across AWS Regions[^19]. `$.AwsRegion` is supported only for Lambda ARNs and Lex ARNs[^19].

Instances that still use the older awsapps.com/connect access domain cannot properly configure Global Resiliency until the domain is updated to the my.connect.aws format[^14].

### Setup order

The documented setup order is as follows, in this sequence[^24]:

- Create a replica with ReplicateInstance.[^24]
- Create a traffic distribution group and confirm that its Status is ACTIVE.[^24]
- Claim phone numbers to the traffic distribution group.[^24]
- Update the traffic distribution with UpdateTrafficDistribution.[^24]

After phone numbers are claimed to a traffic distribution group, the default distribution is 100% to the source instance and 0% to the replica[^8].

### The replica instance

The replica instance is created in the same AWS account as the source instance and has the same instance ID[^21]. After the initial ReplicateInstance copy, changes to mirrored resources are synchronized continuously and bidirectionally between source and replica in near real time[^7]. If that synchronization fails, Global Resiliency attempts to sync updates within 30 minutes[^7].

ReplicateInstance does not synchronize Lambda functions, Amazon Lex bots or other third-party integrations[^13]. The customer must ensure redundancy across Regions for front-end and back-end integrations such as SSO, Lambda and Lex[^13].

Some resources in the mirrored set have their own limits[^11]:

- Prompts stored in S3 are not mirrored.[^11]
- Schedules attached to saved reports are not replicated.[^11]
- Only Views in a published state are replicated.[^11]

Global routing, analytics and contact search are enabled by default for all new Global Resiliency instances created on or after September 1, 2026[^9]. Existing Global Resiliency instances can migrate to that feature set on request[^9].

## Operating a Global Resiliency failover

Telephony traffic and agents can be distributed across the 2 linked instances in 10% increments or shifted all at once[^10]. An UpdateTrafficDistribution call fails with InvalidRequestException if any of these requirements is not met[^27]:

- Telephony distribution is given for both linked instances.[^27]
- The distribution totals 100%.[^27]
- The distribution is expressed in 10% increments.[^27]

When telephony traffic is shifted to the other Region, agents or agent sign-ins must also be shifted[^25]. Otherwise, voice calls go to the shifted Region with no agents available to receive them[^25].

Agents are signed in to both instances in the traffic distribution group, regardless of the SignInConfig setting[^26]. SignInConfig only selects which Region's sign-in servers are used[^26]. SignInConfig can be changed only on the default traffic distribution group[^26].

To let the agent workspace shift between Regions, each linked instance's Access URL must be added to the other instance's Approved origins, without a trailing slash[^6]. When agents are shifted across Regions, they can complete active voice contacts first[^5]. An agent on a contact sees a regional-switch banner[^5]. That agent is moved to the new Region automatically after finishing the contact and closing after-contact work[^5]. Agents must set their status to Available after they are shifted[^23].

AWS tells Global Resiliency customers to perform monthly failover testing to validate the failover procedure and runbook[^12]. Where a full failover test is not feasible, AWS tells customers to create a test traffic distribution group pointed to the replica Region and to test critical flows monthly without affecting production traffic[^12].

## Microsoft Teams Direct Routing Survivable Branch Appliance

During an internet outage, users can make and receive PSTN calls through the local SBA/SBC[^49]. In SBA offline mode, an incoming PSTN call to a call queue or auto attendant number can be redirected to a local agent or to an alternative call queue or auto attendant number[^47].

The SBA feature is supported on Teams Windows desktop, Teams macOS desktop and Teams Phones[^46]. SBA mode activates only on desktop clients running on a physical machine[^46]. Virtual machines and web clients are not supported[^46].

In SBA mode, Teams users can still make emergency calls, but location information is not shared[^48]. The SBA does not support Emergency Call Routing Policies[^48]. As a result, emergency calls fail through the SBA if no pattern in the regular voice routing policy matches the emergency dial strings[^48].

If a tenant uses Continuous Access Evaluation tokens, the SBA is operational for only about 30 minutes[^45]. Otherwise, the SBA supports expired client authentication tokens for up to 7 days from expiry[^45].

## Applicability

Applies to: Amazon Web Services Amazon Connect, Amazon Web Services Amazon Connect Global Resiliency, and Microsoft Teams Phone Direct Routing. Deployments: multi-tenant. Sources checked 2026-09-30. Amazon Connect Global Resiliency applies only to instances created in the Regions listed under Regions and pairs above[^20]. The default enablement of global routing, analytics and contact search applies to Global Resiliency instances created on or after September 1, 2026[^9]. Instances that still use the awsapps.com/connect access domain must move to the my.connect.aws format before Global Resiliency can be properly configured[^14]. The US toll-free carrier statement applies to inbound US toll-free calls and outbound calls[^31]. SBA mode applies only to Teams desktop clients on a physical machine and to Teams Phones[^46].

## What remains uncertain

Webex Contact Center recovery time objectives, recovery point objectives and service credit terms are not covered by the sources below. Webex Contact Center PSTN and voice POP failover behaviour during a carrier or media region outage is not covered by the sources below. Whether Webex Calling Site Survivability preserves Customer Assist or call queue behaviour is not covered by the sources below. A Webex Contact Center emergency closure message pattern using a global variable set by supervisors is not covered by the sources below. Global routing, analytics and contact search are enabled by default for new Amazon Connect Global Resiliency instances created on or after September 1, 2026[^9]. The detailed behaviour of global routing and of chat across Regions, as described on the Global Resiliency child pages, is not covered by the sources below. The exact list of AWS regions hosting Webex Contact Center is not covered by the sources below. Whether AWS documentation now prints the product name as Connect Customer instead of Amazon Connect is not covered by the sources below. Agent location failover for remote agents who lose power or internet, and alternate site arrangements, are not covered by the sources below.

## Sources

[^1]: In Amazon Connect's single-region architecture, an agent's browser chooses from at least two servers across multiple Availability Zones, based on reachability. Source: [Resilience in Connect Customer](https://docs.aws.amazon.com/connect/latest/adminguide/disaster-recovery-resiliency.html), Section 'Single-region telephony and softphone architecture', numbered item 4. Checked 2026-09-30.
[^2]: AWS documents that if one Availability Zone fails, that node is taken out of rotation without impacting production for an Amazon Connect instance. Source: [Resilience in Connect Customer](https://docs.aws.amazon.com/connect/latest/adminguide/disaster-recovery-resiliency.html), Introduction, paragraph beginning 'Within each AWS Region you can create'. Checked 2026-09-30.
[^3]: An Amazon Connect instance is created within one AWS Region across a minimum of three Availability Zones and is propagated across them in an active-active-active configuration. Source: [Resilience in Connect Customer](https://docs.aws.amazon.com/connect/latest/adminguide/disaster-recovery-resiliency.html), Introduction, paragraph beginning 'Within each AWS Region you can create'. Checked 2026-09-30.
[^4]: Access to Amazon Connect Global Resiliency is obtained by contacting an AWS Solutions Architect or Technical Account Manager; it is not a self-service toggle per the setup page. Source: [Set up Connect Customer Global Resiliency](https://docs.aws.amazon.com/connect/latest/adminguide/setup-connect-global-resiliency.html), Note box at top of page, last sentence. Checked 2026-09-30.
[^5]: When agents are shifted across Regions, they can complete active voice contacts first; an agent on a contact sees a regional-switch banner and is moved to the new Region automatically after finishing the contact and closing after-contact work. Source: [Update agent distribution in your Connect Customer agent workspace across AWS Regions](https://docs.aws.amazon.com/connect/latest/adminguide/update-agents-across-regions.html), Introduction, third paragraph; section 'Regional switch UI banner'. Checked 2026-09-30.
[^6]: To let the agent workspace shift between Regions, each linked instance's Access URL must be added to the other instance's Approved origins, without a trailing slash. Source: [Set up the Connect Customer agent workspace to support agents shifting across AWS Regions](https://docs.aws.amazon.com/connect/latest/adminguide/setup-agentworkspace-switchover.html), Steps 1 to 5 and the Note under step 4. Checked 2026-09-30.
[^7]: After the initial ReplicateInstance copy, changes to mirrored resources are synchronized continuously and bidirectionally between source and replica in near real time; if that fails, Global Resiliency attempts to sync updates within 30 minutes. Source: [Create a replica of your existing Connect Customer instance](https://docs.aws.amazon.com/connect/latest/adminguide/create-replica-connect-instance.html), Section 'Important things to know', second top-level bullet; Note at end of 'What resources are mirrored in the replica instance'. Checked 2026-09-30.
[^8]: After phone numbers are claimed to a traffic distribution group, the default distribution is 100% to the source instance and 0% to the replica. Source: [Get started with Connect Customer Global Resiliency](https://docs.aws.amazon.com/connect/latest/adminguide/get-started-connect-global-resiliency.html), Section 'How to set up Connect Customer Global Resiliency', Note under step 3. Checked 2026-09-30.
[^9]: Global routing, analytics and contact search are enabled by default for all new Global Resiliency instances created on or after September 1, 2026; existing Global Resiliency instances can migrate to that feature set on request. Source: [Set up Connect Customer Global Resiliency](https://docs.aws.amazon.com/connect/latest/adminguide/setup-connect-global-resiliency.html), Note box following the API capability list. Checked 2026-09-30.
[^10]: Amazon Connect Global Resiliency lets telephony traffic and agents be distributed across the two linked instances in 10% increments or shifted all at once. Source: [Set up Connect Customer Global Resiliency](https://docs.aws.amazon.com/connect/latest/adminguide/setup-connect-global-resiliency.html), Bullet list under 'provides a set of APIs that you use to', third bullet. Checked 2026-09-30.
[^11]: Among mirrored resources, prompts stored in S3 are not mirrored, schedules attached to saved reports are not replicated, and only Views in a published state are replicated. Source: [Create a replica of your existing Connect Customer instance](https://docs.aws.amazon.com/connect/latest/adminguide/create-replica-connect-instance.html), Section 'What resources are mirrored in the replica instance', resource list and 'Important notes about specific resources'. Checked 2026-09-30.
[^12]: AWS tells Global Resiliency customers to perform monthly failover testing to validate the failover procedure and runbook, and, where a full failover test is not feasible, to create a test traffic distribution group pointed to the replica Region and test critical flows monthly without affecting production traffic. Source: [Get started with Connect Customer Global Resiliency](https://docs.aws.amazon.com/connect/latest/adminguide/get-started-connect-global-resiliency.html), Paragraph headed 'Perform monthly failover testing' at end of page. Checked 2026-09-30.
[^13]: ReplicateInstance does not synchronize Lambda functions, Amazon Lex bots or other third-party integrations; the customer must ensure redundancy for front-end and back-end integrations such as SSO, Lambda and Lex across Regions. Source: [Create a replica of your existing Connect Customer instance](https://docs.aws.amazon.com/connect/latest/adminguide/create-replica-connect-instance.html), Section 'Important things to know', last bullet; section 'What to do after the replica instance is created', step 1. Checked 2026-09-30.
[^14]: Amazon Connect instances that still use the older awsapps.com/connect access domain cannot properly configure Global Resiliency until the domain is updated to the my.connect.aws format. Source: [Get started with Connect Customer Global Resiliency](https://docs.aws.amazon.com/connect/latest/adminguide/get-started-connect-global-resiliency.html), Important box at top of page. Checked 2026-09-30.
[^15]: AWS states that Global Resiliency is the only AWS-supported solution for multi-region resiliency in Amazon Connect, and that deploying unsupported third-party or custom-built alternatives might result in denied or reduced service limits on the secondary instance and could impact SLA coverage. Source: [Set up Connect Customer Global Resiliency](https://docs.aws.amazon.com/connect/latest/adminguide/setup-connect-global-resiliency.html), Important box. Checked 2026-09-30.
[^16]: Amazon Connect Global Resiliency replicas are limited to fixed Region pairs: US East (N. Virginia) with US West (Oregon) in either direction, Europe (Frankfurt) with Europe (London) in either direction, and Asia Pacific (Osaka) as replica only when the source is Asia Pacific (Tokyo). Source: [Set up Connect Customer Global Resiliency](https://docs.aws.amazon.com/connect/latest/adminguide/setup-connect-global-resiliency.html), Note box at top of page. Checked 2026-09-30.
[^17]: A prerequisite for Amazon Connect Global Resiliency is porting to Amazon Connect all phone numbers that are to be enabled as multi-region. Source: [Connect Customer Global Resiliency requirements](https://docs.aws.amazon.com/connect/latest/adminguide/connect-global-resiliency-requirements.html), Prerequisites list, first bullet. Checked 2026-09-30.
[^18]: AWS instructs Global Resiliency customers to request that all service quotas in the replica instance match those of the source instance through a service quota increase case. Source: [Connect Customer Global Resiliency requirements](https://docs.aws.amazon.com/connect/latest/adminguide/connect-global-resiliency-requirements.html), Prerequisites list, bullet beginning 'Request that ALL service quotas'. Checked 2026-09-30.
[^19]: Before onboarding to Global Resiliency, flows must replace hardcoded Regions with the $.AwsRegion parameter and Lambda functions must have the same name across AWS Regions; $.AwsRegion is supported only for Lambda ARNs and Lex ARNs. Source: [Connect Customer Global Resiliency requirements](https://docs.aws.amazon.com/connect/latest/adminguide/connect-global-resiliency-requirements.html), Prerequisites list, bullets on Lambda function names and hardcoded Regions, and the Note beneath. Checked 2026-09-30.
[^20]: Amazon Connect Global Resiliency is available only for instances created in US East (N. Virginia), US West (Oregon), Asia Pacific (Osaka), Asia Pacific (Tokyo), Europe (Frankfurt) and Europe (London). Source: [Set up Connect Customer Global Resiliency](https://docs.aws.amazon.com/connect/latest/adminguide/setup-connect-global-resiliency.html), Note box at top of page. Checked 2026-09-30.
[^21]: The Global Resiliency replica instance is created in the same AWS account as the source instance and has the same instance ID. Source: [Create a replica of your existing Connect Customer instance](https://docs.aws.amazon.com/connect/latest/adminguide/create-replica-connect-instance.html), Section 'Characteristics of the replica instance', first and last bullets. Checked 2026-09-30.
[^22]: Amazon Connect Global Resiliency requires an existing production SAML 2.0-enabled instance in a supported Region. Source: [Connect Customer Global Resiliency requirements](https://docs.aws.amazon.com/connect/latest/adminguide/connect-global-resiliency-requirements.html), Prerequisites list, third bullet. Checked 2026-09-30.
[^23]: Agents must set their status to Available after they are shifted across Regions. Source: [Set up the Connect Customer agent workspace to support agents shifting across AWS Regions](https://docs.aws.amazon.com/connect/latest/adminguide/setup-agentworkspace-switchover.html), Final Note box. Checked 2026-09-30.
[^24]: The documented Global Resiliency setup order is: create a replica with ReplicateInstance, create a traffic distribution group and confirm its Status is ACTIVE, claim phone numbers to the traffic distribution group, then update the traffic distribution with UpdateTrafficDistribution. Source: [Get started with Connect Customer Global Resiliency](https://docs.aws.amazon.com/connect/latest/adminguide/get-started-connect-global-resiliency.html), Section 'How to set up Connect Customer Global Resiliency', steps 1 to 4. Checked 2026-09-30.
[^25]: When telephony traffic is shifted to the other Region, agents or agent sign-ins must also be shifted; otherwise voice calls go to the shifted Region with no agents available to receive them. Source: [Update telephony traffic distribution across Connect Customer instances and AWS Regions](https://docs.aws.amazon.com/connect/latest/adminguide/update-telephony-traffic-distribution.html), Note box following the first paragraph. Checked 2026-09-30.
[^26]: Regardless of the SignInConfig setting, agents are signed in to both instances in the traffic distribution group; SignInConfig only selects which Region's sign-in servers are used and can be changed only on the default traffic distribution group. Source: [Update agent distribution in your Connect Customer agent workspace across AWS Regions](https://docs.aws.amazon.com/connect/latest/adminguide/update-agents-across-regions.html), Section 'Requirements', item 3; section 'Enable both AWS Regions during regular operations'. Checked 2026-09-30.
[^27]: An UpdateTrafficDistribution call fails with InvalidRequestException unless telephony distribution is given for both linked instances, totals 100%, and is expressed in 10% increments. Source: [Update telephony traffic distribution across Connect Customer instances and AWS Regions](https://docs.aws.amazon.com/connect/latest/adminguide/update-telephony-traffic-distribution.html), Bullet list under 'If the following requirements are not met'. Checked 2026-09-30.
[^28]: AWS Enterprise Support or AWS Unified Operations is required to onboard to Amazon Connect Global Resiliency. Source: [Connect Customer Global Resiliency requirements](https://docs.aws.amazon.com/connect/latest/adminguide/connect-global-resiliency-requirements.html), Prerequisites list, second bullet. Checked 2026-09-30.
[^29]: For instances in Asia Pacific (Tokyo), only phone numbers explicitly enabled for Global Resiliency get complete replication behaviour to Asia Pacific (Osaka), and inbound calls routed through Osaka might take up to 20 seconds to be delivered. Source: [Create a replica of your existing Connect Customer instance](https://docs.aws.amazon.com/connect/latest/adminguide/create-replica-connect-instance.html), Section 'Important things to know', bullet beginning 'For instances in Asia Pacific (Tokyo)'. Checked 2026-09-30.
[^30]: Amazon Connect is integrated with multiple telephony providers that have redundant dedicated network paths to three or more Availability Zones in every AWS Region where the service is offered; a failed component, data center or AZ endpoint is automatically taken out of rotation. Source: [Resilience in Connect Customer](https://docs.aws.amazon.com/connect/latest/adminguide/disaster-recovery-resiliency.html), Section 'Single-region telephony and softphone architecture', first paragraph. Checked 2026-09-30.
[^31]: In Amazon Connect, inbound US toll-free calls and outbound calls are processed through multiple telecom carriers, each connected to multiple Availability Zones active-active; the RespOrg routes US toll-free traffic across multiple carriers in an active-active fashion. Source: [Resilience in Connect Customer](https://docs.aws.amazon.com/connect/latest/adminguide/disaster-recovery-resiliency.html), Section 'Single-region telephony and softphone architecture', second paragraph and numbered items 2 and 3. Checked 2026-09-30.
[^32]: Under 47 CFR 4.9(h)(4) and (h)(5), interconnected VoIP providers must notify a potentially affected 911 special facility as soon as possible and no later than 30 minutes after discovering the outage, and must send the first follow-up notification no later than two hours after the initial contact. Source: [47 CFR 4.9 - Outage reporting requirements - threshold criteria](https://www.law.cornell.edu/cfr/text/47/4.9), 47 CFR 4.9(h)(4) and (h)(5). Checked 2026-09-30.
[^33]: 47 CFR 4.5(a) defines an outage as a significant degradation in the ability of an end user to establish and maintain a channel of communications as a result of failure or degradation in the performance of a communications provider's network. Source: [47 CFR 4.5 - Definitions of outage, special offices and facilities, and 911 special facilities](https://www.law.cornell.edu/cfr/text/47/4.5), 47 CFR 4.5(a). Checked 2026-09-30.
[^34]: Under 47 CFR 4.9(g)(1)(i), an interconnected VoIP service provider must notify the FCC within 240 minutes of discovering an outage of at least 30 minutes that potentially affects a 911 special facility or a 988 special facility, and must also notify the affected facility. Source: [47 CFR 4.9 - Outage reporting requirements - threshold criteria](https://www.law.cornell.edu/cfr/text/47/4.9), 47 CFR 4.9(g)(1)(i). Checked 2026-09-30.
[^35]: Under 47 CFR 4.9(g)(1)(ii), an interconnected VoIP service provider must notify the FCC within 24 hours of discovering an outage of at least 30 minutes that potentially affects at least 900,000 user minutes of interconnected VoIP service and results in complete loss of service, or that potentially affects special offices and facilities. Source: [47 CFR 4.9 - Outage reporting requirements - threshold criteria](https://www.law.cornell.edu/cfr/text/47/4.9), 47 CFR 4.9(g)(1)(ii)(A) and (B). Checked 2026-09-30.
[^36]: Under 47 CFR 4.9(g)(2), an interconnected VoIP service provider must submit a Final Communications Outage Report to the FCC not later than thirty days after discovering the outage. Source: [47 CFR 4.9 - Outage reporting requirements - threshold criteria](https://www.law.cornell.edu/cfr/text/47/4.9), 47 CFR 4.9(g)(2). Checked 2026-09-30.
[^37]: Genesys states that Genesys Cloud Voice number routing changes are processed within up to 10 minutes, showing a Pending status while processing. Source: [Genesys Cloud Voice number routing](https://help.genesys.cloud/articles/number-routing/), Rerouting procedure, statement on processing time (heading not returned verbatim). Checked 2026-09-30.
[^38]: Genesys announced on 2025-09-15, with a planned effective date of 2026-02-02, that Genesys Cloud Voice customers could configure a secondary organization in a different region as a backup destination for preselected phone numbers and revert routing once service is restored. Source: [Disaster recovery routing for Genesys Cloud Voice traffic](https://help.genesys.cloud/announcements/disaster-recovery-routing-for-genesys-cloud-voice-traffic/), Announcement header dates and 'What's changing' (heading as returned). Checked 2026-09-30.
[^39]: Genesys states that not all US and Canada phone numbers support redirection between linked organizations; eligibility is shown per number in a Redirection Capable column. Source: [Genesys Cloud Voice number routing](https://help.genesys.cloud/articles/number-routing/), Limitations statement on redirection-capable numbers (heading not returned verbatim). Checked 2026-09-30.
[^40]: Genesys Cloud Voice organization linking has no automatic failover: routing changes are manual, and during an outage an administrator must log in to the destination organization to reroute traffic. Source: [Genesys Cloud Voice organization linking overview](https://help.genesys.cloud/articles/genesys-cloud-voice-organization-linking-overview/), Limitations / considerations list (heading not returned verbatim). Checked 2026-09-30.
[^41]: The Genesys announcement of disaster recovery routing for Genesys Cloud Voice, dated 2025-09-15, limited the secondary-organization feature to the USE1 and USW2 regions (disputed). Source: [Disaster recovery routing for Genesys Cloud Voice traffic](https://help.genesys.cloud/announcements/disaster-recovery-routing-for-genesys-cloud-voice-traffic/), Announcement body, region limitation statement. Checked 2026-09-30.
[^42]: The Genesys Cloud Voice organization linking and number routing articles state that the feature is currently only available in the US East 1, US West 2 and Canada Central 1 regions (disputed). Source: [Genesys Cloud Voice organization linking overview](https://help.genesys.cloud/articles/genesys-cloud-voice-organization-linking-overview/), Availability note (heading not returned verbatim). Checked 2026-09-30.
[^43]: The 47 CFR 4.9(g) notification duties are addressed to interconnected VoIP service providers; on the text read, they do not by themselves impose outage reporting on an enterprise that merely operates a contact center on such a provider's service (inferred). Source: [47 CFR 4.9 - Outage reporting requirements - threshold criteria](https://www.law.cornell.edu/cfr/text/47/4.9), 47 CFR 4.9(g), opening words 'All interconnected VoIP service providers shall'. Checked 2026-09-30.
[^44]: In the vendor documentation read, protection against a single availability-zone failure is built into the platform (Amazon Connect, Webex Contact Center), whereas protection against a whole-region failure is a separate customer-configured capability that an administrator must set up in advance and trigger (Amazon Connect Global Resiliency, Genesys Cloud Voice organization linking) (inferred). Source: [Set up Connect Customer Global Resiliency](https://docs.aws.amazon.com/connect/latest/adminguide/setup-connect-global-resiliency.html), Note and Important boxes and API capability list, read together with aws-connect-resilience introduction, cisco-help-utqcm7-wxcc-architecture 'Business Continuity and Disaster Recovery', and genesys-help-gcv-org-linking-overview limitations. Checked 2026-09-30.
[^45]: If a tenant uses Continuous Access Evaluation tokens, the SBA is operational for only about 30 minutes; otherwise the SBA supports expired client authentication tokens for up to seven days from expiry. Source: [Survivable Branch Appliance for Direct Routing](https://learn.microsoft.com/en-us/microsoftteams/direct-routing-survivable-branch-appliance), Section 'Known issues and considerations', first bullet group and the Continuous Access Evaluation bullet. Checked 2026-09-30.
[^46]: The SBA feature is supported on Teams Windows desktop, Teams macOS desktop and Teams Phones; SBA mode activates only on desktop clients on a physical machine, and virtual machines and web clients are not supported. Source: [Survivable Branch Appliance for Direct Routing](https://learn.microsoft.com/en-us/microsoftteams/direct-routing-survivable-branch-appliance), Section 'Supported Teams clients'; section 'How it works', sentence beginning 'SBA mode activates only'. Checked 2026-09-30.
[^47]: In SBA offline mode, an incoming PSTN call to a call queue or auto attendant number can be redirected to a local agent or to an alternative call queue or auto attendant number. Source: [Survivable Branch Appliance for Direct Routing](https://learn.microsoft.com/en-us/microsoftteams/direct-routing-survivable-branch-appliance), Section 'How it works', list of calling functionality available in offline mode. Checked 2026-09-30.
[^48]: In SBA mode, Teams users can still make emergency calls but location information is not shared, and the SBA does not support Emergency Call Routing Policies, so emergency calls fail through the SBA if no pattern in the regular voice routing policy matches the emergency dial strings. Source: [Survivable Branch Appliance for Direct Routing](https://learn.microsoft.com/en-us/microsoftteams/direct-routing-survivable-branch-appliance), Section 'Known issues and considerations', list of unsupported user actions in SBA mode. Checked 2026-09-30.
[^49]: With a Direct Routing Survivable Branch Appliance, during an internet outage the Teams client automatically switches to the SBA and ongoing calls continue without interruption; users can make and receive PSTN calls through the local SBA/SBC. Source: [Survivable Branch Appliance for Direct Routing](https://learn.microsoft.com/en-us/microsoftteams/direct-routing-survivable-branch-appliance), Section 'How it works'. Checked 2026-09-30.
[^50]: Webex Calling Survivability Gateway features are available with Cisco IOS XE Dublin 17.12.3 or later. Source: [Site survivability for Webex Calling](https://help.webex.com/en-us/article/d68vi1/Site-Survivability-for-Webex-Calling), Prerequisites / gateway software requirement (heading not returned verbatim). Checked 2026-09-30.
[^51]: Webex Calling Site Survivability uses a local Cisco IOS XE router as a Survivability Gateway that takes over call control when the site loses its connection to Webex, supporting internal calls between on-site endpoints, external calls through a local PSTN circuit or SIP trunk, and E911 calls. Source: [Site survivability for Webex Calling](https://help.webex.com/en-us/article/d68vi1/Site-Survivability-for-Webex-Calling), Overview of Site Survivability and survivability-mode call support (headings not returned verbatim). Checked 2026-09-30.
[^52]: Webex Contact Center business hours include overrides, which define exceptions to regular shifts or working hours and can recur; when holiday lists or overrides conflict on the same day, the higher-priority item takes precedence. Source: [Set up business hours for Webex Contact Center](https://help.webex.com/en-us/article/dqekw4/Set-up-business-hours-for-Webex-Contact-Center), Sections on Overrides and on priority of holiday lists and overrides (headings not returned verbatim). Checked 2026-09-30.
[^53]: Cisco states that parts of the Webex Contact Center system or certain capabilities can be selectively disabled for all customers or select customers to minimize cascading effects of a failure. Source: [Webex Contact Center Architecture](https://help.webex.com/en-us/article/utqcm7/Webex-Contact-Center-Architecture), Section 'Reliability and Availability' (heading as returned by the fetch). Checked 2026-09-30.
[^54]: Cisco describes a Disaster Recovery and Business Continuity process for Webex Contact Center that detects a large-scale outage within a region and puts steps in place to recover services for customers on board in that region. Source: [Webex Contact Center Architecture](https://help.webex.com/en-us/article/utqcm7/Webex-Contact-Center-Architecture), Section 'Business Continuity and Disaster Recovery'. Checked 2026-09-30.
[^55]: Cisco consolidated Webex Contact Center incident, maintenance and complex feature rollout notifications under the Global Service Status platform effective August 1, 2025, discontinuing CJPIM email and Webex room alerts; customers subscribe by email or RSS. Source: [Subscribe to Webex Contact Center Incident and Maintenance Alerts](https://help.webex.com/en-us/article/obit3d), Introductory notice; sections 'Subscribe to incident management email notifications' and 'Subscribe to maintenance notifications'. Checked 2026-09-30.
[^56]: Cisco states that Webex Contact Center services are deployed in three separate availability zones within an AWS region, each a different physical location with independent utilities. Source: [Webex Contact Center Architecture](https://help.webex.com/en-us/article/utqcm7/Webex-Contact-Center-Architecture), Section 'Business Continuity and Disaster Recovery' (heading as returned by the fetch). Checked 2026-09-30.