Domain Migration

[Guzz]

Hey all

I inherited a 3cx system. Currently installed on Windows 10. We are in the process of migrating all systems to a new network and domain. I'm curious for any "Gotchas" when we migrate the machine to the new network/domain.

I understand that port 5000 communication is required.

Should I simply be able to change the IP Settings and Domain settings?

Thanks

 

[cobaltit]

If by domain you mean Windows Domain 3CX doesn't know or care about it. As far as what you need to do, that depends on what version of 3CX you are running. Older versions didn't play nice when changing IP addresses. Newer versions are better but personally I'd just do a backup and uninstall, do your thing with the machine and then reinstall/restore. Hopefully you have a plan for getting the phones to find it again.

 

[JohnS_3CX]

Hi,

The main issue would be with the port forwards that will likely break when moving to a new network, and with local phones that will no longer find the IP of the PBX and will need to be reprovisioned.

 

[Guzz]

Thanks ALL.
Current Version

Product	Enterprise Perpetual
Version Number	16.0.619

I basically have two networks between two firewalls. Communication has been setup between each firewall. We have already moved the phones to the new network.

My thoughts.
Backup current server. Create a new server on the new network. Restore from backup. Change the Network Interface to the new network. The new system should see the existing phones with their existing IP's. Keep SIP and Tunnel ports the same.

I know I'm missing something.

 

[cobaltit]

If it's a new physical network but the same IP/subnet then it really is that simple. If it's a new IP/subnet (for 3CX) then the phones need to know how to find 3CX. The easiest thing to do in that point would most likely be DHCP Option 66.

 

[Guzz]

It is a new physical network and new subnet. The phones have already been moved to the new network, so when the server is moved to the new network, they should be able to find the server. Right now they are communicating between the two firewalls.

Thanks again, keep poking holes in my plan. .

 

[cobaltit]

So I'm not sure if the phones are using DNS or IP to find the PBX but either way, things will break. I will assume they are looking for the PBX by IP and because you have a S2S between the networks the are still working. When you move the PBX to a new IP, this will stop working. If they are using DNS then it would just be a matter of updating DNS to point to the new IP. If they are using the IP then you have some work to do.

 

[JohnS_3CX]

You might be able to get away with it, or you might need to use Option 66 as @cobaltit mentioned.

If the phones got provisioned with say 192.168.1.100 as their PBX, and the IP of the new PBX will be anything other than that, then they will stop registering.

If they were provisioned with a local FQDN and that resolves to the new IP, then they should be fine.

Same goes with public FQDN, so long as you have it resolving to the right LAN IP

Worst case, you will have to reset and re-provision all phones