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

[BearCreekTech]

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.

 

[BearCreekTech]

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.

 

[Aaron Falzon]

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.

 

[nooma.solutions]

Update?

 

[BTComp]

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 list

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!

 

[David1819]

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.