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-11-03T17:25:46+00:00

    I had an MP50 that wouldn't initiate a call made via the MP50's dialpad, either on a Mac or PC.

    Recent updates to Teams appear to have fixed that for Windows as it works fine now. On a Mac, whilst it does now attempt to connect a call made via the dial pad, it rings a couple of times then the call cuts off - the call history shows it tried to dial a completely different number than the one I dialed, most often it's just a random string of numbers.

    Incoming calls are fine.

    Whilst the first number on the call history below looks like a real number, it bears no relation to the number I entered in the dialpad and the call failed.

    This thing is cursed.

    Was this answer helpful?

    0 comments No comments
  2. Anonymous
    2022-10-24T09:39:14+00:00

    Hi Jase, we're not using the MP50 devices but, as previously noted in the thread, myself and a couple of colleagues are using the similar WH66 wireless headset and are also seeing the random dial string issue on our Macs

    Was this answer helpful?

    0 comments No comments
  3. Anonymous
    2022-10-19T23:45:16+00:00

    Hi all, we're running 26358 on a Mac and can now answer calls but still can't dial out using the dial pad. I thought this was fixed from the looks of this thread, but depending on which build you have installed?

    Anyone else on Mac with reports of successfully using the dial pad to dial out?

    When we dial the number on the phone - it says it's out of service but its show random number sequences. You can see this here in the screenshot below:

    Inbound calls when the device is primary can be answered now.

    ta,

    Jase.

    Was this answer helpful?

    0 comments No comments
  4. Anonymous
    2022-10-17T12:07:35+00:00

    Yet again miraculously this now seems to be working? Just did some testing and we could respond to phone tree options via dial pad.

    I just tried on mine and it still doesn't work. I'm still on 1.5.00.21668 as of 8/30/2022.

    Was this answer helpful?

    0 comments No comments
  5. Anonymous
    2022-10-17T02:52:51+00:00

    Yet again miraculously this now seems to be working? Just did some testing and we could respond to phone tree options via dial pad.

    Was this answer helpful?

    0 comments No comments