Good day,
I've seen a few posts relating to this and suggesting what to have done beforehand but did not see an instant solution. I'm posting this for future searches if anyone finds themselves in the same scenario.
If you migrate a 3CX installation to a new machine or OS and/or for any reason have to change the local IP address of the 3CX after an initial installation, be advised that the individual extensions' LAN provisioning links will not be updated automatically. Albeit a hassle to individually address them, it's faster than a reinstall. Just flip the provisioning method briefly to SBC or STUN then back to LAN and the URL will update to the appropriate URL. The next time the phones phone home, they will receive the correct URL. You’ll have to remedy any that already received the incorrect address.
I've seen a few posts relating to this and suggesting what to have done beforehand but did not see an instant solution. I'm posting this for future searches if anyone finds themselves in the same scenario.
If you migrate a 3CX installation to a new machine or OS and/or for any reason have to change the local IP address of the 3CX after an initial installation, be advised that the individual extensions' LAN provisioning links will not be updated automatically. Albeit a hassle to individually address them, it's faster than a reinstall. Just flip the provisioning method briefly to SBC or STUN then back to LAN and the URL will update to the appropriate URL. The next time the phones phone home, they will receive the correct URL. You’ll have to remedy any that already received the incorrect address.
