Configuring Zoom Phone Local Survivability service module
Once a Zoom Node Phone server and ZPLS service module have been deployed, the service will need to be configured before starting the service for use in failover situations.
Requirements for configuring Zoom Phone Local Survivability
- Business, Education, or Enterprise account
- Zoom Node subscription
- Zoom Phone subscription
- Account owner or admin privilege
- A deployed Zoom Phone Local Survivability service module
- Multiple Sites is enabled for Zoom Phone
How to configure Zoom Phone Local Survivability
Assign a Local Survivability server to a site
- Sign in to the Zoom web portal as an admin with the privilege to edit account settings.
- In the navigation menu, click Phone System Management, then click Company Info.
- Click Account Settings.
- Under Zoom Node, locate Local Survivability.
- Click Manage.
- Click Assign to.
- Select the site the server will be assigned to.
- Click Save.
Enable Zoom Phone Local Survivability
While the Zoom Phone Local Survivability module can be enabled at the account level, it can also be enabled at the group, and user levels as well. Additionally, the setting can be enabled under the Policy tab of a site as well.
How to configure the Session Border Controllers (SBC)
A SIP Trunk must be established between the SBC and the ZPLS module. The SBC will need to have the DigiCert root and intermediate certificates installed to establish TLS connectivity to both the ZPLS module (as well as the Zoom cloud).
Adding the SBC within the Administration portal does not directly create the SIP Trunk between the ZPLS module and SBC. The SBC needs to be associated with a Survivability Route Group which is then associated with the appropriate Site/Account- only at this stage is the ZPLS module made aware of the IP Address details of the SBC that is used for external call routing
Integrate an SBC with the Local Survivability service module
- In the navigation menu, click Phone System Management, then click Company Info.
- Click Account Settings.
- Under Routing, locate Session Border Controllers.
- Click Manage.
- Click Add.
- Enter the Display name and Public IP address for the SBC.
Note: The IP address for the SBC needs to be reachable from the Local Survivability service module over port 5061. If utilizing 1:1 NAT, the addresses must be static. - Enable Bring Your Own PBX - Premises to ensure that BYOC numbers are routed correctly under normal conditions.
- Enable OPTIONS Ping Status, which will allow admins to verify the SIP Trunk connections between the SBC as well as the ZPLS module and the Zoom Cloud.
- Enable In Service.
- For IP Address for Local Survivability Connectivity for the ZPLS module, enter the IP address designated for routing traffic from the Local Survivability module to this Session Border Controller (SBC).
This address will be utilized by the module once the Suriviability Route Group has been added to a site.
Note: Zoom recommends utilizing the private address to avoid routing through the firewall and potentially needing to add complete route reflection rules.
Assign an SBC to a route group
Two route groups should be created at the account or phone site level to ensure PSTN connectivity is functional with the survivability solution:
- A route group is needed for assignment to the specific Phone System site that is enabled for survivability - the Survivability Public/Private IP Address defined within the SBC is pushed to the ZPLS module. Upon entering failover mode, ZPLS will send external calls to the SBC IP address contained within the Survivability Route Group. This route group does not contain a Region since the purpose of this route group is to establish a connection to the ZPLS module.
- At least one additional Route Group is required for routing incoming calls to BYOC numbers during normal conditions. In this instance, a SIP trunk is created between the Zoom Phone SIP Zone(s) contained within the Region(s) and the SBC Public IP address. Backup route groups are possible with this BYOC route group but not the survivability route group.
To add a route group:
- Sign in to the Zoom web portal as an admin with the privilege to edit account settings.
- In the navigation menu, click Phone System Management, then click Company Info.
- Click Account Settings, then click Route Groups.
- Click Add.
- Select the Session Border Controller added in the previous steps.
- Click Save.
Assign a Route group to a Local Survivability Service Module
- In the navigation menu, click Phone System Management, then click Company Info.
- Click Account Settings.
- Under Zoom Node, locate Local Survivability.
- Click Manage.
- Click Assign to.
Note: The selected Server should be assigned to a specific Site and when PSTN connectivity is required the survivability Route Group should also be assigned. - Select the Route Group created in the previous steps.
- Click OK.
How to configure call forwarding and BYOC numbers
To invoke Call Forwarding for the Survivability of native Zoom Phone numbers to users and devices located within the site undergoing an outage, BYOC numbers associated with the PSTN connection attached to the survivability SBC must be acquired. The number of BYOC extensions required is determined by the number of unique extensions needed during a failover. For example, if 100 users require a Direct Inward Dial service during an outage, 100 extensions must be acquired from the BYOC provider and subsequently, 100 Zoom Native numbers can be forwarded to the aforementioned 100 BYOC numbers.
Note: Zoom Native numbers can only be forwarded to BYOC numbers assigned to users within the Site that is being configured for Call forwarding Local Survivability.
In addition to Call Forwarding, a single BYOC number is required for emergency services support. This unique BYOC number can be configured as the Emergency Location Identification Number (ELIN) for the specific Site and must not be assigned to any user or Zoom Phone entity.
Add BYOC numbers for survivability
To add BYOC Numbers:
- In the navigation menu, click Phone System Management, then click Phone Numbers.
- Click the BYOC tab.
- Add or import via CSV any BYOC numbers that will be utilized for survivability.
Once the BYOC numbers have been added to the Site enabled for survivability, they must be assigned to users that will be enabled for survivability (the exception being the BYOC number dedicated as the ELIN for the Site). To add the numbers:
- In the navigation menu, click Phone System Management, then click Phone Numbers.
- Click the Assigned tab.
- Assign the BYOC numbers added previously to the desired users.
At this stage, users will be configured with a Zoom-provided PSTN number and in addition, a BYOC carrier-provided PSTN number. In the event of a failover, only the BYOC carrier-provided PSTN number will be functional.
ELIN configuration
Each site can be configured with a single Emergency Location Identification Number (ELIN). To configure the ELIN:
- Sign in to the Zoom web portal.
- In the navigation menu, click Phone System Management, then click Company Info.
- Click on the name of the desired Site.
- Click the Settings tab.
- Under Zoom Node, navigate to the Emergency Location Identification Number (ELIN) setting.
- Click Add Number.
- In the dropdown, select the desired BYOC number to be utilized for ELIN.
Note: This BYOC number must be unassigned. - To verify the ELIN number, click Phone System Management, then click Phone Numbers.
The BYOC number assigned as the ELIN will be displayed as assigned to Local Survivability.
Configure Call Forwarding numbers
Before any outage, administrators should set up call forwarding logic to determine how Zoom Native numbers are redirected in the event of an outage. To set up call forwarding:
- Sign in to the Zoom web portal as an admin with the privilege to edit account settings.
- In the navigation menu, click Phone System Management, then click Company Info.
- Click the name of the desired Site.
- Click the Settings tab.
- Under Zoom Node, navigate to the Call Forwarding Local Survivability setting.
- Click Manage.
- Click Add.
- For the Source Number(s), select the numbers being forwarded (can be a number or extension assigned to Users, Common Area Phones, Share Line Groups, Call Queues, and Auto Receptionists).
Note: Multiple source numbers can be forwarded to a single destination number. - For the Destination Number, select the BYOC numbers enabled for Local Survivability that has been assigned to users within the site.
- Click Save.
Note: By default the forwarding status of each source number is disabled.
Enable Call Forwarding
During an outage, admins will need to access the web portal and enable Call Forwarding for the selected numbers (the Select All option can be utilized to enable forwarding for all defined Source Numbers). To enable Call Forwarding Local Survivability:
- Sign in to the Zoom web portal as an admin with the privilege to edit account settings.
- In the navigation menu, click Phone System Management, then click Company Info.
- Click on the name of the desired Site.
- Click the Settings tab.
- Under Zoom Node, navigate to the Call Forwarding Local Survivability setting.
- Click Manage.
- Click Enable Forwarding.
How to configure routing rules for Local Survivability
Routing Rules that are being used under normal conditions can be preserved while survivability is active.
Note: Typically Routing Rules are used for customized call routing for BYOC-P in addition to preserving users’ legacy dialing habits. When routing rules are used by ZPLS, the Routing Path (SIP Group) is ignored, however, number translations are preserved.
- Sign in to the Zoom web portal as an admin with the privilege to edit account settings.
- In the navigation menu, click Phone System Management, then click Company Info.
- Click the name of the desired Site.
- Under the Zoom Node section, enable Enable Routing Rules.
- Click Save.
Note: Routing Rules defined at the Site level can be preserved by ZPLS. Rules at the account level will not be preserved.
Post configuration validation
Once your organization has deployed the Zoom Phone Local Survivability service module and configured the Local Survivability service, administrators can simulate a failover to verify the service is working as intended.