Forum Discussion
External users often stuck in lobby without being noticed. Known issue or bug?
DanHuber , experienced this issue today. External user joined teams meeting, was directed to the lobby. No one could see they were in the lobby or able to add them from the lobby. Is this problem being looked at?
I have found that problem to. I have tried to re join a meeting but i get stuck in the lobby. The organiser can't see me and i don't know why no one else has problems.
Hello NatHxGN ,
Funny coincidence. I am "battling" with a support engineer at Office 365 support since weeks. He resends sends me the same PowerShell commands to configure the room to allow externals to jump the lobby, again and again... and I tell him again and again that this setting is applied since months and that the problem still comes up for about 30% of external attendees..
In short, Microsoft support says "it should work".
Not much on real support beyond that, I'm afraid. Case ID is 19181100.
So, I still have this issue.
In the meantime I was able to figure out when this happens. Well, at least I think.
In my case, it happens to about every third or fourth external attendee who joins via a supported browser. External users using Teams seem not be affected.
I also found a possible workaround: the organizer should enter the meeting, check if all attendees are there yet. If someone is missing, leave the meeting and rejoin right afterwards. In most cases, the organizer then gets a popup that people are waiting in the lobby and they can be let in.
Please let me know if that works in your cases too.
Actually the room is setup to automatically let attendees bybass the lobby/waitingarea. But exactly that does not seem to work reliably.
The recommended setup is as follows (from the support engineer). Perhaps it works for you, but again, I have those settings applied since months and it still does not work 100%.
I also created new policies and reassigned them to all users, still no luck.
Policies as such seemed to have some issues a couple of weeks ago, though.
---
New-CsTeamsMeetingPolicy -Identity NoLobby -AllowOrganizersToOverrideLobbySettings $True -AllowPSTNUsersToBypassLobby $True -AllowAnonymousUsersToStartMeeting $False -AutoAdmittedUsers Everyone
Get-CsOnlineUser -Filter {Enabled -eq $true} | Grant-CsTeamsMeetingPolicy -PolicyName NoLobby
Get-CsOnlineUser -Filter {Enabled -eq $true} | Format-List userprincipalname
Set-CsTeamsMeetingPolicy -Identity NoLobby -AllowOrganizersToOverrideLobbySettings $True -AllowPSTNUsersToBypassLobby $True -AllowAnonymousUsersToStartMeeting $True -AutoAdmittedUsers Everyone
Set-CsTeamsMeetingPolicy -Identity NoLobby -AllowOrganizersToOverrideLobbySettings $True -AllowPSTNUsersToBypassLobby $True -AllowAnonymousUsersToStartMeeting $False -AutoAdmittedUsers Everyone
---
The last two cmdlets are unnecessary in my opinion, but the supporter insisted me to do it anyway. So
I did, no harm done.
Dan
