Solved Yealink W80B firmware 103.83.0.80

[AWS2P]

I Have a Yealink DECT Base W80B alone managing 10 handset W53H.
Tonight I got the bad idea to update firmware version DECT base from W80B-103.83.0.65 to W80B-103.83.0.80

After reboot now firmware changed Base role to Base manager and none of handsets are seen registred on 3cx console.
It's impossible to downgrade to previous firmware (i have the file) I Get each time same error

Update failed
software limit
Reboot
Wanted to try to switch to DM mode with W80DM-103.83.0.80 file firmware but this one too is failing.
Message displayed said firmware is the same
reboot

What do i need now to retrieve my phones working?

 

[Quentin D]

http://support.yealink.com/forward2...AKbd5WHVuhSplusSymbol2zdVIpEbCWNKJTP2MjhJkkfF

Page 4 ;-)

 

[AWS2P]

According to new firmware ....83.80 this option 3 DM-Base no more exist
My customer will be surely happy to know he needs now 2 Bases to do same work as before. Really good job.

 

[Quentin D]

What an excellent idea...

 

[AWS2P]

My idea to push that firmware has been brilliant
but there's no warning from yealink or from 3cx to take care about so important change.

 

[Quentin D]

Don't they have changed the profile name ?

 

[complex1]

Have you tried a factory reset already?

 

[AWS2P]

No this update has been done remotely saturday night, so customer site is closed, problem will be tomorrow morning ,with no phones working.
Well inspired I have been

 

[AWS2P]

Don't they have changed the profile name ?

What do you mean about profile name?

If you are user of W80B alone ( no multicell, as in my case) DON'T Upgrade more than 103.83.0.65

 

[AWS2P]

Yealink ask my provider to send me a new base for free to add as role Base. I've been forgotten from their customer list to be aware of that important change way of working
I needed to use interim firmware .79 to switch From Base to Dect Manager and then reflash to latest .80 firmware.

 

[JohnS_3CX]

Hi @aws2p

This was purely a decision of the manufacturer, and since we support the device we will have to follow their releases accordingly for new templates and firmware as they were sent to us in their current form.

W80 series owners that have an issue with this will have to contact the manufacturer or device reseller directly.

 

[complex1]

As state in the release notes "Yealink W80 DECT IP Multi-Cell System Release Notes of Version 103.83.0.70"
(I suppose its also valid for the newer firmware 103.83.0.80)

- New Features.
Separated the firmware of base station W80B and DECT Manager W80DM.

- New Features Descriptions
If you want to upgrade your multi-cell system, you should upgrade the DECT Manager to its interim version W80DM Intermin-103.83.0.69, and then upgrade it to W80DM-103.83.0.70. After the upgrade is completed, all the devices in your multi-cell system will be upgraded to the newest version, and the system can work properly.

 

[AWS2P]

Latest firmware is .80 and interim .79 , there's no warning to prevent problems like mine. Nothing on Yealink website ; nothing to alert in firmware itself too.
So you're confident to push your file like many others before and this turns into customer disaster with no phones working . Really good , I really appreciate to manage this with a yealink ticket on sunday and following on monday with my whosaler to have today a new dect w80B to add.
Calling customer on Sunday to inform him with a good news, I updated your DECT base and now you have no phone working and I can't downgrade to previous.

I've done a check on firmware of the new one, it was on 103.83.0.80 and role Base, I set a static IP and added IP of DM already running on site. I thought, now easy , I just need to plug POE cable and i leave.

Not at all, even if everything seemed good, all the phones stated as unregistred on DECT Base.
As there's no 3CX guide to follow for an install with 2 bases i didn't knew what to check first and in which order settings need to be done
Finally i scratched DM settings and reprovisionned DM , after that, something changed good to working state and cherry on the cake I had to pair all the phones.

Really nice to do this for free with customer on my back asking why this happens, and the need of 2 bases now to do same job as previously with only one.

 

[AWS2P]

Hi @aws2p

This was purely a decision of the manufacturer, and since we support the device we will have to follow their releases accordingly for new templates and firmware as they were sent to us in their current form.

W80 series owners that have an issue with this will have to contact the manufacturer or device reseller directly.

Hi John, my problem is from 2 way, the first one is Yealink giving access to firmware in 3CX section so you think you are confident to apply as there's no warning at all on their site nor in firmware, firmware could check your update starting point and display alerts BEFORE applying.

Now on 3CX side there is nothing up to date also, Install guide is always explaining how to set one base alone including Base and DM roles, something that no more exist since 2 release now .

 

[complex1]

Do you never inform yourself of the release notes before updating the firmware?
That's scary.

 

[AWS2P]

Thanks for that one , in general when a release is available for 3CX, recommendation is to push it on PBX, Be honnest do you always take time to read in details before applying?
If downgrade was not impossible to do , my problem should have been solved in few minutes instead of 3 days of pressure.

 

[JohnS_3CX]

@aws2p I get what you are saying but since this is the direction the manufacturer took, this is something you will have to raise with them or the reseller at the end of the day.

As I personally understand it, going forward they will only support this base in the split firmware mode unless they state otherwise, so our choices are to either drop support or support it in the way the manufacturer does (regardless of whether this split was a good or bad idea).

 

[AWS2P]

@JohnS_3CX
Hi
I've done with manufacturer and wholesaler, Yes a got a new free base to add, but it has been hard to retrieve service working and here 3cx is involve too as the guide is always for a standalone base not for two separate with splitted firmawre.
So guide give no help on complete overview and in which order to do settings .

Problem is solved now , so just refresh guide to new way of use with 2 bases

 

[JohnS_3CX]

Yep, like i said since we support the device we will have to follow their releases accordingly for new templates and firmware.

The firmware is (and always was) available directly from Yealink via this page, and a revised guide is already in the works to cater for the changes.

 

[AWS2P]

Ok, this can be closed, thanks.