Upgrading your system

Upgrading FreePBX
Note: These directions are for source based installs, we recommend using Module Admin to upgrade your FreePBX GUI whenever possible. You may need to install subversion for your linux distribution if you have any errors. Do this by typing yum -y install subversion at the root prompt.

Upgrading to the latest Release Candidate: 2.11.0rc1
You will want to pull the release tarball, and follow the instructions below. Once you have installed it you will want to navigate to Module Admin menu item and update all modules as well as install other available modules not included in the release tarball.

cd /usr/src/
wget http://mirror.freepbx.org/freepbx-2.11.0rc1.tar.gz
tar zxvf freepbx-2.11.0rc1.tar.gz
cd freepbx-2.11.0rc1
./start_asterisk start # for upgrades use: amportal start
./install_amp

You can also pull directly from SVN for beta/RC testing by following the instructions below but using the 2.11 branch instead of what is listed.

Upgrading to the latest Released Version: 2.10.0
You will want to pull the release tarball, and follow the instructions below. Once you have installed it you will want to navigate to Module Admin menu item and update all modules as well as install other available modules not included in the release tarball.

cd /usr/src/
wget http://mirror.freepbx.org/freepbx-2.10.0.tar.gz
tar zxvf freepbx-2.10.0.tar.gz
cd freepbx-2.10.0
./start_asterisk start # for upgrades use: amportal start
./install_amp

On some rare cases you may experience an issue with the SQL database not being correctly updated. If that appears to be the case, you can safely add the --force-version option. For example, if you were upgrading from version 2.6.0 you might type:

cd /usr/src/freepbx-2.10.0
./install_amp --force-version=2.6.0

(Replace 2.6.0 with the version you are upgrading from, or an earlier version which is also safe)

You can also pull directly from SVN for beta/RC testing by following the instructions below but using the 2.10 branch instead of the 2.8 branch.

You can also pull directly from SVN for beta/RC testing by following the instructions below but using the 2.10 branch.

Upgrading to the latest stable 2.10 branch from SVN
If you prefer to pull directly from the SVN repository you can follow these instructions below. Once you have installed FreePBX it is important to navigate to Module Admin in FreePBX and upgrade your modules. Installing FreePBX in this way (vs. using the release tarball) is not recommended for initial installs unless you are very familiar with the project. Without loading critical modules like core, framework, voicemail and some others your system will not be able to do anything for you or will function improperly.

cd /usr/src/
svn co http://svn.freepbx.org/freepbx/branches/2.10 freepbx-2.10

Installation instructions are the same as above after exploding the tarball

Note:Need to get the new func_devstate features to take advantage of the optional BLF? You can get a version that works on 1.4 from this website, and then you simply put the file in your apps subdirectory of your asterisk source and re-run make and make install. To use this mode, amportal.conf needs the setting:

USEDEVSTATE=true

Upgrading to 2.6 From trixbox
If you are using a version of trixbox that no longer connects to the FreePBX repository and does not provide you with the 2.6 Upgrade Tool, you can upgrade to 2.6 by following these simple instructions. The process will simply install a special version of the Upgrade Tool and then you will upgrade just the same as the normal GUI upgrade process. Although the tool may indicate you are upgrading to a beta or release candidate program, since 2.6 has gone final, you will actually be upgraded to the current 2.6 released version. The steps are simply:

  1. Download the upgrade module to your desktop by pressing this link: Download trixbox Upgrade Tool
  2. Navigate to Module Admin in FreeBPX, click on the Upload module link and then browse to the module you downloaded in step 1, choose it, and then press upload.
  3. Now you simply install the module as if you were downloading it from the Online Repository and then you can follow the instructions provided by the module to upgrade!

The process is almost identical to pulling the module from our repository and once you do this, you will have access to all the great features and many bug fixes no present elsewhere.
Upgrading to the trunk branch
The trunk is where active development happens. The project tries hard to keep it relatively stable and you will find it is fairly safe to run off of this branch most of the time, although it is actively being developed on so glitches can occur. This differs from release branches where they are limited to the latest bug fixes. You can access the development trunk as described below.
To run off of trunk and keep up-to-date with every change even before modules get published, there is a set of tools that will help you build an install environment where you do NOT use Module Admin to keep up-to-date. The instructions are:

cd /usr/src/
svn co http://svn.freepbx.org/freepbx/trunk freepbx-trunk
cd freepbx-trunk
./setup_svn.php

At this point, you will now have a special SVN environment where all the FreePBX modules are pulled into your install directory. You can then do a normal install:

./install_amp --force-version=2.4.1

Note that you will always want to do a force-version in case there are new schema changes introduced since the last time you updated. If you are updating from a release prior to 2.4.1, you should use that release number the first time, but 2.4.1 after that is fine.
Now, instead of using Module admin with this setup, you can simply follow the following procedure to update yourself to the newest updates that may have been committed:

cd /usr/src/freepbx-trunk
svn update
./install_amp --force-version=2.4.1 #(*)

(*) if there were no updates pulled, then there is no need to do an install amp again
The install will take longer because it will be going through the process of reinstalling all modules, but it will do such with all new changes even before they are published to the Online Repository.

Taxonomy upgrade extras: