From owner-freebsd-hackers Sat Aug 9 17:56:43 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id RAA23966 for hackers-outgoing; Sat, 9 Aug 1997 17:56:43 -0700 (PDT) Received: from dyson.iquest.net (dyson.iquest.net [198.70.144.127]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id RAA23961; Sat, 9 Aug 1997 17:56:39 -0700 (PDT) Received: (from root@localhost) by dyson.iquest.net (8.8.6/8.8.5) id TAA00209; Sat, 9 Aug 1997 19:56:32 -0500 (EST) From: "John S. Dyson" Message-Id: <199708100056.TAA00209@dyson.iquest.net> Subject: Re: ISDN drivers/cards In-Reply-To: from Tom Samplonius at "Aug 9, 97 05:41:23 pm" To: tom@sdf.com (Tom Samplonius) Date: Sat, 9 Aug 1997 19:56:32 -0500 (EST) Cc: dyson@freebsd.org, joerg_wunsch@uriah.heep.sax.de, hackers@freebsd.org, jamil@counterintelligence.ml.org Reply-To: dyson@freebsd.org X-Mailer: ELM [version 2.4ME+ PL31 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > > > I was involved/tracking the various ISDN standards. NI-1 is pathetic, mostly > > due to the non-AT&T switch manufacturers very lame implementations. Other > > switch manufacturers have been holding back progress. NI-2 is better, but > > I'm aware of anyone using NI-2 on BRI. I'm pretty sure NI-2 is only for > PRI. I'm not aware of any end-user device that can do NI-2 on BRI either. > NI-2 is also meant for BRI, mostly with new auto-provisioning features. NI-3 might contain better call control across multiple BRI's. PRI's many times don't provide features, even though vendors are working on it. PRI's often supply PBX's which provide the feature set. (Often, not always.) John