Hello, Human!

This is unexpected!

You're a human! Only other robots (like curl, or wget) are expected to come and visit here.

Are you looking for instructions on how to Come Home 2 FreePBX? It's easy!

Create a new FreePBX Distro machine

You need a NEW machine. This is the machine that your DONOR machine will be converted to. Download the latest SNG7 ISO from The FreePBX Distro Download page. You can use the 'Legacy' images, but they're not recommended. SNG7 is the best way to go.

After you have downloaded and installed it, make sure it is Activated. Activation creates a secure cryptographic key that is used to encrypt data between the old and new machine, and for validation while it's in transit. Activation is, of course, free, and just requires a couple of extra clicks.

Now you've created your NEW machine, you need to reserve a slot in the conversion service.

On the NEW machine run the command curl -s https://convert.freepbx.org | bash to attempt to reserve a slot. It will look like this!

[root@freepbx ~]# curl -s https://convert.freepbx.org | bash
Checking that 'curl' exists ... OK!
Validating sha256 integrity ... OK!
Trying to download converter to /tmp/tmp.AKctIWjXSd ... Complete
Validating download ... OK!
Testing connectivity to Conversion server...Success!

FreePBX Conversion Wizard
-------------------------

The FreePBX Conversion Wizard needs to be run on two machines, the NEW
machine, which must be an ACTIVATED FreePBX Distro machine, and then it must
be run on the DONOR machine.
The DONOR machine is the machine that is currently processing calls, and is
the machine that will be migrated to the NEW machine. No changes will be made
to the DONOR machine, and this script will not stop or restart any services
that may cause an outage.
If this is the NEW machine, just push 'Enter' to prepare this machine

Enter ID (blank if this is NEW):        (Just push 'enter' here)
Testing FreePBX functionality ... Success!
Getting Deployment ... 12345678
Getting all Module versions (for conversion) ... OK
Reserving a conversion slot ... Reserved!

The Conversion process is now ready. Please run the script on the
DONOR node now, and when asked for a slot identifier, please enter
the following ID:

	12345789-abcd-4ef0-1234-56789abcdef0

[-] Waiting for Donor...
			

Now you need to do the same thing on the old machine!

Convert the old machine

Now you have reserved a conversion slot, you can paste the slot identifier into the DONOR machine, like this

[root@elastix25 ~]# curl -s https://convert.freepbx.org | bash
Checking that 'curl' exists ... OK!
Validating sha256 integrity ... OK!
Trying to download converter to /tmp/tmp.lmSjx27299 ... Complete
Validating download ... OK!
Testing connectivity to Conversion server...Success!

FreePBX Conversion Wizard
-------------------------

The FreePBX Conversion Wizard needs to be run on two machines, the NEW
machine, which must be an ACTIVATED FreePBX Distro machine, and then it must
be run on the DONOR machine.
The DONOR machine is the machine that is currently processing calls, and is
the machine that will be migrated to the NEW machine. No changes will be made
to the DONOR machine, and this script will not stop or restart any services
that may cause an outage.
If this is the NEW machine, just push 'Enter' to prepare this machine

Enter ID (blank if this is NEW): 12345789-abcd-4ef0-1234-56789abcdef0
Testing FreePBX functionality ... Success!
Checking Slot ID ... OK!
Getting modules to convert ... Complete! 109 modules
Dumping astdb ... Complete!
Creating encrypted backup for new machine ... Complete!
Sending encryption key and backup details to new machine ... Complete!
        Module announcement (Skipped 1, Completed 0) ... announcement
        Module callback (Skipped 13, Completed 1) ... callback
        Module callrecording (Skipped 16, Completed 2) ... callrecording callrecording_module
        Module cidlookup (Skipped 21, Completed 3) ... cidlookup cidlookup_incoming
        Module conferences (Skipped 21, Completed 4) ... meetme
        Module core (Skipped 24, Completed 5) ... sip dahdi featurecodes incoming trunks users devices dahdichandids globals language_incoming languages outbound_route_patterns outbound_route_sequence outbound_route_trunks outbound_routes outroutemsg trunk_dialpatterns trunks
        Module customappsreg (Skipped 25, Completed 6) ... custom_destinations custom_extensions
        Module daynight (Skipped 28, Completed 7) ... daynight
			

That will continue, exporting and converting all the configuration of your existing machine. When it is finished, the NEW machine will attempt to download the (encrypted) backup automatically. If the NEW machine can not reach the DONOR machine, you will need to copy the backup manually (from /var/www/html/conversion_backup.crypt on the DONOR machine, to /tmp/conversion_backup.crypt on the NEW machine. The encryption key is not recoverable, so if you exit the script on the NEW machine, you will have to restart.