From owner-freebsd-isdn@FreeBSD.ORG Thu Nov 8 22:43:39 2007 Return-Path: Delivered-To: freebsd-isdn@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 2A77416A41A for ; Thu, 8 Nov 2007 22:43:39 +0000 (UTC) (envelope-from hselasky@c2i.net) Received: from swip.net (mailfe05.swip.net [212.247.154.129]) by mx1.freebsd.org (Postfix) with ESMTP id B00C213C48D for ; Thu, 8 Nov 2007 22:43:38 +0000 (UTC) (envelope-from hselasky@c2i.net) X-Cloudmark-Score: 0.000000 [] Received: from [85.19.218.45] (account mc467741@c2i.net [85.19.218.45] verified) by mailfe05.swip.net (CommuniGate Pro SMTP 5.1.13) with ESMTPA id 581389023; Thu, 08 Nov 2007 22:43:19 +0100 From: Hans Petter Selasky To: freebsd-isdn@freebsd.org Date: Thu, 8 Nov 2007 22:43:47 +0100 User-Agent: KMail/1.9.7 References: In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200711082243.48348.hselasky@c2i.net> Cc: Subject: Re: echo cancellation / suppression in chan_capi & isdn4bsd by HPS X-BeenThere: freebsd-isdn@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Using ISDN with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 08 Nov 2007 22:43:39 -0000 Hi Michael, On Wednesday 07 November 2007, Michael Iedema wrote: > Greetings everyone, > > I'm trying to understand what options are available to me regarding > echo cancellation and suppression in chan_capi and isdn4bsd from HPS > (http://www.turbocat.net/~hselasky/isdn4bsd/). > > Great software, just trying to understand it a bit more thoroughly. > > In the chan_capi code, I see references to: > - echo cancellation in hardware > - echo cancellation in software > - echo suppression in software > > I understand the chan_capi options to mean: > - echocancel - activates hardware echo cancellation if it is > available or software echo cancellation in the i4b driver if it is > not. > - echosquelch - activates some "light" echo cancellation in the > chan_capi code itself The "echocancelold" can just be ignored. It is not used within I4B. > - echocancelold - must be activated for older cards not supporting the > new echo cancellation method > - echotail - echo can tap count > > Here's what I'm still not clear on: > - What do the g164, g165 and force options cause on the "echocancel" line? Try google. Setting these does not affect anything currently. > - Are the echocancel/echosquelch options smart enough to only be > activated if the "better" of the two is already activated? No. > - Is there a way to tell if a card needs "echocancelold" to be set? You don't need to set it. > - What is the value range for "echotail"? (32, 64, 128, 256?) Currently has no effect. It should set the number of samples or milliseconds that the echo cancel filter should cover. --HPS