Upgrading FreePBX
Note: 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 Released Version: 2.4.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.4.0.tar.gz
tar zxvf freepbx-2.4.0.tar.gz
cd freepbx-2.4.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.1.3 you might type:

cd /usr/src/freepbx-2.4.0
./install_amp --force-version=2.1.3

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

Upgrading to the latest stable 2.4 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.4 freepbx-2.4

Installation instructions are the same as above after exploding the tarball

Upgrading to the trunk branch
The trunk is where active development happens. The project tries hard to keep it relatively stable but it is a dynamic place a times. This differs from release branches where they are limited to the latest bug fixes. You can access the development trunk as described below.

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

Note: this code is under active development, and may be broken at times. However, there's usually new things in SVN that you may want to play with. Also, when you're using SVN, you must specify the last 'released' version you were using. This ensures that the database layout is up to date. You do this with the command:

cd /usr/src/freepbx-trunk
./install_amp --force-version=2.1.3

(Replace 2.1.3 with the version you are upgrading from)

Changing the URL from a previously checked SVN checkout
You may already have already performed an svn co from the repository and when you now try to access the repository (e.g. doing an svn update) it no longer works because the URL has been changed from some of the recent SVN changes. You can simply change the URL to point to the new repository location with the following instructions:

1. Go to the root of your checked out branch and type svn info
2. you will see something such as: https://amportal.svn.sourceforge.net/svnroot/amportal/freepbx/branches/2.3 as part of the information.
3. you would then execute the following command:
   

   svn switch --relocate https://amportal.svn.sourceforge.net/svnroot/amportal/freepbx/branches/2.3 http://svn.freepbx.org/freepbx/branches/2.3
   

4. That would be it, you should now be pointing to the proper repository. You may need to modify the above URL depending on what you get from your svn info command.

Related Content