Desktop Client - PBX internal IP change

[VH IT]

I am going to be moving our pbx to a different machine with a different local/internal IP. I have noticed in the account config of our windows client machines that there is a location "in office" local ip and an "out of office" pointing to the fqdn.

Just wondering how this will work. If these clients can't reach by in office internal ip because I moved the pbx and that ip address no longer works, will the client try out of office and connect?

Thats my hope/theory, which would be good because I have extensions set to reprovision on startup, so then the new internal IP would get pushed to them. Is this the case or am I going to have to push out new configs to every user once I move the pbx?

 

[SweetAction]

Your best bet is to setup SplitDNS and then just use the FQDN. For devices in network, resolve the DNS to the internal IP and for devices out of network resolve the DNS to the external IP.

You can then update all extensions to use FQDN for 3CX Apps and not IP in just a few clicks...
3CX MC -> Users -> Checkbox for all users -> Edit
Phone Provisioning tab

Click the network dropdown, select the FQDN listed there, and save (Ok button at the top)

Then the 3CX client just needs to be restarted (exit / open) and it will get the new setting.

For IP Phones using IP, you will need to edit each extension and make the same change, then "reprovision" button on the phone tab or reboot the phone or wait 24 hours.

 

[VH IT]

Awesome. Thank you! I see that now. I always saw that and saw the fqdn and internal ip as options but didn't think of it right. I already am splitting dns, so I will just have to update the extensions to point to fqdn as well.

 

[SteveITS]

Same, but here's the 3CX doc on split DNS: https://www.3cx.com/docs/creating-fqdn-split-dns/. Note it says "must," and per other posts here split DNS will at some point be required.