I am running CVS HEAD. How can I tell which software echo canceller I am using?<br><br><div><span class="gmail_quote">On 10/28/05, <b class="gmail_sendername">Matthew Fredrickson</b> <<a href="mailto:creslin@digium.com">
creslin@digium.com</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><br>On Oct 27, 2005, at 12:38 AM, <a href="mailto:gw@adcomcorp.com">
gw@adcomcorp.com</a> wrote:<br>> My question is, what is the direction in relation to analog boards and<br>> such?<br><br>Right now, it looks like the current fad of the asterisk group is<br>hardware echo<br>cancelation. However, there is work that is occurring on the software
<br>echo<br>cans to improve them. In fact, I just committed basically an update to<br>KB1<br>(which was until now the latest and greatest version of MEC2) that is<br>supposed<br>to provide somewhat significant improvements.
<br><br>><br>> Quite a few people tend to have difficulties with echo, and although<br>> the<br>> WIKI has some very helpful advice, from a business standpoint I would<br>> think that it would be an important step to come up with a final
<br>> solution to the problem.<br>><br>> Many companies who make the higher end equipment seem to have tackled<br>> the issue on their hardware.<br>><br>> Do we know if digium is spending time on solving the issue? For
<br>> example, having a tool to run on a digium analog or t1 board to analyze<br>> the line statistics and come up with the proper gain settings could be<br>> extremely helpful.<br>><br>> Such a tool would require a firm knowledge of the causes and solutions
<br>> to echo however, but I would assume that digium should have a grasp on<br>> this.<br>><br>> It just seems difficult to suggest to companies to use an asterisk<br>> based<br>> solution (if they do not use pri) when there is the possibility that an
<br>> installation will have issues with echo.<br>><br>> At this point, it feels more like a trial experience to eliminate echo<br>> in various environments.<br><br>Unfortunately, that's the way it is right now. Getting to the point
<br>where you have<br>enough knowledge to be able to work on these things is not an<br>insignificant task.<br>It seems like we're slowly getting there, and now that we have some<br>more interest<br>on improving the software echo cans we might be a little be closer to
<br>getting to the<br>point where it "just works".<br><br>><br>> I have used local tone from the CO to help narrow things down, but a<br>> tool that would loop dial a line and do an analysis could reduce the
<br>> implementation time from days to hours.<br><br>Well, there isn't anything that does the "whole job" right now.<br>There's a bunch<br>of pieces that go together, and if you have the necessary knowledge of
<br>how to<br>put the pieces together, you can get pretty close to it "just working".<br> It's not that<br>bad though, one can also see it as job security as well :-)<br><br>Matthew Fredrickson<br><br>_______________________________________________
<br>--Bandwidth and Colocation sponsored by <a href="http://Easynews.com">Easynews.com</a> --<br><br>Asterisk-Users mailing list<br><a href="mailto:Asterisk-Users@lists.digium.com">Asterisk-Users@lists.digium.com</a><br><a href="http://lists.digium.com/mailman/listinfo/asterisk-users">
http://lists.digium.com/mailman/listinfo/asterisk-users</a><br>To UNSUBSCRIBE or update options visit:<br> <a href="http://lists.digium.com/mailman/listinfo/asterisk-users">http://lists.digium.com/mailman/listinfo/asterisk-users
</a><br></blockquote></div><br>