Hello, I recently deployed some Yealink MP50 USB phone devices to my agency users who are on Teams Voice. For some, the MP50 works perfectly: plug and play and away we go. Unfortunately, for most users they can't start, answer, or end calls but the pause/resume and mute/unmute work fine during a call. If they start a call from the phone's controls it looks like it is attempting to dial out but nothing happens on the PC and it eventually ends If they receive a call it shows up on the MP50's screen but the answer and decline buttons do not work and neither does pressing speakerphone or picking up the handset. If a user starts or answers a call on the PC they can use the MP50 for microphone and audio Picking up the handset switches it from speakerphone to handset, If I do a test call on the troubled setup, Teams displays a banner saying "No device call controls. Exit other calling apps so you can use your device call controls with teams. I have worked with Yealink support through a lot of troubleshooting, but unfortunately have not resolved the issue. I will give a rundown of the troubleshooting. Our Teams accounts are in Teams only mode and we do not have Skype for Business I have troubleshot the issues for a couple of months, so it has persisted throughout Teams updating I have troubleshot on a couple of different firmware versions of the MP50 For those having issues, I switched them to a device that worked on another PC but it didn't work on theirs For those having issues, I took their device and put it on another PC that had a working one and it worked there I've tried multiple device resets I've deleted out all drivers out of device manager and reinstalled it, multiple times I've tried completely removing Teams and all files/folders from the PC and then reinstalling and setting up Teams Here is a rundown of some extensive process of elimination troubleshooting I did, with users A and B MP50 works on user A's setup but not user B's setup User B logs into their Teams account on user A's PC with user A's domain account logged in, the MP50 works User B logs into their Teams account on user A's PC with user's B's domain account, the MP50 works User A logs into their Teams on user B's PC with user B's domain account logged in, the MP50 doesn't work User B logs into their Teams account on user B's PC with user A's domain account logged in, the MP50 works To me, this eliminates the possibility of the device, the PC, the Teams accounts, and the Domain account from being the issue and just leaves it to being an issue with the local Windows profile on the PC. I hope someone can provide some other troubleshooting options. I may have to look at alternatives, but what from I've seen it sounds like most other phones run Teams as a separate instance, creating several other drawbacks, or else have to be dumbed down to operate similar to the MP50 which makes them a waste of money. Thanks

I have it working on 25769, but the same build at a colleague didn't work. My other colleague build did work, few days later the next one, after that mine suddenly started working. All using 25769

Was told by Microsoft the latest release for teams public preview has reported to fix phone issues. This is not the case for me. Any others have success? Some do work again, , but only a small set, no clear solution on who can and who can't

We've made some progress with the WH66 DECT headsets here, too. They're very similar, hardware and firmware wise, to the MP50s and just have a wireless DECT headset and touchscreen in place of the MP50's handset and keypad. We were previously unable to dial out with them on Mac or Windows Teams clients, as I detailed earlier in the thread. My one test Windows user can now successfully dial from the WH66, but my colleague and I with Macs are seeing a new failure mode. Whereas before we saw no dialling activity in the Mac Teams client (but sometimes heightened CPU usage), we're now seeing the Teams client attempt to place a call, but with a completely mangled dial string that fails. For example, trying to dial my mobile number as 07989XXXXXX (number obfuscated for posting here, obvs.) the WH66 appears to instruct Teams to dial '1080*090*0208030306090', and the same number is stored in the call history on the WH66 itself. If, however, I dial the same number directly in the Teams interface on the Mac it is dialled and connects correctly. The mangled number is reproducible; whatever you dial you always get a matching mangled number. I've tried this in the Preview (25762) and regular versions (22362) and see the same behaviour.

Yes, I have Yealink USB Connect software installed. I assume you have Teams version Teams 1.5.00.25769(64bit) from a Public Preview (as I did). That's the only non-standard part of the set-up I have. I'm sure this hasn't been overlooked given how many times you appeared to have tried and tested this, but when people have tested on 1.5.00.25769, have they made sure to set the Yealink as the audio device in the Teams client? I only ask as I made that mistake a couple of times when testing in haste.

Before today, all General releases of teams would not let you dial-out from the Yealink phones. Microsoft fixed the issue and only has released it for Public Preview as of last Friday. Today Microsoft is supposed to release it as a General Release update, maybe depending on where you are in the world you might get it a different times. I have not received it yet. If you aren't using Public Preview and need it to work right away, enable it, if you can wait, I hope the General release comes out at any time.

Teams: Yealink MP50 unable to start, answer, or end calls

Anonymous

Hello,

I recently deployed some Yealink MP50 USB phone devices to my agency users who are on Teams Voice. For some, the MP50 works perfectly: plug and play and away we go.

Unfortunately, for most users they can't start, answer, or end calls but the pause/resume and mute/unmute work fine during a call.

If they start a call from the phone's controls it looks like it is attempting to dial out but nothing happens on the PC and it eventually ends
If they receive a call it shows up on the MP50's screen but the answer and decline buttons do not work and neither does pressing speakerphone or picking up the handset.
If a user starts or answers a call on the PC they can use the MP50 for microphone and audio
Picking up the handset switches it from speakerphone to handset,
If I do a test call on the troubled setup, Teams displays a banner saying "No device call controls. Exit other calling apps so you can use your device call controls with teams.

I have worked with Yealink support through a lot of troubleshooting, but unfortunately have not resolved the issue. I will give a rundown of the troubleshooting.

Our Teams accounts are in Teams only mode and we do not have Skype for Business
I have troubleshot the issues for a couple of months, so it has persisted throughout Teams updating
I have troubleshot on a couple of different firmware versions of the MP50
For those having issues, I switched them to a device that worked on another PC but it didn't work on theirs
For those having issues, I took their device and put it on another PC that had a working one and it worked there
I've tried multiple device resets
I've deleted out all drivers out of device manager and reinstalled it, multiple times
I've tried completely removing Teams and all files/folders from the PC and then reinstalling and setting up Teams

Here is a rundown of some extensive process of elimination troubleshooting I did, with users A and B

MP50 works on user A's setup but not user B's setup
User B logs into their Teams account on user A's PC with user A's domain account logged in, the MP50 works
User B logs into their Teams account on user A's PC with user's B's domain account, the MP50 works
User A logs into their Teams on user B's PC with user B's domain account logged in, the MP50 doesn't work
User B logs into their Teams account on user B's PC with user A's domain account logged in, the MP50 works

To me, this eliminates the possibility of the device, the PC, the Teams accounts, and the Domain account from being the issue and just leaves it to being an issue with the local Windows profile on the PC.

I hope someone can provide some other troubleshooting options. I may have to look at alternatives, but what from I've seen it sounds like most other phones run Teams as a separate instance, creating several other drawbacks, or else have to be dumbed down to operate similar to the MP50 which makes them a waste of money.

Thanks

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments

132 answers

Anonymous

2022-09-26T12:20:58+00:00

I have it working on 25769, but the same build at a colleague didn't work. My other colleague build did work, few days later the next one, after that mine suddenly started working. All using 25769
Was this answer helpful?

0 comments No comments
Anonymous

2022-09-26T12:17:29+00:00

Was told by Microsoft the latest release for teams public preview has reported to fix phone issues. This is not the case for me. Any others have success?

Some do work again, , but only a small set, no clear solution on who can and who can't
Was this answer helpful?

0 comments No comments
Anonymous

2022-09-26T10:48:36+00:00

We've made some progress with the WH66 DECT headsets here, too. They're very similar, hardware and firmware wise, to the MP50s and just have a wireless DECT headset and touchscreen in place of the MP50's handset and keypad.

We were previously unable to dial out with them on Mac or Windows Teams clients, as I detailed earlier in the thread. My one test Windows user can now successfully dial from the WH66, but my colleague and I with Macs are seeing a new failure mode.

Whereas before we saw no dialling activity in the Mac Teams client (but sometimes heightened CPU usage), we're now seeing the Teams client attempt to place a call, but with a completely mangled dial string that fails.

For example, trying to dial my mobile number as 07989XXXXXX (number obfuscated for posting here, obvs.) the WH66 appears to instruct Teams to dial '1080*090*0208030306090', and the same number is stored in the call history on the WH66 itself. If, however, I dial the same number directly in the Teams interface on the Mac it is dialled and connects correctly. The mangled number is reproducible; whatever you dial you always get a matching mangled number.

I've tried this in the Preview (25762) and regular versions (22362) and see the same behaviour.
Was this answer helpful?

0 comments No comments
Anonymous

2022-09-23T22:28:26+00:00

Yes, I have Yealink USB Connect software installed.

I assume you have Teams version Teams 1.5.00.25769(64bit) from a Public Preview (as I did). That's the only non-standard part of the set-up I have.

I'm sure this hasn't been overlooked given how many times you appeared to have tried and tested this, but when people have tested on 1.5.00.25769, have they made sure to set the Yealink as the audio device in the Teams client?

I only ask as I made that mistake a couple of times when testing in haste.
Was this answer helpful?

0 comments No comments
Anonymous

2022-09-23T21:05:03+00:00

Before today, all General releases of teams would not let you dial-out from the Yealink phones. Microsoft fixed the issue and only has released it for Public Preview as of last Friday. Today Microsoft is supposed to release it as a General Release update, maybe depending on where you are in the world you might get it a different times. I have not received it yet. If you aren't using Public Preview and need it to work right away, enable it, if you can wait, I hope the General release comes out at any time.
Was this answer helpful?

0 comments No comments