For whatever reason trixbox is not releasing Asterisk updates in their repository for their 2.6 versions. (see rant at bottom) Luckily, where trixbox slacks digium delivers. With little trouble I was able upgrade a trixbox distribution so that I can get the latest updates of the asterisk software direct from digium, while continuing to keep my trixbox software up to date through trixbox. Here is the rundown:
Bring your system up to date with the trixbox repository
yum update
Modify the repository settings.
trixbox by default has the centos repos, and its own trixbox repo. We need to add the digium repo and remove the kernel exception from the centos repo.
wget http://packages.asterisk.org/centos/5/current/i386/RPMS/yum-repos-asterisk-1.0.0-1_centos5.noarch.rpm rpm -i yum-repos-asterisk-1.0.0-1_centos5.noarch.rpm
in /etc/yum.repos.d/CentOS-Base.repo under the section titled [base] comment out exclude kernel:
#exclude=kernel*
Update your kernel
yum update kernel kernel-headers reboot
Replace the asterisk software from trixbox with the latest software from digium
To find all the currently installed packages that you will need to remove use the commands:
rpm -qa | grep asterisk rpm -qa | grep zap
You will not need to remove all of these packages, only the ones that are provided by digium through packages.asterisk.org. In my case I left both tbm-asteriskinfo, asterisk-perl installed and removed the rest. Here are the packages i removed:
rpm -e --nodeps asterisk-sounds-1.2.1-2 asterisk-1.4.22-4 asterisk-addons-1.4.7-2 zaptel-modules-1.4.12.9-1_trixbox.2.6.18_128.1.10.el5 zaptel-1.4.12.9-1_trixbox
This order of operations left some driver cruft that I had to manually remove:
rm -Rf /lib/modules/2.6.18-164.el5/weak-updates/zaptel/*
Now we can install the latest asterisk software from digium’s repo:
yum install asterisk14 dahdi-tools asterisk14-addons
Now this new asterisk system will use all the same old configuration files that are still in place, except for 2 which we will modify now. Both of these modifications are related to the name change from zaptel to dahdi.
/etc/dahdi/system.conf
This is really just a new name for what was /etc/zaptel.conf. Simply copy /etc/zaptel.conf to /etc/dahdi/system.conf and you’re done. If rpm moved your zaptel.conf then copy /etc/zaptel.conf.rpmsave to /etc/dahdi/system.conf.
/etc/dahdi/modules
This is a new name and syntax for /etc/sysconfig/zaptel. Open it up and comment out the modules you will not be needed, based on the hardware you have installed. Compare against your /etc/sysconfig/zaptel if you are at a loss.
Lastly, modify /etc/asterisk/asterisk.conf by adding this directive to the [options] section:
[options] dahdichanname=no
Now reboot and voila!
Rant
trixbox doesn’t respond to bug reports, doesn’t maintain their changelog, has little in the way of developer support, doesn’t integrate bugs fixes of opensource software that it repackages. I am currently testing asterisknow as an alternative.







