X4U-V2 as SBC - over time laggy LCD buttons and slow/crackly audio / FW 2.12.16.20

Status
Not open for further replies.

BTComp

Bronze Partner
Joined
Mar 3, 2021
Messages
18
Reaction score
4
Hi All

We have 3CX hosted on a brand new customer using 6x Fanvil X4U-V2 phones.

All are set up as SBC router phones so they can be taken home and work the same if needed, don't rely on other phones etc

3CX version 18.0 Update 8 (Build 939)Version

Phone Firmware version 2.12.16.20 (latest according to https://www.3cx.com/docs/phone-firmwares)

The issue:
All seemed fine at first, but over a couple of weeks the phone handset that the receptionist uses (95% of all calls are done just on this phone) became incredibly laggy to use, to the point calls took 3+ seconds to begin after picking up (caller cannot hear the worker say initial hello), calls were crackling for the receptionist and device was basically unusable. Calls were fine from POV of external callers (after that large initial delay).

Pushing buttons on phone itself (to dial a number or navigate menus) showed a delay of around a second to respond/update the LCD.

The receptionist uses a headset with the phone - Jabra Mono Pro 920 with the required adapter.

When this happened the first time I attended site and power cycled the phone, it said SIP Register failed at that point, so I factory reset it which solved that, then re-enabled the EHS function so the headset would work again and left site with it working as it did at initial install.

Less than two weeks later it's happened again - crackly audio, laggy LCD interface on phone. I tried factory reset but the crackly audio has remained (better but still unsatisfactory levels for customer)

For now I have installed SBC on the user's PC and changed this phone to run via that, instead of using the SBC of the phone itself, and calls are now perfect as you'd expect.

I saw comments about a memory leak that should have been patched out already - I am wondering if anyone else is still seeing bad behaviour from this new phone model, especially if using the EHS (headset) function.

The other phones work fine but as mentioned only take maybe 5% of calls.

I like the dual LCD feature of the X4U-V2 but no way am I ordering more of these until I can be sure firmware bugs are gone!

Thanks for your attention everyone :)
 
Last edited:
Hello. I'm having similar issues with a pair of X3U phones.

How do I access/modify the configuration file? Can I access it through the phone UI or does it need to change it in 3CX? My X3Us are provisioned from an SBC phone.

To clarify the config file should look like this?:
Output Device :.syslog.file

Thank you.
 
  • Like
Reactions: OlegR_3CX
I checked the config file on the X3U phones and did not have the "stdout" prefix. But, I did find that syslog was enabled and set to "debug". I decided to disable syslog all together and the X3U phones started working. They've only been online for a few hours, but they are working great so far. It seem like syslog may have been making them lag. Thanks.

X3U Syslog Offf.png
 
  • Like
Reactions: OlegR_3CX
Hi Internally, we removed the "stdout" from the configuration file and retested by setting the syslog level to "error." We have conducted stress testing for 15 days, and the same issue has not recurred. We suspect that this problem may be related to the syslog level. I recommend you also try this configuration method.

View attachment 40179

We have made this setting change on some V64 devices and the users are still reporting the poor quality, other phones we have moved to a windows SBC and this has resolved it.

Will there be some firmware or something released soon to resolve it?

Cheers,

Aaron.
 
A week later now after setting it up for my own extension (with EHS20+Jabra connected and EHS enabled on phone). I'm not even using it for calls as the crackle and lag started after a couple of days, it's just sitting there doing nothing.

I came in today and the X4U-V2 is showing SIP Register failed on the LCD.

I then found this in the 3CX phones tab (see attached image)...8 Fanvil phones all of different models (but similar first 6 digits on MAC for 7 of them) claiming to be ready for adoption (plus one generic "IP phone").

This is the only Fanvil on our LAN, so I have to wonder where these random models are coming from.

Is the desk phone crashing and sending out different model requests (even though they don't share firmware versions), or are these REAL phones from other companies talking to our LAN SBC over th einternet??? Worrying.

To finish it off, The actual model and LAN IP of the X4U-V2 aren't even in this listxD

Sent the logs off to Fanvil via our wholesaler last week and no word yet (sent files from this latest development off as well).


Just to finish up our part, we returned the phone to supplier for credit and have moved on. The other users still have their Fanvils at that site but they do not run headsets.

Given the glacial rate of support from Fanvil on this issue we are not likely to buy them again any time soon. The Yealinks across multiple customer sites have been no issue and even third party USB headsets seem to be plug and play in the back of the phones. Worth the extra $ in saved tech support time on our end!
 
  • Like
Reactions: digitalMD
One work around I have found is to setup a timed reboot on the phones time plan. If you go to phone settings and then select time plan on the Fanvil web GUI. You can schedule daily, weekly or monthly reboots. This resolves any memory leaks that accumulate over time. Below in the attachment I have my X5U set to reboot every day at 4am.
 

Attachments

  • reboot.jpg
    reboot.jpg
    24.9 KB · Views: 16
Last edited:
Status
Not open for further replies.

Forum statistics

Threads
111,974
Messages
590,081
Members
164,899
Latest member
mazet