[asterisk-users] OSLEC and zaptel-1.4.5.1

[Alan Lord]

Dave Fullerton wrote:
> Replies/Comments inline...

Ditto :-)

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

This seems to be most peoples experience with 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.

I might try and "downgrade" to zaptel-1.4.4 and see if that helps.

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

Yep - I manually went through the 1.4.4 patch and ensured it was applied 
cleanly to the zaptel source tree. Like this:

.../* #define ECHO_CAN_MARK2 */
/* #define ECHO_CAN_MARK3 */
/* #define ECHO_CAN_KB1 */
/* This is the new latest and greatest */
/* #define ECHO_CAN_MG2 */
#define ECHO_CAN_OSLEC


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

Yes, clean source. I used the 1.4.4. and it applied cleanly (just with a 
bit of fuzz). I went through and did it manually too - just to make sure.

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

Tried that too!

>   > In my kernel modules/misc directory I have:
> 
> <snip>
> 
> Hope that helps.
> 
> -Dave

Thanks for the comments. It's good to know it does work but perhaps 
there is something in the 1.4.5.1 sources... Think I'll do a quick grep 
for "#define ECHO_CAN_MG2" and see if it being set elsewhere.

Alan


-- 
The way out is open!
http://www.theopensourcerer.com