I tried it, but Skype was still using random ports.Versions / Builds Affected2015 StatusResolved Problem SummaryUnable to block Skype even when HTTPS scanning is enabled TT / JIRAID2007 How to IdentifyWhen a policy is created to block Skype the end users can still actively use Skype.

Third option, but it didn't work for me: you can specify a custom port in Skype connection options, then eventually authorize it in your policies.

If you don't want to allow those categories in the webfilter, skype will be blocked on standard ports and will use a RANDOM port to connect, so you must open ALL ports in your policy (since it's impossible to guess which one will be used) in order for the Skype to work. If I block 'Security Risk' category -> not working ! Even worse than that: putting the categories on 'monitor' also seems to block skype calls ! You must select AUTHORIZE.Ĭonclusion: Skype calls are blocked by the webfilter.Īllow skype to connect on standard ports by authorizing all websites in the webfilter, since it looks like skype is blocked in multiple web categories. Then apply, wait a few seconds, boom: Skype calls are working ! If I block pornography websites -> Skype is not working. My only option if I don't want to open all ports on my LAN policy in order for random Skype ports to work is to AUTHORIZE ALL WEBSITES IN THE WEBFILTER. All ports being open in my GUEST policy: CALLS ARE WORKING ! And the random port not being allowed in my LAN policy -> Skype calls are not working.įor the users under the GUEST policy, Skype is also blocked by the webfilter, then use another random port. After reading Skype documentation, i know that if Skype is blocked on standard ports (80 or 443), it will use a random port to connect.įor the users under my LAN policy, Skype is blocked by the webfilter, then use another random port. Logs are telling me that on BOTH policies, Skype is blocked by the webfilter. The only difference is: LAN policy only has a few ports open, while GUEST policy has ALL ports open. Both policies are using the SAME webfilter. I have 2 IPV4 policies for 2 types of users (let's call them LAN and GUEST). I investigated a bit and I found the culprit: webfilter.

I had the same problem on a Fortigate 90D: Skype chat works, but not calls.

Skype for web firewall block