From owner-freebsd-isdn Mon Dec 24 17: 5:51 2001 Delivered-To: freebsd-isdn@freebsd.org Received: from iafrica.com (cpt-dial-196-30-178-55.mweb.co.za [196.30.178.55]) by hub.freebsd.org (Postfix) with ESMTP id A17BA37B41B for ; Mon, 24 Dec 2001 17:05:46 -0800 (PST) Received: (from ayon@localhost) by noya (8.11.6/8.11.6) id fBNJZtQ12833 for freebsd-isdn@FreeBSD.org; Sun, 23 Dec 2001 21:35:55 +0200 (SAST) (envelope-from ayon) Date: Sun, 23 Dec 2001 21:34:29 +0200 From: Francois Kritzinger To: freebsd-isdn@FreeBSD.org Subject: Re: i4b/isdnd panic on incoming call Message-ID: <20011223213429.A12821@noya> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i Sender: owner-freebsd-isdn@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Hi, I'd just like to report back on the problem I was having a couple of months ago (in the 04-Nov-2001 section of the list archives). I said I was going to dial up in Windows to see whether it was indeed my local phone exchange that was corrupting the incoming frames, or whether it was my setup. Well, I dialled in on Windows for many weekends after that, and the connection stayed open without a problem. However, I have since upgraded to FreeBSD 4.4 (I was using 4.3) which includes i4b 1.something (I was using i4b 0.96), and now the connection is pretty much perfect. Thanks again for the help, and sorry for not reporting back sooner. -- Francois To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isdn" in the body of the message