Solved Auto Provisioning on Local Lan not Working

[Dave3CX]

Hi.

I have an issue with our 3CX, manged by someone outside but they cannot fix the issue.

Our system is on its own network separate from the data network, when I try to auto provision an extension it won’t do anything, it just sits there looking stupid. I have to change it to “Stun”, reset the phone, it will then provision, but it will not do it on the local lan.

The url for stun is https://fqdn:5001/*

The url for Local lan is Http://192.168.*.*:5000/*

Using an Internet browser I can get to a cfg file on the https:5001 but I cannot on http:5000.

I have checked the Nginx file and it looks ok, any help would be appreciated.



Thanks,

Dave

 

[Saqqara]

What do you mean by 'auto provision' ?. If you reset the phone, does it appear within the 3CX management console, and then you try to add to an extension.

Is the 3CX server on the same network as the phones ?

When you say ' checked the Nginx file' have you made any manual changes.

 

[Dave3CX]

Hi.
Thanks for the quick reply.
If I reset the phone it wont appear in the console if the provisioning is set to "Local Lan", the phones are on the the same network as the server, all internal, no hosting involved.
Regarding the Nginx, like all problems I started with Google, one mentioned that the IP addresses in the Nginx file could be incorrect,

Dave

 

[Saqqara]

The 3CX installation will take care of all the nginx requirements , you do not have to manually change any settings. The only change is if you are using your own fqdn and ssl certificate.

As a change has broken something somewhere - probably best to backup your existing system and reinstall from scratch using the backup

As you running on Windows or Debian OS

 

[Dave3CX]

Hi.
I haven't changed anything in any files, my knowledge level is not good enough for me to have the confidence to do this without guidance.
The system is exactly as installed by the provider.

Dave

 

[JohnS_3CX]

Hi Dave,

This is clearly a networking issue. You can fix it, or your can work around it.

The way it works is that phones announce their presence on a multicast channel so the PBX can see them and allow you to auto-provision them. As I understand, your PBX is isolated on another network, making this communication impossible.

So, you can either change the network to address this, or you can resort to using DHCP option 66
https://www.3cx.com/sip-phones/dhcp-option-66/

Ideally, the person installing the system would have to advise you of this or provide you with a solution, but I cannot comment on this part because I don't know what the original requirements were or if there were some restrictions that could not be avoided.

 

[Dave3CX]

Hi @JohnS_3CX
Thanks for the reply. Our PBX is on the same network as the phones, just isolated from our data network.

Dave

 

[JohnS_3CX]

Hi Dave,

Ok in this case, you will have to sort out multicast.
Check that the PBX machine is listening first as this is the first thing that can go wrong:
https://www.3cx.com/docs/plug-and-play-ip-phone/

Then check that your network equipment allows multicast traffic to pass through. I cannot help you with this part though, you will have to look it up.

 

[Dave3CX]

Just an Update:
After following the thread that @JohnS_3CX sent, checking showed that the sip.mcast.net service wasn't running, this then lead me to another thread from Workspace: , this worked.
Thanks to all for helping and it is a bit annoying that I had to do this and not my provider. May need to ask for a reduction in support costs.

Dave

 

[JohnS_3CX]

Glad to hear it was sorted Dave!