Article View: digex.general
Article #50Re: SLCs, Digex and BA (Was: Re: DIGEX Customer Newsletter)
From: Jim Jagielski
Date: Tue, 19 Dec 1995 00:00
Date: Tue, 19 Dec 1995 00:00
41 lines
3152 bytes
3152 bytes
doug@ss2.digex.net (Doug Humphrey) writes: >In article <4aq3m1$9jb@shado.jaguNET.com>, >Jim Jagielski <jim@jaguNET.com> wrote: >>However, you could blame Digex for using this technique to handle remote >>calling areas. >Your understanding of our situation is not clear - we are not using >this to avoid putting in POPs - we are being FORCED to use this as the >way that BA gets 2000 dialtones into the building that we are in. Other >dialup providers will hit this wall if they grow to the point where they >need to have that many lines in a single place, and there is not enough >copper to handle it, and they are using POTS (plain old telephone service) >lines. Every single phone line into our facility here uses this technology >from BA, even the voice lines and dialups that are served out of the Central >Office about 500 yards away. Ahhh... that was the part I wasn't sure about. You're right; BA is behind the times when it comes to being able to provide a large number of dialtones to one location (at a reasonable cost that is... T1s to a channel bank don't make sense all the time). Not only that, but their preference (which most of the time you _can't_ avoid) is to provide 2 copper conductors per line, which is a supreme waste and a clear indication of things not scaling directly and optimally. The technology for getting rid of all that copper most definately exists, but BA either drags their feet or makes it incredibly expensive. Of I course I hate to break it to everyone, but it's only gonna get worse fellas. As more and more RBOCs switch totally over to digital, you'll see your bandwidth drop down even more, since the voice-compression technology that works so well with voice plays havoc with data. Some implementations are so bad that you can't even get a 14.4k link ! Of course, this is all good for the phone co's, since they can either charge you for another "data grade" line or ISDN or similar. -- Jim Jagielski << jim@jaguNET.com >> | "Wind the frog!" ** jaguNET Access Services ** | - Woody (from Toy Story) ++ Email: info@jaguNET.com +++ Voice: 410-931-3157 ++ ++ http://www.jaguNET.com/ +++ Data: 410-931-7060 ++
Technical Details
Message-ID:
<4b72vs$6eb@shado.jaguNET.com>Path:
arc1-ca.pugleaf.net!unknown!not-for-mailReferences:
<4a6a30$2n2@ss2.digex.net> <ACF4CA5B966843BEA@ehrice.his.com> <4apsfr$rr8@news4.digex.net> <4aq3m1$9jb@shado.jaguNET.com> <4b4rk6$i7v@ss2.digex.net>Show Full Headers
Complete Article Headers
X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: 10a9ce,d1501dbbe4ab84f7 X-Google-Attributes: gid10a9ce,public X-Google-Thread: 15ff9f,d1501dbbe4ab84f7 X-Google-Attributes: gid15ff9f,public X-Google-Thread: 109e7a,d1501dbbe4ab84f7 X-Google-Attributes: gid109e7a,public X-Google-Thread: 101049,d1501dbbe4ab84f7 X-Google-Attributes: gid101049,public From: jim@jaguNET.com (Jim Jagielski) Subject: Re: SLCs, Digex and BA (Was: Re: DIGEX Customer Newsletter) Date: 1995/12/19 Message-ID: <4b72vs$6eb@shado.jaguNET.com> X-Deja-AN: 122356980 references: <4a6a30$2n2@ss2.digex.net> <ACF4CA5B966843BEA@ehrice.his.com> <4apsfr$rr8@news4.digex.net> <4aq3m1$9jb@shado.jaguNET.com> <4b4rk6$i7v@ss2.digex.net> organization: jaguNET Access Services - MD ISP, 410-931-3157 reply-to: jim@jaguNET.com newsgroups: digex.general,digex.slip,balt.general,dc.general