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

Out of 4 --> 3 Users can call now on the 21688 General build, 1 can't.

This can’t be accurate. I’m getting different feedback from MS. If the GC ring from august is the fix then we all have that release. Its 21668. That release does not resolve the issue. Still no general release for September. That should be the fix. Either way if “deployment” is happening now we’d be able to manually download it and know what gc version is the fix. Unless the public preview 25769 is the up and coming GC version that resolves the issue. I wish we could get a straight answer from Microsoft. Agreed, that were my first questions in the begin of july with a meeting with Yealink and later MS. It began with some devices at our office, over time more. But all running the same build. Downgraded yesterday to general channel, running 21668, and calling is working now... Would be more logical if it was a backend change / patched server. Yealink and Microsoft have refused to answer those simple questions. If it was a client app issue, why don't provide a temporary beta download. Gonna test a few other devices with users today

This can’t be accurate. I’m getting different feedback from MS. If the GC ring from august is the fix then we all have that release. Its 21668. That release does not resolve the issue. Still no general release for September. That should be the fix. Either way if “deployment” is happening now we’d be able to manually download it and know what gc version is the fix. Unless the public preview 25769 is the up and coming GC version that resolves the issue. I wish we could get a straight answer from Microsoft.

Thank you for this information. I will check the general ring next week.

FYI, answer from MS Yesterday Thank you for your response. As per the lates update received from Product group team.The fix was released in Aug 2022 and this fix is under deployment on general ring and only 30% is done as of now.The expected completion time is end of the week.Please check the behavior next week on Monday 03/10/2022 and as per PG team the deployment should be completed by end of the week. If it is fixed in the Teams Client Update, which build / version? The update is released from Microsoft Teams we are still waiting for the update version details from PG team.

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-28T08:51:28+00:00

Out of 4 --> 3 Users can call now on the 21688 General build, 1 can't.
Was this answer helpful?

0 comments No comments
Anonymous

2022-09-28T07:29:12+00:00

This can’t be accurate. I’m getting different feedback from MS. If the GC ring from august is the fix then we all have that release. Its 21668. That release does not resolve the issue. Still no general release for September. That should be the fix. Either way if “deployment” is happening now we’d be able to manually download it and know what gc version is the fix.

Unless the public preview 25769 is the up and coming GC version that resolves the issue. I wish we could get a straight answer from Microsoft.

Agreed, that were my first questions in the begin of july with a meeting with Yealink and later MS. It began with some devices at our office, over time more. But all running the same build. Downgraded yesterday to general channel, running 21668, and calling is working now... Would be more logical if it was a backend change / patched server. Yealink and Microsoft have refused to answer those simple questions. If it was a client app issue, why don't provide a temporary beta download. Gonna test a few other devices with users today
Was this answer helpful?

0 comments No comments
Anonymous

2022-09-27T12:18:28+00:00

This can’t be accurate. I’m getting different feedback from MS. If the GC ring from august is the fix then we all have that release. Its 21668. That release does not resolve the issue. Still no general release for September. That should be the fix. Either way if “deployment” is happening now we’d be able to manually download it and know what gc version is the fix.

Unless the public preview 25769 is the up and coming GC version that resolves the issue. I wish we could get a straight answer from Microsoft.
Was this answer helpful?

0 comments No comments
Anonymous

2022-09-27T11:41:36+00:00

Thank you for this information. I will check the general ring next week.
Was this answer helpful?

0 comments No comments
Anonymous

2022-09-27T07:12:45+00:00

FYI, answer from MS Yesterday

Thank you for your response. As per the lates update received from Product group team.The fix was released in Aug 2022 and this fix is under deployment on general ring and only 30% is done as of now.The expected completion time is end of the week.Please check the behavior next week on Monday 03/10/2022 and as per PG team the deployment should be completed by end of the week.If it is fixed in the Teams Client Update, which build / version? The update is released from Microsoft Teams we are still waiting for the update version details from PG team.
Was this answer helpful?

0 comments No comments