From owner-freebsd-isdn@FreeBSD.ORG Mon Oct 25 11:54:31 2004 Return-Path: Delivered-To: freebsd-isdn@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3BF3816A4CE for ; Mon, 25 Oct 2004 11:54:31 +0000 (GMT) Received: from mail.vtec.ipme.de (C3B3C654.dial.de.easynet.net [195.179.198.84]) by mx1.FreeBSD.org (Postfix) with ESMTP id 45C8C43D45 for ; Mon, 25 Oct 2004 11:54:30 +0000 (GMT) (envelope-from vwerth@vwsoft.com) Received: from [192.168.16.24] (unknown [192.168.16.24]) by bellona.sz.vwsoft.com (Postfix) with ESMTP id 788B45C39; Mon, 25 Oct 2004 12:30:49 +0200 (CEST) Message-ID: <417CD5D9.8020608@vwsoft.com> Date: Mon, 25 Oct 2004 12:30:49 +0200 From: Volker Werth Organization: Volker Werth Software User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.7.2) Gecko/20040822 Thunderbird/0.7+ Mnenhy/0.6.0.101 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Christoph Kukulies References: <200410250702.i9P725gE058017@www.kukulies.org> In-Reply-To: <200410250702.i9P725gE058017@www.kukulies.org> X-Enigmail-Version: 0.85.0.0 X-Enigmail-Supports: pgp-inline, pgp-mime Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit cc: freebsd-isdn@freebsd.org Subject: Re: current i4b status X-BeenThere: freebsd-isdn@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Using ISDN with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 25 Oct 2004 11:54:31 -0000 Chris, well yes, i4b is available under 5-STABLE as it has never been removed. Like under 4-STABLE it's running fine. I've had stability problems (on 6-CURRENT and 5.3-BETA[3..6]) related to locking (Giant) but this problem has been corrected two weeks ago and i4b is working well again under 5.3RC. Probably one problem has been left but I don't know where it's coming from. I'm even unable to tell if it's really a software problem: When using an IbC connection for some hours the connection eventually _may_ be dropped with a statement in the i4b logs as 'call disconnected (local) cause: 0'. Again, I don't know if it's really a bug or if it's i4b or ppp causing or the stars are currently in a bad constellation. It doesn't happen with every long term connection. I still haven't done any further tests also I've not done any troubleshooting. Perhaps I've overseen a timeout value somewhere (my guess). HTH, Volker On 2004-10-25 09:02, Christoph Kukulies wrote: > Hi, > > what is the current status on availablity, stability etc. of i4b under > -current, 5.3RC1 or 5.2.1? > > -- > Chris Christoph P. U. Kukulies kuku_at_kukulies.org > _______________________________________________ > freebsd-isdn@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-isdn > To unsubscribe, send any mail to "freebsd-isdn-unsubscribe@freebsd.org" > -- Volker Werth Software weighing - communication - office - solutions fon: +49-3322-2798920 fax: +49-3322-2798923 web: www.vwsoft.com GPG/PGP fingerprint: 2C9F 37EC A680 B474 D885 9098 7604 5B28 5EEB 374A