Upgrading to 2.x

From Taridium

(Difference between revisions)
Jump to: navigation, search
(Configuration Hints)
(Configuration Hints)
 
(2 intermediate revisions not shown)
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
+
This documents describes the configuration changes that need to be made in order to upgrade from Taridium's ipbx 1.x to 2.x. If you want to make use of Taridium's integrated features, such as IVR, Groups, Dynamic Queueing etc., make sure to 'restore' the default ipbx v.2.x dialplan.
== Configuration Hints ==
== Configuration Hints ==
Line 32: Line 32:
* remove crontab entry for ipbx v.1.2 (old tasker process)
* remove crontab entry for ipbx v.1.2 (old tasker process)
* Go through dialplan and make sure all user/ scripts are updated with ipbx/ - E.g. user/stdexten.agi is now ipbx/stdexten.agi)
* Go through dialplan and make sure all user/ scripts are updated with ipbx/ - E.g. user/stdexten.agi is now ipbx/stdexten.agi)
-
* If you want to use the built-in dialplan, go to the Admin GUI and select Configuration -> Advanced Setup -> Maintenance -> '''Clear Dialplan and restore to default'''
+
* If you want to use the built-in dialplan, go to the Admin GUI and select '''Configuration''' → '''Advanced Setup''' → '''Maintenance''' → '''Clear Dialplan and restore to default'''
* Check location of music-on-hold directory and adjust to /var/lib/asterisk/moh-native (also check config.php MOHDir variable to point to the former).
* Check location of music-on-hold directory and adjust to /var/lib/asterisk/moh-native (also check config.php MOHDir variable to point to the former).
* Make sure all that all extensions have a feature table entry, otherwise extension calls will fail! If necessary use the User consolidation feature.
* Make sure all that all extensions have a feature table entry, otherwise extension calls will fail! If necessary use the User consolidation feature.
Line 43: Line 43:
       [applicationmap]
       [applicationmap]
       nway-start = *9,self/both,agi,ipbx/nway.agi
       nway-start = *9,self/both,agi,ipbx/nway.agi
 +
* Check if the system is bootproof (DAHDI/Zaptel/Wanrouter)

Latest revision as of 17:31, 8 April 2010

This documents describes the configuration changes that need to be made in order to upgrade from Taridium's ipbx 1.x to 2.x. If you want to make use of Taridium's integrated features, such as IVR, Groups, Dynamic Queueing etc., make sure to 'restore' the default ipbx v.2.x dialplan.

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