Upgrading Elastix to 1.6

Upgrading Xorcom XR1000/2000/3000 servers from Elastix 1.5 to Elastix 1.6

Document version: 1.0

Modification date: 03 February 2010

Prior to performing the upgrade, it is strongly recommended that you backup your current server using the Xorcom Rapid Recovery tool.

1. In the /etc/yum.repos.d/elastix.repo file, define parameter 'exclude' for [elastix-base] and [elastix-updates] repositories as follows:
   exclude=elastix-mysqldbdata *dahdi *dahdi-devel asterisk asterisk-devel asterisk-sounds* libpri*


2. Remove the libsupertone packages using the following command (they are not required for Elastix 1.6 and cause some packages dependency problems):
   yum remove libsupertone libsupertone-devel
   Note that libmfcr2 will be removed automatically.
   
   
3. Update the software:
   yum update
   Approximately 450 MB of data will be downloaded from the Internet during this upgrade.


4. Elastix 1.6 includes a new Linux kernel (version: 2.6.18-164.el5) that will be installed automatically by 'yum'. Afterwards, the XEN kernel version will be set as the default boot manager option. In order to fix this issue, edit the /boot/grub/menu.lst file and define the parameter 'default' in such a way that it will point to the 'title CentOS (2.6.18-164.el5)'.
   Note that the kernels are numbered starting from 0. For example:
   default=0
   timeout=5
   splashimage=(hd0,0)/grub/splash.xpm.gz
   #hiddenmenu
   title CentOS (2.6.18-164.el5)
     root (hd0,0)
     kernel /vmlinuz-2.6.18-164.el5 ro root=LABEL=/
     initrd /initrd-2.6.18-164.el5.img
   title CentOS (2.6.18-164.el5xen)
     root (hd0,0)
     kernel /xen.gz-2.6.18-164.el5
     module /vmlinuz-2.6.18-164.el5xen ro root=LABEL=/
     module /initrd-2.6.18-164.el5xen.img
   title Elastix (2.6.18-92.1.22.el5xen)
     root (hd0,0)
     kernel /xen.gz-2.6.18-92.1.22.el5
     module /vmlinuz-2.6.18-92.1.22.el5xen ro root=LABEL=/
     module /initrd-2.6.18-92.1.22.el5xen.img
   title Elastix-base (2.6.18-92.1.22.el5)
     root (hd0,0)
     kernel /vmlinuz-2.6.18-92.1.22.el5 ro root=LABEL=/
     initrd /initrd-2.6.18-92.1.22.el5.img
   As you can see, the 'default=0' points to the correct kernel.


5. Reboot the server.


6. Reset the Astribank devices:
   /etc/init.d/asterisk stop
   /etc/init.d/dahdi stop
   /usr/share/dahdi/xpp_fxloader reset
   
   wait until lsusb command shows the Astribank units as e4e4:1162 devices. For example:
   #lsusb
   Bus 002 Device 001: ID 0000:0000
   Bus 001 Device 005: ID e4e4:1162
   Bus 001 Device 001: ID e4e4:1162
   Bus 003 Device 001: ID 0000:0000
   Bus 004 Device 001: ID 0000:0000
   
   After that, start DAHDI and Asterisk again:
   
   /etc/init.d/dahdi start
   /etc/init.d/asterisk start


7. Connect to the Web interface, go to the "Unembedded freePBX", select the "Module admin" menu option and check that all modules were updated successfully.


8. Fix the IAX2 settings if necessary.
   Starting with Asterisk 1.4.26.2 the IAX2 implementation has some strong security enhancements. Unfortunately, these enhancements are not currently supported by the majority of third party IAX2 soft and hard IP phones. As result of these enhancements, after an Asterisk upgrade these IP phones stop communicating unexpectedly.
   For example, the iaxmodem cannot register on Asterisk and, as a result, the Elastix fax2mail service does not work anymore. Communication with the popular IAX2 softphone Zoiper is also affected. According to the Digium IAX2-security.pdf: "... to bypass the security enhancements completely and have Asterisk work exactly as it did before, the following options can be specified in the [general] section of iax.conf:
   
   [general]
   ...
   calltokenoptional = 0.0.0.0/0.0.0.0
   maxcallnumbers = 16382
   ......"
   
   To apply the workaround for the Xorcom XR1000/XR2000/XR3000 IP-PBX, the parameters mentioned above must be defined in the /etc/asterisk/iax_general_custom.conf file.


9. Fix the /etc/amportal.conf file.
   Add the following line at the end of the amportal.conf file:
   AMPBADNUMBER=false
   
   This will eliminate a 3-second delay in the call establishment process when dialing from the FXS extensions. It will also eliminate the misleading “All circuits are busy...” voice message that plays when a PBX user dials a number that does not match any configured phone number pattern. Note: it is necessary for FreePBX to rebuild the extensions* files. The simplest way to do this is to change something in the PBX extensions settings via the Web interface and then to apply the changes.
   
   
10. Reinstall rapid-tunneling packages using the following command:
    yum reinstall rapid-tunneling-gui rapid-tunneling

 Download these instructions in PDF format (88.63 Kb)