How can we make Microsoft Teams better?

← Public

BToE

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.

113 votes
Sign in
(thinking…)
Sign in with: Facebook Google
Forgot password?
Create a password
Signed in as (Sign out)
Close
Close

We’ll send you updates on this idea

JR Walters shared this idea  ·   ·  Flag idea as inappropriate…  ·  Admin →

23 comments

Attach a File
Sign in
(thinking…)
Sign in with: Facebook Google
Forgot password?
Create a password
Signed in as (Sign out)
Close
Close
Submitting...
An error occurred while saving the comment
  • cosmicNavigator commented  ·   ·  Flag as inappropriate

    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.

  • AKArt commented  ·   ·  Flag as inappropriate

    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.

  • Anonymous commented  ·   ·  Flag as inappropriate

    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  ·   ·  Flag as inappropriate

    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.

    MS guidance article: https://techcommunity.microsoft.com/t5/Skype-for-Business-Blog/Skype-for-Business-Certified-IP-Phones-with-Microsoft-Teams/ba-p/286073

    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.

  • FHM commented  ·   ·  Flag as inappropriate

    I'll throw away my Polycom and my Microsoft PSTN dialing if this isn't sorted out soon!

  • Dave commented  ·   ·  Flag as inappropriate

    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?

  • Brad commented  ·   ·  Flag as inappropriate

    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.

  • Anonymous commented  ·   ·  Flag as inappropriate

    We also need BToE support on Teams before moving -- the feature is paramount to the success of S4B in conjunction with the desk phone. Teams will seem like a downgrade and will not be accepted if the users are losing features that they rely upon now.

  • Craig Jacko commented  ·   ·  Flag as inappropriate

    This is a must for desk bound users that have both headsets and Yealink desk phones. Our users need to be able to easily switch between both devices while in a call, which is easily accomplished in SfB.

  • Anonymous commented  ·   ·  Flag as inappropriate

    Same request here - we have 100's of VVX phones and we need to plan our migration to MS Teams. The BToE compatibility is a must. Polycom will not answer to this either!

  • Anonymous commented  ·   ·  Flag as inappropriate

    Agreed, the customers we support require this feature and are unwilling to move untill it is available

  • Justin commented  ·   ·  Flag as inappropriate

    This is a must or we will NOT move to Teams. Our users use this feature heavily.

← Previous 1

Forum Home

Reference Information for Teams

Public: IP Phones

Feedback and Knowledge Base

(thinking…)

More Teams Information



You are about to visit the UserVoice site for Microsoft Teams

We have partnered with UserVoice, a 3rd party service providing public discussion forums for product-specific feedback.

By clicking "Continue to UserVoice" you agree to UserVoice's Privacy Policy and Terms of Use.