Provisioning for FXS/DECT not working

[pbr]

I want to connect a Gigaset N670 IP Pro with my 3cx (Version 18.0 Update 7 (Build 312)). Therefore, I configured the Gigaset in the FXS/DECT section of 3CX.

Now I want to use the provisioning provided by 3cx to get the config in the Gigaset device. But unfortunately I get an error. Gigaset can't read the xml. It says “provisioning failed”.

So I tried to look up what's in the xml of the provisioning link from 3cx and realized that the link does not work. It's no difference if I use the internal link (http://192.168.xx.yy:5000/provisioning/xxxxxxx/yyyyyyyy.xml) or the external link (https://FQDN:5001/provisioning/xxxxxxxx/yyyyyyyyy.xml). I always get the following error message:

This page contains the following errors:
error on line 111 at column 58: xmlParseEntityRef: no name
Below is a rendering of the page up to the first error.

Has anybody a guess what's wrong there?

 

[SweetAction]

Right click the link, do "save link as" and save the XML file (without viewing in the browser).
Then edit the XML with your tool of choice (Notepad++ for me)

 

[JohnS_3CX]

Hi,

Check the name of your extensions please and remove any characters that may be part of XML formatting.

You may have inadvertently broken the XML structure, but fixing the name of the extension by removing any special characters should take care of it.

 

[pbr]

@JohnS_3CX Thanks, that was the solution. I had "&" and "." in some extensions. Without the provisioning works now. But why are these characters a problem, when 3CX accepts them for names?

 

[JohnS_3CX]

Hi,

3CX allows you to include anything you want in the names because we don't have a limitation (even though some devices do). It's no issue at all on the apps and web client as well as a number of other devices (Yealink, Grandstream, Snom, Htek) so no reason really to disallow it

Some devices however cannot handle special characters, they have a firmware limitation (ie. Fanvil) so we have this listed in the Known Limitations in our guides. I just noticed now that the Gigaset guide does not include this note so we will make sure to update it soon to reflect this. Thanks for bringing that to my attention.