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

From Microsoft last week. I would like to inform you that this Issue " Unable to make Outbound calls from Yealink MP 50 Devices" is already reported to our engineering & identified as a Bug. Our Engineering has already developed a fix for this which is expected to be released in General Ring by 3rd of week of August. As per the comments from Engineering, this should get resolved by 22nd of August however this is a tentative date & could be changed if there would be some roadblocks in the fix code.

I have same problem with 50 phones awaiting deployment because can't dial out from Yealink MP50 phone. I opened a request with Yealink about 2 months ago, and I'm really hoping that this firmware update from the poster with 5,000 phones happens and resolves everything. At the time I was told that they could replicate the problem (Yealink) and that they believed it was a Teams update and that their R&D team was working on a solution. Was also asked to open a case with Microsoft. I opened a case with Microsoft with no mention at all from them that they are aware of this issue and request for information/logs, which my perception is that it's not getting anywhere and not passed their initial tier 1 techs which keep changing. Dealt with microsoft on another issue with a different phone a couple years back and at that time it was days and weeks and months of data collection and always end up in the same starting place and no indication that these logs were of any use. I feel frustrated that this might be the case now. My hopes are in Yealink and this update but also frustrated that communication hasn't been clear, I am hearing about this firmware update here, yet I think another poster earlier posted about an update coming for them and nothing has happened, so I really hope something is ocurring and there is real collaboration between these companies. As sitting on thousands of dollars for equipment that doesn't work is not a good place to be in.

I received the following from Yealink on Monday, so hopefully a fix is available soon: Dear Customer, For this issue, We also have other customers encounter, currently after our local testing, R&D analysis. This has been confirmed to be a Microsoft issue. The good news is that Microsoft has already validated the solution in their internal environment and they expect to complete the entire internal test on August 1, When Microsoft internal validation is complete, a version will be provided to us and we will perform local validation in our side, which is fast and only takes 1-2 days. Once the local validation in our side is complete, Microsoft will release the version to the public environment for everyone to update. So basically it depends on the speed of Microsoft's solution, we cannot guarantee that they will submit their versions to us on time, but we internally have urged Microsoft to speed up the progress. When I receive feedback from Microsoft, I will let you know immediately!

Thanks! I really hope this is so and we all can get a resolution.

Well today is supposedly the day? Once someone gets the new version and validates functionality please post the version.

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-03T22:03:36+00:00

From Microsoft last week.

I would like to inform you that this Issue " Unable to make Outbound calls from Yealink MP 50 Devices" is already reported to our engineering & identified as a Bug. Our Engineering has already developed a fix for this which is expected to be released in General Ring by 3rd of week of August.

As per the comments from Engineering, this should get resolved by 22nd of August however this is a tentative date & could be changed if there would be some roadblocks in the fix code.
Was this answer helpful?

0 comments No comments
Anonymous

2022-08-03T22:03:45+00:00

I have same problem with 50 phones awaiting deployment because can't dial out from Yealink MP50 phone.

I opened a request with Yealink about 2 months ago, and I'm really hoping that this firmware update from the poster with 5,000 phones happens and resolves everything.

At the time I was told that they could replicate the problem (Yealink) and that they believed it was a Teams update and that their R&D team was working on a solution. Was also asked to open a case with Microsoft.

I opened a case with Microsoft with no mention at all from them that they are aware of this issue and request for information/logs, which my perception is that it's not getting anywhere and not passed their initial tier 1 techs which keep changing.

Dealt with microsoft on another issue with a different phone a couple years back and at that time it was days and weeks and months of data collection and always end up in the same starting place and no indication that these logs were of any use. I feel frustrated that this might be the case now.

My hopes are in Yealink and this update but also frustrated that communication hasn't been clear, I am hearing about this firmware update here, yet I think another poster earlier posted about an update coming for them and nothing has happened, so I really hope something is ocurring and there is real collaboration between these companies.

As sitting on thousands of dollars for equipment that doesn't work is not a good place to be in.
Was this answer helpful?

0 comments No comments
Anonymous

2022-08-03T22:08:14+00:00

I received the following from Yealink on Monday, so hopefully a fix is available soon:

Dear Customer,

For this issue, We also have other customers encounter, currently after our local testing, R&D analysis. This has been confirmed to be a Microsoft issue. The good news is that Microsoft has already validated the solution in their internal environment and they expect to complete the entire internal test on August 1, When Microsoft internal validation is complete, a version will be provided to us and we will perform local validation in our side, which is fast and only takes 1-2 days. Once the local validation in our side is complete, Microsoft will release the version to the public environment for everyone to update.

So basically it depends on the speed of Microsoft's solution, we cannot guarantee that they will submit their versions to us on time, but we internally have urged Microsoft to speed up the progress. When I receive feedback from Microsoft, I will let you know immediately!
Was this answer helpful?

0 comments No comments
Anonymous

2022-08-03T22:19:45+00:00

Thanks! I really hope this is so and we all can get a resolution.
Was this answer helpful?

0 comments No comments
Anonymous

2022-08-22T15:10:36+00:00

Well today is supposedly the day? Once someone gets the new version and validates functionality please post the version.
Was this answer helpful?

0 comments No comments