X7 Provisioning Not Working

[kevinfwb]

I'm running 3CX V20 in Lightsail

I have X7's at two separate locations that will not provision. They went offline sometime over the weekend and I am unable to get them to provision. I've deleted the phone, re-added it, verified that the firmware is up to date, and recreated the phone.

I've done a lot of digging into log files trying to figure out what exactly is happening. Both locations are behind an SBC and I had no issues provisioning a Grandstream phone. I think that I've narrowed down the issue but I'm stuck on my next troubleshooting steps.

From the logs on the X7 (v1) firmware 2.4.12 I'm getting a 200 OK when downloading the cfg file from the server and a few lines down there is "uAesDecrypt The data is invalid" and then finally an "Invalid config file"

If I use the same URL the config file downloads without issue in a browser and I'm able to manually load it onto the phone UI.

I'm really at a loss and could use some assistance.

Kevin

2024-03-05 19:17:07 User.Debug 192.168.1.190 Mar 6 08:17:09 platform[311]: D/vcore.mt.main | mtCurrentContextPrint ********* end *******
2024-03-05 19:17:07 User.Debug 192.168.1.190 Mar 6 08:17:09 platform[311]: D/vcore.mt.cfgUpdate | cfgUpdateFromFd Start !
2024-03-05 19:17:07 User.Debug 192.168.1.190 Mar 6 08:17:09 platform[311]: D/vcore.mt.main | mtEventRaise: source=[ap] file=[XXXXX3e02e9b0.cfg] state=[downloading]!
2024-03-05 19:17:07 User.Debug 192.168.1.190 Mar 6 08:17:10 platform[311]: D/vcore.curl.client | curlClientOperationFinish: curlCode=0
2024-03-05 19:17:07 User.Debug 192.168.1.190 Mar 6 08:17:10 platform[311]: D/vcore.curl.client | curl_easy_perform curlErrorCode 0 return code 200 this_url=[https://xxxxxxxxxxxxx.south.3cx.us/rps/105:*************.cfg]
2024-03-05 19:17:07 User.Debug 192.168.1.190 Mar 6 08:17:10 platform[311]: D/vcore.curl.client | curlClientOperationFinish: curlErrorCode=0
2024-03-05 19:17:07 User.Debug 192.168.1.190 Mar 6 08:17:10 platform[311]: D/vcore.mt.cfgUpdate | readLen=29490
2024-03-05 19:17:07 User.Debug 192.168.1.190 Mar 6 08:17:10 platform[311]: D/vcore.mt.cfgUpdate | digest=[],tempDigest=[8da590e8bd7d186ed516d674411a6a93]
2024-03-05 19:17:07 User.Error 192.168.1.190 Mar 6 08:17:10 platform[311]: E/vcore.utils.aes | uAesDecrypt The data is invalid.
2024-03-05 19:17:07 User.Info 192.168.1.190 Mar 6 08:17:10 platform[311]: I/vcore.mt.cfgUpdate | mtFormatConfig Start!
2024-03-05 19:17:07 User.Info 192.168.1.190 Mar 6 08:17:10 platform[311]: I/vcore.mt.cfgUpdate | mtFormatConfig End.
2024-03-05 19:17:07 User.Warning 192.168.1.190 Mar 6 08:17:10 platform[311]: W/vcore.cfg.utils | Invalid config file!
2024-03-05 19:17:07 User.Info 192.168.1.190 Mar 6 08:17:10 platform[311]: I/vcore.mt.main | mtUpdateRequest: source=[ap] file=[XXXe02e9b0.cfg] result=file invalid
2024-03-05 19:17:07 User.Debug 192.168.1.190 Mar 6 08:17:10 platform[311]: D/vcore.mt.main | mtEventRaise: source=[ap] file=[XXXXe02e9b0.cfg] state=[terminated]!
2024-03-05 19:17:07 User.Debug 192.168.1.190 Mar 6 08:17:10 platform[311]: D/vcore.ap.main | apDownloadTask mtUpdateResult=file invalid
2024-03-05 19:17:07 User.Info 192.168.1.190 Mar 6 08:17:10 platform[311]: I/vcore.ap.main | apDownloadTask download result=error
2024-03-05 19:17:07 User.Info 192.168.1.190 Mar 6 08:17:10 platform[311]: I/vcore.ap.main | apTaskCenter: sourceType=PhoneFlash,commonCfgDownloadResult=error,deviceCfgDownloadResult=error
2024-03-05 19:17:07 User.Info 192.168.1.190 Mar 6 08:17:10 platform[311]: I/vcore.ap.main | apModuleDownloadStart: type=[0]
2024-03-05 19:17:07 User.Info 192.168.1.190 Mar 6 08:17:10 platform[311]: I/vcore.ap.main | apNeedRebootGet: flag=[0].
2024-03-05 19:17:07 User.Debug 192.168.1.190 Mar 6 08:17:10 platform[311]: D/sdevDbEmb | [SELECT ID FROM smss WHERE type = '1' AND flag = '1' ORDER BY time DESC;]
2024-03-05 19:17:07 User.Warning 192.168.1.190 Mar 6 08:17:10 platform[311]: W/vcore.pfm.smsDb | smsSearch: num==0
2024-03-05 19:17:07 User.Debug 192.168.1.190 Mar 6 08:17:10 platform[311]: D/vcore.pfm.mwi | pfmMwiGetNewMessageNums: Mwi: nums=0
2024-03-05 19:17:07 User.Debug 192.168.1.190 Mar 6 08:17:10 platform[311]: D/return_val_if_fail | xuiDrawBmp:958 picInfo failed.

 

[kevinfwb]

I forgot to mention that this exact same behavior is occurring on all 5 of our X7 phones as well as a hardwired X7A.

 

[nikolascx]

Hi Kevin Thanks for reporting. We will check this and help you out no problem.
From the logs it looks like the decryption fails which of course results in an invalid config.

Can you contact the manufacturer in the meantime so we work in parallel? I mean you did all the right tests.
The browser can parse the file but the phone tries and fails. I think it is something inside the phone.

I would try and give it a manual firmware upgrade (from the phone's web interface) in order to flush out any previous firmware remains and have the new firmware in place. You do this. in the meantime, our team is checking with an inhouse X7 and get the manufacturer to see your logs also.

We will keep in touch - have a great day ahead.

 

[nikolascx]

We have confirmed and you are right. This is broken. But it broke now (recently)
It is not related to a firmware image because the last image and the one you are using is a stable one for 3 years.

For sure it seems to be something related to Fanvil RPS. We informed Fanvil - please do the same. Thank you so much for reporting.

 

[kevinfwb]

Thank you for confirming and letting me know. When everyone left the office on Friday all of the phones were working but once they came in on Monday they were all offline.

 

[nikolascx]

You are welcome. You also narrow down the failure for me.
We will inform them that this problem started between 1-3rd March.
Thank you so much.

 

[kevinfwb]

Just for pure sake of curiosity, I manually upgraded the firmware to 2.4.13 and it provisioned just fine.

 

[nikolascx]

Great news - but ok - still there is a problem.
In the meantime we received a confirmation from Fanvil that they reproduced this internally. So they are aware and are working on it.

I guess we wait for updates. Thank you for your report.

 

[LogicTom]

Just to add, looks like we are having the same issue with a newly purchased X3U, however FW 2.4.13 is not available for this device from the Fanvil website.

 

[nikolascx]

@LogicTom I would get the latest 3CX supported firmware for X3U and upload that manually to the phone.

Version 18

• Fanvil X3U - 2.4.12
• Fanvil X3U Pro - 2.4.7.5

Version 20

• Fanvil X3U - 2.4.12
• Fanvil X3U Pro - 2.4.13.3

What firmware do you see on your device when you power on the device?

 

[LogicTom]

Hi, we're on V18 with X3U non pro, firmware V 2.4.12 downloaded from your FW page.

I was just mentioning that the workaround suggested by Kevinfwb of using a higher fw of 4.13 was not available to us, and also have the same issue on 2.4.12.1 provided by Fanvil directly.

Hopefully Fanvil are able to correct this soon.

 

[nikolascx]

Understood - open a support ticket on Fanvil in the meantime so they are aware of your case.
Thanks so much for your input.

 

[Fanvil Technical Support]

Hi
If you have any questions or feedback about Fanvil IP phones, you can send your feedback to our support email. The email address is: [email protected].