V20 - Unable to upgrade yealink Firmwares

[Neil_Mc]

Hi All

Post update to V20, our firmware upgrades are not working

Provisioning the phones works fine, i can factory reset them and even recreate the extension but when sending upgrade, nothing happens on the phone.


Looking at other threads, i understand that the extension config provides a URL to the phone to download the firmware from. Checking a phone config, it has a firmware URL as follows:
#######################################################################################
## Configure the access URL of firmware ##
#######################################################################################
#Before using this parameter, you should store the desired firmware to the provisioning server.

firmware.url = https ://pbx.[mydomain].com.au/provisioning/xxxxxxxxxxxx/firmware/yealink/

it does appear that there are files in the yealink folder (we're on Windows)

Mode LastWriteTime Length Name
---- ------------- ------ ----
-a--- 18/11/2024 9:36 PM 347008 patchT54W(T57W,T53W,T53,T53C,T54,T57)-96.86.0.23.rom
-a--- 18/11/2024 9:36 PM 29228320 T4XS-66.84.0.35.rom
-a--- 18/11/2024 9:36 PM 29208656 T4XS-66.84.0.95.rom
-a--- 18/11/2024 9:36 PM 25559152 T4XS-66.85.0.5.rom
-a--- 18/11/2024 9:37 PM 23192144 T4XS-66.86.0.15.rom
-a--- 18/11/2024 9:36 PM 23180704 T4XS-66.86.0.5.rom
-a--- 18/11/2024 9:36 PM 36793152 T4XU-108.86.0.20.rom
-a--- 18/11/2024 9:36 PM 39492992 T4XU-108.86.0.77.rom
-a--- 18/11/2024 9:38 PM 48067392 T4XU-108.86.0.93.rom
-a--- 18/11/2024 9:36 PM 42373888 T54W(T57W,T53W,T53,T53C,T54,T57)-96.86.0.23.rom
-a--- 18/11/2024 9:36 PM 33026048 T5XW-96.85.0.5.rom
-a--- 18/11/2024 9:36 PM 45812896 T5XW-96.86.0.71.rom
-a--- 18/11/2024 9:37 PM 45811712 T5XW-96.86.0.72.rom
-a--- 18/11/2024 9:37 PM 47048128 T5XW-96.86.0.74.rom
-a--- 18/11/2024 9:37 PM 47213184 T5XW-96.86.0.76.rom
-a--- 18/11/2024 9:37 PM 47237264 T5XW-96.86.0.77.rom
-a--- 18/11/2024 9:39 PM 47230560 T5XW-96.86.0.81.rom


My selected example extension is a t46S running 66.85.0.5, when failing. I updated it manually to 66.86.0.5.rom (copied from the instance folder) but this still failed to upgrade.

 

[Neil_Mc]

Hi Nicholas

On my Lan, i have a single authoritative zone which resolves my FQDN to an local IP on the 3cx Instance. There is no firewall between the yealink phone and 3CX. As you can see the URL is https and when i visit the URL the certificate validation is good.
So in this instance there is no Hairpin NAT in use internally. If the client roams to external, DNS directs them to a public IP which is 1:1 NAT through to the same Server IP, and this also works well (also with valid certificate matching)