Note: As our world comes together to slow the spread of COVID-19 pandemic, the Zoom Support Center has continued to operate 24x7 globally to support you. Please see the updated Support Guidelines during these unprecedented times.




Deploying the Meeting Connector Follow

Overview

Zoom offers a public or hybrid cloud service. In the hybrid cloud service, you can deploy meeting communication servers known as the Zoom Meeting Connector within your company's internal network. User and meeting metadata are managed in the public cloud while the meetings are hosted in your private cloud. All meeting traffic including video, voice, and data sharing goes through the on-premise Zoom Meeting Connector. 

Note: Starting with release 4.5.201900.0926, the meeting connector has SSL Encryption enabled by default, so the Zone Controller and MMR must be configured with separate addresses, as both utilize port 443 for SSL. 

The Zoom Meeting Connector is packaged as an OVF and can be deployed onto any virtualization platform that supports OVF including:

System specifications for the VM can be found here

This article covers:

Prerequisites 

  • Business, Education, or Enterprise account
  • Host user type set to On-Prem
  • VM Client

Server setup

  1. Logged in as an Admin, click Advanced then Meeting Connector.
  2. Click Enable Meeting Connector.
  3. Click the Download tab.
  4. Click and download both the OVF and VMDK files under Controller VM.
  5. Open/Import the OVF and VMDK into your VM client.
  6. Once the Virtual Machine has been started, log in with the default credentials:
    • Username: admin
    • Password: This will be randomly generated on startup, but can set to a specific password that will not be displayed on startup.
  7. Use the command ifconfig to check the IP address of the server. If the server does not have an IP address, configure one manually. 
  8. In your browser, navigate to the web console at https://IPaddress:5480, with the IP address being the inet address listed in the ifconfig results. 
  9. Login with the default credentials. During first login, change the password.
  10. Click Network > Address
  11. Set the network address information for Eth0 Info and Eth0:0 Info.
    Note: eth0 Info can be set for DHCP, but eth0:0 Info has to be set as a separate static address provided by your networking group, as it utilizes IP aliasing.
  12. Click Submit. 
  13. On the Configure tab:
    • Enter the token from the Meeting Connector page of the Zoom web console.
    • The ZC and MMR IPv4 Addresses will autofill with the addresses assigned in the Network Address settings.
    • (Optional) Enter another address for a Zone Controller in the Another ZC IPv4 Address field if you have already set up another meeting connector, for High Availability. 
  14. Click Submit
  15. Go to Network, and check that both the zctrl and mmr processes are running.

Note: One Meeting Connector Controller OVF includes one Controller VM and an MMR VM. Each MMR supports up to 200 concurrent participants. You can always add more MMR VMs later, to increase overall capacity. 

Switching to production

  1. Logged in as an admin, click Advanced then Meeting Connector.
  2. Select the Monitor tab.
  3. Check that your Zone Controller is showing under Running ZCs.
  4. Select the Go Live tab, and click Switch to Production mode.
  5. On-Prem users on the account will now be able to host meetings using the new meeting connector.

Changing the Admin login password

  1. In the VM click Login.
  2. Login in with the admin credentials.
  3. Click User > Manage.
  4. Click Change Password next to the admin account
  5. Enter the current Admin password, then enter the new password, and re-enter it to confirm.
  6. Click Modify.

Advanced network configuration 

For more advanced network configurations, including firewall rules, 1 to 1 NAT, port forwarding, and DMZ configuration see: 

Managing the Meeting Connector

Restarting services

If the server needs to be rebooted for any reason, always check that all processes are running:

If processes are not running, click Stop, then start to restart the services.