Forum Discussion
Yealink MP56 Microsoft Teams Certified handsets do not sync Outlook contacts
We've deployed a number of Yealink MP56 headsets and cannot get Outlook contacts to sync. We've attempted just about everything to force a sync, but it appears as though the handsets only display contacts in the Speed Dial list from the desktop client. Has anyone come across a fix for this, or is it just a Teams bug? Microsoft Teams desktop client syncs great, however, those contacts don't sync on the handset.
Hi ChapmanBryan,
Just came across your post and i've recently started at a business (as IT Admin) that uses MP56 phones with Teams and they have the contacts synced. I know you posted this back in May but no-one's come back on this so thought i'd create an account and try to help in case you're still waiting.
First question: How do you currently sync contacts from Outlook to Teams (desktop) in the first place?
Second, and probably done already: Have you made sure the firmware is up to date on the handsets?
The sync would be with the users Outlook contacts to Teams desktop client. That works, it just breaks as soon as you provision the MP56. Only shows Speed Dial contacts from Teams.
We've also had numerous complains about the Yealink MP56 phones because of poor call quality. There has been severe latency issues that otherwise forced our hands to deploy the Polycom CCX models or the AudioCodes C450HD handsets. The moment we plugged these phones into the same network, latency issues were gone. Have you too also had issues with latency? We've gone through Yealink Support and Engineering teams to try and mitigate these issues, across multiple firmware updates, but it seems as those these are a constant problem with these phones. Almost as if they are underpowered for MS Teams to begin with.
Any help would be greatly appreciated.
Okay, and just to double check do all the users you've got on the Outlook contact list have their relevant phone numbers in the 'business' field?
We've had some minor latency issues but nothing particularly bad, and we have a minor issue to do with picking up the handset often doesn't answer the call, you have to use the touch screen to 'accept', but other than that they've been alright for us.
ChapmanBryan It's November, we're still seeing latency issues. Just deployed 122.15.0.60 yesterday and praying it improves our situation across 60 users. We've contacted Yealink and they blame MSFT, but other manufacturers don't seem to have the same issues. We're working on automation to reboot nightly to help mitigate the slowness and instability that seem to increase as runtimes increase.
The change management for users going to new phones/Teams is tough enough when everything is working perfectly. It's much worse and harder when the phones don't do the basics well: pickup when users lift the handset fails sporadically, audio is delayed on calls, sidecars go blank, just to name a few of the pain points with the MP56 device.
We're evaluating the warrantee of these devices which aren't performing as expected and may have to return them all and re-deploy another device, which will impact us as an IT team as well as every one of our users.
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
- Hi Mickkey, we worked with Yealink to get the firmware 122.15.1.27 and had it running only on few phones since it a BETA release. We were assuming that the November 3rd release of 122.15.0.60 from 122.15.0.44 would fix the issues as stated in the release notes:
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
