May 06 2021 08:51 PM
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.
Aug 06 2021 08:20 AM - edited Aug 06 2021 08:24 AM
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?
Aug 06 2021 09:24 AM
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.
Aug 09 2021 12:44 AM
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.
Aug 09 2021 12:05 PM
Aug 10 2021 12:56 AM
Aug 10 2021 07:17 AM
@Mickkey Interesting, thanks for trying! much appreciated. We ended up just replacing the Yealink MP56 handsets with the AudioCode C450HD and most, if not all our problems were resolved at our client site. It has been a three month RMA process going back and forth with Yealink support and engineering team.
Aug 10 2021 07:35 AM
Aug 11 2021 10:34 PM
Aug 26 2021 08:31 PM
@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.
Aug 27 2021 12:34 AM
Aug 28 2021 04:39 AM
Hi, I have also tested a few Teams Phones and do not see any personal contacts on the phone. However I found this in the manual of the Audiocodec C450HD
If a user creates a contact within Microsoft Outlook, their information appears under the
People app on the phone screen. Contacts in Microsoft Outlook are available in read-
only mode. While only phone numbers currently appear, users can search on the phone
for contacts and easily call the people they may email or meet with, using Outlook.
Here's the manual: https://www.audiocodes.com/media/15946/c448hd-c450hd-ip-phone-for-microsoft-teams-users-and-administ...
Can someone confirm?
Thanks S
Sep 13 2021 09:47 PM
Nov 17 2021 06:48 AM
@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.
Nov 17 2021 07:48 AM - edited Nov 17 2021 07:49 AM
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
Nov 17 2021 08:46 AM
Nov 17 2021 08:53 AM
Nov 23 2021 08:47 AM
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.
Dec 02 2021 02:28 AM
Dec 02 2021 05:46 AM