Applying USEHIST patch to asterisk on my trixbox
Hi everyone,
Okay, I am patching asterisk on my trixbox with the history caller id patch (http://www.lusyn.com/resources/asterisk/index.htm). This is all fine and i have managed to do this with no problems apart from the fact that i can nolonger receive faxes into my box. It detects them but doesnt do anything with it.
I decided to compare the modules list in the system before and after i rebuilt asterisk. Now i can see that there are 13 modules taht are missing.
What source code is trixbox built off of? I downloaded the same version of zaptel, asterisk and asterisk-addons but it seems as though the trixbox is using some other version.
These modules are missing....
app_flite
app_nv_backgrounddetect
app_nv_faxdetect
app_rxfax
app_speech_utils
app_txfax
chan_alsa
chan_h323
codex_speex
format_ogg_vorbis
res_config_odbc
res_odbc
res_speech
So how do i build these then?
Thanks
Joys! I don't suppose you have a list of places to get them?
Oh and just looking through the repository there is a package for asterisk developement "asterisk-devel.i386 Development package for asterisk". What is this for? I notice that it is version 1.2.14?
Thanks
Ok, i am a bit dumb when it comes to *nix boxes, but can someone explain to me why after you recompile asterisk, the original modules do not work the the newly compiled ones?
For example, i have some missing modules, so if i copy a missing module into the asterisk folder, when i start asterisk, the module crashes it? Why is this???
Also, i have found this....
http://yum.trixbox.org/centos/4/SRPMS/repodata/repoview/asterisk-...
Now i assume this is the source that is used by trixbox to compile asterisk? If i used this instead of the code from the digium site, would this compile up some of the missing modules?
Many Thanks all,
Lol, i'm learning more about *nix systems by using this thatn when i just had an ubuntu play vm.
Right, now i am really confused!!!! The source package....
http://yum.trixbox.org/centos/4/SRPMS/repodata/repoview/asterisk-...
Looks like it has got the code in it to apply the "usehist" patch, but i don't think it works because it looks like the basic files provided by author of the patch. I know that you actually have to modify these files to apply the patch sucessfully, here are they files plus a little guide i have knocked up...
This is for version 1.2.22 of asterisk and 1.2.19 of Zaptel
http://www.fileden.com/files/2007/5/23/1105940/asterisk-usehist.z...
Note, there is a part which asks you to download the Rhino drivers. You do not need to do this if you don't have a Rhino card. The only reason i recompile the Rhino drivers is because the machine crashes when detecting hardware otherwise.
The source rpm only contains part of the patch as you have to modify the zaptel drivers as well (zaptel-base.c, and zaptel.h).
So Kerry, is it possible to fully implement this patch properly into trixbox as it is an exteremly handy patch to get CallerID working in a couple of countries for generic cards.
Thanks
Right, i sucessfully manage to apply this to my Trixbox 2.2.3 last night, so here is a guide and the patches which should apply without any issues...
http://www.fileden.com/files/2007/5/23/1105940/trixbox2.2.3-usehi...
Here is the guide....
Install kernel dev module from repository
cd /usr/src/kernels/2.6.9-34.0.2.EL-smp-i686/include/linux
mv spinlock.h spinlock.h.old
wget nerdvittles.com/aah27/spinlock.h
cd /usr/src
wget http://ftp.digium.com/pub/zaptel/releases/zaptel-1.2.19.tar.gz
tar -xzvf zaptel-1.2.19.tar.gz
ln -s zaptel-1.2.19 zaptel
wget http://ftp.digium.com/pub/libpri/releases/libpri-1.2.4.tar.gz
tar -xzvf libpri-1.2.4.tar.gz
ln -s libpri-1.2.4 libpri
wget http://ftp.digium.com/pub/asterisk/releases/asterisk-1.2.22.tar.g...
tar -xzvf asterisk-1.2.22.tar.gz
ln -s asterisk-1.2.22 asterisk
wget http://ftp.digium.com/pub/asterisk/releases/asterisk-addons-1.2.7...
tar -xzvf asterisk-addons-1.2.7.tar.gz
ln -s asterisk-addons-1.2.7 asterisk-addons
cd /usr/src/zaptel cd /usr/src/asterisk mv -v /usr/lib/asterisk/modules/app_speech_utils.so /usr/lib/asterisk/modules/app_speech_utils.so.old amportal stop cd /usr/src/zaptel **** This bit if only for people with rhino cards **** cd /usr/src/libpri cd /usr/src/asterisk cd /usr/src/asterisk-addons shutdown -r now Edit /etc/asterisk/zapata.conf and use the following three lines for CallerID :
patch
patch -p0
make clean
make install
cd /usr/src/zaptel
wget ftp://ftp.rhinoequipment.com/Drivers/rhino-1.1.0.tbz2
tar -xjvf rhino-1.1.0.tbz2
cd rhino-1.1.0
make
make install
depmod
*******************************************
make clean
make install
make clean
make install
make clean
make install
nano -w /etc/asterisk/zapata.conf
usecallerid=yes
cidsignalling=v23
cidstart=usehist
The zaptel history patch from http://www.lusyn.com/resources/asterisk/usehist.htm does not work with the latest Trixbox release because the zaptel-base.c and zaptel.h files are now in the /zaptel/kernel/ directory. Also, the second chunk of the Zaptel patch fails due to an extra variable being declared in the latest Zaptel zaptel-base.c file (char *s;). I’ve uploaded an updated patch that does work with Trixbox 2.6.07 here if you would like to test it: http://www.novavox.co.uk/dev/patch/x100pse/zaptel-usehist-1-4-10.....
However, even though Asterisk/Zaptel compile fine and there are no debug messages when receiving a call, unfortunately Caller ID still doesn’t work on our test system. I’ve played with various Zapata.conf parameters such as adjusting the tx/rx gains, commenting in/out ukcallerid=yes, disabling fax detection, and even disabling echo cancellation but nothing so far has made any difference. The CID parameters are set to:
usecallerid=yes
cidsignalling=v23
cidstart=usehist
callerid=asreceived
As there aren’t any error/debug messages its difficult to determine what the issue might be. I’m going to try starting from scratch again with a fresh install and see if that makes any difference. I’ll reply back to this thread with the results.
Blueivy, I’ve documented the setup steps to get Caller ID working on UK BT lines with X100P cards in the following document:
The instructions have been used to successfully setup UK Caller ID by a number of users with Trixbox 2.6.07 systems. The guide also explains exactly why Caller ID cannot be detected in the UK on BT lines in the normal way, i.e. due to the wcfxo driver not supporting polarity reversal detection.

Member Since:
2007-07-27