Update your Yealink Firmware Today

[cobaltit]

Doh.. and you clearly said that. I just misread your edit.

 

[cobaltit]

So I think there is a problem. My T41 updated fine but T46 won't update. It looks like 3CX is pushing the wrong firmware path. Viewing the config file 3CX pushes T41-36.83.0.55.rom but in the T46 config file it's trying to push patchT46-28-83.0.55.rom . It should be trying to push T46-28.83.0.55.rom.

 

[cobaltit]

@YiannisH_3CX Please ask the team to look at the above issue

 

[Marari]

@Marari So I haven't tried it but my understanding of the phrasing is that if there is a firmware released AFTER the .55 release you won't be able to update from the console. Meaning .20 -> .55 should work fine but say .20 -> .75 (just making that version up) won't. A fairly common situation when there is a major firmware structure change. Just like the SPA phones where you have to update to 7.5.2 before going higher. Don't have any T29's to test but my T41P's upgraded just fine.

T42, T58, T27 all worked fine.

T29G is the only one giving me trouble on the network.

 

[cobaltit]

I bet if you look in the folder you'll see a patchT29 and then the full file. It's probably the same error as I'm getting on the T46

 

[Marari]

I bet if you look in the folder you'll see a patchT29 and then the full file. It's probably the same error as I'm getting on the T46

Yep. That's exactly the case. But it's something that 3CX needs to fix. Right @YiannisH_3CX ?

 

[AramS_3CX]

Hello guys,
I'll try to answer to all existed questions.
1. Why is this update is so urgent?
The previous 3CX supported firmware version (xx.83.0.20) was provided by the Yealink team with the very major issue.
The problem here was that by mistake the Yealink team added some restriction which was not allowing the phones to download the files bigger than 2MB. This makes the FW update using the HTTP (HTTPS) URLs impossible - you still can download the file and manually upload it to the phone directly, but the firmware update from 3CX was not working.
You need to move to the xx.83.0.55 version which is fixing that problem and allows you to update the Yealink FW versions using the 3CX Management Console (using the HTTP (HTTPS) URLs)

2. How the update works and why do you need to have the custom "patch" files.
To fix the mentioned issue the Yealink team provided us with the "patch" files that will use some scripts to disable the mentioned restriction.
When the user will perform the firmware update on the Yealink phones from the 3CX Management Console, 3CX will provide 2 files to the phone - first the "patch" file to remove the restriction and then the actual firmware file.

In this example the phone will download the "patchT29-46.83.0.55.rom" file, it will remove the restriction, the phone will automatically download the actual "T29-46.83.0.55.rom" file and update.

3. New "Warning Display" feature
This is the new feature added by Yealink.
For security reasons, all provisioned phones must have a non-default web password.
If you are using the default "admin/admin" login you can be easily hacked. This is why the phone is warning you to change it.

4. @Marari
To manually update the phones you need to use the "T29-46.83.0.55.rom" firmware file (and NOT the "patch" one)

5. @Marari and @cobalit
I can't reproduce your issues. Right now, I'm successfully updated 2 of T29G models (one local and one remote) and 2 of T46G models (one local and one remote). Please check the provisioning settings and try again.
If you still will have the problems, please contact to our Support team so they will help you to understand why you are not able to update these particular phones.

 

[Marari]

@Aram

Thank you for the reply.

The problem is that while the "patch" script is downloading, I cannot get any of the T29's to update.

They are running behind a 3CX SBC talking to a Google Cloud implemented 3CX installation.

 

[AramS_3CX]

@Aram

Thank you for the reply.

The problem is that while the "patch" script is downloading, I cannot get any of the T29's to update.

They are running behind a 3CX SBC talking to a Google Cloud implemented 3CX installation.

View attachment 8881

It's very strange, because one the T29G phones that I updated was behind the SBC too.
Is it possible that the one of the FW files was corrupted during the download?
Here are real sizes of the T29G files:

Please have a look and if you still have the problem, please contact to our Support.

Another idea: Are you trying to update all of them together? If so, please try one by one - probably it's a limitation from the Google Cloud.

 

[Marari]

It's very strange, because one the T29G phones that I updated was behind the SBC too.

Please have a look and if you still have the problem, please contact to our Support.

Another idea: Are you trying to update all of them together? If so, please try one by one - probably it's a limitation from the Google Cloud.

I tried all and one-by-one.

File sizes are:

 

[AramS_3CX]

I tried all and one-by-one.

File sizes are:

View attachment 8884

The file sizes looks correct. Can you try to manually download the FW file from the 3CX PBX and try to update one of your phones manually?
The link will look like this: https://YOUR_PROVISIONING_URL/firmware/yealink/T29-46.83.0.55.rom

 

[Marari]

The file sizes looks correct. Can you try to manually download the FW file from the 3CX PBX and try to update one of your phones manually?
The link will look like this: https://YOUR_PROVISIONING_URL/firmware/yealink/T29-46.83.0.55.rom

Updating manually works just fine (for one). I just don't want to do 22+ phones manually.

 

[AramS_3CX]

Then, I think, you have some specific problem that needs to be investigated by our Support team.
Please contact to our Support so they will help you to fix it.

 

[jvivona]

we are seeing the same thing with our T46s connected via STUN. We've rebooted them and reprovisioned, they rebooted - thought they were downloading the firmware (red light was flashing) - but still no dice.

 

[cobaltit]

2. How the update works and why do you need to have the custom "patch" files.
To fix the mentioned issue the Yealink team provided us with the "patch" files that will use some scripts to disable the mentioned restriction.
When the user will perform the firmware update on the Yealink phones from the 3CX Management Console, 3CX will provide 2 files to the phone - first the "patch" file to remove the restriction and then the actual firmware file.

In this example the phone will download the "patchT29-46.83.0.55.rom" file, it will remove the restriction, the phone will automatically download the actual "T29-46.83.0.55.rom" file and update.

So how exactly is this part supposed to work? The config file generated by 3CX points to the patch file which makes sense given your explanation, but then how is the phone supposed to know to get the full file?

For the record we have a cloud-based instance with a SBC in our office. The T41P phones upgraded just fine but the T46G's will not. Going to try and switch one to STUN to see if it will upgrade.

 

[bbaker73]

we are seeing the same thing with our T46s connected via STUN. We've rebooted them and reprovisioned, they rebooted - thought they were downloading the firmware (red light was flashing) - but still no dice.

I've just started on my systems, and seems the T46s (STUN) are the ones having the most trouble with this update. A few small systems did ok, but some do not. Can't seem to find rhyme or reason.

 

[AramS_3CX]

So how exactly is this part supposed to work? The config file generated by 3CX points to the patch file which makes sense given your explanation, but then how is the phone supposed to know to get the full file?

For the record we have a cloud-based instance with a SBC in our office. The T41P phones upgraded just fine but the T46G's will not. Going to try and switch one to STUN to see if it will upgrade.

Hi cobalit,
The name of the "full file" is written in the patch file.

 

[AramS_3CX]

we are seeing the same thing with our T46s connected via STUN. We've rebooted them and reprovisioned, they rebooted - thought they were downloading the firmware (red light was flashing) - but still no dice.

Hi,
Don't reboot it. Just perform a Firmware Update.

 

[AramS_3CX]

I've just started on my systems, and seems the T46s (STUN) are the ones having the most trouble with this update. A few small systems did ok, but some do not. Can't seem to find rhyme or reason.

Hi bbaker73,
Check the System restrictions, probably multiple HTTPS requests to the same file are not allowed by the system.

 

[phonemaster]

Spent 2 days to update the phones on all customer's Phone Systems - everything past smoothly, except two T48G phones (provisioning method - STUN). After performing the firmware update from the 3cx PBX they reboot but didn't update. The second manual reboot fixed issue. This customer has a very slow internet connection - probably that was an issue.
Except for these two phones, the update of around 120 yealink phones to ".55" version passed without any problems. If someone interested here is the approximate list: 15 of T48G, 10 of T46G, 60 of T4xS, 10 of T29G, 5 of T27 and 20 of T5xS models.
3CX thanks for this update! Hope the yealink guys will not miss this type of issues anymore.