We have recently moved from Lync 2010 to Office 2016 that uses Skype For Business we are now seeing a problem where voice calls are dropped after only 5 seconds screen sharing seems to work OK as does IM when using our Anyconnect VPN solution. As soon as you connect your VPN tunnel Skype is not able to make calls any longer however calls started prior to connecting the VPN continue to work.
If the issue is still existedthe problem may caused by your accounttry to disable the account and re-enable the account in SFB control pannel.
Skype not working with cisco vpn. I make several calls a day and decided to get skypeOutIn. Make sure the field Local Address is not empty. Please consult your VPN appliance vendors documentation for more information on configuration recommendations.
A private IP address has the following form. Configuration of the VPN appliance is considered out of scope for this document. We didnt see any issues with the old Lync 2010 solution.
If it is fill in a private IP address. I take the laptop offsite log on to the corporate VPN and access Lync successfully. While on the VPN I can access Skype and the headsetmic work fine in that application.
I can hear but the mic does not work while using the same equipment as when I am onsite. I work in AZ but the parent company is in DC. Assumption is that the VPN works for other users from the same location.
I can also use Skype with no issues. I have Skype and a Cisco VPN client installed on Win2k and WinXp and no problems so it can work. I can IM and share desktops with another user.
I work at home and want to use a Cisco vpn client and skype connection at the same time. A tunnel-all VPN policy does not allow traffic to bypass the tunnel and does not work with this solution. If the issue is missing the problem is related to your pcFirst remove the mcafee in your computeryou could change another VPN and make a test.
Only problem is that I cannot connect to the home office and use skype at the same time. What the problem in your case is is hard to tell because I am assuming you track a Microsoft DLL or even Registry problem.