Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!sun-barr!lll-winken!decwrl!hayes.fai.alaska.edu!accuvax.nwu.edu!nucsrl!telecom-request
From: bryanr@ihlpy.att.com (Bryan M Richardson)
Newsgroups: comp.dcom.telecom
Subject: Re: MCI Cable Cut Disrupts Thousands of Calls
Message-ID: <13174@accuvax.nwu.edu>
Date: 8 Oct 90 16:26:40 GMT
Sender: news@accuvax.nwu.edu
Organization: AT&T Bell Laboratories
Lines: 23
Approved: Telecom@eecs.nwu.edu
X-Submissions-To: telecom@eecs.nwu.edu
X-Administrivia-To: telecom-request@eecs.nwu.edu
X-Telecom-Digest: Volume 10, Issue 723, Message 7 of 12


In article <13027@accuvax.nwu.edu> you write:

>The overflow of calls from MCI on Wednesday went mostly to AT&T, with
>some of the traffic going to Sprint. The overflow caused the AT&T
>network throughout the northeast to be sluggish and very slow most of
>the day.

How do you mean "sluggish?"  Either calls complete or they don't-- the
switches do not queue them up in long lines.  I didn't hear any
reports of network congestion.


Bryan Richardson
AT&T Bell Laboratories


[Moderator's Note: My experience that day was that while some calls
got rejected with fast busy signals, others simply got lost in
transit. That is, they wandered away into dead silence, no ring/no
busy. After a waiting period of maybe fifteen or twenty seconds, I'd
simply abandon the call and dial over.  PAT]