Forum Discussion
Yealink MP56 Microsoft Teams Certified handsets do not sync Outlook contacts
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.
Mickkey the issue you are experiencing where call are not answered automatically by picking up the handset, and where the user has to press the "Accept" button - have you found a solution for that? Is it a setting somewhere on the handset itself?
We're experiencing this same issue after the latest MP56 firmware update, too.
