🚀 go-pugleaf

In article <esmythe-1112951938460001@nesbitt.digex.net>,
Erich Smythe <esmythe@access.digex.net> wrote:
>In article <4ahmuo$sr2@access4.digex.net>, moobox@access4.digex.net (Moo's
>Access Point) wrote:
>
>[deleted]
>> 
>> People seem to have this very bizarre notion that:
>> 
>>         A) Bell Atlantic can be told what to do
>> 
>>         B) There is significant competition for BA dial-tone
>>            services in the areas we serve.
>> 
>> B is conditionally true; there is competition for dial-tone and other 
>> services, via MFS and other carriers, but I doubt MFS or Teleport is
>> going to unconditionally promise to deliver 28.8K analog dial up because
>> if a call crosses from BA to MFS or Telport and there's a SLC in the 
>> middle... <slice>
>
>That's the rub.  Even if Digex can get the bandwidth to support 28.8k
>delivered to their door, it won't do some of us any good.  In my case, no
>matter what Digex does I'm just not going to get 28.8 to Greenbelt.  I
>have more than three miles of analog copper between me and the first
>switch, and that switch is, guess what, a SLC.  I'm happy if I get 24K.

I have 6 or 7 miles (minimum) of copper from this location to the Central 
Office, and have a solid 28.8 connection right now to the 605-2700 
dialin. I also routinely get 28.0 or 28.8 to other services thoughout the 
Baltimore area.


>The V.34 protocol is designed to exploit a line with characteristics that
>exceed tariff specs.   You will only get full throughput if the path
>between you and the other modem is significantly better than what the
>phone company is required to provide.  

And in many cases it is.

I have the following questions for Digex:

1. Since Digex found out about the bandwidth problem, what action(s) have 
been taken?

2. Has Digex attempted to request BA replace the SLC, even at Digex's 
cost, to improve service for Baltimore area users?

3. Has Digex investigated locating equipment or telco interfaces at 
another location,in order to improve service for Baltimore area users?

4. What are Digex's short and long term plans (if any) for bringing 
Baltimore service up to the level required by customers?

Other ISPs should view this as an excellent opportunity to grab a chunk 
of Digex's market. Work with BA, get a decent telco interface, and offer 
users top notch service. 

I can't speak for others, but a lot of my frustration comes from the fact 
that Digex took the one working Baltimore dialin (605-2700) away from 
SLIP users. I've started running TIA from that dialin again, since I can 
get much better performance. Kinda ironic that I get much better 
performance from a "fake" SLIP service than the real thing. 

Chris