Upgrading to 2.x

From Taridium

Revision as of 17:28, 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).

• Update repository accordingly to install ipbx:

 [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

• perform yum upgrade (install ipbx)
• Always check that the 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
• 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)
• check that /etc/asterisk/* files are all present. Pay special attention to modules.conf, extconfig.conf and asterisk.conf, these can be usually copied over from /usr/local/ipbx/install/etc/asterisk since they are rarely customized.
• Check asterisk.conf for correct location of run directory (now always /var/run/asterisk)
• Disable the manager proxy usage in `pbx` table (mysql -> UPDATE pbx SET proxy=0;) and disable astmanproxy (process and startup). The package can be removed if not needed. E.g. rpm -e astmanproxy
• Make sure that ipbx service is running, (service ipbx restart) and that it's setup to start at boot, chkconfig ipbx on!
• 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)
• 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).
• Make sure all that all extensions have a feature table entry, otherwise extension calls will fail! If necessary use the User consolidation feature.
• Check that Voicemail options have been changed to | (pipe) syntax NOT sb124@default when upgrading from Asterisk 1.2
• Check that correct Caller ID variables are used: e.g. CALLERID(num) and CALLERID(name) and NOT CALLERIDNAME in your dialplan.
• Check that any G.729 codec modules and licenses have been updated if manually installed.
• Copy over /usr/local/ipbx/install/etc/asterisk/http.conf and /usr/local/ipbx/install/etc/asterisk/manager.conf to /etc/asterisk and check extconfig.conf for completeness (ensure that queue configuration is set for realtime). If in doubt copy from /usr/local/ipbx/install/etc/asterisk
• Possibly adjust sendmail masquerading if necessary, e.g.: MASQUERADE_AS(`example.com')dnl FEATURE(masquerade_envelope)dnl AND FEATURE(masquerade_entire_domain)dnl in sendmail.mc
• Add the following to the Integrated Features Configuration:

     [applicationmap]
     nway-start = *9,self/both,agi,ipbx/nway.agi