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

Hi, I've found another issue on the MP50. If i start a call with dialing +.... on the dialpad of the MP50 and press the call button on the screen of the MP50, Microsoft Teams starts the call without the +. Only the digits behind + are called from Teams So calls starting with + with the MP50 Dialpad and Microsoft Teams are not possible By the way (+ will be dialed if you hold the 0 Button) Do you have the same issue? Can you check this please. Thank you Markus

Has anyone thought to push this towards Yealink, for a firmware upgrade from them for the MP50. We purchased one MP50 for testing when they were first available, well over a year ago and to our knowledge Yealink has never provided a firmware upgrade. We had issues from the jump with this phone on Teams, and even after we switched to a Teams-only mode across our network the phone still had issues...mainly the user's status indicator in Teams does not flow to the same status indicator on the MP50. Was told by Yealink back then that a firmware upgrade would be coming to resolve this...never seen it. Now, as of last week, with some late-breaking changes to Office 365, what we thought were only look-and-feel changes, now we find the MP50 "Teams" button (under the * keypad key) doesn't light any longer. Haven't tested other functions and features of the phone yet but won't be surprised if we find other things not working. As a side note, on day one of this phone on our network while still in the Skype-as-primary mode the phone worked perfectly, all functions, buttons, displays and features worked correctly on Skype, strange for a phone sold specifically as a Teams-compatible phone.

OK I think we've got to the bottom of this. The test account which we configured in SfB to replicate the issue, but in fact worked with the phone, had a coexistence mode of Teams Only ! Why this was not Org Wide, with the Skype for Business options I have no idea, because in fact the user is homed in SfB and is working on SfB. However, as soon as we changed the coexistence mode to Org Wide the phone stopped working correctly. We tried to flip it back to Teams Only, and it rightly said that it couldn't do this as the user is homed in SfB. So why was it set on this in the first place!! So, it seems once we have fully migrated off of SfB onto Teams, with the coexistence mode set correctly, the MP50 should work with no issues for users. Very confusing.

It wasn't what I was hoping for :D The idea was to create a test account that wasn't working, and then home it into Teams to see if it started working. Never expected it to just work. I can only think that the different accounts are enabling and disabling certain APIs or hooks in Teams that the phone uses to control calls. We're not signing out of the PC, just switching account on Teams. So we can reliably repro this, and fix it. We just need to determine what the difference is between these accounts.

That's interesting. One thing Yealink was adamant about was that for the device to properly work with Teams the account should be in Teams only mode. Sounds like you've found some sort of workaround to make a SfB account work with it in Teams.

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

2021-12-27T11:23:58+00:00

Hi,

I've found another issue on the MP50. If i start a call with dialing +.... on the dialpad of the MP50 and press the call button on the screen of the MP50, Microsoft Teams starts the call without the +. Only the digits behind + are called from Teams

So calls starting with + with the MP50 Dialpad and Microsoft Teams are not possible

By the way (+ will be dialed if you hold the 0 Button)

Do you have the same issue? Can you check this please.

Thank you

Markus
Was this answer helpful?

0 comments No comments
Anonymous

2021-12-03T15:41:02+00:00

Has anyone thought to push this towards Yealink, for a firmware upgrade from them for the MP50. We purchased one MP50 for testing when they were first available, well over a year ago and to our knowledge Yealink has never provided a firmware upgrade. We had issues from the jump with this phone on Teams, and even after we switched to a Teams-only mode across our network the phone still had issues...mainly the user's status indicator in Teams does not flow to the same status indicator on the MP50. Was told by Yealink back then that a firmware upgrade would be coming to resolve this...never seen it. Now, as of last week, with some late-breaking changes to Office 365, what we thought were only look-and-feel changes, now we find the MP50 "Teams" button (under the * keypad key) doesn't light any longer. Haven't tested other functions and features of the phone yet but won't be surprised if we find other things not working. As a side note, on day one of this phone on our network while still in the Skype-as-primary mode the phone worked perfectly, all functions, buttons, displays and features worked correctly on Skype, strange for a phone sold specifically as a Teams-compatible phone.
Was this answer helpful?

0 comments No comments
Anonymous

2021-11-24T17:27:21+00:00

OK I think we've got to the bottom of this.

The test account which we configured in SfB to replicate the issue, but in fact worked with the phone, had a coexistence mode of Teams Only!

Why this was not Org Wide, with the Skype for Business options I have no idea, because in fact the user is homed in SfB and is working on SfB. However, as soon as we changed the coexistence mode to Org Wide the phone stopped working correctly. We tried to flip it back to Teams Only, and it rightly said that it couldn't do this as the user is homed in SfB. So why was it set on this in the first place!!

So, it seems once we have fully migrated off of SfB onto Teams, with the coexistence mode set correctly, the MP50 should work with no issues for users.

Very confusing.
Was this answer helpful?

0 comments No comments
Anonymous

2021-11-24T16:33:12+00:00

It wasn't what I was hoping for :D

The idea was to create a test account that wasn't working, and then home it into Teams to see if it started working. Never expected it to just work.

I can only think that the different accounts are enabling and disabling certain APIs or hooks in Teams that the phone uses to control calls. We're not signing out of the PC, just switching account on Teams. So we can reliably repro this, and fix it. We just need to determine what the difference is between these accounts.
Was this answer helpful?

0 comments No comments
Anonymous

2021-11-24T16:27:57+00:00

That's interesting. One thing Yealink was adamant about was that for the device to properly work with Teams the account should be in Teams only mode. Sounds like you've found some sort of workaround to make a SfB account work with it in Teams.
Was this answer helpful?

0 comments No comments