Hi, I've tried all the other methods of dispelling the x100p echo mystery such as echo training rx tx gain through ztmon and swapping POTS lines etc etc. Can someone mail me a step by step guide to changing the echo cancellation algorithms such as Mark,Mark2, Steve etc. Muchos! Taff. --------------------------------- Yahoo! Messenger - Communicate instantly..."Ping" your friends today! Download Messenger Now -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.digium.com/pipermail/asterisk-users/attachments/20040321/1db4d86e/attachment.htm
> I've tried all the other methods of dispelling the x100p echo mystery > such as echo training rx tx gain through ztmon and swapping POTS lines > etc etc. Can someone mail me a step by step guide to changing the echo > cancellation algorithms such as Mark,Mark2, Steve etc.There isn't much to the step-by-step -- in the ztconfig.h file you will see the various echo cancellation algorithm defines: /* * Pick your echo canceller: MARK2, MARK3, STEVE, or STEVE2 :) */ /* #define ECHO_CAN_STEVE */ /* #define ECHO_CAN_STEVE2 */ /* #define ECHO_CAN_MARK */ #define ECHO_CAN_MARK2 /* #define ECHO_CAN_MARK3 */ In the example MARK2's defined. The general consensus is that MARK2's the best, IIRC. There is also the agressive cancellation code, which I think practically everyone wants but it breaks things like POS machines and faxes, although I think now if the driver hears a fax tone it will disable the aggressive code: /* * Uncomment for aggressive residual echo supression under * MARK2 echo canceller */ /* #define AGGRESSIVE_SUPPRESSOR */ Once you've made the changes, save 'em and make clean && make && make install. Regards, Andrew
> I've tried all the other methods of dispelling the x100p echo mystery such > as echo training rx tx gain through ztmon and swapping POTS lines etc etc. > Can someone mail me a step by step guide to changing the echo cancellation > algorithms such as Mark,Mark2, Steve etc.I spent a fair amount of time back in the October/November timeframe mucking around with echo problems. I had substantial issues with it at that time. Mark made some changes based on lots of complaints back in that timeframe. One of the things that is not at all clear (in postings and other doc) is that changes made to the zapata.conf file "must" be followed by a total restart of asterisk. That includes changes to rxgain, txgain, etc. A reload does not cause the x100p driver to re-read zapata.conf. I've been running with Dec 4th version of the zapata CVS and the following x100p config, and echo is just barely perceptable during the first half second or so of a call. context=inbound-home switchtype=national signalling=fxs_ks echotraining=yes usecallerid=yes hidecallerid=no callwaiting=yes callwaitingcallerid=no threewaycalling=no echocancel=yes echocancelwhenbridged=yes rxgain=-0.0 txgain=-0.0 callgroup=2 immediate=no callprogress=no musiconhold=default channel => 1 Rich