From owner-freebsd-isp Mon Aug 26 01:46:48 1996 Return-Path: owner-isp Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id BAA27987 for isp-outgoing; Mon, 26 Aug 1996 01:46:48 -0700 (PDT) Received: from sasami.jurai.net (root@sasami.jurai.net [206.151.208.162]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id BAA27982 for ; Mon, 26 Aug 1996 01:46:43 -0700 (PDT) Received: from localhost (winter@localhost) by sasami.jurai.net (8.7.5/8.7.3) with SMTP id DAA00491; Mon, 26 Aug 1996 03:45:29 -0500 (CDT) Date: Mon, 26 Aug 1996 03:45:29 -0500 (CDT) From: "Matthew N. Dodd" To: Joe Greco cc: freebsd-isp@freebsd.org Subject: Re: 128k ISDN vs. T1 In-Reply-To: <199608251355.IAA29158@brasil.moneng.mei.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-isp@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Sun, 25 Aug 1996, Joe Greco wrote: > ISDN PRI? You are suggesting multiplexing > 2 ISDN B's? Eeeeccch... > > I think I have to agree with the original poster... since "technically > possible" and "something you would want to do" are two very different things. We've got unmetered ISDN here, so its not something I wouldn't consider doing, under the right circumstances. Get something like a Pipeline 400B or a Max 1800 and you could have a total of 8 or 16 B channels to use in your MPP call to your provider. I think for some applications, this would be pretty slick with a bandwidth on demand setup running. You could nail up 1 B channel and configure each end to bring up more when there was the need for them. Since FT1 isn't tariffed here, this is an option I would consider. I'd be more likely to suggest FR, but some cusotmers have this thing for ISDN. *shrug* Have a good one. | Matthew N. Dodd | winter@jurai.net | http://www.jurai.net/~winter | | Technical Manager | mdodd@intersurf.net | http://www.intersurf.net | | InterSurf Online | "Welcome to the net Sir, would you like a handbasket?"|