I’m planning to switch from Trixbox 2.8.0.4 to FreePBX since Trixbox is a dead project.
There’s a slight problem and that is that I do NOT want to start from scratch as the Trixbox is really being used on a large scale. (lots of extensions, ringgroups, timegroups, IVR, etc etc…)
Is it possible to migrate from Trixbox to FreePBX without it being too much of a problem?
as per the other thread backups and restores between different versions don’t really work. However at least for extensions and inbound routes you could look at creating CSV files of the existing setup so that you could import these into FreePBX using the bulk import utility provided under the tools menu. For other things I’m afraid that it down to doing it by hand. The problem is that database formats (and other things) change between versions so your existing MySQL database that contains all of your Trixbox setup may not be compatible with the database formats for the latest FreePBX releases.
I agree having done it myself. I tried to find a way to migrate but in the end I decided the quickest and easiest thing to do was to start from scratch.
I had to use the same server as the trixbox was on so I put the latest version of fpbx distro on an old laptop and built the system there.
Once built I backed up using the backup module, took down the trixbox and loaded the free pbx distro on it and restored the backup from the laptop. I had a few small issues which were simple to sort out and I was back on line in less than an hour.
Since then I have not looked back, it was well worth the effort.
Just download freepbx 2.9 and run the following:
./install_amp --force-version=2.5.0
Say yes if it asks to overwrite any standard files
then edit the trixbox conf file in /etc/httpd/conf
change the AuthMySQLPasswordField to : password_sha1
and change the AuthMySQLPwEncryption : SHA1
save & restart httpd and you should be up and running.
Ive done several TB installations now and this works every time for me.
you can also remove all the tbm_ rpms if you like, but I usually keep them in place for most installations - everything such as the endpoint, cdrs etc will still work!
As PHP I have never used the force version command like that. Good tip.
Problematic though as it leaves you with the hacked up Asterisk, old CentOS and just one accidental yum update away from disaster. You update one module dependent on PBX Config and all the TBM stuff fill overwrite the FreePBX since it was not done with a package manager.
You are also tuck at 2.9 FreePBX unless you manually build Asterisk.
Going to 2.10 will be rough as PHP need an upgrade.
Worked perfectly. it throws all kinds of errors, and tells you to connect to the web interface when you shouldn’t, but if you just let it run, when it says “NOT REBOOT”, and drops to a shell prompt, if you reboot you have a fully functional FreePBX, minus FOP (so ignore any errors related to it, or install fop2), with all your extensions, voice mail, etc. intact.