[asterisk-users] OSLEC and zaptel-1.4.5.1

[Dave Fullerton]

Replies/Comments inline...

Alan Lord wrote:
> 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.

I am using OSLEC on my home pbx. I used to have echo on some calls prior 
to OSLEC but have been echo free since I installed it.

> Has anyone managed to get oslec to work with recent zaptel and kernel 
> (I'm running 2.6.23)?

I'm only using 2.6.17 and zaptel-1.4.4 at the moment. But if the patches 
apply it should work.

> 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....

Check the zconfig.h file in the zaptel source and make sure that the line:
#define ECHO_CAN_OSLEC
is not commented out but all the lines for the other echo cancelers are.

Did you start with a clean source (or at least did a make clean) before 
you compiled? Are you using the zaptel-1.4.4.patch from the oslec SVN or 
some other patch?

> 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

Just for kicks, try inserting the oslec module by hand (insmod oslec) 
and see if that makes a difference.

  > In my kernel modules/misc directory I have:

<snip>

Hope that helps.

-Dave