From owner-freebsd-isdn@FreeBSD.ORG Mon Nov 5 11:07:00 2007 Return-Path: Delivered-To: freebsd-isdn@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 65A7916A57E for ; Mon, 5 Nov 2007 11:07:00 +0000 (UTC) (envelope-from owner-bugmaster@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 3E4AA13C4AA for ; Mon, 5 Nov 2007 11:07:00 +0000 (UTC) (envelope-from owner-bugmaster@FreeBSD.org) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.1/8.14.1) with ESMTP id lA5B70Fe026345 for ; Mon, 5 Nov 2007 11:07:00 GMT (envelope-from owner-bugmaster@FreeBSD.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.1/8.14.1/Submit) id lA5B6xQf026341 for freebsd-isdn@FreeBSD.org; Mon, 5 Nov 2007 11:06:59 GMT (envelope-from owner-bugmaster@FreeBSD.org) Date: Mon, 5 Nov 2007 11:06:59 GMT Message-Id: <200711051106.lA5B6xQf026341@freefall.freebsd.org> X-Authentication-Warning: freefall.freebsd.org: gnats set sender to owner-bugmaster@FreeBSD.org using -f From: FreeBSD bugmaster To: freebsd-isdn@FreeBSD.org Cc: Subject: Current problem reports assigned to freebsd-isdn@FreeBSD.org 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: Mon, 05 Nov 2007 11:07:00 -0000 Current FreeBSD problem reports Critical problems Serious problems Non-critical problems S Tracker Resp. Description -------------------------------------------------------------------------------- s kern/79117 isdn [iavc] iavc(4) for AVM B1 PCI does not attach 1 problem total. From owner-freebsd-isdn@FreeBSD.ORG Wed Nov 7 16:13:23 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 3CA9416A473 for ; Wed, 7 Nov 2007 16:13:23 +0000 (UTC) (envelope-from michael@askozia.com) Received: from ug-out-1314.google.com (ug-out-1314.google.com [66.249.92.170]) by mx1.freebsd.org (Postfix) with ESMTP id C289113C4BB for ; Wed, 7 Nov 2007 16:13:22 +0000 (UTC) (envelope-from michael@askozia.com) Received: by ug-out-1314.google.com with SMTP id y2so206414uge for ; Wed, 07 Nov 2007 08:13:05 -0800 (PST) Received: by 10.67.20.11 with SMTP id x11mr1054458ugi.1194450467354; Wed, 07 Nov 2007 07:47:47 -0800 (PST) Received: by 10.67.92.17 with HTTP; Wed, 7 Nov 2007 07:47:47 -0800 (PST) Message-ID: Date: Wed, 7 Nov 2007 16:47:47 +0100 From: "Michael Iedema" To: freebsd-isdn@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline Subject: 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: Wed, 07 Nov 2007 16:13:23 -0000 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 - 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? - Are the echocancel/echosquelch options smart enough to only be activated if the "better" of the two is already activated? - Is there a way to tell if a card needs "echocancelold" to be set? - What is the value range for "echotail"? (32, 64, 128, 256?) Thanks in advance for any feedback on this. -Michael I. 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 From owner-freebsd-isdn@FreeBSD.ORG Fri Nov 9 18:38:12 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 ED12B16A46B for ; Fri, 9 Nov 2007 18:38:12 +0000 (UTC) (envelope-from ovb@ovb.ch) Received: from ovbis01.ovb.ch (ovbis01.ovb.ch [213.188.32.144]) by mx1.freebsd.org (Postfix) with ESMTP id BB87513C4B5 for ; Fri, 9 Nov 2007 18:38:10 +0000 (UTC) (envelope-from ovb@ovb.ch) Received: from ovbas07.ovb.ch ([213.180.173.199] helo=[192.168.30.103]) by ovbis01.ovb.ch with esmtpa (Exim 4.68) (envelope-from ) id 1IqYJS-0007zV-Bd for freebsd-isdn@freebsd.org; Fri, 09 Nov 2007 19:10:38 +0100 Message-ID: <4734A29E.2080409@ovb.ch> Date: Fri, 09 Nov 2007 19:10:38 +0100 From: Oliver von Bueren User-Agent: Thunderbird 2.0.0.6 (Windows/20070728) MIME-Version: 1.0 To: freebsd-isdn@freebsd.org References: In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Authenticated-Id: ovb 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: Fri, 09 Nov 2007 18:38:13 -0000 Hi Michael Michael Iedema wrote: > - echosquelch - activates some "light" echo cancellation in the > chan_capi code itself > I have set this to yes in capi.conf (and only this, all others don't work for me at all) Next thing I did to improve the echo situation on calls from IP phones to ISDN is to change a default value in i4b_global.h from 9 to 10: #define I4B_ECHO_CANCEL_P_COMPLEX (10) Without that, it was pretty bad and my wife complained! You'll find this file in /usr/src/sys/i4b/include After the change you have to compile the kernel, I usually do this with: # cd /usr/src # make buildkernel installkernel KERNCONF=YOURKERNEL -DNOCLEAN -DNO_CLEAN" BTW: I've got an AVM Fritz Card on a Point2Point ISDN BRI from our national telco provider. # isdnconfig controller 0 = { Layer 1: description : AVM Fritz!Card PCI type : passive ISDN (Basic Rate, 2xB) channels : 0x3 serial : 0xabcd power_save : on dialtone : enabled attached : yes PH-state : Activate indication (priority=8/9) Layer 2: driver_type : DRVR_DSS1_P2P_TE } The only negative thing I have is that I can't reboot without loosing a channel on the card. After a reboot one channel stays dead. It looks like the initialization of the card isn't reaching the same state after a cold vs. warm reboot. Anyway, I'll have to get something more decent I think. Oliver