Forum Discussion
Teams status not changing from Active
Hi there, I've recently started using a Yealink MP56 Business Smart Phone and signed in there with my Microsoft account using MS Teams to make calls. I am signed into Teams on the desk phone and ...
Hi Adam,
Did you ever find anything out on this problem? I can confirm what you described is a repeatable issue. We recently deployed Yealink MP54, 56 and 58 Teams desk phones to 80% of users at one location. Every user who received a MP54 or MP56 has had their Teams presence stuck on “Available” continuously since the roll out (been almost 2 months now). Issue has persisted through at least one Yealink firmware update.
Presence for users assigned an MP58 (or no desk phone) behaves normally. We had one user assigned a MP54 who suffered from incorrect presence issue for a week before it went back to normal. Upon review we found his phone’s login token had expired and signed him out. As soon as he re-did (http://microsoft.com/devicelogin) sign in, Teams presence issue came back.
We’ve tried clicking “reset status” on both user’s teams desktop client AND on the Yealink phones themselves.
One other piece of evidence it’s the phones: we had a power outage long enough for UPS on PoE user switches to die but not switches powering out AP’s (that is, desk phones went dead but user’s idle laptops could still connect to wifi). During that outage all malfunctioning user’s presence changed from “Available” (incorrect) to “away” (correct). Once power and phones came back on in middle of night all MP54/56 user’s presence changed back to “Available”.
Hopefully you or someone else out there has figured out the trick to this annoying bug!
Thanks,
Ed
Did you ever find anything out on this problem? I can confirm what you described is a repeatable issue. We recently deployed Yealink MP54, 56 and 58 Teams desk phones to 80% of users at one location. Every user who received a MP54 or MP56 has had their Teams presence stuck on “Available” continuously since the roll out (been almost 2 months now). Issue has persisted through at least one Yealink firmware update.
Presence for users assigned an MP58 (or no desk phone) behaves normally. We had one user assigned a MP54 who suffered from incorrect presence issue for a week before it went back to normal. Upon review we found his phone’s login token had expired and signed him out. As soon as he re-did (http://microsoft.com/devicelogin) sign in, Teams presence issue came back.
We’ve tried clicking “reset status” on both user’s teams desktop client AND on the Yealink phones themselves.
One other piece of evidence it’s the phones: we had a power outage long enough for UPS on PoE user switches to die but not switches powering out AP’s (that is, desk phones went dead but user’s idle laptops could still connect to wifi). During that outage all malfunctioning user’s presence changed from “Available” (incorrect) to “away” (correct). Once power and phones came back on in middle of night all MP54/56 user’s presence changed back to “Available”.
Hopefully you or someone else out there has figured out the trick to this annoying bug!
Thanks,
Ed
EdCurtRLT
Have you heard any updates on this issue? We're piloting a Teams Voice rollout and using MP54 and MP56 devices and have noticed the same. I'm always available, even with the phone locked, my laptop off, my mobile not signed into Teams app - always green due to the phone.
We've reached out to Yealink but have not heard back yet.
- Unfortunately, no. Issue persists even after upgrading to Yealink FW version 122.15.0.80. Is it worth even trying Microsoft support, or are they just going to dump this on Yealink?
- I can confirm as well, upgrading the most recent firmware didn't resolve the issue. Microsoft tried to say my firmware wasn't up to date and sent me an old link of firmware updates *face palm*.
This is what they sent me to "troubleshoot" and ended with putting in a support ticket to Yealink. Which FYI, I did that before going to MS.
With the power shall Commends
1. Check phone status. If phone is booting or lost network, YDMP will show offline status.
2. Update phone firmware to latest one then have a test:
http://support.yealink.com/documentFront/forwardToDocumentFrontDisplayPage
3. Check dm configurations.
a. Export phone configurations
1) Login phone web interface
2) Navigate to Settings > Configuration > Export All Settings
b. Check dm settings, make sure that dm.cfg update successfully and port/server are correct.
4. Check the ports requirements.
a. Run command to check firewall status.
systemctl status firewalld
b. If firewall is inactive, run command to enable it
systemctl start firewalld
c. If firewall is active, run commands below to open the ports
firewall-cmd --permanent --zone=public --add-port=80/tcp
firewall-cmd --permanent --zone=public --add-port=443/tcp
firewall-cmd --permanent --zone=public --add-port=9989/tcp
firewall-cmd --permanent --zone=public --add-port=9090/tcp
firewall-cmd --permanent --zone=public --add-port=8446/tcp
d. Reload firewall
firewall-cmd –reload
e. Check opening ports
firewall-cmd --permanent --list-port --zone=public
5. If all above can’t solve question, get diagnose file from YDMP and phone side.
a. Get diagnose file from phone side, refer to:
http://support.yealink.com/faq/faqInfo?id=707
b. Get logs from YDMP, mark the time when issue happen
1) Login YDMP background
2) Entering the directory of dm logs
cd /var/log/yealink/microdm
3) Then download the latest syslog
sz microdm.log
c. Get these diagnose file then create a ticket at https://ticket.yealink.com/
