Fanvil Phone Testing Issues with 3CX (Firmware and BLF)

[mujin1]

Hi,

I am currently testing the X series phones before going into production. I noticed that the PnP works very nicely but when assigned BLF or attempt the upgrade the firmware nothing happens. The phone will restart but the firmware is not pulled down. I have also confirm the URL to the 3CX supported FW works but there is no auto upgrade occurring.

I can see in the {mac}.cfg:

<Auto_Pbook_Url>http://10.2.20.2/provisioning/qobhxh9mn5cw/fanvil_phonebook.xml</Auto_Pbook_Url>
<Auto_Image_Url>http://10.2.20.2/provisioning/qobhxh9mn5cw/firmware/fanvil/x61.4.4.2.z</Auto_Image_Url>

Current firmware is: 1.4.4.1 (one revision behind 3CX preferred)

This is a newly build system 3CXPhoneSystem 15.5.15502.6 on debian
Has anyone had issues with Fanvil and firmware upgrades from the 3CX console, or when assigning the BLF nothing happens on the phone.

Thank you in advance.

 

[mujin1]

Full syslog output from the phone is here:
https://pastebin.com/FdZHAfgX

 

[Saqqara]

First port of call, update the firmware to 3cx supported version

 

[mujin1]

Hi, thanks for the reply.

Any suggestion on mass firmware updates. If I go ahead with this for a production deployment I am not so keen on doing this one by one before the FW update button works in the GUI.

 

[phonemaster]

Hi, thanks for the reply.

Any suggestion on mass firmware updates. If I go ahead with this for a production deployment I am not so keen on doing this one by one before the FW update button works in the GUI.

Hi,
I think you have a problem with the phone re-provisioning:
......
Jan 1 09:00:37 10.2.20.17 platform[310]: I/vcore.nc.element | ncElementAddByName: start element not match, start name=[cfg], dotname=[]!#015
Jan 1 09:00:37 10.2.20.17 platform[310]: I/vcore.nc.parse | ncParseDot: parse[] failed!#015
Jan 1 09:00:37 10.2.20.17 platform[310]: I/vcore.nc.element | ncElementAddByName: start element not match, start name=[cfg], dotname=[]!#015
Jan 1 09:00:37 10.2.20.17 platform[310]: I/vcore.nc.parse | ncParseDot: parse[] failed!#015
Jan 1 09:00:37 10.2.20.17 platform[310]: I/vcore.nc.element | ncElementAddByName: start element not match, start name=[cfg], dotname=[]!#015
Jan 1 09:00:37 10.2.20.17 platform[310]: I/vcore.nc.parse | ncParseDot: parse[] failed!#015
Jan 1 09:00:37 10.2.20.17 platform[310]: I/vcore.nc.element | ncElementAddByName: start element not match, start name=[cfg], dotname=[]!#015
Jan 1 09:00:37 10.2.20.17 platform[310]: I/vcore.nc.parse | ncParseDot: parse[] failed!#015
Jan 1 09:00:37 10.2.20.17 platform[310]: E/vcore.cfg.save | There is no valid item in this module[<PROP CONFIG MODULE>].#012#015
Jan 1 09:00:37 10.2.20.17 platform[310]: E/vcore.cfg.save | There is no valid item in this module[--Code Plan List-- :].#012#015
Jan 1 09:00:37 10.2.20.17 platform[310]: E/vcore.cfg.save | There is no valid item in this module[<CONFIG SCREENSAVER>].#012#015
Jan 1 09:00:37 10.2.20.17 platform[310]: E/vcore.cfg.save | There is no valid item in this module[<CONFIG USER CHANGE BACKGROUND>].#012#015
Jan 1 09:00:37 10.2.20.17 platform[310]: E/vcore.cfg.save | There is no valid item in this module[<DSP CONFIG MODULE>].#012#015
Jan 1 09:00:37 10.2.20.17 platform[310]: I/vcore.ap.phoneFlash | apPhoneFlashStart start#015
Jan 1 09:00:37 10.2.20.17 platform[310]: I/vcore.ap.main | apRequestEventProcess !#015
Jan 1 09:00:37 10.2.20.17 platform[310]: I/vcore.ap.main | apRequest: sourceTypehoneFlash, url:http://10.2.20.2/provisioning/qobhxh9mn5cw/0C383E0E75AC.cfg#015
.....

Are you using the default provisioning template?
Can you try to manually download the config file (http://10.2.20.2/provisioning/qobhxh9mn5cw/0C383E0E75AC.cfg) and check is it corrupted or does it contain all required components?
Remember: The Fanvil phones requires the config files in pure (clean) XML format.

 

[mujin1]

Hi. I am using the default template as its a fresh install. As far as I know I have made any modifications to the templates. All template files have been updated from the 3CX website and seeing this with all the fanvil phones I have. Yealink seems to work straight away. When I provision phone I usually just set the LLDP to enable and the timezone to JST +0900 from the GUI.

I found formatting error in the xml though

<Register_User>>#########</</Register_User>
<Register_Pswd>>#########</</Register_Pswd>
<Register_TTL>120</Register_TTL>
<Enable_Reg>1</Enable_Reg>

<Proxy_Addr></Proxy_Addr>
<Proxy_Port></Proxy_Port>



<Proxy_User>>#########</</Proxy_User>
<Proxy_Pswd>>#########</</Proxy_Pswd>
<FWD_Timer>60</FWD_Timer>
<Ring_Type>0</Ring_Type>

Also looking at my template file the syntax appears to be correct

After re-apply the phone I can see the brakets are no longer there.... I will come back later when I am in the office to retest this.

 

[phonemaster]

Hi. I am using the default template as its a fresh install. As far as I know I have made any modifications to the templates. All template files have been updated from the 3CX website and seeing this with all the fanvil phones I have. Yealink seems to work straight away. When I provision phone I usually just set the LLDP to enable and the timezone to JST +0900 from the GUI.

I found formatting error in the xml though

<Register_User>>#########</</Register_User>
<Register_Pswd>>#########</</Register_Pswd>
<Register_TTL>120</Register_TTL>
<Enable_Reg>1</Enable_Reg>

<Proxy_Addr></Proxy_Addr>
<Proxy_Port></Proxy_Port>



<Proxy_User>>#########</</Proxy_User>
<Proxy_Pswd>>#########</</Proxy_Pswd>
<FWD_Timer>60</FWD_Timer>
<Ring_Type>0</Ring_Type>

Also looking at my template file the syntax appears to be correct

After re-apply the phone I can see the brakets are no longer there.... I will come back later when I am in the office to retest this.

Hi,
Never saw something like this, even in earlier (old) fanvil templates.
Is it possible that someone modified the 3cx generated username and passwords to something like this:
>username</
>password</

 

[mujin1]

I am going to close this thread off to avoid any confusion, I tried many more time but I could not re-create that issue. Still I am having some trouble though with Fanvil but I will post as a different thread to avoid any confusion with this particular issue. Thank you all for the input.