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: Oldest
  1. Anonymous
    2022-07-26T12:02:27+00:00

    Hi Larry, I just setup a brand new WH66 on a Mac with macOS 12.4 and Teams 1.5.00.17261, and am having exactly the same problem.

    I've got Yealink USB Connect running (125.432.0.15) and it has updated the WH66 and attached headset to the latest firmware.

    When I connected the device to my Mac Teams spots that a certified device has been connected, and the WH66 show my name on the screen, but:

    • pressing the Teams button on the WH66 has no effect
    • placing a call from the dialpad on the WH66 does nothing
    • there are no contacts/favourites from Teams visible on the device

    Going into "Advanced Settings" on the device I noted that the "platform" was set to "UC" mode, rather than "Teams", and while changing this rearranged some UI elements it didn't fix any of the problems.

    I'v never had Skype installed on this machine, but do have Cisco Jabber, which may be messing with the dialler/telephony API stuff in a similar way.

    *edit*

    It may also be relevant that the "Yealink USB Connect" software reports "No supported softphone detected" in the "Softphone Settings" section of the Setting UI

    Was this answer helpful?

    0 comments No comments
  2. Anonymous
    2022-07-26T13:21:36+00:00

    Hello, I'm not sure about your model of teams phone, but if it is a yealink dummy phone, there is a known issue with Macs. I had to get a standalone Yeahlink phone to sign directly into, not plugged into my computer. We had to do that with all of my companys users that had Macs. Hope this helps.

    Was this answer helpful?

    0 comments No comments
  3. Anonymous
    2022-07-26T14:12:41+00:00

    Hi Everyone,

    Some feedback regarding the Yealink MP50 USB phone if you are unable to dial from the physical phone's dial pad or touch screen dialing pad. Yealink and Microsoft is now in communication with each other regarding the firmware and they are aware of this issue. We hope that this will be rectified soon. Only work around for now is to use the Teams application on the PC to make calls.

    Was this answer helpful?

    0 comments No comments
  4. Anonymous
    2022-07-26T14:46:37+00:00

    Thanks Christian, it's a USB/DECT headset with a display on it that mirrors the Teams UI on the Mac or PC it's connected to. I suspect the technology is very similar, if not identical to, the MP50 "dummy" USB phone. It just has a DECT headset attached instead of a phone handset.

    Was this answer helpful?

    0 comments No comments
  5. Anonymous
    2022-07-28T13:48:03+00:00

    Rudi, thanks so much for that insight. We just received about 100 phones all with this issue and we're holding off on deployment for this exact reason. Glad to hear there is a fix rolling out at least.

    Was this answer helpful?

    0 comments No comments