We need BToE support with our Polycom deskphones. Without it, we will have to always run Skype for Business side by side to sign in our users to the phones.
Wim Allegaert commented
I could not get an order of 600 IPP's approved if this function is missing. Microsoft, please put this on the roadmap.
rob geach commented
you're selling teams native ip phones with 2 rj45 jacks and 0 bluetooth adapters.
obviously the best solution is to ignore the IP stack and instead build a solution from scratch around bluetooth.
Would love to have a BToE system where we can initiate calls using the PC client and then use our Teams desk phones. It shouldn't be so hard, having the desk phone connect to the PC to be a selectable audio device for communication via the PC client. It worked so well on SfB, why is this functionality missing in Teams.
Our company is holding off on 'upgrading' to Teams until there is something similar to BToE for our new Teams Yealink handsets. For now we have downgraded all of them to Skype for Business firmware.
Leo White commented
I have one company that is already on SFB Cloud PBX and want to move to Teams. I told them that it was possible because Teams had reached feature parity with SFB. Now it looks like they can't have a handset that integrates with there computer like SFB. That is not feature parity.
We invested thousands on Polycom phone betting on MS and SFB. We need a BTOE for Teams and VX Phone profiles.
Antoine Delaunay commented
We need this feature too urgently !
Mike Lahosky commented
We have just performed a migration from Lync 2010 to Teams cloud using the Yealink T55A and T58A phones. This is now a very big issue with the users when they want to have a video call on PC and have audio via their Yealink Teams certified phones. What is the ETA for the BToE feature?
Stace Hamilton commented
@Kruthika Ponnusamy Is there any sort of timeline for the better together experience?
Kruthika Ponnusamy commented
We are working on providing a "Better Together" experience with proximity support via Bluetooth for Teams phones. Once this feature is supported, the better together experience will work on Teams certified phones (https://products.office.com/en-us/microsoft-teams/across-devices/devices/category?devicetype=34) and the Teams desktop client.
Jay Hadley commented
BTOE is great when you want to dial from your PC and use your desk phone. I have spoken to a few customers that are hanging on the Skype for Business because this functionality is not in Teams
I have installed MS Teams on my PC and iPhone.
I have several Polycom Deskphones: excellent devices if you work in an office.
Simply enter your credentials directly to the Polycom Desk Phone.
If someone dials my MS Teams phone number, my iPhone rings as well as the Polycom Desk phone. This avoids using BToE or the MS Teams app on my PC.
I think the best option right now is to disable password expiration, and enable compensating controls like MFA and complexity requirements, so users just do web sign-in on a 3PIP phone and forget it.
Microsoft's baseline configuration policy is going to soon dump password expiration on Windows 10, but it comes with the caveat that you should be using MFA and some detective controls to understand when a password gets compromised.
We've been "upgraded" to Teams from SfB. We were using VVX600 with BToE on SfB. Now on Teams and no call control. Tried talking to Microsoft, who had never heard of CTI, or BToE, or call control. Oblivious to the need to connect with what they call "legacy" hardware. Was advised to switch to using a Yealink T58A, certified for Teams. Did this, but of course no device control there either. I can't believe the stupidity of MS sometimes. The majority of office user still use phone handsets and are likely to do so for many years.
Karl Peterson commented
I was wandering through and noticed this conversation, so wanted to chime in:
We are Microsoft partners, and involved in a variety of Teams Voice projects.
The guidance we have received from both Polycom and Microsoft is that BToE will not be coming to teams and VVX series phones. BToE as a standalone PC <-> Endpoint solution likely dies with S4B. What will happen instead is that Teams will gain better ability to interact with other teams endpoints on the same account - That way this functionality works whether you have a phone, a mobile app, or a desktop app. This will require all endpoints be teams-native however. So it won't work with any of the 3PIP devices.
It should also be noted that there are no guarantees as to overall 3PIP performance, just a best effort commitment, and Microsoft is now advising all teams users to plan for 3PIP replacement with native teams hardware.
You'll note that BToE is _NOT_ on the list of features they are planning to support for 3PIP /w teams.
Further proof here, by polycom employee back in March: https://community.polycom.com/t5/Skype-for-Business/Multifactor-Authentication-BToE-and-Teams/td-p/103678
Note I am not part of Microsoft, I'm just relaying information. We are migrating users to headsets + PC app as we move clients to teams, with some receptionists and call handlers getting a new teams-native phone.
I'll throw away my Polycom and my Microsoft PSTN dialing if this isn't sorted out soon!
We still need this ... we are scheduled to migrate next week and this is a show stopper. Is this a Microsoft issue or a Polycom issue?
Stace Hamilton commented
Agreed. We cannot move to full Teams without BToE or something else to bridge Teams and handset.
We just started upgrading our users from Skype for Business Online with CCE on-prem to using Teams with Direct Routing and quickly noticed that Teams doesn't support BToE. Or perhaps the phone vendor's software doesn't support Teams? Either way it makes for a horrible experience as Teams tries its best to use the handset as its input/output device. Safe to say we're rolling everyone back to Skype for Business.
Durwin Ritter commented
This is also mandatory. We cannot move to Teams without BToE support.