Overview

In Zoom On-Premise deployments, organizations are able to build virtual machines in their internal network that will work as meeting connectors for multiple meetings. Consequently, both the user and meeting metadata remain in the Zoom public cloud and are therefore still accessible from the cloud. The On-Premise Meeting Connector, Virtual Room Connector, and Recording Connector, in conjunction with the On-Premise Meeting Connector, is used to carry out all meeting communications (video, voice, chat in-meeting, and data sharing) in the private cloud of our organization.

It contains several types of virtual machines which form the Meeting Connector environment on-premise, including the Meeting Connector controller, the Multimedia Router, and the Recording Connector. Each of these virtual machines is dependent on the Meeting Connector controller. Meeting connector controllers actually consist of two server processes that run simultaneously, being the Zone Controller (ZC) and Multimedia Router (MMR). An MMR VM contains just the MMR process, as opposed to a Multimedia Router (MMR) VM. It is the Meeting Management Resource (MMR) that manages the meeting traffic, while the Zone Controller serves as the aid that chooses which MMR is to be used for connecting to the meeting.

Additionally, the Virtual Room Connector can be used in conjunction with the Meeting Connector. In order to connect to Zoom Meeting a SIP/H.323 room system needs to be installed as a standalone process or virtual machine. Meeting Connector does not have to be setup in this case.

Note:

As a default, all new Zoom customers, as well as existing customers that do not currently have connectors installed, do not have access to the Meeting Connector, Cloud Recording Connector, and Virtual Room Connector downloads. In order to be enabled for any of these features, Zoom customers must contact their sales representative for assistance. This change does not affect existing customers who have already deployed their Zoom instances. Please contact Zoom Sales if you would like to have this feature enabled.

Capacities

Meetings and Webinars

Multimedia Routers (MMRs) are capable of supporting up to 200 concurrent users. In order to calculate the MMRs and Meeting Connector Controllers that the client will need, you will need to figure out the scope of their system. It goes without saying that if you need to handle 1,000 participants at any one time, you must have at least 5 Meeting Connector Virtual Machines (one Meeting Connector VM and four additional Meeting Connector VMs). A system like this could support up to 1,000 participants in a meeting at the same time.

Meeting Connector can be found in the Meeting Connector Core Concepts link, which provides more information about Meeting Connector, including the networking schema for the on-premise service.

Please refer to: Getting Started with the Meeting Connector if you would like instructions on how to deploy Meeting Connectors.

Cloud Recordings

There is a limit of two simultaneous recordings for each CPU core for the On-Premise Recording Connector (RC). Increasing the computing resources of your VM or deploying multiple Recording Connectors is necessary for a higher capacity of simultaneous recordings.

Please refer to the following article: Getting Started with the Recording Connector for detailed instructions on how to deploy recording connectors.

SIP/H.323 devices

There is a default setting of The Virtual Room Connector (VRC) that supports two simultaneous SIP/H.323 connections. It should also be able to handle more simultaneous connections for SIP/H.323 by assigning additional resources to the VM. You need at least 8.4 GBs of memory if a single VRC is going to support up to 4 SIP/H.323 devices at a time. As an example: If you need to support up to 4 SIP/H.323 devices at the same time, you should have a VRC with 8 CPU Cores. If you wanted to deploy two VRC VMs with four CPU cores each and 8 GB of memory, you could do so by deploying them both. To achieve large-scale deployments, there is also an available load balancer.

Please refer to Getting started with Virtual Room Connectors for information on how to deploy Virtual Room Connectors.

Telephony

In order to make phone calls, the Zoom Cloud will still need to be used. For this purpose, it will be necessary for the Meeting Connector to be publicly accessible by:

• Public IPs in DMZ
• Configured with 1:1 NAT
• Configured with Port Forwarding

High Availability Configuration

On-premise deployments can be configured to support High Availability (HA). In order to achieve this, the Zone Controllers need to be configured as Zone Controller 1 and Zone Controller 2 to ensure that failover is possible.

Multiple Zone Deployment

Multiple geographic zones can be deployed with On-Premise deployment. By changing a value in the /opt/zoom/conf/ssb.cfg file, the user can manually configure this in the configuration file. To learn more about deploying Meeting Connector with multiple zones, please see Deploying Meeting Connector with Multiple Zones