Fanvil v64 Update Loop - 3CX 20 Update 9

lancerichards

Platinum Partner
Advanced Certified
Joined
Aug 14, 2024
Messages
159
Reaction score
196
Hi Team

We are seeing in Update 9 V64 going in to a boot loop

Downloading...
1782186755846.png

Upgrade Failed!
1782186775119.jpeg

It keeps trying and does not succeed.

I don't have much faith in Fanvil testing their firmware releases.
 
Are you trying to update the firmware from the PBX, or did you manually add the firmware to the phone?
Neither. The phone is obviously hitting the provisioning URL and trying to download the new firmware and going in this loop.
We started getting calls about it after U9 went through on the weekend.

We're just doing some further testing with a manual update via 3CX to see if that resolves it but still too early to tell as we have only done 2 or 3.
 
Neither. The phone is obviously hitting the provisioning URL and trying to download the new firmware and going in this loop.
We started getting calls about it after U9 went through on the weekend.

We're just doing some further testing with a manual update via 3CX to see if that resolves it but still too early to tell as we have only done 2 or 3.
I suggest trying to upgrade the firmware first before trying to provision it. If it does not upgrade from the PBX, then download the firmware from the link below manually and apply it to the phone.

https://www.3cx.com/docs/phone-firmwares/
 
I suggest trying to upgrade the firmware first before trying to provision it. If it does not upgrade from the PBX, then download the firmware from the link below manually and apply it to the phone.

https://www.3cx.com/docs/phone-firmwares/
Sorry @NikolasA_3CX I think you have misunderstood.
These are existing phones already provisioned for some time, out in the field which every hour or so this is what is happening.
 
Hi Lance,

Let's take a look at that particular Fanvil:

1. What exact version is it running right now?

2. Is it actually rebooting or just attempting and aborting without preventing the use of the phone? (ie. just a nag message on screen)

3. Can you take a look at its config file, specifically the link encased in <Auto_Image_Url> ? This will show you where the phone is trying to upgrade from. Perhaps this is a now invalid link, or perhaps the phone cannot reach that link for some reason. Perhaps the firmware was previously purged, but the phone still remembers the link from before the cleanup. It keeps trying and failing.
 
Following this post; we have updated firmware for 200+ V64 sets to 2.12.21.32 from 2.12.20 and experiences sluggish performance, inability to answer/end calls; choppy voice; long delay to talk path, no talk path at all, etc. 3CX says Fanvil issue; Fanvil ticket open with no response yet. We would like to restore all the sets back to 2.12.20 but direct upgrades through web interface fail. 3CX says there is no way to force the downgrade. It sounds like your system is forcing a firmware change somehow. Would like to understand how that works so we could potentially force the downgrade automatically. Long shot but looking for a solution.
 
  • Like
Reactions: atmomin
Following this post; we have updated firmware for 200+ V64 sets to 2.12.21.32 from 2.12.20 and experiences sluggish performance, inability to answer/end calls; choppy voice; long delay to talk path, no talk path at all, etc. 3CX says Fanvil issue; Fanvil ticket open with no response yet. We would like to restore all the sets back to 2.12.20 but direct upgrades through web interface fail. 3CX says there is no way to force the downgrade. It sounds like your system is forcing a firmware change somehow. Would like to understand how that works so we could potentially force the downgrade automatically. Long shot but looking for a solution.


Hi,

Please follow up with Fanvil for further details, we cannot assist you any further from our end.

If it helps to know, I was able to downgrade one in the past, but only when its in the factory default state.
Not while it was provisioned, and not via 3CX, only manually.

Those models are known to have some issues, please read this post here if you haven't seen it already:
..and then you can follow up with Fanvil where they will advise you how to proceed.
 
Hi @JohnS_3CX
Unfortunately, Fanvil Support are less than helpful. I note they are not even active in the forums any more.

Rename the extension to .z to upload to the phone.
This is the only tested and working version which is working with the 3CX Routerphone Firmware without lag.
I would recommend that you release this as the "supported" version for 3CX v64. We spent hundreds of hours testing with Fanvil.
It does disable Bluetooth and Wireless to achieve this.

I doubt they are testing their new firmware in any great detail to validate end user experience to find these bugs. :(

Best
Lance
 

Attachments

  • Like
Reactions: rayt and Evolute IT
Hi Lance,

In the past we looked at the possibility with them to have those disabled only when in router mode, but it looks like this is not doable as its baked into the firmware.

Their solution is to release a new hardware revision of the V64 that doubles the RAM.

As they have informed us, they will look at tickets on a case by case basis, and decide whether to replace your devices with the new revision, at Fanvil's own discretion.

The remaining alternative is to not use them as router phones and have a dedicated SBC (Windows/Debian/Pi or the new A710 device).
 
Hi @JohnS_3CX
Unfortunately, Fanvil Support are less than helpful. I note they are not even active in the forums any more.

Rename the extension to .z to upload to the phone.
This is the only tested and working version which is working with the 3CX Routerphone Firmware without lag.
I would recommend that you release this as the "supported" version for 3CX v64. We spent hundreds of hours testing with Fanvil.
It does disable Bluetooth and Wireless to achieve this.

I doubt they are testing their new firmware in any great detail to validate end user experience to find these bugs. :(

Best
Lance
Appreciate the firmware share; happy to report it downgraded a phone. Fanvil support has not responded at all yet.
 
  • Like
Reactions: lancerichards
So interesting we have the same issue since upgrade to v9, however on x4u v2 phones. Firmware on the devices are: 2.12.25.6
Looked at the config files on the devices, and the only thing I could see related was this, so that would suggest the firmware update isn't been pulled from the phone, so is something been pushed from the 3cx end. These devices have been in place a couple of years, and has only started with this latest version 9 update.
<fwCheck>
<EnableAutoUpgrade>0</EnableAutoUpgrade>
<UpgradeServer1></UpgradeServer1>
<UpgradeServer2></UpgradeServer2>
<AutoUpgradeInterval>24</AutoUpgradeInterval>
</fwCheck>
 
  • Like
Reactions: lancerichards
We're experiencing issues with the V64. Our setup includes two phones, one of which is acting as a router/SBC.
The problem began with over-ringing—the phone continued to ring even after the user picks up. Additionally, once the call was connected, there's a delay of about 2-3 seconds before the call was actually established.
We also have a Fanvil X4U on the same setup, which has been working without any issues. After installing a Raspberry Pi to act as an SBC, the V64 problem went away. I hope the next Fanvil's firmware update fix this issue.
 
Hi @JohnS_3CX
Unfortunately, Fanvil Support are less than helpful. I note they are not even active in the forums any more.

Rename the extension to .z to upload to the phone.
This is the only tested and working version which is working with the 3CX Routerphone Firmware without lag.
I would recommend that you release this as the "supported" version for 3CX v64. We spent hundreds of hours testing with Fanvil.
It does disable Bluetooth and Wireless to achieve this.

I doubt they are testing their new firmware in any great detail to validate end user experience to find these bugs. :(

Best
Lance
Hi Lance. Thanks for sharing the F/W!!
I couldn't find this version anywhere and Fanvil haven't responded to my ticket (yet).
The "released" F/W versions on their website wouldn't install for me, but your one worked ;) .
I just need to test it now and, all going well, will install in the customer's phones.
 
Well, everything seems to be good now with v2.12.21.6. Thanks Lance, you're a lifesaver!

Anyway, 3CX keeps wanting to "upgrade" to v2.12.21.32 :oops: - wouldn't that be a downgrade?? (I had to disable auto update on provisioning) so I am hoping that someone (probably Fanvil, maybe 3CX?) will let us know when there is an approved update available, so that I can get these phones back to a clean/current/approved firmware and not see the red "upgrade" notification in the console.

For now I'm happy though. Thanks for the many hours you spent on this in the background Lance. I owe you one ;).

Cheers.
Ray
 
  • Love
Reactions: lancerichards
Actually I realise I am not thinking in the right terms. 6 vs 32 (-24 minor revisions) as opposed to 6x vs 3x (+3 "major versions").
Anyway, the fact remains, Fanvil need to get their act together!
(still haven't had a response to my ticket with them)
 
We have 3 V64 working as SBC at different sites, after last firmware upgrade to 2.12.21.32, it killed itself and other phones connected via it. Very disappointing to see such poor testing of firmware before release. I temporarily reconfigured phones as local to make it work until firmware issue is fixed. I hope Fanvil and 3CX will figure out the issue sooner than later.
 
We have 3 V64 working as SBC at different sites, after last firmware upgrade to 2.12.21.32, it killed itself and other phones connected via it. Very disappointing to see such poor testing of firmware before release. I temporarily reconfigured phones as local to make it work until firmware issue is fixed. I hope Fanvil and 3CX will figure out the issue sooner than later.
I installed v2.12.21.6 from @lancerichards attachment above, which fixed the issue.

Also, finally had a response from Fanvil, which was to offer me an A710 SBC, I guess that means they don't intend to fix the problem :mad:.

I still haven't received the A710 yet. Lucky I used the above F/W or the client would still be down.
 

Members Online Now

Forum statistics

Threads
111,832
Messages
589,278
Members
164,662
Latest member
DejanMDS