The Zoom On-Premise deployments, allow organizations to deploy meeting connector virtual machines within their internal company network. In doing so, user and meeting metadata are still managed in the Zoom public cloud. However, all meeting traffic (video, voice, in-meeting chat, and data sharing) is hosted in the organization's private cloud through the On-Premise Meeting Connector, Virtual Room Connector, and Recording Connector.
The On-Premise Meeting Connector environment comprises of several types of Virtual Machines: the Meeting Connector Controller, Multimedia Router, and the Recording Connector. These all require a Meeting Connector Controller to be deployed. The meeting connector controller contains two server processes: the Zone Controller (ZC) and Multimedia Router(MMR). While a Multimedia Router(MMR) VM simply contains just the MMR process. The meeting traffic is processed through the MMR while the Zone Controller helps decide which MMR to connect to for the meeting.
In addition to the Meeting Connector, there is also the Virtual Room Connector. This is a stand-alone process/virtual machine that allows SIP/H.323 room systems to connect to the Zoom Meeting. This does not require a Meeting Connector setup.
Note: The Meeting Connector, Cloud Recording Connector, and Virtual Room Connector downloads are disabled by default for all new Zoom customers and existing customers that do not currently have the connectors deployed. Customers who want to deploy any of these functionalities must contact Zoom to request enablement. This change does not impact existing customers with instances that are already deployed. To have this feature enabled, please contact the Zoom Sales team.
Multimedia Router (MMRs) each supports up to 200 concurrent participants. Depending on the scope of their system, you will want to calculate the MMRs and Meeting Connector Controllers that are needed. For example: If you need to support up to 1,000 meeting participants at any given time, you would need to deploy at least 5 MMRs (A Meeting Connector VM plus 4 additional MMR VMs). This setup would support up to 1,000 concurrent meeting participants.
For more information on the Meeting Connector concepts, including the networking schema for the on-premise service, please see Meeting Connector Core Concepts.
For instructions on deploying Meeting Connectors, please see: Getting Started with the Meeting Connector.
The On-Premise Recording Connector (RC) can support up to 2 simultaneous recordings for each CPU core. For a higher capacity of simultaneous recordings, you would need to increase the VM resources or deploy multiple Recording Connectors.
For instructions on deploying recording connectors, please see: Getting Started with the Recording Connector.
By default, The Virtual Room Connector (VRC) can support 2 SIP/H.323 connections at a time. The VM can be given more resources to support more simultaneous SIP/H.323 connections. For example: If you need to support up to 4 SIP/H.323 devices at a given time, you would need to have a single VRC with 8 CPU Cores and at least 8.4 GBs of memory. You could also deploy 2 VRC VMs each with 4 CPU Cores and 8 GBs of memory. A load balancer is also available for large scale deployments.
For instructions on deploying Virtual Room Connectors, please see Getting started with Virtual Room Connectors.
Telephony connections will still need to utilize the Zoom Cloud. To support this, the Meeting Connector will need to be publically accessible by:
On-premise deployment supports High Availability (HA). To configure this, the Zone Controllers will be configured as Zone Controller 1 and 2 to support failover.
On-Premise deployment supports multiple geographic Zones. This can be configured manually in the configuration file by changing a value within the /opt/zoom/conf/ssb.cfg file. For more information, please see Deploying Meeting Connector with Multiple Zones