From owner-freebsd-isdn@FreeBSD.ORG Thu Feb 17 21:55:52 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 2483B16A4CE for ; Thu, 17 Feb 2005 21:55:52 +0000 (GMT) Received: from rproxy.gmail.com (rproxy.gmail.com [64.233.170.201]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8F36743D3F for ; Thu, 17 Feb 2005 21:55:51 +0000 (GMT) (envelope-from jgale.work@gmail.com) Received: by rproxy.gmail.com with SMTP id a41so387873rng for ; Thu, 17 Feb 2005 13:55:51 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:mime-version:content-type:content-transfer-encoding; b=iwDYUWU63GJZwUmSG0ZBlbG5PCYHa+sw0CEciXZENRtvEMYTl3jS8rd6BFvTeZrzE7OIXknp5lacK+IPF0CqBl6uaG7YmO+Ij+8GDVK/iwFoGlRiiqiU7J0nLDPvcf6W9YEIxwC97ZBS29F3zCFHW0MrJapYpnym2UaqOjDWSVU= Received: by 10.38.73.16 with SMTP id v16mr42318rna; Thu, 17 Feb 2005 13:55:50 -0800 (PST) Received: by 10.38.71.63 with HTTP; Thu, 17 Feb 2005 13:55:50 -0800 (PST) Message-ID: <1a4ba29305021713554b46170a@mail.gmail.com> Date: Thu, 17 Feb 2005 14:55:50 -0700 From: Jeremy Gale To: freebsd-isdn@freebsd.org Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Subject: Network Interfaces and PRI questions X-BeenThere: freebsd-isdn@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: Jeremy Gale List-Id: Using ISDN with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 17 Feb 2005 21:55:52 -0000 Hi all, I'm pretty new to ISDN and i4b but I'm supposed to be writing a NetBSD driver for a custom hardware ISDN-based card. I'm trying to evaluate if I can use the i4b framework. Our card needs to be able to support multiple trunks - both multiple BRIs and PRIs. We are planning to use a Cologne chip for BRIs and a IDT chip for PRIs. 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? How is the PRI support in i4b? It looks like the PRI support is #if 0'd out in NetBSD but functional in FreeBSD in the iavc driver. Any thoughts on the feasibility of doing this? Is there anywhere else I can read more high-level information on ISDN network interfaces? I've read The Care and Feeding of ISDN4BSD but any other resources would be appreciated. Thanks very much in advance! Jeremy From owner-freebsd-isdn@FreeBSD.ORG Thu Feb 17 22:03:15 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 A7A3F16A4CF for ; Thu, 17 Feb 2005 22:03:15 +0000 (GMT) Received: from mail.duskware.de (mail.duskware.de [213.146.108.170]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9554643D4C for ; Thu, 17 Feb 2005 22:03:14 +0000 (GMT) (envelope-from martin@duskware.de) Received: by mail.duskware.de (Postfix, from userid 205) id 6F8D833B00; Thu, 17 Feb 2005 23:03:12 +0100 (CET) Date: Thu, 17 Feb 2005 23:03:12 +0100 From: Martin Husemann To: Jeremy Gale Message-ID: <20050217220311.GC18968@drowsy.duskware.de> References: <1a4ba29305021713554b46170a@mail.gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1a4ba29305021713554b46170a@mail.gmail.com> User-Agent: Mutt/1.4.2.1i cc: freebsd-isdn@freebsd.org Subject: Re: Network Interfaces and PRI questions 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: Thu, 17 Feb 2005 22:03:15 -0000 On Thu, Feb 17, 2005 at 02:55:50PM -0700, 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? Nope, those are just potential users of B channels. There is no network interface associated with a call itself, but once you start speaking PPP on top, you get a ippp interface. > 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. What is the problem here? This interface are going to be clonabel soon (it's realy a bug that they are not yet) > Or does it represent more of a > physical ISDN connection between two endpoints? No, it's just a carrier for network configuration. You do not need to use them at all (like userland ppp does). > How is the PRI support in i4b? AFAIK it's functional, at least with the iavc driver. Martin From owner-freebsd-isdn@FreeBSD.ORG Thu Feb 17 23:30:58 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 550A616A4CE for ; Thu, 17 Feb 2005 23:30:58 +0000 (GMT) Received: from mandy.eunet.fi (mandy.eunet.fi [193.66.1.129]) by mx1.FreeBSD.org (Postfix) with ESMTP id C040A43D4C for ; Thu, 17 Feb 2005 23:30:57 +0000 (GMT) (envelope-from jml@cubical.fi) Received: from snorkkeli.homeip.net (ip212-226-169-74.adsl.kpnqwest.fi [212.226.169.74]) by mandy.eunet.fi (Postfix) with ESMTP id 037BF13E713; Fri, 18 Feb 2005 01:30:54 +0200 (EET) Received: from [192.168.2.252] (wazoo.koti2.net [192.168.2.252]) j1HNUrma011575; Fri, 18 Feb 2005 01:30:53 +0200 (EET) In-Reply-To: <1a4ba29305021713554b46170a@mail.gmail.com> References: <1a4ba29305021713554b46170a@mail.gmail.com> Mime-Version: 1.0 (Apple Message framework v619.2) Content-Type: text/plain; charset=US-ASCII; format=flowed Message-Id: <74fbe7179f95b1dd47d3d76da38557ea@cubical.fi> Content-Transfer-Encoding: 7bit From: Juha-Matti Liukkonen Date: Fri, 18 Feb 2005 01:31:00 +0200 To: Jeremy Gale X-Pgp-Agent: GPGMail 1.0.2 X-Mailer: Apple Mail (2.619.2) cc: freebsd-isdn@freebsd.org Subject: Re: Network Interfaces and PRI questions 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: Thu, 17 Feb 2005 23:30:58 -0000 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi! On 17.2.2005, at 23:55, Jeremy Gale wrote: > How is the PRI support in i4b? It looks like the PRI support is #if > 0'd out in NetBSD but functional in FreeBSD in the iavc driver. We (Cubical) are using the iavc PRI support actively in our products on FreeBSD (I'm actually the original author of the capi and iavc support for i4b). I don't know why the T1 initialization code is #if 0'd out in NetBSD-current (dev/pci/iavc_pci.c) - perhaps the PRI support has simply not been tested on NetBSD? The code seems functional enough. I do know that PRI interfaces are quite expensive, and even we do not have one available for testing purposes. Which means that you may get by just removing the #if 0... but I can guarantee it works well in FreeBSD out of the box :-) Br, Juha - -- Juha-Matti Liukkonen - Systems Architect, Cubical Solutions Ltd tel: +358-40-5280142 e-mail: jml@cubical.fi -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (Darwin) iD8DBQFCFSk0KDUn3bh7M9gRAvuMAKDt4RxfATW9Mni1JvMBq7Xf1pP+rwCfVqYY BDwxy8kUN72ix+xTOiAG6M4= =MfvT -----END PGP SIGNATURE----- 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