![]() Announcements This option will only be available if dial-in conferencing is configured.You can only modify the selection of this check box if the previous drop-down list has either of the following options selected: People I invite from my organization or Anyone from my organization. Select this check box if you want meeting attendees that are calling in to bypass the virtual meeting lobby. Callers enter directly This option is only available if dial-in conferencing is configured.Anyone (no restrictions) Anyone can bypass the virtual meeting lobby.Anyone from my organization Anyone from the meeting organizer's organization can bypass the virtual meeting lobby.People I invite from my organization Only invited meeting attendees from the meeting organizer's organization can bypass the virtual meeting lobby.Only me, the meeting organizer Only the meeting organizer can bypass the virtual meeting lobby.Select a meeting access setting from the drop-down list: Direct Meeting Access This setting allows the meeting organizer to control who can enter the meeting directly, without waiting in the virtual meeting lobby for entry approval.Specify the Availability for the room by entering the dates and times you want in the Start Date and Time and End Date and Time drop-down lists.Ĭlick Show Advanced Properties to edit Advanced Properties. Select the Account Name from the drop-down list.Īdd a Description of the meeting in the space provided. Select Lync from the drop-down list and click Apply. Hope someone finds a solution for this issue.Important You can reuse the same room names for Microsoft Lync accounts. Have no possibility to detect, if the request is from a Lync Client.īecause we do not know to which non-federated access edges the internal clients want or have to be able to connect, we cannot configure bypasses on the proxy. They also are not willing to disable HTTPS inspection and on the proxy, we Companies which force redirection of tcp/443 from their internal clients to their web proxy, are not willing to change this. We know now the reason, but we do not have a solution. Of tcp/443 to their proxy, can join meetings of non-federated companies. Companies which do not have HTTPS inspection or do not force redirection All companies which have a proxy with active HTTPS inspection couldnt join the meetings hosted by non-federated companies. We could reproduce this behaviour with several installation. If we configure the web proxy to bypass all traffic to the access edge (and also web conf edge for whiteboarding, Q&A, polls, etc.) joining the meeting works. But the requests to the access edge are not HTTPS (which is SIP and not HTTP over TLS), so it cannot be done correctly and the authentication of Lync Client A at access edge B will fail. Because of the active inspection, the web proxy decryptĪnd encrypt all pakets over TLS. The web proxy is enabled for HTTPS inspection. The firewall of company A redirects all traffic, which seems to be web requests (in fact all traffic over tcp/80 and tcp/443) to their own web proxy. The requests contains requests to the reverse proxy of company B for the meeting URL and also SIP over tcp/443 to the access edge of company B. Lync Client A will join the meeting and sends all requests directly over tcp/443 trought the company A's firewall. Scenario: Lync Client from company A is in the LAN of company A and tries to connect to a conference of company B. Maybe we found the reason, why it is not working, but we didn't find a solution.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |