Deploying the Zoom Phone Local Survivability module

The Zoom Phone Local Survivability (ZPLS) module leverages the platform and OS provided by Zoom Node to allow organizations to have an on-premise failover for their Zoom Phone system.

This article covers:

• How to deploy the Zoom Phone Survivalbility VM
• How to install the Zoom Phone Local Survivability module

Prerequisites for deploying the Zoom Phone Survivability module

• Business, Education, or Enterprise account
• Zoom Node subscription
• Account owner or admin privilege
• VMware ESXI hypervisor

How to deploy the Zoom Phone Local Survivability VM

1. Sign in to the Zoom web portal.
2. In the navigation menu, click Node Management then click Modules.
3. Click the drop-down button , and click Phone Local Survivability.
4. Click the Nodes tab.
5. Click Add Nodes.
6. Click Download to download the Node OVA file. 
7. (Optional) Set the time for the Code Expiration in minutes. 
8. Click Generate.
9. Click Copy, to copy the registration code, and save it for use later.
10. Complete the deployment of the Zoom Node VM.

How to install the Zoom Phone Local Survivability module

Once the Zoom Node Phone VM has been deployed and registered, the Local Survivability module can be deployed on the server.

1. Sign into the Zoom Web Portal 
2. In the navigation menu, click Node Management then click Modules.
3. Click the drop-down button , and click Phone Local Survivability.
4. Click the Services tab.
5. Click Add Services.
6. In the new dialog window, click Local Survivability.
7. In the next window, fill in the following information
   • Install on a Server: Select the Zoom Node Phone server where the module will be deployed.
   • Internal IP: The internal IP address utilized for the module.
     Note: This address needs to be one that was assigned to the Node server during the initial configuration.
8. (Optional)
9. (Optional) Add a prefix for the Internal domain.
10. Click Add.

The Local Survivability module and components will proceed to install on the server. Once complete, the status of the module will be set to Stopped.

DO NOT start the module, until it has been assigned to a site during the configuration of the module.