I just ran the command once. I just called one, and I heard myself in the background, but I did not get that message in dmesg. Still, that message about it being disabled worries me because I get really bad echo on SOME calls. I got that disabled echo cancel message 4 times in my dmesg, but I am not sure when those messages appeared.
Tad On 10/4/05, Andrew Kohlsmith <[EMAIL PROTECTED]> wrote: > On Tuesday 04 October 2005 10:59, Tad Heckaman wrote: > > zaptel Disabled echo canceller because of tone (rx) on channel 16 > > I just did dmesg -c and thats what I got... I think there was a call > > allready in progress. Whats that about? > > Was that after the first or second dmesg -c? > > Procedure: > > dmesg -c > place call that will have terrible echo > finish call > dmesg -c > > After the 2nd dmesg -c did you see that message? I'm also assuming a > relatively unloaded system, and if that "on channel 16" was the channel your > call went through (You'll see Zap/16-1 or something to that effect in the * > CLI) then you've identified the problem. > > -A. > _______________________________________________ > --Bandwidth and Colocation sponsored by Easynews.com -- > > Asterisk-Users mailing list > Asterisk-Users@lists.digium.com > http://lists.digium.com/mailman/listinfo/asterisk-users > To UNSUBSCRIBE or update options visit: > http://lists.digium.com/mailman/listinfo/asterisk-users > -- Tad Heckaman _______________________________________________ --Bandwidth and Colocation sponsored by Easynews.com -- Asterisk-Users mailing list Asterisk-Users@lists.digium.com http://lists.digium.com/mailman/listinfo/asterisk-users To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
