Relocation of site from London to Leicester on VM

[Manish Dave]

Hi
My client is relocating the 3CX with is currently based in London to Leicester. This is first time I doing a relocation and wondering if anyone can give me and idea of IP addressing. As far as I know is that the internal IP where they are registering should remain the same to minimise changes to phones. Or register the phones to FQDN. Any ideas would helpful.
Thanks in advance

 

[ChrisC_3CX]

As far as I know is that the internal IP where they are registering should remain the same to minimise changes to phones.

That actually depends. If you don't have local IP Phones or anything else that uses the local IP of the PBX then there's really no reason to keep the same local IP.

If you do have local IP phones though, keeping the same local IP means you don't have to reprovision them as they will already be able to reach the PBX when they come online.

As far as remote devices are concerned they need to have the FQDN resolve to the correct IP. This will automatically happen if you're using a 3CX FQDN since we are the ones managing the DNS records. Once you deploy the new machine, the DNS record should be updated with the new IP. Do bear in mind that STD and PRO licenses have a DNS TTL of 6 hours and the ENT license has a DNS TTL of 5 minutes.

There may be more things you can do to make sure you have a smooth migration but that depends on the situation. You might want to consider the following:

• What exact 3CX version are you currently running? Is it the latest one already or will you need to upgrade?
• What 3CX endpoints are you using (IP Phones, 3CX Apps, 3CX Webclients, etc)? Will you need to factory reset and reprovision?
• Are all users remote or on the same LAN or both?
• Are you using a 3CX FQDN?
• How will you be migrating, are you going to deploy a new machine and restore a backup, what OS?
• What SIP Provider are you using, will they need to know your new Public IP?

 

[Manish Dave]

Some users are connected to 3CX locally and others remote sites are thru VPN pointing to 192.168.20.225 directly. Will need to change all to FQDN. And others are 3CX windows, Web clients & Phone App will need to be resend welcome details.

 

[ChrisC_3CX]

If they are all using 3CX apps it means they all already also have the FQDN and the HTTPS port meaning they will be able to reconnect when they lose the local/VPN connection so no need to worry. Just make sure that you use the exact same FQDN and HTTPS port for the new PBX.