Problem with provision after update

Status
Not open for further replies.

zkaesberg

New Member
Sep 8, 2018
3
0
1
46
At some point in the past I had grandstream provisioning working with no problems. After the last update that I did on Sunday Sept 23rd provision is no longer working.
I have provision enabled in the default settings.
I have the correct path in the config server path on the phone. ie domain.com/app/provision.
I have the phone and MAC in the devices list.
When I click on the "provision" button on the phone the status in the device list changes to the current date and time.
If I go to Devices->Device->Files->Download it shows the Mac.xml file in the list, I can download it and it has the correct data.
The only weird thing that I can see is in the NGINX log when a provision takes place I get the following in the error log.

2018/09/25 05:35:23 [error] 621#0: *1836 open() "/var/www/fusionpbx/app/provision/cfggxp2160.xml" failed (2: No such file or directory), client: 104.3.142.209, server: fusionpbx, request: "GET /app/provision/cfggxp2160.xml HTTP/1.1", ho$
2018/09/25 05:35:23 [error] 621#0: *1837 open() "/var/www/fusionpbx/app/provision/cfg.xml" failed (2: No such file or directory), client: 104.3.142.209, server: fusionpbx, request: "GET /app/provision/cfg.xml HTTP/1.1", host: "tkla*.vm****

Any help with this would be great. Please let me know if more information is needed.
 

Kenny Riley

Active Member
Nov 1, 2017
243
39
28
36
What happens when you browse to your config file over the web? Do you reach a valid XML config file?

domain.com/app/provision/YOURMACADDRESSHERE.cfg
 

zkaesberg

New Member
Sep 8, 2018
3
0
1
46
After actually looking at the file closer... it is not a valid xml file. It contains all of the information for the provision in it but it is NOT in xml format. Any ideas on what would cause this?
 

brb5548

Member
Sep 26, 2018
53
9
8
46
Just now reading your post (after posting about a similar issue). I can't get the grandstream gxp2160 to provision either. I can confirm the <mac>.xml file is valid xml but the phones/nginix can't find the cfggxp2160.xml or cfg.xml files.
Did you ever make any progress on this issue?
 
Status
Not open for further replies.