[asterisk-users] OSLEC and zaptel-1.4.5.1

Wed Oct 24 11:08:00 CDT 2007

Hi Alan.
I've installed OSLEC with zaptel-1.4.5.1 applying the patches made for the 1.4 version and I have had the same problem.
Looking at the compiler options I've found that the symbol ECHO_CAN_FROMENV is defined by default and this prevents the echo selection from zconfig.h.
I've solved changing the first part of Makefile.kernel26 (in the zaptel directory) this way:

ifndef ECHO_CAN_NAME
  ECHO_CAN_NAME := OSLEC
endif

This forces the compiler to include OSLEC as echo cancellation engine (probably there is a better way but I don't know it).

I've then rebuilt zaptel and installed through normal make procedures.

To be able to modprobe it I've then copied the oslec.ko file build by the OSLEC distribution in the kernel driver directory (my own is /lib/modules/2.6.18.8-0.5-default/misc and it's where zaptel drivers are installed). I've then run the depmod command to regenerate the modules dependencies.

I'm now able to modprobe zaptel and to have oslec automatically installed as you can see below:

> lsmod | grep zaptel
zaptel                199992  6 zttranscode,wctdm
oslec                  23332  1 zaptel
crc_ccitt               6272  1 zaptel

I hope this could help you.

Best regards,
Marco Signorini.

> 
> Hi all,
> 
> After reading great things about the OSLEC Echo Canceller
> (http://www.rowetel.com/ucasterisk/oslec) and seeing the reactions of
> people who have tried it on a recent Trixbox thread
> (http://www.trixbox.org/forums/trixbox-forums/open-discussion/need-people-echo-problems),
> it sounds like it is the "bees knees" for sorting out echo problems with
> cards like the x100p.
> 
> Has anyone managed to get oslec to work with recent zaptel and kernel
> (I'm running 2.6.23)?
> 
> Lots of information below. Comments/suggestions welcome.
> 
> Having followed the instructions on the oslec site, and ensuring the
> patch for zaptel takes O.K (I manually installed the patch into the
> zaptel source tree just to make sure). I can build the oslec module, and
> build a patched zaptel-1.4.5.1-oslec without any compilation issues.
> 
> However when I reload the system during boot-up dmesg tells me:
> 
> Zapata Telephony Interface Registered on major 196
> Zaptel Version: 1.4.5.1
> Zaptel Echo Canceller: MG2
> Zaptap registered 'sample' char driver on major 33 (This means the patch
> went in O.K.)
> ACPI: PCI Interrupt 0000:00:08.0[A] -> GSI 17 (level, low) -> IRQ 22
> wcfxo: DAA mode is 'FCC'
> Found a Wildcard FXO: Wildcard X100P
> 
> Notice the choice of echo canceller....
> 
> If I look at what modules are installed:
> 
> # lsmod
> Module                  Size  Used by
> zttranscode             6280  0
> ztdummy                 3432  0
> wcfxo                   9760  0
> zaptel                200120  7 zttranscode,ztdummy,wcfxo
> crc_ccitt               1792  1 zaptel
> 
> No oslec :-(
> 
> In my kernel modules/misc directory I have:
> -rw-r--r-- 1 root root 10727 2007-10-24 14:44 oslec.ko
> -rw-r--r-- 1 root root 65372 2007-10-24 14:41 pciradio.ko
> -rw-r--r-- 1 root root 91321 2007-10-24 14:41 tor2.ko
> -rw-r--r-- 1 root root 18901 2007-10-24 14:41 torisa.ko
> -rw-r--r-- 1 root root 12605 2007-10-24 14:41 wcfxo.ko
> -rw-r--r-- 1 root root 15989 2007-10-24 14:41 wct1xxp.ko
> drwxr-xr-x 2 root root  4096 2007-10-24 14:41 wct4xxp
> drwxr-xr-x 2 root root  4096 2007-10-24 14:41 wctc4xxp
> drwxr-xr-x 2 root root  4096 2007-10-24 14:41 wctdm24xxp
> -rw-r--r-- 1 root root 41046 2007-10-24 14:41 wctdm.ko
> -rw-r--r-- 1 root root 32882 2007-10-24 14:41 wcte11xp.ko
> -rw-r--r-- 1 root root 45804 2007-10-24 14:41 wcte12xp.ko
> -rw-r--r-- 1 root root 16527 2007-10-24 14:41 wcusb.ko
> drwxr-xr-x 2 root root  4096 2007-10-24 14:41 xpp
> -rw-r--r-- 1 root root 81616 2007-10-24 14:41 zaptel.ko
> -rw-r--r-- 1 root root  8270 2007-10-24 14:41 ztd-eth.ko
> -rw-r--r-- 1 root root  5530 2007-10-24 14:41 ztd-loc.ko
> -rw-r--r-- 1 root root  5297 2007-10-24 14:41 ztdummy.ko
> -rw-r--r-- 1 root root 11687 2007-10-24 14:41 ztdynamic.ko
> -rw-r--r-- 1 root root  8639 2007-10-24 14:41 zttranscode.ko
> 
> My /etc/zaptel.conf is:
> loadzone=uk
> defaultzone=uk
> 
> fxsks=1
> 
> My /etc/asterisk/zapata.conf is
> 
> ; Zapata telephony interface ;
> ; Configuration file
> [channels]
> ;Hardware defaults for the x100p card
> ;usecallerid=yes
> ;hidecallerid=no
> ;callwaiting=no
> ;threewaycalling=yes
> ;usedistinctiveringdetection=yes
> ;transfer=yes
> ;usecallingpres=yes
> ;callwaitingcallerid=yes
> ;cancallforward=yes
> ;callreturn=yes
> echocancel=yes
> echotrainingwhenbridged=no
> ;echotraining=400
> rxwink=300 ; Atlas seems to use long (250ms) winks
> 
> ;cidsignalling=v23 ; Added for UK CLI detection
> ;cidstart=usehist ; After patching the driver from here :
> ; http://www.lusyn.com/resources/asterisk/usehist.htm
> ;callerid=asreceived ; propagate the CID received from BT
> ;rxgain=1.0
> ;txgain=1.0
> 
> ;define channel
> context=main_menu
> language=en
> signalling=fxs_ks
> channel => 1 ;Our x100p
> 
> --------------------------
> 
> Alan
> 
> -- 
> The way out is open!
> http://www.theopensourcerer.com
> 
> 
> _______________________________________________
> --Bandwidth and Colocation Provided by http://www.api-digital.com--
> 
> asterisk-users mailing list
> To UNSUBSCRIBE or update options visit:
>    http://lists.digium.com/mailman/listinfo/asterisk-users
> 
> 