<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
</head>
<body bgcolor="#ffffff" text="#000000">
Tzafrir Cohen wrote:
<blockquote id="mid_20080604172002_GE11544_xorcom_com"
cite="mid:20080604172002.GE11544@xorcom.com" type="cite">
<pre wrap="">On Thu, Jun 05, 2008 at 03:00:01AM +1000, Rob Hillis wrote:
</pre>
<blockquote id="StationeryCiteGenerated_1" type="cite">
<pre wrap="">Brent Davidson wrote:
</pre>
<blockquote id="StationeryCiteGenerated_2" type="cite">
<pre wrap="">We're currently using Asterisk 1.4.19, Zaptel 1.4.10,
Oslec SVN, Rhino R4FXO-EC cards, and Snom 300 Phones.
</pre>
</blockquote>
<pre wrap="">Why on earth are you running two layers of echo cancellation - hardware
and software? To be honest, I think this is asking for trouble - I've
seen two occasions where having Oslec and hardware echo cancellation has
caused significant problems with audio quality - the usual symptoms are
gaps in the conversation as the hardware cancellation eliminates the
majority of the echo and the software cancellation subsequently
eliminates parts of the conversation.
</pre>
</blockquote>
<pre wrap=""><!---->
If you use a hardware EC (or technically: a span-specific echo
cancellation method) the generic Zaptel echo canceller (software-based,
OSLEC in this case) will not be used.
</pre>
</blockquote>
<br>
<br>
Is there any indication of this in Zaptel? This is the output of my
ztcfg -vv:<br>
<br>
Zaptel Version: 1.4.10<br>
Echo Canceller: Oslec<br>
Configuration<br>
======================<br>
<br>
<br>
Channel map:<br>
<br>
Channel 01: FXS Kewlstart (Default) (Slaves: 01)<br>
Channel 02: FXS Kewlstart (Default) (Slaves: 02)<br>
<br>
2 channels to configure.<br>
<br>
I removed Oslec when I first installed the R4FXO-EC cards, but echo was
terrible and made the calls unusable. My gut instinct is telling me
that my hardware echo cancellation is not working.<br>
<br>
Thanks,<br>
Brent<br>
</body>
</html>