Forum Discussion
Yealink MP56 Microsoft Teams Certified handsets do not sync Outlook contacts
Hi Roger Navarro If you find that 122.15.0.60 doesnt improve it at all, we've recently started running 122.15.1.27 which is supposedly the most up to date firmware. Whilst we still have the same occasional issues with pickup on handset lift/no dial-tone on handset lift, it does seem to be slightly better overall.
If you need the ROM file (we were only given it after our separate support company chased Yealink for ages) i've uploaded it to "WeTransfer" since the file size is too large to attach here or send via email (even zipped the file is 700mb, what do they put in there!?)
Link: https://we.tl/t-Ur1dpISOoS
Cheers,
Mike
1. Optimized audio latency.
2. Optimized UI reflection latency.
3. Optimized screen saver timeout
4. Fixed an issue that device is offline from TAC.
Now we have 11 phones offline in TAC showing as software update failed, rebooting, signing in/out does not fix. The phones do show online in the Yealink Management Cloud Service with the new firmware (122.15.0.60) and you can redeploy it as it fails because it's the same version. I suppose I will update offline phones with the firmware to 122.15.1.27 and see what happens.
Thanks all for posting!
Scott
- MickkeyNov 17, 2021Copper ContributorHi scottphayre , you're right, in my TAC it's showing a whole host of "non-urgent health status'" due to the firmware wanting to update, despite being as up to date as it can be, which I hadn't thought to include in my above post. As it doesnt effect the users (and I log onto the IP UI of each phone individually if I need to (small team)) i'm happy to have the TAC look awful whilst the users benefit from slightly better performance.
If you remember to, come back here and update us with how it goes!
Cheers,
Mike- scottphayreNov 23, 2021Copper Contributor
Update. Upgraded a phone from 122.15.0.60 to 122.15.1.27 via phone web console. Same results. Phone is online/working, but offline in TAC. Waited a while to make sure, still not showing up.
Downgraded to 122.15.0.44 and it popped back into Teams. Upgraded to 122.15.1.27 phone stayed online/working in TAC and Yealink Management Cloud Service.
My next test was to downgrade the remaining phones to 122.15.0.44 (only way to get them back in TAC) and via TAC going to try update to 122.15.0.60
Surprisingly the 10 phones that were offline in TAC, that were originally on 122.15.0.44 and were upgraded to 122.15.0.60 via TAC and failed, after downgrading again and updating to 122.15.0.60 they came back online. Only one issue that I have seen. One device is showing it needs an update, but it’s the same darn update.
Rebooted phone and same thing. After about 30 min showed up in TAC as not needing any updates.
- FriskySpider29347654Dec 02, 2021Copper ContributorHalf my gosh darn luck, I'm new to the Physical handset + Teams game as been dealing mostly with teams as a softphone.
And I should deploy MP56 for my first physical rollout. Now I am having both of these problems, outlook contacts not syncing and devices showing as offline in the Teams Admin Centre.,
I tried the downgrade to .44 and then back to .60...... no go! (The link to the beta firmware above is expired).
Pretty rotten to be facing this. I think I will be avoiding anything Yealink and Teams going forward, what a hassle and it looks like it's been going on for a while now! Users haven't used the devices long enough for mew to know if there are latency issues etc yet, but I'm not holding my breath.
Should be caled Nolink phones, Nolink to TAC....