Upgrading to 2.x

From Taridium

(Difference between revisions)
Jump to: navigation, search
Line 1: Line 1:
 +
This documents describes the changes that need to be made in order to upgrade from Taridium's ipbx 1.x to 2.x
 +
== Configuration Hints ==
== Configuration Hints ==
-
Upgrade to v.2 is fairly straightforward - particular attention has to be paid to permissions when using Zaptel/DAHDI interfaces. ipbx v2 and related applications run as non-privileged users.
+
Upgrade to v.2 is fairly straightforward - particular attention has to be paid to permissions when using Zaptel/DAHDI interfaces. ipbx v2 and related applications run as non-privileged users. Another important change is the fact that the ipbx package itself is now architecture agnostic (aka noarch RPM).
* Update repository according to install ipbx
* Update repository according to install ipbx
Line 22: Line 24:
* Always check that database has been upgraded, running ipbx-config never hurts.
* Always check that database has been upgraded, running ipbx-config never hurts.
* Make sure that /etc/udev/permissions.d/zaptel.permissions on Centos 4.x has (also uncomment root perm in 50-udev.permissions) zap/*:asterisk:asterisk:660
* Make sure that /etc/udev/permissions.d/zaptel.permissions on Centos 4.x has (also uncomment root perm in 50-udev.permissions) zap/*:asterisk:asterisk:660
 +
* On CentOS 4.x make sure you enable the CentOS plus repository and check php.ini for the correct version of the Ioncube encoder.
* Make sure zaptel permissions are correct, especially /dev/zap (needs to be readable by asterisk)
* Make sure zaptel permissions are correct, especially /dev/zap (needs to be readable by asterisk)
* check that /etc/asterisk/* files are all present. Pay special attention to modules.conf, extconfig.conf and asterisk.conf
* check that /etc/asterisk/* files are all present. Pay special attention to modules.conf, extconfig.conf and asterisk.conf

Revision as of 17:23, 8 April 2010

This documents describes the changes that need to be made in order to upgrade from Taridium's ipbx 1.x to 2.x

Configuration Hints

Upgrade to v.2 is fairly straightforward - particular attention has to be paid to permissions when using Zaptel/DAHDI interfaces. ipbx v2 and related applications run as non-privileged users. Another important change is the fact that the ipbx package itself is now architecture agnostic (aka noarch RPM).

 [core]
 name=taridium core repository
 baseurl=http://[username]:[password]@repo.taridium.com/centos/$releasever/core/$basearch/
 gpgcheck=1
 gpgkey=http://[username]:[password]@repo.taridium.com/centos/RPM-GPG-KEY-taridium5
 
 [core-noarch]
 name=taridium core noarch repository
 baseurl=http://[username]:[password]@repo.taridium.com/centos/$releasever/core/noarch/
 gpgcheck=1
 gpgkey=http://[username]:[password]@repo.taridium.com/centos/RPM-GPG-KEY-taridium5

For CentOS 4 replace http://[username]:[password]@repo.taridium.com/centos/RPM-GPG-KEY-taridium4

     [applicationmap]
     nway-start = *9,self/both,agi,ipbx/nway.agi
Personal tools
Namespaces
Variants
Actions
Toolbox