On premises Lync Server 2010. Clients mix of Lync 2013 and 2010.
We have a change in security requirements where dialin users now have to wait in the lobby whether the meeting organiser likes it or not. So, the global policy (the only policy) we set to PstnCallersBypassLobby $false. (See below.) However, PSTN dialin users still drop right into meetings without stopping off at the lobby. If I go into the meeting options (a newly created meeting), it says "Anyone (no restrictions)" which would explain it I guess. If I change it to "Only me..." then PSTN callers land in the lobby as you'd expect. My question is: if I have to set this on a per-meeting basis (or even if I "Remember Settings...), what is the point of the server-based PstnCallersBypassLobby option? I thought that the policy-based setting on the server was supposed to take precedence over the user settings?
I have check DB replication - it's all working fine, there are no event log errors anywhere and to be safe I have rebooted the whole Lync envionment. But, PstnCallersBypassLobby still seems to be ignored. Is this intended behaviour?
Get-CsMeetingConfiguration
Identity : Global
PstnCallersBypassLobby : False
TIA
m
EDIT: http://www.lynced.com.au/2014/07/set-all-conference-participants-to-wait.html implies that actually, PSTN users should not bypass the lobby with the above, so perhaps it's something wrong with the environment?
- Edited by M.a.r.k.T. _ Friday, January 30, 2015 3:47 PM