Solved Grandstream HT801 missing xml file

Status
Not open for further replies.

Enoch

Customer
Joined
Mar 5, 2015
Messages
42
Reaction score
2
Hi Community,

3CX Version: 15.5.20000.6

I have been trying to getting our Grandstream HT801 as a fax line out. Have been following the direction here:

https://www.3cx.com/voip-gateways/grandstream-ht-fxs/

All is good until we get to Step 7: Upload the configuration to the gateway. The Provisioning Link does not work because the cfgXXXXXXXXXXXX.xml does not exist on the server.

Any one have any ideas has to why my 3CX is not creating the necessary xml/config files?
 
When you are working on Step 7 have you right clicked the provisioning link and chose save as.

That downloads the XML file to your computer from the PBX.
 
When you are working on Step 7 have you right clicked the provisioning link and chose save as.

That downloads the XML file to your computer from the PBX.
Yes, I know that... Like I said, the file does not exist on the server side...
 
The first thing you need to do is to upgrade to the latest 3CX version. Once you do try again and let us know if that works.
Also you need to Press OK on the top of the page to save the configuration and then go back into the device configuration and press the link again.
 
  • Like
Reactions: JohnS_3CX
The first thing you need to do is to upgrade to the latest 3CX version. Once you do try again and let us know if that works.
Also you need to Press OK on the top of the page to save the configuration and then go back into the device configuration and press the link again.
Working on the upgrade... Its bigger than expected from previous versions as it says it requires Windows Server 2016. But if 3CX V16 can run on Windows Server 2012 R2 we could do the update right away.

Thanks for the remind about pressing OK, but I'm not that noob when it comes to 3CX. Any other suggestions to where the problem may be?

Just to confirm I am working with the correct directory right?

C:\ProgramData\3CX\Instance1\Data\Http\Interface\provisioning\xxxxxxxxxx
 
Hi Enoch,

3CX generates the provisioning files automatically when requested by the device, they are not statically stored in a folder. What you will find in the folders are templates, but those are not provisioning files.

Important note: The jump from 3CX V15.x to V16.x on Windows requires that you take a full backup of your 3CX and store the backup safely in a different folder, then uninstall the old version and install the new version of 3CX. You can restore your backup during the installation of V16.

If you cannot upgrade the Windows OS immediately (to be compatible with V16), you also have the option of using a VM on your existing server, and deploying our Debian ISO.

Let us know if you prefer this method and we can guide you.
 
Hi Enoch,

3CX generates the provisioning files automatically when requested by the device, they are not statically stored in a folder. What you will find in the folders are templates, but those are not provisioning files.

Important note: The jump from 3CX V15.x to V16.x on Windows requires that you take a full backup of your 3CX and store the backup safely in a different folder, then uninstall the old version and install the new version of 3CX. You can restore your backup during the installation of V16.

If you cannot upgrade the Windows OS immediately (to be compatible with V16), you also have the option of using a VM on your existing server, and deploying our Debian ISO.

Let us know if you prefer this method and we can guide you.
I've tested this again. Right-clicked on the link and Save link as and after confirming the save location and filename, Chrome reports "Failed - No file" so it seems our 3CX is not automatically generating these files on request.

Any settings to check within 3CX or on the Windows host?

Re: Upgrade - Since we are using our 3CX for a call centre and cannot be down for long periods of time, it is possible to have grace period where we can have some time to build up a new Windows 2016 server with 3CX installed and tested with the same license so we can ensure functionality all works before going live?
 
I think I know what might be happening. Are you logging in to the management console using Chrome, via your FQDN?

ie. https://mypbx.3cx.com:5001/
 
just to be clear, my computer has access to both networks.
 
Ah ok, the thing is V15 was released a while ago before browsers became more strict, and since then Chrome has introduced a security measure where it will not open plain HTTP links from within HTTPS sites as this is no longer considered secure in 2021.

This is now blocking you from downloading the config file since the link is plain HTTP.

Try logging into the management console from http://10.0.1.1:5000/ and then it should allow you to download the file just fine.
 
Status
Not open for further replies.

Latest Posts

Forum statistics

Threads
112,324
Messages
591,897
Members
165,475
Latest member
lastshadow