Upgrade from V15.5 to V16--No manual provisioning URL

[jrh_dowco]

I have upgraded from 15.5 to 16 on a new server and restored from backup. Everything works but I don't have the manual provisioning URL. It shows a 404 when trying to go to the URL. The folder does exist in C:\ProgramData\3CX\Instance1\Data\Http\Interface\ but nginx conf doesn't reference it. I am trying to provision remote phones over a site2site vpn tunnel and see the best way is to manually provision them.

Has anyone else run into this and if so would adding a line to the nginx conf work to make that provisioning URL work? I see a reference to "myphone" from that same directory in the nginx config and it resolves. I am thinking this may be a security reason not to include it by default since it exposes the config files over http.

Thanks in advance!

 

[nub]

make the folder?

 

[JohnS_3CX]

Hello

It is indeed correctly showing a 404 error when you try to reach the URL manually - this is normal.

Manual links are formed using your URL+MAC of the device and depending on the device vendor the URL might change

Have you first tried PnP provisioning? If your VPN allows multicast then you should be able to see your phones in the Phones section and simply assign them to your device which is the best preferred method to provision, otherwise you will have to follow our guides to manually provision your phones, selecting the correct guide according to the phone brand and model https://www.3cx.com/support/

 

[jrh_dowco]

Hello John,
Thank you for your reply! That is what I thought based on the guides and forums I have read. It is just confusing on the phone provisioning page of the admin console how it shows that provisioning URL below the provisioning method box.

My site to site VPN does not support multicast so I will attempt to provision using the Remote STUN method. Most of my phones are Snom models that are end of life so I am preparing to do some manual work for a bit until we replace those needed.

Jason

 

[craigreilly]

The URL is to enter into the phones provisioning section.
It will build the remainder of the URL on its own.

 

[cobaltit]

So I guess the million dollar question is... if you are upgrading why are you changing anything? Phones that were registered and working under v15.5 should still be registered and working under v16 without having to touch anything. The URL they already have should still be working.

 

[jrh_dowco]

I can cash that one!

They are working and I didn't change anything, just asked the question to rationalize our support protocol. I had a couple of phones at remote sites of recent employment separations that I was using to test the process in case I need to replace a phone. Being a proactive admin so I know what to expect. It turns out to be pretty manual without the ability to multicast over our IPSec VPN but I can manually set all the settings via the web interface to get them working. The folders and data are all still there from the upgrade, more just concerned about why the admin shows a URL that isn't resolvable.

 

[cobaltit]

Why be proactive when it's so much more fun to be reactive!

As @craigreilly mentioned 3CX is showing you the base URL which is all you should need as far as device provisioning goes. The devices will request the config files by appending something like MAC.cfg or MAC.xml depending on the make/model. You aren't able to browse that location because it doesn't actually existing as a folder on the PBX. Legitimate requests are generated on the fly from the database.

Also, you can do option 66 and put the URL in for your remote sites instead of manually provisioning them.

 

[jrh_dowco]

@cobaltit Option 66...I have that option setup AND I didn't update the URL with port 5000 instead of 80...Dangit!

Updated DHCP and testing again.

Thanks for the nudge. I totally overlooked it!

 

[jrh_dowco]

@cobaltit Update to Option 66 with the correct port in URL fixed it up. I was able to factory reset the phone and have it come back up and reprovision properly! Thank you very much for your suggestion!

Now I can go be pro-reactive on something else! haha

 

[cobaltit]

No problem, glad I could help