The Zoom Community is here!
We welcome all Zoom customers to come together on the Zoom Community to ask questions, find solutions,
and collaborate with peers. Login with your Zoom account credentials and start collaborating!

Zoom Support Maintenance: 9/18/2021

Date and time: 9/18/2021 at 1PM PST for 10 hrs 30 min

We will be performing routine maintenance for Zoom Support. During this time, users may experience system delays or longer than expected wait times when contacting Zoom Support via phone, chat or web submission. All other request methods, based on your plan, will be available during this time. Please refer to https://support.zoom.us/hc/articles/201362003 for available contact options.

Affected components: Zoom Support Center

Enhanced Zoom Connector for SIP/H.323 devices Follow

Overview

Note: Starting January 18, 2021, new accounts provisioned with Cloud Room Connector licenses will automatically have access to the new enhanced API Room Connector for SIP/H.323 devices. If your account was provisioned a CRC license after January 18, use our enhanced room provisioning and management instructions for managing and deploying new rooms. 

The Zoom Connector Enhancement program is an architectural update of the Zoom Cloud Room Connector (CRC) management service. The current system has been re-built to become more scalable, enable new features, and become consistent with the Zoom web application framework.

The CRC Interop Service is responsible for: Registering and configuring SIP/H.323 managed devices (e.g. Cisco, Poly, Lifesize, etc.) to join Zoom Meetings, manage in-meeting device experience, and utilize one-touch calendar integration for quick joining of meetings. 

It is recommended that customers preparing for Microsoft's retirement of Basic Authentication should migrate to the updated Zoom Connector as soon as possible to take advantage of OAuth authentication for Calendar Integration.

This article covers:

Accessing the enhanced Zoom Connector

For customers currently using the legacy API Connector, access to the enhanced Zoom Connector for SIP/H.323 can be requested by contacting Customer Support. Once configured for the enhanced connector, you can migrate your devices from within the web portal.

Note: If you only want to migrate some of the SIP/H.323 devices in your account, you will need to set up an additional API Connector. Contact Customer Support for more information.

Additional features and enhancements

Improved interface- The improved management interface allows for easier yet more comprehensive device management.

Restart API connectors remotely- While the current room management API connector must be restarted locally, the enhanced API connector can be remotely restarted within the web portal. This can be useful when troubleshooting issues by admins of the Zoom account, especially if they do not have access to the local device or virtual machine the API connector is running on.

Unified calendar integration- The enhanced Zoom Connector utilizes a unified calendar integration API, which allows management sharing and management of calendar integration services between your SIP/H.323 rooms and Zoom Rooms. This improves calendar integration with SIP/H.323 rooms by:

  • Allows adding and managing of SIP/H.323 rooms calendar services and resources without adding the calendar mailbox address first
  • Supporting OAuth authorization for Office 365/Exchange and Google calendar services
  • Support for impersonation for Office 365/Exchange calendar services
  • Automatic syncing of calendar resources

Mute sync with Cisco and Poly devices- The enhanced Room Connector API allows for mute/unmute syncing between the Zoom meeting interface/Cloud Room Connector and a Cisco or Poly SIP/H.323 device. If the participants in the room mute the device using the remote or local interface, the mute status will sync with their Zoom audio status, and vice versa as well.

API Connector Scalability- With the enhanced API Connector, users can manage up to 400 devices per API Connector, allowing for greater scalability while utilizing fewer virtual machines.