Fanvil Phones do not update

[ilushka85]

We have several brand new fanvil phones, but when clicking to upgrade their firmware the upgrade never takes place. They are behind an sbc. What can we check?

 

[cobaltit]

You don't mention what model but one of these guides may help:

https://www.3cx.com/sip-phones/fanvil-x3-x5/
https://www.3cx.com/sip-phones/fanvil-h3/
https://www.3cx.com/sip-phones/fanvil-c-series/

 

[Alphabetic]

Give one a reboot first then try again.

 

[JohnS_3CX]

Hi @ilushka85

Sometimes the firmware is too old and the manufacturer does not allow the phones to jump directly to the latest version.

In those cases you need to update them manually by visiting their site and upgrading step by step until you reach the version before our version.

 

[ilushka85]

They are barely couple numbers apart from the current version. We have x2 and x3 here is a screenshot:

 

[JohnS_3CX]

Seems a bit more, they are 2.10.0.xxxx whereas now we are on 2.10.1.xxxx

Try upgrading one phone manually to 2.10.1.6806 from the manufacturer's site
As soon as it is done then try again from your 3CX management console.

Are you using 3CX V16?

 

[ilushka85]

Seems a bit more, they are 2.10.0.xxxx whereas now we are on 2.10.1.xxxx

Try upgrading one phone manually to 2.10.1.6806 from the manufacturer's site
As soon as it is done then try again from your 3CX management console.

Are you using 3CX V16?

Will try and yes we are on v16. I do have another forum post open about v16 and api not working properly. Not sure if you can help but events for call connections are no longer raised while other events like registrations are.

 

[JohnS_3CX]

Ok let us know how the upgrade goes then and we can troubleshoot further if necessary.

Unfortunately I cannot help you on the API part. You posted it in the correct section though so the people that can help will see it.

 

[ilushka85]

Upgraded to 2.10.1.6806 on two different phones and tried to do firmware upgrade via 3cx. Phones reboot when I click the upgrade button but do not ever upgrade their firmware

 

[JohnS_3CX]

Sometimes the Fanvil devices will stop accepting the firmware upgrade process after a failure.
Try to do a cold restart on the phone by unplugging and plugging it again to allow it to a make another attempt.

If that does not work, then we will need to see if the firmware can actually be downloaded from the PBX. To do this, you will need to form the download link manually by using the following syntax

https://mypbx.3cx.com:5001/provisioning/{randomfolder}/firmware/fanvil/x3s_2.10.1.6836.z

• Assuming your HTTPS port is 5001 - adjust accordingly if you changed it
• {randomfolder} - can be seen in your provisioning link this is unique to your system

Then, enter this link in your browser, but your computer must connect from the same network that the phones are connected to replicate the same conditions. If you cannot download the file, the phones won't be able to either.

 

[SimoneNesi]

It's a very detailed explanation, I will make a test just receive a new firmware update message.
Thanks a lot
Simone

 

[JohnS_3CX]

For locally hosted servers, you just need to adjust the first part of your link to include the server's private IP instead of the FQDN (non https) and adjust the port accordingly

http://10.1.1.50:5000/provisioning/{randomfolder}/firmware/fanvil/x3s_2.10.1.6836.z

 

[ilushka85]

The problem is that it appears to be trying to download from the sbc and not the 3cx server. It continues to fail

 

[Alphabetic]

Are you able to reboot 1 phone via the phones tab?

I had an issue with X4 via STUN where the FW wouldnt push unless I rebooted a phone first.

Also, whats your internet speed like? Are you trying to DL all at once?

 

[ilushka85]

Yes rebooting works but still doesn't update. we have gigabit fiber speed isn't an issue.

 

[Alphabetic]

Are you able to download the FW via URL as John suggested?

 

[JohnS_3CX]

The problem is that it appears to be trying to download from the sbc and not the 3cx server. It continues to fail

The PBX sends them a URL with the firmware image so that's what they should be trying to download.

How did you figure out that they are trying to download from the SBC?