-

SIP/H.323 Video endpoint vs. Native Zoom Room

While there are many approaches to providing high quality video experiences this article is going to explore the differences between using a standards-based codec approach compared to the native software-based codec approach on the Zoom platform. My opinions expressed in this article are solely mine. The Cloud Room Connector (CRC) from Zoom provides a gateway that enables standards-based codecs to join a Zoom Meeting.
Below is a diagram of how the CRC gateway approach works from Zoom:




Traditional SIP/H.323 video endpoints offer interoperability and flexibility allowing customers to pivot between different video strategies and platforms albeit on-prem video bridges from Poly, Cisco, Pexip to VaaS platforms such as Zoom or BlueJeans.  Many of these endpoints can register to more than one platform or at least video dial into many platforms using a one button to push (OBTP) experience.

The benefits of using a standard based codec include:
  •  Investment protection from video platform uncertainty
  •  Basic support for multiple video infrastructure and VaaS platforms
  •  Wide availability of room automation and integrations using control processors
  •  Occupancy based automation


At the same time SIP/H.323 video endpoints have many considerations.  Typically, the feature set has a lower fidelity experience compared to native video software solutions. Let me explain, while Poly and Cisco have a high number of proprietary features and functionality on their own platforms which include the RMX bridge and CMS Bridge respectively, these endpoints do not have the same rich feature set that is available from the Zoom platform running a native Zoom Room Solution provides. I equate it to using an open SIP phone from Yealink or Poly on a Cisco CallManager.  You get only a limited set of features also known as Sip-19 compared to a Cisco Phone.  We can of course argue the merits of out of band features like paging and multiple line registrations but none the less the feature set is limited compared to a native Cisco phone that can take advantage of all the features of the Cisco CallManager platform. Same is true with the Zoom Room software. Video solutions that depend on protocol level integration or gateways will only achieve basic functionality compared to the enhanced feature set of a system built purposely for the platform.

Zoom has also added One Touch Join capabilities for the Zoom Room platform through third party interoperability gateways provided by BlueJeans and WebEx CMR. Pexip and Poly RealConnect gateways provide one touch join capabilities into Teams meetings [reference: ‘https://support.zoom.us/hc/en-us/articles/360001163206-Join-a-Third-Party-Meeting-from-a-Zoom-Room’].  Zoom, Microsoft and Cisco also recently announced direct third party join using built in WebRTC browser on each respective platform. 

This level of interoperability diminishes the value proposition associated with a standards-based codec over a Native Zoom room system when using Zoom. And with the soon to be released Crestron Flex MX series which combines the best of both the Zoom native experience plus BYOD further makes the benefits of open standards-based video approach less relevant on the Zoom VaaS offering.  Demonstration here: 


I advise my customers looking at Zoom or who have Zoom to leverage native solutions based on the Crestron Flex system as it comes with one year free of Crestron Xio Cloud which is a centralized and zero touch provisioning management service built on Azure IoT Hub.  The merits of Xio Cloud  will be discussed in an upcoming blog. 

The benefits of going with the Zoom native experience include:
  •           Enhanced feature set
  •       Fewer incompatibility issues
  •           In band management and monitoring tools
  •           User Interface consistency which mirrors the desktop and mobile clients
  •           PSTN voice integration without third party middle or infrastructure-ware
  •           Shorter development cycles
  •            Better long-term security  
  •       Crestron API room automation control 
  •       Native Digital Signage solutions
  •       Native scheduling panel software
Instead of listing thousands of features comparing standards-based endpoints joining through a CRC connector I am going to spare you and provide you the links to the Zoom Website that shows the features.  You will notice a new category of appliances devices as well that are not PC based that show promise but they do not yet have feature parity with the software-based codec applications running on a MAC or PC.

Zoom Room Features: https://support.zoom.us/hc/en-us/articles/360038970952-Zoom-Rooms-Features

Zoom Rooms Controller Features: https://support.zoom.us/hc/en-us/articles/115000542566-Zoom-Rooms-Controller-Features

New Updates for Cloud Room Connector (CRC): https://support.zoom.us/hc/en-us/articles/201361983-New-Updates-for-Cloud-Room-Connector-CRC-

Comments

Post a Comment

Popular posts from this blog

Troubleshooting Microsoft Teams Proximity Join

-
Image
Troubleshooting Proximity Join Microsoft Teams Proximity join with Auto Answer for the Microsoft Teams Room system is an important feature in achieving the virtual ‘no touch conferencing room’. Using a mobile phone or personal computer we can start a meeting by selecting a nearby MTR using Bluetooth or by the Suggested room list which is a list of rooms that you’ve used recently on your calendar coming from the Exchange address room list.  The mobile phone or PC is used as the content sharing source in this case. The proximity join feature provides Bring Your Own Calendar (BYOC) with BYOD.  This feature provides increased calendar privacy without displaying your meetings on the touch controller interface and physical health & safety in not having to touch the conference room controller to start a meeting. But their are rules to be aware of when using these features and the tips and tricks that follow will help optimize the experience: 1. Make sure yo...
Read more

Automated Decline on No Show Meetings

-
Image
Microsoft Teams Room System with Occupancy based Automation Crestron recently introduced a new firmware that enables the pairing of the TSS scheduling panel and POE occupancy sensor together without the need for a control processor or Crestron Fusion. The scheduling panel talks directly to Microsoft Exchange and uses the same credentials as the Microsoft Teams Room (MTR) system. If a meeting on the calendar has been booked and no one has checked into the room from the scheduling panel or triggered the occupancy sensor with motion, the meeting will be canceled and the  Room along with the MTR will now be made available for use by other parties.    The CEN-ODT-C-POE occupancy sensor covers up to a 2000 square foot space. In addition to this functionality the LED lightbars and room signs indicate the following presence states:       þ   Green means the room is Available and not occupied   þ    Blue means the room...
Read more

Why can't I join Meetings from External Exchange Organizations?

-
Image
Joining Video Conferences hosted by external Exchange Organizations  You have now setup your Microsoft Teams Room system, Zoom Room system or any other Video conferencing endpoint and want to join meetings from external organization using One button to Push. But you find out anytime you forward the meeting to the Mailbox/Calendar for the room nothing ever shows up on the Calendar.  Sound familiar? The reason is because resource room mailboxes do not accept external calendar requests by default due to security considerations. This extends to both directly addressed or forwarded invites to the the video endpoint room's mailbox/calendar. We can confirm the 'resource room mailbox' does not allow external processing of calendar requests by running the following command.  This is just an example and your resource mailboxes names will likely be different. Get-CalendarProcessing "MTR" | fl Process*   To enable the Exchange resource room mailbox t...
Read more