topic Re: Resource Room - simple Q in Webex Meetings and Webex App

Resource Room - simple Q

Accelit21 — Tue, 12 Aug 2025 05:06:55 GMT

I think I'm missing something simple. Corporate location. We have a Logitech TapIP.

We have a ResourceRoom (shared) Microsoft Acct. Goal: be able to join Webex meetings sent to ResourceRoom in the same manner as ResourceRoom can join a Zoom meeting. (After my testing, Zoom & Webex meeting invites may be sent to us by users external to our company & domain. Our users, such as Sales dept, can forward external invites to ResourceRoom.)

Yes I can create a free Webex test meeting and copy the details. I can create a meeting in Outlook (tap "Don't Host Online" to remove Teams meeting links) and then send the invite to ResourceRoom. ResourceRoom does automatically accept this meeting on calendar, with Zoom link or Webex link. My test meeting I hosted showed up as Webex meeting on the TapIP interface.

Yes, I can tap the Join button and join Webex meeting. I can go to the Lobby. So far, so good.

PROBLEM: When I tried to allow ResourceRoom to join my test meeting, Webex in browser had no buttons to allow ResourceRoom to Join from the Lobby. Webex told me that ResourceRoom was not authenticated or signed in, so Webex can't verify their identity.
There is no email Inbox for Microsoft shared ResourceRoom accounts. Users listed as Delegates can accept (or reject) Calendar items, aka meetings. ResourceRoom account seemingly can't receive the webex_comm@webex.com email with the 6-digit confirmation code, because this specific email isn't a Calendar item. That prevents me from making ResourceRoom authenticated or signed in, per Webex rules. I don't see an option in Webex to override the listed rules for authentication for this ResourceRoom account. ResourceRoom is in the same domain as the Host of the test account. I obviously trust ResourceRoom.

I think I'm missing something simple. How do I get past this barrier?

Re: Resource Room - simple Q

Jonathan Schulenberg — Tue, 12 Aug 2025 22:53:51 GMT

The unverified label is merely an advisory to everyone else on the meeting that Webex has no idea if that guest participant is actually whatever name they typed in when joining because they didn't sign in first. Administrators can disable it (not recommended) for meetings hosted on their site but it wouldn't change the actual problem you're having: lobby control.

The default behavior is to contain unverified guest participants and external authenticated participants to the lobby until a host or co-host admits them while internal authenticated users and video endpoints* bypass the lobby to join the meeting directly. Again, these settings can be changed by an admin for meetings hosted on their site but they are important safeguards against malicious joins (a.k.a. "Zoombombing"). Note there there are separate controls for scheduled & PMR meetings; the linked help article covers both.

* For a video endpoint to bypass the lobby it must be recognized as an internal participant. There are two ways to achieve this in Cisco's ecosystem:

A Cisco video endpoint uses Cloud Device Registration or Webex Edge for Devices with Optimized Join Experience to join a customer's Webex Control Hub tenant. Devices operating in this state are inherently trusted.
A SIP join that uses mutual TLS with a DNS domain that is at least verified in the customer's Webex Control Hub tenant.

The expectation is that a host or co-host manually admits this device from their laptop/mobile device. A Cisco cloud-reg or cloud-aware video endpoint (#1 above) can also serve as a co-host to admit folks from the lobby.

Re: Resource Room - simple Q

Accelit21 — Wed, 13 Aug 2025 18:42:55 GMT

THANK YOU for all the clarifications. NO FURTHER RESPONSE NEEDED at this time. I will try another test meeting, using the following steps (from Google AI):

Individual Admission: Select the checkbox next to the participant's name and click "Let in". [I didn't see that option."my embarrassed-face"]

----------

Considering that these future meetings will be infrequent, created by a Webex customer who is external to our company, and our device isn't a Cisco device, then that Host should have the power to admit our Logitech TapIP device aka ResourceRoom at ourcompany dot com to their meeting. I didn't see that option in my first test meeting. Maybe an embarrassing oversight on my part.

Re: Resource Room - simple Q

Accelit21 — Wed, 13 Aug 2025 21:55:16 GMT

Now this worked. I had clicked [Join] on the device aka ResourceRoom user but at some point back at my desk, ResourceRoom user must have exited the Lobby or timed out. I saw no visible option to "let in" as described in online documents.

Today, I saw the option for "waiting in the lobby" briefly for one second, then it vanished. Now I knew what to do.

I went back to the Logitech device and clicked the [Join] button again. I hurried back to my desk and my running meeting. Then the interface made it possible to move ResourceRoom user from Lobby to the meeting. Worked perfect.