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.
In addition to assigning a single server to a site, a Node group can also be assigned to a site.
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.
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.
Learn more about configuring a Session Border Controller with ZPLS.
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.
To add BYOC Numbers:
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:
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.
Each site can be configured with a single Emergency Location Identification Number (ELIN). To configure the ELIN:
Before any outage, administrators should set up call forwarding logic to determine how Zoom Native numbers are redirected in the event of an outage. 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). Learn more about configuring Call Forwarding with ZPLS.
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.
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.