From owner-freebsd-isdn@FreeBSD.ORG Fri Feb 18 17:19:57 2005 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 AC4A816A4CE for ; Fri, 18 Feb 2005 17:19:57 +0000 (GMT) Received: from swip.net (mailfe05.swip.net [212.247.154.129]) by mx1.FreeBSD.org (Postfix) with ESMTP id 84BB143D2F for ; Fri, 18 Feb 2005 17:19:56 +0000 (GMT) (envelope-from hselasky@c2i.net) X-T2-Posting-ID: Y1QAsIk9O44SO+J/q9KNyQ== Received: from mp-217-198-86.daxnet.no ([193.217.198.86] verified) by mailfe05.swip.net (CommuniGate Pro SMTP 4.2.9) with ESMTP id 104975440; Fri, 18 Feb 2005 18:19:54 +0100 From: Hans Petter Selasky To: freebsd-isdn@freebsd.org, Jeremy Gale Date: Fri, 18 Feb 2005 18:20:35 +0100 User-Agent: KMail/1.7 References: <1a4ba29305021713554b46170a@mail.gmail.com> In-Reply-To: <1a4ba29305021713554b46170a@mail.gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200502181820.36340.hselasky@c2i.net> Subject: Re: Network Interfaces and PRI questions X-BeenThere: freebsd-isdn@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: hselasky@c2i.net List-Id: Using ISDN with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 18 Feb 2005 17:19:57 -0000 On Thursday 17 February 2005 22:55, Jeremy Gale wrote: > > One thing I'm still not clear on... what does a network interface > (i4bipr/i4bisppp or irip/ippp in NetBSD-ese) represent? Does it > represent an ISDN call? If you want a call on each B-channel of an > ISDN BRI, does that mean you should have two devices, e.g. i4bipr0 and > i4bipr1? This is an important consideration for me because it could > mean literally hundreds of interfaces. Or does it represent more of a > physical ISDN connection between two endpoints? Layer1 provides one or more channels at any rate. Layer4 can connect each of those channels to a "driver+unit" eg. tel0, tel1, rbch0, rbch1; Mulitiplexing more than one channel into the same driver is not supported. But maybe you can create "dummy drivers" that ignore the unit number when setting up a channel, so save memory? In my ISDN driver you can call the the function "i4b_setup_driver" to connect a (controller+channel) to a (driver+unit) from anywhere. Be aware that I4B versions up to 1.0 does not support more than one D-channel driver, which is DSS1, except if you are using CAPI! If you want to use another protocol on the "D-channel" you need to use my version of I4B available from: http://home.c2i.net/hselasky/isdn4bsd/privat/temporary/ Also my driver has generic support for Cologne chip NT+TE mode. Currently I've only ported it for FreeBSD, but there are macros in the source code to enable execution in a non-mutex oriented environment. So it might compile on NetBSD with some tweaks. Yours --HPS