Add BToE standard component into Lync Client
At this moment 3PIP phone vendors have to create it's own version of BToE PC client and add the function to the phone fw.
The results are not so good and very different between vendors, so the user experience is not uniform.
I think MS should add a standard BToE component into Lync Client, so the 3PIP vendors only need to add the BToE to the phone code, and the IT stuff do not need to add a separete BToE client.
This is the one thing stopping us from using Lync as a phone system. Most of our users use remote desktop server in the office and all of them use it at home. Our current system allows phone control over the network but Lync does not and I haven't found any vendor that enables it for RDS users.
Randy Chapman commented
This could be such a fantastic addition to Lync/S4B. The ability to pair the desktop client with the IP Address of a SIP Phone would open up so many possibilities. The biggest and most obvious one (to me) is the ability to pair the client running on a remote desktop with a SIP phone plugged in beside them. The other advantage is for using standard SIP phones as endpoints without the need for middle-ware such as SPS. Companies can "Flash" their phones with a generic SIP image and use them for Lync/S4B, thus extending the life of existing assets. This is often a barrier to sale of the ultimate MFST goal of Enterprise Voice in the product.