Provisioning Issue when local IP is changed - New Debian install from ISO with configuration restoration

[interactive7]

This is to highlight an issue I observed, twice, when moving from Windows to Debian VM.

1. A full backup was taken from Windows.(xxx.xxx.xxx.100) (Provisioning URL uses the IP)
2. Old Windows VM is retired. (offline)
3. 3CX installed from Debian ISO on a new VM
   1. During the install process, the VM is assigned an IP via DHCP. (xxx.xxx.xxx.123)
4. Previous configuration is restored
5. Static local IP is assigned that matches the old static IP from the Windows VM (xxx.xxx.xxx.100) (This is needed so my phones reach the new install)
6. Reboot new VM

Provisioning is set to use local in-office interface.
At this point, 3CX provisioning URLs show the initial (invalid) IP (xxx.xxx.xxx.123) and not the expected (xxx.xxx.xxx.100)
So while the PBX is running on xxx.xxx.xxx.100 and this is the selected interface in 3CX, the provisioning URLs show something different and any phone provisioned at this time will have the xxx.xxx.xxx.123 as the PBX address, which is invalid.

If a phone is a rebooted at this point it is provisioned with the invalid IP (xxx.xxx.xxx.123) and will not connect.
I have to login to the phone UI and change back to the correct IP (xxx.xxx.xxx.100)

I also now have to go through each extension "Phone Provisioning" tab and Delete, then Add a new phone configuration so the provisioning URL shows the correct IP (xxx.xxx.xxx.100)

With many extensions, this is not feasible.

 

[Saqqara]

Give the Debian install the same ip address of the old windows machine Step 2.4 https://www.3cx.com/docs/manual/installing-debian-linux-pbx/