Lync For Mac 14.4.3 On Vpn

Lync For Mac 14.4.3 On Vpn 7,9/10 6595 votes
Notes

Here's a strange issue we've come across at our company. I loaded the Lync 2011 client on my Mac.

Mar 14, 2017 - This download contains an update for Lync for Mac 2011.

It connects to our Lync server just fine while plugged into the network at work. It connects just fine while at home, or anywhere else on the internet for that matter. However, when I connect to the VPN (we use the Cisco Anyconnect client), it has issues.

It will log in a quickly show me my contact list, and then immediately log me out. It never grabs any presence information either. On the server logs, I see where the user connected and downloaded the contact list, but then it gives me some errors, like these two: SIP/2.0 403 Location profile only available when UC enabled SIP/2.0 401 Unauthorized I'm not sure where the problem comes from. The Communicator 2011 client connects successfully, and on Windows we aren't seeing any problems like this either. It seems to be something going on in the Lync 2011 client.

Mac pro for video editing. This way, you can stabilize shaking images with one click, create a picture-in-picture effect with multiple videos playing at the same time, adjust the playback speed to view the action in fast or slow motion, add personalized subtitles and text messages to introduce or describe specific scenes, adjust the volume to put the viewer into the targeted mood, and insert photos between video frames and create interesting effects.” 5/5 –.

Has anyone else this behavior, or can anyone else test this in their environment? I ran into something similar, might not be related at all I have a lync environment with no enterprise voice enabled and had no issues with communicator. When trying Lync for Mac had the same issue you are reporting. This was on my internal network and not on VPN. I ended up changing the telephone association from Lync to the still resident communicator client in the preferences section and was able to sign in and all worked well. Still troubleshooting but found your findings interestingly similar to what I have going on.