Migration of RaspberryPI PBX to Intel/Debian PBX - how to retain the PBX name?

[k.lee]

Hi,

My RaspberryPI PBX EOL'ed today and it's no longer contactable by 3CX clients from external network. There's a red circle beside the instance in the portal. However, it still works internally on wifi.

I'm preparing to set up a new Intel/Debian PBX. Was exploring the Startup FREE version but it doesn't suit my setup as I'm using non supported trunks and the current implementation only has a list of drop down SIP providers.

I've registered a new license for the Intel/Debian PBX with a new PBX name. Once I get it all configured correctly, is there a way for me rename it to the old name so that the clients doesn't need to be reconfigured? I'm thinking like in server hw migrations, once all is setup and tested, we just make the hostname change in the DNS and all the clients point to the new server.

thx
kenneth

 

[SteveITS]

You can back up the existing server including the license and FQDN, and restore on the new server during installation.
https://www.3cx.com/docs/manual/pbx-backup-restore-failover/

If you're trying to release and re-use the same FQDN there's no guarantee you'd get it again.
https://www.3cx.com/docs/fqdn-management-allocation/#h.rd7e4vvzupdu

 

[k.lee]

My current license is a "raspberrypi" license which is no longer supported. Hopefully when I do a configuration restore from the raspberry instance into the intel instance, it would go smoothly.

when u mention "release" FQDN, i don't see any release option in the portal. Only a delete license option.
do u mean delete the old license and reapply a new license with the old name?

btw thx for pointing out license / fqdn backup. i just made a backup without them just in case i need to use a new pbx name and license.

 

[SteveITS]

There is no such thing as licenses for different types of hardware. IOW the license is portable.

I’m not advising releasing your FQDN but the above links should give you info on it. I’ve never done that so don’t know details off the top of my head. I’d consider “release”=“give up on.”

 

[k.lee]

>There is no such thing as licenses for different types of hardware. IOW the license is portable.
oh, in that case that will make hw migration so much easier. when I set up the new intel/debian hw, i'll try the old licence and pbx name. if it works, it's just a matter of restoring config from the backup.

will try it out in the next few days and report here.

thx!

 

[SweetAction]

If you take a full backup on the old box, including license/fqdn, then when you restore onto the new box the first step - point it to the backup file - and it will pick everything back up.

It's simpler then it sounds. It take less than 15 minutes.

 

[k.lee]

Happy to report that I've successfully migrated my RaspberryPI instance to debian instance in an intel PC.
Here are the steps that I took:

3CX migrating from RaspberryPi to Intel/Debian

Do a full backup of RaspberryPI (RPI) using the 3CX backup option.
Download the 3CX configuration into a USB stick.

Go to 3CX portal.
Request a new instance.
Get link to download debian ISO image.
Delete instance in portal (we just need the link to the ISO image).

Go to balenaEtcher portal download etcher
https://www.balena.io/etcher/

Get a 4GB USB stick.
Use etcher to copy debian ISO image to USB stick.

Setup BIOS in new PC (mine's a ThinkCentre M92p I3 8GBram 256GBssd)
- for PC to start up when powered is supplied.
- boot up via USB stick

Insert USB stick and connect PC to network
apply power to PC
Select Install, go through the installation steps
Upload the 3CX configuration.
Check that the extensions, trunks, inbound/outbound rules are there.

Set IP of new server to RPI in router/LAN/DHCP.
Set IP of RPI to something else in router/LAN/DHCP.
Reboot old server.
Reboot new server.
Reboot router.

Run firewall check - had multiple failures.
In the Settings/ Network / Dynamic Public IP (enable).
Run firewall check - no more failures.
Once ok, set back to static.
Run firewall check. - no more failures.

Setup the backup location path in new server as it is not restored.
Stop the backup in old server.
Test the backup.

Test the 3CX phones in mobile phones etc.

The hostname was retained. All clients, internal and external, are able to access the PBX using their existing credentials and the migration was quite transparent to them. The only downtime was during the equipment reboots.

Thx everyone for your advice.