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 Lee, if you take the time to read through this thread you’ll see everyone is having the same problem and we’re waiting on MS to push out a Teams update to fix it.

Received from Microsoft today. I would like to update you that we followed up with engineering to see if there is a way by which we can prioritize the Roll out of the fix to general Build. As per Engineering “As Teams is an application which is used by hundreds of millions of users. Engineering is required to go through many careful testing/checks before rolling out a code change to ensure that it should not impact any other functionality. In our scenario, I understand that many Users are impacted by this Issue however we would like to point out a workaround, where users can use the Teams Application or the web version to make outbound calls using the Dial Pad. I am afraid to inform you that we may not be able to do much on this case until the fix has been rolled out. The Fix would be in Public Preview by mid of September & you can surely enable Public preview until it comes to General Ring.

This is horrible. We just deployed this phone to the whole company just to discover that we can not call out?

Anyone have a date the Sept Teams release is suppose to drop? That way we can anticipate when to be let down when it's postponed again or still doesn't work properly?

my preview version was last updated 8/25 so probably gonna be around 9/25 for the next update. we will both be mildly disappointed and completely expected together. the "but fixing issues in teams is hard" excuse is my favorite excuse. on the other hand, maybe they don't want to hear about broken MP50s every 10 minutes at ignite and will actually get it done since it will impact them personally if they let it stew anymore. hope springs eternal.

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-08-25T17:21:27+00:00

Hi Lee, if you take the time to read through this thread you’ll see everyone is having the same problem and we’re waiting on MS to push out a Teams update to fix it.
Was this answer helpful?

0 comments No comments
Anonymous

2022-08-26T14:12:40+00:00

Received from Microsoft today.

I would like to update you that we followed up with engineering to see if there is a way by which we can prioritize the Roll out of the fix to general Build.

As per Engineering “As Teams is an application which is used by hundreds of millions of users. Engineering is required to go through many careful testing/checks before rolling out a code change to ensure that it should not impact any other functionality.

In our scenario, I understand that many Users are impacted by this Issue however we would like to point out a workaround, where users can use the Teams Application or the web version to make outbound calls using the Dial Pad.

I am afraid to inform you that we may not be able to do much on this case until the fix has been rolled out. The Fix would be in Public Preview by mid of September & you can surely enable Public preview until it comes to General Ring.
Was this answer helpful?

0 comments No comments
Anonymous

2022-09-09T13:35:48+00:00

This is horrible. We just deployed this phone to the whole company just to discover that we can not call out?
Was this answer helpful?

0 comments No comments
Anonymous

2022-09-16T20:13:39+00:00

Anyone have a date the Sept Teams release is suppose to drop? That way we can anticipate when to be let down when it's postponed again or still doesn't work properly?
Was this answer helpful?

0 comments No comments
Anonymous

2022-09-16T20:50:56+00:00

my preview version was last updated 8/25 so probably gonna be around 9/25 for the next update. we will both be mildly disappointed and completely expected together. the "but fixing issues in teams is hard" excuse is my favorite excuse.

on the other hand, maybe they don't want to hear about broken MP50s every 10 minutes at ignite and will actually get it done since it will impact them personally if they let it stew anymore. hope springs eternal.
Was this answer helpful?

0 comments No comments