Additional features, settings, or issues not covered by specific Microsoft Teams categories
I have tried this to no avail. Same results on the dev preview at least from my end.
This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
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.
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.
Here is a rundown of some extensive process of elimination troubleshooting I did, with users A and B
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
Additional features, settings, or issues not covered by specific Microsoft Teams categories
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.
This answer has been deleted due to a violation of our Code of Conduct. The answer was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.
Comments have been turned off. Learn more
This answer has been deleted due to a violation of our Code of Conduct. The answer was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.
Comments have been turned off. Learn more
I have tried this to no avail. Same results on the dev preview at least from my end.
MSFT suggests switching to the public preview version. This is a known Teams desktop App problem.
bn
Does the latest Public Preview version fix some of these issues? Has anyone tried it?
MSFT suggests switching to the public preview version. This is a known Teams desktop App problem.
bn