Toggle sidebar Toggle sidebar

Update your Yealink Firmware Today

Status
Not open for further replies.
Vincent S said:
Tried updating one of our clients with 35 phones (T48S Phones) through the console at 10pm . Never updated during the night. Next day during business hours around 11am eastern the phones started during an firmware update and got stuck in a loop. (Phone kept restarting)

Had to shutdown the 3cx Server to stop the loop. At that point I had my team manually update the phones. We missed one which wasn't important and did it through the console that night and it worked like a charm.

Next time there is an update we will restart the 3cx server first.
Click to expand...
Hi Vincent S,

As I already informed the guys here, the additional reboots (or a loop) can happen when the downloaded firmware file is corrupted.
I think (this is only a hypothesis), in your case, 35 phones started to download the same file. The chance that this file can corrupt in not ideal networks (I'm talking not only about the speed, but also about the firewalls, switches, network cards, wires and etc) is very high.
These 35 phones were continuously downloading the file at the same time and corrupting it because of the big surge in the network (one corrupted bit can break the update procedure).
The forgotten phone "was alone" and there was not the big surge in the network, this is why it updated like a charm.
Next time, please try to update them one by one and check the difference.
 
bbaker73 said:
Maybe related, maybe not. I have T46S and T42G on the new .55 FW.

I wanted to test something on a different downloaded Yealink FW version on the 46S.
Update from the web UI fails.
Reset to defaults, same thing.
Tried a 2 or 3 FW versions from Yealink site. Updated failed.
Tried another PC browser, moved phone to another network. Update failed.

Tried on a second T46S that is on .55. Tried to upgrade to newest Yealink website FW 66.84.0.10. Update failed.

Then I decided to try a T42G that's on the new .55 FW. Tried to downgrade it to Yealink FW 29.83.0.50 and 29.83.0.30. Update failed.

Has anyone else tried to manually change the FW version once the phone is on this new .55 version as I don't seem to be successful.
Click to expand...
Hi bbaker73,

To avoid the unexpected downgrades to the broken firmware versions, the Yealink guys are decided to block the downgrade functionality on the "xx.83.0.55" version.
They are not sure which version can have this firmware update problem too (Yealink is also providing some custom firmware versions) and this why they restricted the downgrades by date. So, you can't downgrade the phone to the versions that were prepared before the "xx.83.0.55" version.
The "xx.84.0.10" was prepared before the "xx.83.0.55" (ignore the version numbers - the date is urgent) this is why you can't update to that version too.

We already informed the Yealink guys about this and they assured us that the next V84 firmware will be fully compatible with 3CX (including all the features, provisioning types and firmware update functionality) and they will test it very-very-very carefully.
 
Last edited:
  • Like
Reactions: bbaker73
Aram said:
Hi Vincent S,

As I already informed the guys here, the additional reboots (or a loop) can happen when the downloaded firmware file is corrupted.
I think (this is only a hypothesis), in your case, 35 phones started to download the same file. The chance that this file can corrupt in not ideal networks (I'm talking not only about the speed, but also about the firewalls, switches, network cards, wires and etc) is very high.
These 35 phones were continuously downloading the file at the same time and corrupting it because of the big surge in the network (one corrupted bit can break the update procedure).
The forgotten phone "was alone" and there was not the big surge in the network, this is why it updated like a charm.
Next time, please try to update them one by one and check the difference.
Click to expand...

I wish I saw this before I troubleshooted for an hour but glad it’s here now. Anyone who has a firmware boot loop try it.
Worked like a charm, noticed a few rebooting like mad and trying to update the FW from phones page fixed it. I tried manually updating the FW locally and it would just loop nonstop.

Ty for this quick resolution and continued support.
 
luckystrikes said:
I wish I saw this before I troubleshooted for an hour but glad it’s here now. Anyone who has a firmware boot loop try it.
Worked like a charm, noticed a few rebooting like mad and trying to update the FW from phones page fixed it. I tried manually updating the FW locally and it would just loop nonstop.

Ty for this quick resolution and continued support.
Click to expand...
Hi luckystrikes,

I'm happy that the provided solution helped you.
Please remember that it's a Yealink behavior and not the 3CX. I hope you can find this information somewhere in Yealink phone's documentation or Yealink forums.
We can't guess what type of questions/issues you can have and providing the information per customers request.
 
Update:

I sent a reboot command to all the T29Gs on the customer site via the console. All but 3 of them rebooted. Once the phones had rebooted, I was able to push the firmware update through the console.

I had to have the client manually reboot the remaining 3 phones. Once they came up and I was able to send a reboot command from the console, I was able to update those phones as well.

Hope this helps.
 
Weird. What would account for this?

Have client site with 6 T46G's that, like all the other clients, T46G's would not update. Tried many times a few weeks ago. Sometime last week I tried again with no success. Client just called and 5 out of 6 of them just decided out of the blue to apply the firmware update and reboot. How is this delay possible?

Edit. So after this happened, I went back to all the clients with 46G's that wouldn't update. After sending reboot commands (again), a lot of them updated. Some I had to send FW update commands as well and got them all updated. Same procedures I had done a few weeks ago, so not sure why now is any different, but they're finally all updated.
 
Last edited:
Last edited:
Status
Not open for further replies.

Latest Posts

Forum statistics

Threads
111,991
Messages
590,166
Members
164,929
Latest member
Cloudstar
3CX Logo Footer Copyright © Sitemap Privacy
Top Bottom