Solved 3CX su Priemise Gigaset IP 510N Provisining not found

[Alle CTEC]

https://www.3cx.com/community/threads/3cx-on-priemise-gigaset-ip-510n.128089/

The previous post was marked as solved but provisioning of gigaset 510n dect cells is not working in http.

Trying to download the file via the web and then import it into the cell with a format error? So the cell does not receive it either automatically or via configuration loading - the only solution was to edit the file with example notepad++, look for the parameters and configure them manually

 

[JohnS_3CX]

Hi Alle,

This should work (I have verified it) so long as the PBX and N510 base are on the same LAN.
Once you paste the link like seen below, and reboot the base, it should download the file.

In case you do not have split DNS pointing to the local IP of 3CX, you can also change the link type in the DECT page to use the IP and save. Then open the DECT page again and you should see the IP based link which you can copy and paste into the N510 user interface.

 

[Alle CTEC]

Then it's a V20 so split dns is a prerequisite. ok if I move the provisioning to https and try to download the file from a browser, for example it returns not found, from the provisioning cell it doesn't work. If I use http the provisioning doesn't work but I can download the xml file from the browser and if I try to import it into the dect cell it gives me a format error.

 

[JohnS_3CX]

ok if I move the provisioning to https and try to download the file from a browser, for example it returns not found

There is no option for HTTPS for this model. There's either

a) FQDN, for which we provide http for that specific model (requires SplitDNS pointing to PBX LAN IP).

b) IP, which again provides http only for that model

Now since you can download the file from your browser, this means your PBX works.

if I try to import it into the dect cell it gives me a format error

cool, then this is a likely candidate reason why it is failing, not because it cannot download the file.

Perhaps, you have tried to provision extensions on it that contains unescaped characters, effectively leading to a broken XML.

The specific characters could exist in the extension name, or in the Auth ID and Password (which you could have manually typed back in the V18 days).

So either check your XML to find out what that could be, or create 1 brand new extension (don't copy) using a simple name like TEST, assign only that extension to the device, and then try again.

 

[Alle CTEC]

Sorry, I checked it's not in https, I was typing wrong. the 3cx was updated from V18 to V20, so the problem is this I should reconfigure the cells from 0

 

[JohnS_3CX]

Let us know the outcome please and we can follow up

 

[Alle CTEC]

Hi, so if I export the file and try to load it from error, but if I set the provisioning in ip or fqdn and restart the cell it will resume the updated configuration file.

Thank you

You can mark the post as solved.