Since the host of the meeting has their own Skype for Business servers, this setup will only work with them. In total, we allowed one URL and three IP addresses. Once all of these addresses were added to the rule, our users could attend a fully functional Skype for Business meeting. Unfortunately, this did not solve the problem until we monitored the outgoing traffic and discovered that our attendees were trying to communicate with IP addresses apart from the one we allowed by URL. Basically, a rule that went no deeper than layer 3 They were unable to see the host's shared desktop or participate in VoIP in any way.Īs advised by Fortinet tech support, I created a firewall rule that allowed my users to reach the host's Skype for Business URL, allowing all services (all TCP/UDP ports), without application filtering, web filtering, anti-virus, or SSL inspection. On a Fortinet UTM and a policy that included application filtering (allowing Skype) and web filtering (allowing the domain name of the meeting host) along with anti-virus scanning and SSL inspection, I found that users were allow to enter a meeting, view a participant list and participate in chat. Some Skype for Business traffic does not survive packet inspection.

Microsoft does not make a standing meeting available for testing.For those looking for answers, this is what I have been able to find out.

Join skype meeting as guest