Zoomtopia is here. Unlock the transformative power of generative AI, helping you connect, collaborate, and Work Happy with AI Companion.
Register nowEmpowering you to increase productivity, improve team effectiveness, and enhance skills.
Learn moreKeep your Zoom app up to date to access the latest features.
Download Center Download the Zoom appDownload hi-res images and animations to elevate your next Zoom meeting.
Browse Backgrounds Zoom Virtual BackgroundsEmpowering you to increase productivity, improve team effectiveness, and enhance skills.
Zoom AI CompanionUser groups are unique spaces where community members can collaborate, network, and exchange knowledge on similar interests and expertise.
Help & Resources is your place to discover helpful Zoom support resources, browse Zoom Community how-to documentation, and stay updated on community announcements.
The Events page is your destination for upcoming webinars, platform training sessions, targeted user events, and more. Stay updated on opportunities to enhance your skills and connect with fellow Zoom users.
2022-09-21 03:02 PM
Today we tried to join a meeting hosted by a courthouse that has a zoomgov account.
Upon entering the meeting ID from the Zoom Room we received Error 100068000
https://support.zoom.us/hc/en-us/articles/5719956746765-Zoom-error-code-100068000
We were able to join the meeting by clicking the link from a laptop. For what it's worth, the laptop was connected to the same network as the Zoom Room.
Is this expected behavior?
If so is there any way to provide the capability to join meetings host by zoomgov customers from our Zoom Rooms, preferably without ruining anything else?
2022-11-25 01:35 PM
Zoom did have the option to join ZoomGov meetings from Zoom.us (commercial cloud). It is possible this option was disabled. You can try change Zoom cloud for your ZR from Zoom.us (default option) to Zoom for Government and then sign in into a ZoomGov meeting.
2022-11-28 07:12 AM
thanks avs, I forgot to close the loop on this... turns out that data decryption at our FW level was interfering