Solved Fanvil X210 / X6U Provisioning Issues

[Chad Cyr]

3CX Version 16.0.9

On Premise 3CX Server (Windows 10 Pro X64)

Provisioning Method: Local

No Custom Phone Templates

Firewall Checker Passes

Phone Makes/Models:
(5) Fanvil X210 v2.2.13
(14) Fanvil X6U v2.2.13 / v2.2.11 / v2.05
(50) Fanvil X3SP v2.12.1.7297
(1) Fanvil i18s v2.6.0.6682
(1) Yealink CP920 v78.85.05


Initially thought the issue was limited to the Fanvil X210 phones on FW 2.2.13 as I was attempted to assign additional BLF keys per the end user’s request and could not re-provision the X210 phones though 3CX. Further troubleshooting has me scratching my head and starting a new thread.

Upon initial installation of 3CX for the customer, we pre-provisioned and pre-registered all the phones to the 3CX without issue a few weeks back. As the phones were installed in their permanent locations, they also registered fine. I also initially added and provisioned BLF keys for the main office X210 phones for line keys, shared parking, public address and their door video phone.

This week, I was asked to populate the rest of the X210’s built-in sidecars but the phones seemingly will not provision the changes I have made in 3CX for each extension. Searching the 3CX forums I found a post regarding Fanvil FW 2.2.13 and BLF issues and assumed this was the culprit.

However, I had managed to downgrade firmware on two of the X210s to 2.2.11 and 2.2.05 and I still could not get them to re-provision. I also tried factory defaulting one of the X210s and I could not get it to provision back to its assigned extension; I even deleted the phone from the system and tried to provision it to a different extension without success. For sanity’s sake, I had my tech bring one of the X210s w/ FW 2.2.13 to our office and I was able to provision the phone to my own extension on our 3CX system without issue. The difference without our office 3CX server is that it was using an older version template 109356 versus the 109359 of the customer’s server. I replaced their newer template with ours and still no change.

This morning I tried the following tasks and yielded the corresponding results:

• Provisioned a new X3SP spare phone to replace a defective X6U without issue. Was also able to update the firmware from the 3CX GUI.
• Factory defaulted the Yealink CP920 and re-provisioned/re-registered it via 3CX GUI without issue.
• Factory defaulted both an X210 and X6U but could not re-provision/re-register them via 3CX GUI. I restored both with a backup of their configs I made before I defaulted them. After they registered, I added some BLFs on those phones but I could not provision the changes.

I’m not sure what to try next. Does anyone not recommend I reinstall from scratch and restore a backup?

Thanks,
Chad

 

[JohnS_3CX]

Hi Chad,

I can propose the following test to see whether the X210's config file is valid:

1. Edit an extension with an X210, go to the Phone provisioning tab

2. Copy the provisioning link as you see it there, plus the MAC and construct the whole link which will look something like this:

http://192.168.1.100:5000/provisioning/akjrbvfug4i8/00ABCDE123456789.cfg

4. At the customer's premises, factory reset the X210, and connect your laptop to to its "PC" ethernet port, so you can get passthrough internet via the phone and you should also get an IP from the same network as the phone would.

5. From your laptop, ensure your internet works and now paste the entire link we constructed

If the file 00ABCDE123456789.cfg gets downloaded to your laptop then the phone should also be able to provision itself. If not then it's not the phone's fault and we have to look elsewhere

As you probably understood from the above, the goal is to simulate whether the phone can reach the PBX and download its provisioning file. You should then open the provisioning file and ensure it is not corrupted, compare it with a similar file you got from your own extension at your office.

I suspect you will find a problem here (since at your office the phone behaved just fine)

 

[N0NAME]

This may be completely unrelated, I had an issue with a Fanvil phone that would not reprovision, I factory defaulted the phone and it still wouldn't provision. Turns out the user (who has access to manage her own extension) added a BLF speed dial and had an ampersand (&) in the name.

It is listed in the 3CX Known Limitations section for Fanvil

• Do not use special characters in Extension names or BLF labels.

 

[Chad Cyr]

Hi Chad,

I can propose the following test to see whether the X210's config file is valid:

1. Edit an extension with an X210, go to the Phone provisioning tab

2. Copy the provisioning link as you see it there, plus the MAC and construct the whole link which will look something like this:

http://192.168.1.100:5000/provisioning/akjrbvfug4i8/00ABCDE123456789.cfg

4. At the customer's premises, factory reset the X210, and connect your laptop to to its "PC" ethernet port, so you can get passthrough internet via the phone and you should also get an IP from the same network as the phone would.

5. From your laptop, ensure your internet works and now paste the entire link we constructed

If the file 00ABCDE123456789.cfg gets downloaded to your laptop then the phone should also be able to provision itself. If not then it's not the phone's fault and we have to look elsewhere

As you probably understood from the above, the goal is to simulate whether the phone can reach the PBX and download its provisioning file. You should then open the provisioning file and ensure it is not corrupted, compare it with a similar file you got from your own extension at your office.

I suspect you will find a problem here (since at your office the phone behaved just fine)

Hi John,

We were able to download the provisioning file. The next reply regarding special characters is what corrected our issue. Thank you for your assistance!

Cheers,
Chad

 

[Chad Cyr]

This may be completely unrelated, I had an issue with a Fanvil phone that would not reprovision, I factory defaulted the phone and it still wouldn't provision. Turns out the user (who has access to manage her own extension) added a BLF speed dial and had an ampersand (&) in the name.

It is listed in the 3CX Known Limitations section for Fanvil

• Do not use special characters in Extension names or BLF labels.

This was totally related and was exactly the issue! The extension list the customer provided was full of special characters. I edited all the extension names and defaulted a few of the X210s; I was able to provision all the phones and populate and modify the BLF keys without issue. This is something new to me as I have used Yealink phones exclusively until just recently and this is first large deployment of them. I wasn't aware of the limitation. I can't thank you enough!

Cheers,
Chad