If Zoom was interested in customer security and compatibility with cloud-reg'd devices they could use the xAPI to communicate with the endpoint via the cloud, and therefore not require any action on the endpoint or its web UI, nor remove any of the management or support capabilities from Control Hub, while still giving Zoom plenty of access and the ability to get call status and info (what it'd need to verify an incoming call as being from an authenticated and licensed device). That's going to be a hell-no from me, considering Zoom doesn't have a good track record there. Here's the catch, the room kit will need to be managed by zooms platform. support and allow joining from an endpoint. Looks like free Webex accounts do have SIP/H.323/etc. I was wondering why some of the meetings I'd been invited to didn't have video addresses on them. If you're unaware, if you SIP dial into a zoom meeting host on a free account, You'll get an error saying the host does not have a H.323 license. The best solution would be for zoom to ditch the free account platform so anyone who wanted to use it had to pay. I promise our users will not appreciate having to ender a code to authenticate the device every time they join a customer or clients free zoom meeting. My question is, is there a way to set up co-managed room kit devices, managed by webex cloud and zoom, so that the authentication of our h.323 license will be seamless, while retaining management and integration with webex cloud? So, I called up Zoom sales, and found out that we, as an organization, could purchase H.323 licenses and use our license to join the meetings via WebEx room kit. Turns out, a majority of our clients use Zoom's free accounts. That's fine, we showed them where to find SIP dial-in information on various meeting platform invites, and all was well, or so we thought. Our company wants the ability to join any meeting platform on our room kit devices. Our room kits are registered to the WebEx cloud.
We currently have a few room kits available around the office.
0 kommentar(er)
