Provisioning link has changed!

[GBC_James]

Hello all,
3Cx v16.0.8.9 on a Windows Server 2019 Standard box on prem (well actually in a data centre 5 miles away)

We started getting random handset problems today, yealink T42G's, saying "no service".
I took one, reset it, and tried to reprovision, but it failed. I tried again and noticed that under the Phone provisioning tab, the provisioning link has changed.
It was https://ourFQDN/provisioning/provisiong folder but now it shows the ip address of one of our nic's the external web facing one (we have 2, one for our internal network and one web facing)

We have know idea how or why this has changed, but I am guessing that is the problem.
Our internal handsets all sit on our private 172.26.*..*
Our internal nic also sees the 172.26.*.* network
the external nic has a 5.2.*.* ip

Can anyone help please?

Many thanks

James

 

[GBC_James]

Hang on, I can see that if i change the interface i can select our fqdn but i then have to change the provisioning method to either SBC or Stun, and then back to local Lan, and then it resolves the provisioning link back to the fqdn.

Odd. Why might this have changed?

 

[JohnS_3CX]

Hi James,

This depends mainly on the networking setup. In this case, I imagine you have a segregated network with:

- An internet facing side (no phones attached here) NIC1
- A private facing side (phones attached on this subnet) NIC2

1. Make sure that NIC2 172.26.x.x does NOT have a gateway assigned (see Segregated network here)
2. Make sure in the PBX >> Settings >> Network >> "Select Network Card Interface" has the external NIC1 selected
3. Make sure you edit each and every phone under your extensions, and select the correct interface (172.26.x.x) - the value will be changed after pressing OK to save
4. Now reset and reprovision your phones to be 100% certain that their config is clean and they did not retain any wrong settings.

If your network is setup otherwise, please read the link I mentioned above to understand which network configurations 3CX supports.

 

[GBC_James]

Thanks for the help JohnS

 

[JohnS_3CX]

You're welcome, let us know how it goes!