Upgrading ipbx

From Taridium

Revision as of 19:30, 9 August 2012 by Webmaster (Talk | contribs)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to: navigation, search

Free ipbx updates are provided to all registered and licensed customers. Contact support@taridium.com if you can't access the repositories.


ipbx upgrades consist of two parts:

  1. The ipbx software and related components as licensed by Taridium.
  2. The Asterisk Open Source back-end as distributed by Taridium. These packages are available for the Asterisk version 1.4 (support expired), version 1.6 (limited support) and version 1.8 (current) branches. We only suggest upgrading Asterisk where needed for security and specific feature reasons. Features described in the change log usually DO NOT require a switch upgrade unless mentioned otherwise.

Upgrades of ipbx should be performed during off hours, but will usually not affect any ongoing voice traffic unless the switching package asteriskXX - e.g. asterisk14, asterisk16, asterisk18 (formerly also the asterisk package) and/or related components need to be upgraded. See the change log for details on each upgrade.


Contents

Upgrading ipbx via Web Interface

Go to Advanced SetupMaintenance and click on check for updates - if an update is available, you can select install update to perform the upgrade. Depending on your connection speed, the upgrade can take up to 5 minutes.

Upgradeipbx.gif

Warning.gifYou will not be able to upgrade via web interface if you have changed your MySQL default password - use the command line upgrade instead.

Upgrading ipbx via Command Line

Make sure your system is connected to the internet and that name resolution is working properly. To upgrade via command line, log into your system as root and enter:

 [root@ipbx ~]# yum update ipbx

Once the update has been completed run ipbx-config and select option 6 to upgrade the database. Some updates will not include a database upgrade, but it is always advisable to run the database upgrade, to make sure any changes have been applied. It is normal that several revisions of the database will be applied if you haven't upgraded with every new version. Note that failing to upgrade the database might prevent your PBX from working properly, so always check for database upgrades!

 [root@ipbx ~]# ipbx-config
 
 ************************************************************
                                                             
   ipbx 2.3 Configuration                      
   (c) 2011 taridium                                   
                                                             
 ************************************************************
 
 
 Select Configuration Option:
 
 1 <- Configure ipbx for the first time and use default
      configuration
 2 <- Create full database backup
 3 <- Fix file system permissions
 4 <- Restore default ipbx database (will erase all settings)
 5 <- Reset admin password
 6 <- Upgrade ipbx database (safe mode)
 
 0 <- Exit
 
 please enter your choice:

Upgrading Asterisk

Upgrading using the Switch Updater

ipbx 2.3 and higher include a package updater for Asterisk, which allows you to switch between Asterisk 1.4, 1.6 and 1.8 depending on your needs.

 [root@ipbx ~]# cd /usr/local/ipbx/scripts/
 [root@ipbx scripts]# ./switch-updater 
 
 switch-updater version 1.0
 Updates or installs the Asterisk switch components for ipbx
 Copyright (c) 2011  Taridium
 
 Usage: switch-updater [VERSION]
     VERSION     The target version can be: 14, 16 or 18


Example Usage:

 [root@ipbx scripts]# ./switch-updater 18

If you specify your current release, the current packages will be upgraded, if available. If you specify a different release, the packages will be removed and replaced by the specified version!

Restart Asterisk after you have completed your upgrade:

 [root@ipbx scripts]# service asterisk restart

Check if the ipbx configuration manager can connect to Asterisk:

 IPBX*CLI> realtime mysql status 
 Connected to ipbx@localhost, port 3306 with username ipbx for 12 seconds.
 IPBX*CLI> cdr mysql status 
 Connected to ipbx@localhost, port 3306 using table cdr for 12 days, 17 hours, 48 minutes, 22 seconds.
 Wrote 5661 records since last restart.

Manual Upgrade prior to ipbx 2.3

To upgrade Asterisk, first check which major version packages are currently in use on your system. Standard distributions are named asterisk14 and asterisk16 (this package was previously called asterisk only) Login to your system as user root:

 [root@ipbx ~]# rpm -q asterisk16

or

 [root@ipbx ~]# rpm -q asterisk14

To upgrade your current package replace XX with your major version (or asterisk only), below:

 [root@ipbx ~]# yum update asteriskXX

After all packages have been updated you can restart asterisk:

 [root@ipbx ~]# service asterisk restart

Check if the ipbx configuration manager can connect to Asterisk:

 IPBX*CLI> realtime mysql status 
 Connected to ipbx@localhost, port 3306 with username ipbx for 12 seconds.
 IPBX*CLI> cdr mysql status 
 Connected to ipbx@localhost, port 3306 using table cdr for 12 days, 17 hours, 48 minutes, 22 seconds.
 Wrote 5661 records since last restart.

Change Log

Detailed information about changes in ipbx releases can be found in the ipbx change log.

Personal tools
Namespaces
Variants
Actions
Toolbox