Yealink MP56 Microsoft Teams Certified handsets do not sync Outlook contacts

%3CLINGO-SUB%20id%3D%22lingo-sub-2333817%22%20slang%3D%22en-US%22%3EYealink%20MP56%20Microsoft%20Teams%20Certified%20handsets%20do%20not%20sync%20Outlook%20contacts%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2333817%22%20slang%3D%22en-US%22%3E%3CP%3EWe've%20deployed%20a%20number%20of%20Yealink%20MP56%20headsets%20and%20cannot%20get%20Outlook%20contacts%20to%20sync.%26nbsp%3B%20We've%20attempted%20just%20about%20everything%20to%20force%20a%20sync%2C%20but%20it%20appears%20as%20though%20the%20handsets%20only%20display%20contacts%20in%20the%20Speed%20Dial%20list%20from%20the%20desktop%20client.%26nbsp%3B%20Has%20anyone%20come%20across%20a%20fix%20for%20this%2C%20or%20is%20it%20just%20a%20Teams%20bug%3F%20Microsoft%20Teams%20desktop%20client%20syncs%20great%2C%20however%2C%20those%20contacts%20don't%20sync%20on%20the%20handset.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-2333817%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3ECalling%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3Econtacts%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3ESync%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EYealink%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2620381%22%20slang%3D%22en-US%22%3ERe%3A%20Yealink%20MP56%20Microsoft%20Teams%20Certified%20handsets%20do%20not%20sync%20Outlook%20contacts%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2620381%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F622785%22%20target%3D%22_blank%22%3E%40ChapmanBryan%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EHi%20ChapmanBryan%2C%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EJust%20come%20across%20your%20post%20and%20i've%20recently%20started%20at%20a%20business%20(as%20IT%20Admin)%20that%20uses%20MP56%20phones%20with%20Teams%20and%20they%20have%20the%20contacts%20synced.%20I%20know%20you%20posted%20this%20back%20in%20May%20but%20no-one's%20come%20back%20on%20this%20so%20thought%20i'd%20create%20an%20account%20and%20try%20to%20help%20in%20case%20you're%20still%20waiting.%3C%2FP%3E%3CP%3EFirst%20question%3A%20How%20do%20you%20currently%20sync%20contacts%20from%20Outlook%20to%20Teams%20(desktop)%20in%20the%20first%20place%3F%26nbsp%3B%3C%2FP%3E%3CP%3ESecond%2C%20and%20probably%20done%20already%3A%20Have%20you%20made%20sure%20the%20firmware%20is%20up%20to%20date%20on%20the%20handsets%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2620671%22%20slang%3D%22en-US%22%3ERe%3A%20Yealink%20MP56%20Microsoft%20Teams%20Certified%20handsets%20do%20not%20sync%20Outlook%20contacts%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2620671%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F1122305%22%20target%3D%22_blank%22%3E%40Mickkey%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThe%20sync%20would%20be%20with%20the%20users%20Outlook%20contacts%20to%20Teams%20desktop%20client.%20That%20works%2C%20it%20just%20breaks%20as%20soon%20as%20you%20provision%20the%20MP56.%26nbsp%3B%20Only%20shows%20Speed%20Dial%20contacts%20from%20Teams.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EWe've%20also%20had%20numerous%20complains%20about%20the%20Yealink%20MP56%20phones%20because%20of%20poor%20call%20quality.%26nbsp%3B%20There%20has%20been%20severe%20latency%20issues%20that%20otherwise%20forced%20our%20hands%20to%20deploy%20the%20Polycom%20CCX%20models%20or%20the%20AudioCodes%20C450HD%20handsets.%26nbsp%3B%20The%20moment%20we%20plugged%20these%20phones%20into%20the%20same%20network%2C%20latency%20issues%20were%20gone.%26nbsp%3B%20Have%20you%20too%20also%20had%20issues%20with%20latency%3F%26nbsp%3B%20We've%20gone%20through%20Yealink%20Support%20and%20Engineering%20teams%20to%20try%20and%20mitigate%20these%20issues%2C%20across%20multiple%20firmware%20updates%2C%20but%20it%20seems%20as%20those%20these%20are%20a%20constant%20problem%20with%20these%20phones.%26nbsp%3B%20Almost%20as%20if%20they%20are%20underpowered%20for%20MS%20Teams%20to%20begin%20with.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EAny%20help%20would%20be%20greatly%20appreciated.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2626447%22%20slang%3D%22en-US%22%3ERe%3A%20Yealink%20MP56%20Microsoft%20Teams%20Certified%20handsets%20do%20not%20sync%20Outlook%20contacts%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2626447%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F622785%22%20target%3D%22_blank%22%3E%40ChapmanBryan%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3EOkay%2C%20and%20just%20to%20double%20check%20do%20all%20the%20users%20you've%20got%20on%20the%20Outlook%20contact%20list%20have%20their%20relevant%20phone%20numbers%20in%20the%20'business'%20field%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EWe've%20had%20some%20minor%20latency%20issues%20but%20nothing%20particularly%20bad%2C%20and%20we%20have%20a%20minor%20issue%20to%20do%20with%20picking%20up%20the%20handset%20often%20doesn't%20answer%20the%20call%2C%20you%20have%20to%20use%20the%20touch%20screen%20to%20'accept'%2C%20but%20other%20than%20that%20they've%20been%20alright%20for%20us.%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2630949%22%20slang%3D%22en-US%22%3ERe%3A%20Yealink%20MP56%20Microsoft%20Teams%20Certified%20handsets%20do%20not%20sync%20Outlook%20contacts%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2630949%22%20slang%3D%22en-US%22%3EGotcha.%3CBR%20%2F%3EWe%20are%20currently%20on%3A%3CBR%20%2F%3ETeams%20version%3A%201.4.00.19572%3CBR%20%2F%3EFirmware%20version%3A%20122.15.0.44%3CBR%20%2F%3EYeah%20our%20policy%20is%20to%20just%20update%20them%20as%20soon%20as%20we%20notice%20a%20new%20firmware%20update%20available.%20Interestingly%20I'm%20trying%20to%20access%20the%20IP%20interface%20of%20the%20handset%20i've%20got%20next%20to%20me%20and%20it's%20stating%20the%20site%20cant%20be%20reached%20despite%20the%20phone%20working%20fine...%3CBR%20%2F%3ETried%20looking%20at%20the%20device%20logs%20for%20it%20but%20cant%20make%20any%20sense%20from%20that%20unfortunately.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2632353%22%20slang%3D%22en-US%22%3ERe%3A%20Yealink%20MP56%20Microsoft%20Teams%20Certified%20handsets%20do%20not%20sync%20Outlook%20contacts%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2632353%22%20slang%3D%22en-US%22%3EYou're%20welcome%2C%20sorry%20I%20couldnt%20help%20in%20the%20end.%20Glad%20you've%20got%20a%20solution%20sorted%20now%20though.%3CBR%20%2F%3EHave%20a%20good%20one.%3CBR%20%2F%3EMike%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2638781%22%20slang%3D%22en-US%22%3ERe%3A%20Yealink%20MP56%20Microsoft%20Teams%20Certified%20handsets%20do%20not%20sync%20Outlook%20contacts%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2638781%22%20slang%3D%22en-US%22%3EHello%3CBR%20%2F%3E%3CBR%20%2F%3EWe%20have%20the%20same%20issue.%20Contacts%20are%20linked%20to%20Outlook%20in%20Teams.%20But%20they%20are%20not%20available%20on%20the%20MP56%20handset.%20Like%20the%20other%20user%20above%2C%20they%20appear%20if%20they%20are%20a%20speed%20dial%2C%20but%20I%20would%20like%20all%20contacts%20to%20be%20viewable%20on%20the%20handset.%20The%20issue%20also%20means%20that%20incoming%20calls%20from%20contacts%20are%20not%20recognised%20by%20name%20on%20the%20handset.%20Only%20the%20callers%20number%20is%20shown%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2690758%22%20slang%3D%22en-US%22%3ERe%3A%20Yealink%20MP56%20Microsoft%20Teams%20Certified%20handsets%20do%20not%20sync%20Outlook%20contacts%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2690758%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F1122305%22%20target%3D%22_blank%22%3E%40Mickkey%3C%2FA%3E%26nbsp%3Bthe%20issue%20you%20are%20experiencing%20where%20call%20are%20not%20answered%20automatically%20by%20picking%20up%20the%20handset%2C%20and%20where%20the%20user%20has%20to%20press%20the%20%22Accept%22%20button%20-%20have%20you%20found%20a%20solution%20for%20that%3F%26nbsp%3B%20Is%20it%20a%20setting%20somewhere%20on%20the%20handset%20itself%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EWe're%20experiencing%20this%20same%20issue%20after%20the%20latest%20MP56%20firmware%20update%2C%20too.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2975465%22%20slang%3D%22en-US%22%3ERe%3A%20Yealink%20MP56%20Microsoft%20Teams%20Certified%20handsets%20do%20not%20sync%20Outlook%20contacts%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2975465%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F622785%22%20target%3D%22_blank%22%3E%40ChapmanBryan%3C%2FA%3E%26nbsp%3B%20It's%20November%2C%20we're%20still%20seeing%20latency%20issues.%20Just%20deployed%20122.15.0.60%20yesterday%20and%20praying%20it%20improves%20our%20situation%20across%2060%20users.%20We've%20contacted%20Yealink%20and%20they%20blame%20MSFT%2C%20but%20other%20manufacturers%20don't%20seem%20to%20have%20the%20same%20issues.%20We're%20working%20on%20automation%20to%20reboot%20nightly%20to%20help%20mitigate%20the%20slowness%20and%20instability%20that%20seem%20to%20increase%20as%20runtimes%20increase.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThe%20change%20management%20for%20users%20going%20to%20new%20phones%2FTeams%20is%20tough%20enough%20when%20everything%20is%20working%20perfectly.%20It's%20much%20worse%20and%20harder%20when%20the%20phones%20don't%20do%20the%20basics%20well%3A%20pickup%20when%20users%20lift%20the%20handset%20fails%20sporadically%2C%20audio%20is%20delayed%20on%20calls%2C%20sidecars%20go%20blank%2C%20just%20to%20name%20a%20few%20of%20the%20pain%20points%20with%20the%20MP56%20device.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EWe're%20evaluating%20the%20warrantee%20of%20these%20devices%20which%20aren't%20performing%20as%20expected%20and%20may%20have%20to%20return%20them%20all%20and%20re-deploy%20another%20device%2C%20which%20will%20impact%20us%20as%20an%20IT%20team%20as%20well%20as%20every%20one%20of%20our%20users.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2976148%22%20slang%3D%22en-US%22%3ERe%3A%20Yealink%20MP56%20Microsoft%20Teams%20Certified%20handsets%20do%20not%20sync%20Outlook%20contacts%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2976148%22%20slang%3D%22en-US%22%3EHi%20%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F1122305%22%20target%3D%22_blank%22%3E%40Mickkey%3C%2FA%3E%2C%20we%20worked%20with%20Yealink%20to%20get%20the%20firmware%20122.15.1.27%20and%20had%20it%20running%20only%20on%20few%20phones%20since%20it%20a%20BETA%20release.%20We%20were%20assuming%20that%20the%20November%203rd%20release%20of%20122.15.0.60%20from%20122.15.0.44%20would%20fix%20the%20issues%20as%20stated%20in%20the%20release%20notes%3A%3CBR%20%2F%3E1.%20Optimized%20audio%20latency.%3CBR%20%2F%3E2.%20Optimized%20UI%20reflection%20latency.%3CBR%20%2F%3E3.%20Optimized%20screen%20saver%20timeout%3CBR%20%2F%3E4.%20Fixed%20an%20issue%20that%20device%20is%20offline%20from%20TAC.%3CBR%20%2F%3E%3CBR%20%2F%3ENow%20we%20have%2011%20phones%20offline%20in%20TAC%20showing%20as%20software%20update%20failed%2C%20rebooting%2C%20signing%20in%2Fout%20does%20not%20fix.%20The%20phones%20do%20show%20online%20in%20the%20Yealink%20Management%20Cloud%20Service%20with%20the%20new%20firmware%20(122.15.0.60)%20and%20you%20can%20redeploy%20it%20as%20it%20fails%20because%20it's%20the%20same%20version.%20I%20suppose%20I%20will%20update%20offline%20phones%20with%20the%20firmware%20to%20122.15.1.27%20and%20see%20what%20happens.%3CBR%20%2F%3E%3CBR%20%2F%3EThanks%20all%20for%20posting!%3CBR%20%2F%3E%3CBR%20%2F%3EScott%3CBR%20%2F%3E%3C%2FLINGO-BODY%3E
Occasional Contributor

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.

17 Replies

@ChapmanBryan 

 

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?

@Mickkey 

 

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.

@ChapmanBryan 

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. 

Yes, all users have their relevant phone numbers in the correct fields. What firmware and Teams version are you currently on, or is your policy to just update immediate as updates are available? We had to go into the Yealink admin portal for each phone to turn off acoustic sound shield. This improved the latency, however, still have considerable delays.
Gotcha.
We are currently on:
Teams version: 1.4.00.19572
Firmware version: 122.15.0.44
Yeah our policy is to just update them as soon as we notice a new firmware update available. Interestingly I'm trying to access the IP interface of the handset i've got next to me and it's stating the site cant be reached despite the phone working fine...
Tried looking at the device logs for it but cant make any sense from that unfortunately.

@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.

You're welcome, sorry I couldnt help in the end. Glad you've got a solution sorted now though.
Have a good one.
Mike
Hello

We have the same issue. Contacts are linked to Outlook in Teams. But they are not available on the MP56 handset. Like the other user above, they appear if they are a speed dial, but I would like all contacts to be viewable on the handset. The issue also means that incoming calls from contacts are not recognised by name on the handset. Only the callers number is shown

@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.

Hi Virgil,
We havent found a definite way unfortunately, it's so intermittent that we're having trouble replicating the issue for a diagnostic to be run, to send onto Yealink. Though doubt they'd do much anyway to be fair.
You can downgrade to previous firmware quite easily though, albeit time-consuming if you have alot of handsets in your business.
On the phones' IP UI, go to Settings > Upgrade > select Upgrade at the bottom and browse to your .rom file. You can download the firmware version you want from the Yealink website, they're like 500+MB for some reason though.

@ChapmanBryan 

 

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

 

 

Yes, this is correct. The AudioCodes C450HD resolves contacts and they did sync immediately once the phone has been deployed. The Yealink MP56 has a number of issues, this being on of them. I would stay away from this model, as we've tested the Yealink MP54, and no issues. Haven't gone to the extent of testing the Yealink MP58, but I can imagine for an executive category phone, you get what you pay for. Although the AudioCodes aren't the best aesthetically pleasing phones, they did resolve the majority of our problems we were running into with the Yealink MP56 handsets we deployed. Just to be clear, we did eliminate any potential risks with it being the network or any other external factors.

Also, be sure to purchase the new C450HD handsets. They just recently released a new model TEAMS-C450HDPS-DBW. This includes dual band WiFi, more internal memory and an external power supply.

@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
Hi @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

@Mickkey @Roger Navarro 

 

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.

scottphayre_0-1637685933498.png

 

Rebooted phone and same thing. After about 30 min showed up in TAC as not needing any updates.