This post was most recently updated on July 3rd, 2022
Depending on the business requirements, Zoom’s On-Premise solution can be configured in a variety of ways. When On-Premise is implemented, it is defaulted to create a single meeting zone, which allocates meetings evenly among all the servers within the zone. It is recommended that you create separate meeting zones for each cluster for servers if the servers will be geographically dispersed. This mode of distributing Zoom’s resources makes sure that Zoom will always choose the most appropriate and available zone for a given meeting, which is a serious job to ensure the quality of meeting and the standard of performance.
In order to support high availability within a zone, we would need at least one controller VM within each meeting zone, and another could be deployed if high availability was required. It is advisable to contact Zoom for best practices if you are deploying more than two zones.
In this article, we will explain how to set up multiple meeting zones. Getting Started with Meeting Connector is an excellent resource for establishing a single meeting zone.
Prerequisites for deploying multiple zones
- A meeting connector that has been deployed
Deploying the secondary meeting connector
Using the standard deployment procedures, first deploy a secondary Meeting Connector before configuring for multiple zones.
How to configure for multiple zones
- The URL pointing to the web management interface, which is provided on the console of the controller VM, may be used to log in. Please use the default administrator and password of the Controller VM.
- Click on the Network tab of the web management interface , edit the network settings and click on Save Settings as soon as they are completed.
- Selecting the Configuration tab, you can specify whether the VM will be the first controller for the meeting zone or the second controller for the meeting zone. The IP addresses for the controllers in the meeting zone should also be inputted.
- By visiting https://zoom.us/account/hybrid, you will be able to copy the account-specific on-premise token.
- The on-premise token has to be pasted under the configuring tab of the web management interface of the Controller VM.
- Click the Save Settings button.
- Using the console of the Controller VM, enter the username and password. The default user name and password are admin and admin respectively.
- You will need to open the following configuration file using a text editor: /opt/zoom/conf/ssb.cfg
- The setting referred to as MMZ is found on the SSB page of the SSB configuration. It should be changed to reflect the appropriate meeting zone by altering the number following the word zone.
- Save the ssb.cfg file.
- Make sure that the Controller Virtual Machine is rebooted.
- Repeat these steps for each additional Controller Virtual Machine.
- In case that there are other on-premise servers deployed, you will need to ensure that these also have the appropriate controller(s) assigned to the meeting zone at their location.