Allow the use of existing USB handset like Polycom CX300
Would love to be able use our existing investment in devices like the Polycom CX300 USB handset with Teams. I can understand why LPE devices won't be supported, but would like to see simple USB phones supported with the client.
Lauren M commented
We've been testing with the Plantronics Calisto P240 Handset. It works with teams although no part of the keypad itself functions. Is there a way to fix this? Or is there another Cheap Handset that would also be compatible with Teams?
Jason lee commented
As of Aug 29 running Teams Version 1.2.00.34155 on OSX the CX300 will now answer a call with picking up the handset and will hangup a call when placing the handset back on the hook switch.
In OSX the dial pad on the handset still does not do anything but the hookswitch does work correctly now. The phone display does however continue to display "Please Upgrade Office Communicator" even-though the handset is working more normally.
On Teams Version 1.3.00.21759 on Windows 10 the device seems to be working correctly now displaying the users name and allowing a call to be started by dialing on the dial pad on the phone.
Kevin Duffy commented
Agreed, we need this as well. This is a simple tool that was great in SfB. Otherwise create BTOE for other hardware platforms.
Leo White commented
I really am annoyed that there is no USB handset that has speaker phone and a handset in one. Having 2 different devices for a user is a pain.
I am also awaiting teams to support the CX300 and will migrate 50+ users once this happens. If not sorted we will move elsewhere
I am currently using a CX200 usb set with Teams and its working with both answer and hangup on the handset. all buttons are working (speaker, headset, mute and volume) nothing more i could wish for. (perhaps an updated teams logo :) )
Wim Allegaert commented
Great news! We want to migrate to Teams, but we have many CX300 phones and Teams-native phones do not support BTOE. Which would make it a hard migration for those use cases.
Matt Bratlien commented
Thank you Ryan for your 2/5/2020 comment. If you could update the link that would be most appreciated.
It would be sooooo great if these CX300 devices could be supported in the future. We've got a few thousand end users waiting for this feature before they move over to Phone System in Office 365 (love the new branding).
The user experience provided through USB is by far superior, intuitive, and easier to support than an Ethernet based IP phone that needs to be setup, secured, and managed. The CX300 Handset gives the non technical end user the comfort of the old way while moving them into the future of Teams.. Please bring back the support that Skype had!
Sometime in the last couple of weeks, https://support.office.com/en-us/article/control-calls-using-a-headset-in-teams-65d6e104-444d-4013-b8c2-f11317dd69a8 has been updated. The notes on the CX300 now say "The Polycom CX300 supports basic call controls such as answering, ending, and muting phone calls. Support for the phone's dial pad and display is expected in a future update."
I tested just now in Teams version 1.3.00.362 (64 bit) and was able to answer an incoming call just by lifting the handset. This is different to about two weeks ago when the hookswitch was completely ignored. This works even when the CX300 is not my default audio device in Teams.
Hanging up the handset does not end the call, it instead transfers it to the CX300's speaker. The mute button does now work. I also tested with the Plantronics 540-M and got the same results.
So, there's some progress! Someone at Microsoft is working on this. Hold on to your hope people
I can't believe there isn't a USB Handset that works with Teams. That was the competitive advantage that Microsoft had over any hosted phone system. Now they have eliminated that advantage in the new system they are forcing their subscribers to move to?!
Mitel and Vonage must be loving this ...
We are also in the same boat, Having invested in the CX300s ourselfs.This is holding us back to make the move towards Teams. If this isnt resolved before we are "forced" to make a choice , we probably wont make the choice towards teams as a voice platform, but take another route.
Indeed very frustrating. We invested in SfB and 50+ polycom CX300's.
Now this investment seems obsolete.
I thought Microsoft was better at supporting businesses.
Maybe it is time to consider Google stuff.
Ernie Hughes commented
Very frustrating, we keep hitting one road block after another trying to migrate to Teams. We have a lot of users that don't want to use a headset, they like the traditional type phone and now those users have to choose either an IP phone which they don't like or a headset that they don't like using. Is there a USB phone out there somewhere that works with Teams? We currently use the CX300 for those users on Skype for business.
Same issue here, our standard phone is the CX300 and this is blocking us adopting Teams...
I had to get a new USB for my Polycom CX300 and I need the pairing code. Can anyone assist me, please?
Can anyone from Microsoft provide a status on improving the CX300 interface with Teams? Maybe there is a software patch or plugin available? Thanks!
We're in the same boat and at 3000+ users, that's a lot of investment. We picked these simple USB phones purely so compatibility could be maintained going forward.
Now MS have announced the discontinuation of Skype for Business Online where we have thousands of users homed using PSTN in the cloud (and increasing every month), this needs fixing, otherwise MS will be losing a cloud revenue stream as we'll have to move everyone back on-premise. as we won't get the money to replace all the phones.
Andrew Laird commented
We have a massive estate of CX300's and this is a real show stopper for us.
Luke Taylor commented
This will block our transfer from SfB also. Too much to replace entire estate
We could even live with the dial pad not working, if pick up and hang up were at least handled properly. There are plenty of USB headsets that can handle pickup/hangup signalling to Teams, so I'm hoping this at least is an easy fix.