Solved v15.5 SP5 - Can't update Yealink firmware?

[Matt (Ignite Solutions)]

Hi there,

I've got a 3CX PBX running in Azure, deployed by the PBXExpress wizard. I've recently updated it to Update 5, which brings with it new approved firmware for the Yealink T56A handset I have. The T56A is now showing in the Phones page as having a Not Supported firmware version. The T65A is currently running ver 58.80.0.25 - the previous approved firmware version.

Easy Peasy! I'll just update the firmware from the 3CX console. Download the new firmware to the PBX. Select the phone on the Phones tab, and click the +Firmware button. And...

...nothing happens

The phone is set to "Direct SIP (STUN - remote)" provisioning, and the MAC address is registered with Yealink. If I factory-reset the phone, it re-provisions perfectly, registers the extension, etc. I can make and receive calls perfectly. But try as I might, I can't get it to remotely upgrade the firmware.

I've read a lot about disabling certificate checking on the phone, but from what I gather that was only a problem with earlier phone firmware, and specifically when upgrading the PBX from v15 to v15. I can't find any newer articles about it, so I'm assuming that's a red herring.

I've upgraded/downgraded phones manually before, so I'm quite happy with that process if I need to. But I understand that the remote upgrade *should* work, so I'm confused as to why it's not happening for me.

Thoughts? What am I doing wrong here?

Cheers,
Matt

 

[CentrexJ]

This generally works fine. We use 3CX deployed on Azure for our own pbx and the remote stun Yealinks updated their firmware fine (they aren’t t56a though).

Are you using the 3cx template or a custom one? More likely to fail on a custom template not up to date with the latest 3CX changes.

 

[JustinC]

I have found that some times it is intermittent in functioning correctly, sometimes holding the mouse button down longer helps helps.. and I have no clue why LOL

 

[[email protected]]

is there an available firmware in the /yealink/firmware folder on the provisioning path?

 

[Matt (Ignite Solutions)]

Thanks for the help everyone - I appreciate it.

This generally works fine. We use 3CX deployed on Azure for our own pbx and the remote stun Yealinks updated their firmware fine (they aren’t t56a though).

Are you using the 3cx template or a custom one? More likely to fail on a custom template not up to date with the latest 3CX changes.

Good to know that it should work, and that I'm not doing anythign wrong.

I'm using standard templates at the moment. I've been thinking about custom ones to be able to provision a customer background image, but want to get the basics nailed down before I get too fancy like that.

I have found that some times it is intermittent in functioning correctly, sometimes holding the mouse button down longer helps helps.. and I have no clue why LOL

I'll give it a shot! I'll try anything at this point .

is there an available firmware in the /yealink/firmware folder on the provisioning path?

I'm not sure how to check that. I've tried hitting :
https://mypbxname.3cx.com.au/provisioning/<provisioningID>/yealink/firmware/ and
https://mypbxname.3cx.com.au/provisioning/yealink/firmware/ in my browser, and both return a 404 error.

I'll try to SSH into the VM and see if I can find where it's holding that folder internally. I can't see anywhere in the UI where it lists downloaded updates and their version files.

Interesting aside - against my better judgement, I actually tried a remote firmware upgrade on one of my client PBXs last night. It's worked perfectly. That's the exact same 3CX version, etc, against a Yealink T58 (different to my T56A). I wonder if it's something specific to the T56A?

Cheers,
Matt

 

[phonemaster]

Thanks for the help everyone - I appreciate it.



Good to know that it should work, and that I'm not doing anythign wrong.

I'm using standard templates at the moment. I've been thinking about custom ones to be able to provision a customer background image, but want to get the basics nailed down before I get too fancy like that.



I'll give it a shot! I'll try anything at this point .



I'm not sure how to check that. I've tried hitting :
https://mypbxname.3cx.com.au/provisioning/<provisioningID>/yealink/firmware/ and
https://mypbxname.3cx.com.au/provisioning/yealink/firmware/ in my browser, and both return a 404 error.

I'll try to SSH into the VM and see if I can find where it's holding that folder internally. I can't see anywhere in the UI where it lists downloaded updates and their version files.

Interesting aside - against my better judgement, I actually tried a remote firmware upgrade on one of my client PBXs last night. It's worked perfectly. That's the exact same 3CX version, etc, against a Yealink T58 (different to my T56A). I wonder if it's something specific to the T56A?

Cheers,
Matt

Hi Matt,
I have a customer that is using 17 yealink T5 models (10 of them are T56A, and 7 are T58).
All of them are provisioned over "Direct STUN" and last night I successfully updated all of them from 58.80.0.25 to 58.80.0.65.
Due that it's a remote server, try to check the actual size of the "T5XA-58.80.0.65.rom" file - probably it was corrupted during the download. The size should be 216064 KB.
Also, check if you have the "SSL Transport and Ciphers" enabled on 3CX PBX (Settings->Security page). If so, disable it and try again. If it will work - update all your phones and after that you can enable it back.

 

[Matt (Ignite Solutions)]

Hi Matt,
I have a customer that is using 17 yealink T5 models (10 of them are T56A, and 7 are T58).
All of them are provisioned over "Direct STUN" and last night I successfully updated all of them from 58.80.0.25 to 58.80.0.65.
Due that it's a remote server, try to check the actual size of the "T5XA-58.80.0.65.rom" file - probably it was corrupted during the download. The size should be 216064 KB.
Also, check if you have the "SSL Transport and Ciphers" enabled on 3CX PBX (Settings->Security page). If so, disable it and try again. If it will work - update all your phones and after that you can enable it back.

Thanks PM - that's great advice. Good to know that it *should* work fine.

I've jumped into the VM now, and I've found the T5XA-58.80.0.65.rom file. It's showing up with a size of 221249056, which by my maths is 216,064kb. So it looks like it's got the right file on the PBX.

That "SSL Transport and Ciphers" option was enabled. I've disabled it and tried another push to the phone. It looks like it's working! The phone turned off for a long time, but it's booted up now and is now running 58.80.0.65!

Thanks so much for that - I never would have thought to turn that option off. I'll re-enable it now as you've stated.

Many thanks again!

Cheers,
Matt

 

[YiannisH_3CX]

Glad to see that issue has been resolves and thank you for updating the thread with your solution