[Asterisk-Users] Will Echo problems EVER be solved, I'm scared

[Rich Adamson]

> > I'd suggest turning off echotraining on the FXS altogether, and perhaps 
> > even
> > killing the echocanceller on FXS entirely.  (you won't be getting 
> > significant
> > echo from the FXS, and the FXO should be handling it anyway) -- 
> > echocancelwhenbridged might be an interesting thing to play with as well.
> >
> > e.g. (assuming port 1-3 are FXO and port 4-7 are FXS)
> >
> > echocancel=64
> > echocancelwhenbridged=yes
> > echotraining=800
> > channel => 1-3
> >
> > echocancelwhenbridged=no
> > channel => 4-7
> 
> Andrew,
> 
> I am sure you know that in zapata.conf parameter settings are in effect 
> until specifically overridden later on in the file. In the first paragraph 
> you suggest that I turn off both echotraining and echocanceler on FXS 
> channels, so may I correct your example, that is, do you mean something like 
> the following?:
> 
> echocancel=64
> echocancelwhenbridged=yes
> echotraining=800
> channel => 1-3
> 
> echocancel=no
> echocancelwhenbridged=no
> echotraining=no
> channel => 4-7
> 
> Please correct me if I'm wrong, in your example echocanceler would still run 
> on connections other than TDM (such as FXS->SIP). Did you knowingly mean it? 
> With my additions above, FXS channels would never use echocanceler. Right?
> 
> Thank you guys for all the help and comments. Rich's last comments were 
> quite enlighthening, as always. I never knew echocanceler could be used on 
> FXS channels. Sorry for my ignorance (but nowhere in docs or wiki could I 
> see this information, I should have thought about it, my bad).
> 
> I'll try and post the results.

There are lots of things like this that aren't documented and probably
never will be given the constant upgrades, code additions, etc.

It will be interesting to hear your results. :)