Article View: digex.general
Article #74Re: DIGEX Customer Newsletter
From: John McGing
Date: Sun, 17 Dec 1995 00:00
Date: Sun, 17 Dec 1995 00:00
46 lines
3389 bytes
3389 bytes
On 17 Dec 1995, Dr. Roger M. Firestone wrote:
> The thought that occurs to me in all this Digex bashing is, "Did Digex
> advertise that it had 28.8 modems, or did it advertise 28.8
> _connections_?" I believe that most ISP's advertise that they have 28.8
> modems but don't guarantee the connections will provide that speed. The
> thrust of the criticism of Digex seems to be that it promised something
> that it couldn't deliver. Did it in fact do so? Or did the customer
> assume that 28.8 modems would guarantee 28.8 kbps connections? If the
> latter is the case, then Digex really doesn't deserve the criticism it
> is getting. So what are the facts here?
>
Excuse me? Is this a troll or is this a legitimate but off the wall
inquiry?
Why in ghods name would any service install modems capable of 28.8 if it
wasn't their intent to provide 28.8 service? The legitimate customer
assumption to being told that a POP has 28.8 modems is that the customer
can, with their own 28.8 modem make 28.8 connections, line conditions
being the uncontrollable variable.
And, since you're coming in here very late and a bunch of dollars short,
Digex and customers in Northern Baltimore County spent a lot of time
chasing down bit slipage that was killing 28.8 connectivity to the 605
POP. Why bother working with the customers and BA in finding the bit
slippage and getting it fixed if actually trying to use the modems to
their rated speeds was not something they (Digex) were trying to do?
Until this debacle with the 898 POP and the built in inability to get
28.8 connections due to the design of their comm architecture, Digex has
been a real good provider who did provide and support real 28.8
connections.
The issue from a customers perspective is the moving backwards from a
nicely working 28.8 setup to a "24.x is the best that can be done because
that's the way we designed it" setup. It used to be that whether or not
you got 28.8 was dependent on the line conditions BA provided you the
customer. Now the inability to get 28.8 is the result of the design that
Digex picked to provide the 898 POP connectivity to their main office.
------------------------------------------------------------------
jmcging@access.digex.net Nobody knows the troubles I've seen
JOHN.PF on GEnie Team OS/2 .... and nobody cares!
http://www.access.digex.net/~jmcging
Technical Details
Message-ID:
<Pine.SUN.3.91.951217101800.5031B-100000@access5.digex.net>Path:
arc1-ca.pugleaf.net!unknown!not-for-mailReferences:
<4a6a30$2n2@ss2.digex.net> <4aiq5c$2hk@news4.digex.net> <4ancah$ghq@news.cais.com> <4aruh2$mco@umbc7.umbc.edu> <4b1evr$3qu@zippy.cais.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: 101049,d1501dbbe4ab84f7 X-Google-Attributes: gid101049,public X-Google-Thread: 15ff9f,d1501dbbe4ab84f7 X-Google-Attributes: gid15ff9f,public X-Google-Thread: 109e7a,d1501dbbe4ab84f7 X-Google-Attributes: gid109e7a,public From: John McGing <jmcging@access.digex.net> Subject: Re: DIGEX Customer Newsletter Date: 1995/12/17 Message-ID: <Pine.SUN.3.91.951217101800.5031B-100000@access5.digex.net> X-Deja-AN: 122098842 references: <4a6a30$2n2@ss2.digex.net> <4aiq5c$2hk@news4.digex.net> <4ancah$ghq@news.cais.com> <4aruh2$mco@umbc7.umbc.edu> <4b1evr$3qu@zippy.cais.net> x-sender: jmcging@access5.digex.net content-type: TEXT/PLAIN; charset=US-ASCII organization: Express Access Online Communications, USA mime-version: 1.0 newsgroups: digex.general,digex.slip,balt.general,dc.general