For Avaya Enterprise Cloud (AEC) deployments, Avaya SBC supports upgrades without any maintenance window and with minimal service disruption.

The following shows a typical setup of AEC deployment with Zero Down Time support:

The AEC deployment has two zones. Each zone has single or multiple Avaya SBCs based on the customer requirement.

Users are distributed across zones. For example, if a customer deployment has 1000 users, 500 users are registered in zone 1 as primary and zone 2 as secondary. And, the other 500 users are registered in zone 2 as primary and zone 1 as secondary.

This process provides seamless upgrade for both remote worker and SIP trunk calls.

You can upgrade a single Avaya SBC at a time or all Avaya SBCs in a zone at once. However, it is recommended to upgrade a single Avaya SBC at a time. Other Avaya SBCs in the same zone continue to function.

Users with no call activity are drained immediately from the current Avaya SBC that is being upgraded to the Avaya SBC in the other zone. Active call users are drained once they complete the call. Users will be able to perform all mid-call operations across the upgrade process.

SIP trunks distribute incoming calls using the DNS-SRV method. DNS SRV records are manipulated by Cloud Orchestrator to redirect SIP trunk traffic from the Avaya SBC that is being upgraded to Avaya SBC in the other zone. New calls are redirected to the other zone whereas active calls continue on the same zone till complete.

Cloud Orchestrator is used for scheduling upgrades for AEC deployments. Cloud Orchestrator monitors the active call count and starts the upgrade process when the active call count becomes zero.

For more information, refer to AEC Application Notes.

Avaya SBC supports registrations of Third-party endpoints such as FlyingVoice endpoints. It also supports Zero Down Time workflows.