I ran across this while testing an issue a reader of my blog posted in the comments of an article I wrote about the Lync Basic 2013 client. They had mentioned that when a user using the Lync Basic 2013 client was set to A/V disabled the options for A/V were still presented in the client. In my testing I found this to be true and in fact the options were not only presented to the user, but A/V wasn't blocked if the user tried to initiate an A/V call to another user. For my testing I was using version 15.0.4420.1017 of the Lync Basic 2013 client. You can see in the screen shot below that even though the user is set to A/V disabled in Lync, the Phone tab and the Call Forwarding options still appear and the user is actually in a call with another user:
In addition, the options for starting an A/V call with another user are available:
Also, when looking at the A/V disabled user's presence from another client, you can see that they show as "Video Capable", even though they should be disabled for video:
If you compare this to the same user signed into the Lync 2013 client, you can see that the Phone tab and the Call Forwarding options are removed, as expected:
Also, the options for initiating an A/V call are removed as well:
So how does the Lync client know what features to make available when the user signs in? The answer is through information received by the client via in-band provisioning. The Lync client sends out a SIP SUBSCRIBE requesting provisioning information:
SUBSCRIBE sip:firstname.lastname@example.org SIP/2.0
The response is a SIP/2.0 200 OK and contained in the response is the setting we're interested in:
The telephonyMode setting can contain a couple of different values, depending on what the user is configured for:
It appears that currently the Lync Basic 2013 client is ignoring this setting and is allowing the user to initiate A/V sessions whether the user is enabled to do so or not.
Oh dear, hope my Lync Users don't read this!!!
Please fix MS!!
You may implement CAC to Limit the bandwidth over the WAN-Links. But not a solution for LAN.
Maybe you can configure static ports for A/V Usage and drop These on a Switch Level or Windows Firewall.
This is still an issue with Lync 2013 Basic 15.0.4517.1504.and Lync 2013 with July 2013 CU.
Is there any way to work around this issue? I tried various registry keys but they seem to get reset every time the client launches. Is there someone at Microsoft you can press to fix this perhaps? It's preventing me from deploying more Lync use in my organization.
The best way to get the product group to fix this is to open a support case. The more customers that raise this as an issue via support, the higher priority it will get when the PG looks at what to include in future updates.
It's definitely a big issue for all Lync Installation. On Office 365 there is no way anymore to disable AV on Lync. - don't understand why this was introduced. MS please solve this quickly. txs.
Indeed, just came accross it during deployment of Lync 2013 for a customer. Version *.1017
I could get at least video disabled using DisablePC2PCVideo registry key (as seen in post linked bellow. But I have not found any similar for disabling audio. DisablePC2PCAudio does not work.
I opened a support case in Microsoft. I'll update here when I get any news.
What did MS say? We are opening a case for this same issue. We want to remove the keypad, audio (phone icon), video (which we are able to do with reg), and the Desktop icon.
The case was archived two days ago. The engineer told us that Product Team already fixed the issue, on 09/19, but they don't have the official date to release it to public.
So, we will have to wait till then. Maybe a Premier Support case could get it faster.
I have been advised by MS that the fix has been identified and will be released in CU5 on 02/02/2104
Of course that should have read 02/02/2014. :-)