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

Anonymous
2021-09-10T18:52:05+00:00

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

Microsoft Teams | Microsoft Teams for business | Other

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 No comments

132 answers

Sort by: Newest
  1. Anonymous
    2022-09-26T17:00:38+00:00

    Yeah I’m aware of going that route. Not sure that solution will work for us having users turn it on. But it’s another option

    Was this answer helpful?

    0 comments No comments
  2. Anonymous
    2022-09-26T16:52:31+00:00

    Agreed. My executives are impatiently waiting for this fix I was told was coming. And it hasn’t. Worst case scenario I have to turn on office current channel preview company wide and risk breaking some of my office applications.

    You can just enable the preview for Teams (In the teams portal), downside is that a user has to update itself via the teams menu. But no Office breakage ;-)

    Was this answer helpful?

    0 comments No comments
  3. Anonymous
    2022-09-26T15:40:51+00:00

    Agreed. My executives are impatiently waiting for this fix I was told was coming. And it hasn’t. Worst case scenario I have to turn on office current channel preview company wide and risk breaking some of my office applications.

    Was this answer helpful?

    0 comments No comments
  4. Anonymous
    2022-09-26T15:31:39+00:00

    It does rather make a mockery of MS's "Teams Certified" program and gives me no confidence in devices bearing that mark, to be honest.

    Was this answer helpful?

    0 comments No comments
  5. Anonymous
    2022-09-26T14:32:09+00:00

    For me there was no new GR, reverted back this morning, just to test this. I have a support case open Since July 27th, with no answer to any of my questions. Begin July I had a Teams meeting with Yealink, stating that the issue was in the MS Teams App, which should be validated on august 1, then would be pubnlished fast after that, but nothing published yet. Still waiting for the answer from Yealink also, which build will be the correct one, etc. Probably going to return the 150 MP50's we have, as both companies do not care at all. This situation can repeat itself, even if MS or Yealink patches it for now.

    Was this answer helpful?

    0 comments No comments