I'm facing some issues with a customer where the Skype app is not working proplerly. Sometimes they cannot even connect to the service. They are using automatic proxy detection features with a wpad.dat file that controls if the traffic is or not sent by the proxies and which proxy should be used based on the IP address of the host.
When some user runs skype app on his computer I can see some requests directed to the WSA and some others sent directly to the ASA (this one drops these connections). At the end the app could either connect or not is random.
Somebody could give me some heads up about some workaround to allow the app through the WSA (Maybe I'm missing something)
Thanks in advance
Keep in mind Skype uses much more than just 80,443.
So not all Skype traffic will get redirected to your WSA. A lot of it will go out your ASA on non web ports.
sorry for the late reply , in the past i was able to make it work via ports 80 and 443 only, probably skype version 7.28 had a bug that was fixed in later versions
Found these links on Cisco and then Microsoft web sites.
It only shows Skype for Business so I don't know if it will help the consumer side.
It looks like you have to add a bunch of URL's and about 200 ip addresses to the exclusion list for the proxy.
I am in the process of adding them now and will let you know if it works.
Thanks for replying, i succesfully worked with Office 365 creating custom url categories that contains all office URLs and ip addressess listed in microsoft article related to SFB.Then i bypass https inspection for those categories and also whitelist them for http traffic and this works for Skype for business but was not working for consumer version. After some testing it seemes the problem was on skype side, in fact newer versions solved the issue, but really i think is not really necessary to install skype consumer if we use SFB 'cause of full integration between consumer and business version so SFB users in a company can fully interact with skype consumer users outside.