Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!utgpu!water!watmath!clyde!rutgers!rochester!bbn!husc6!mit-eddie!ll-xn!ames!ucbcad!ucbvax!DEEP-THOUGHT.MIT.EDU!S.PAE
From: S.PAE@DEEP-THOUGHT.MIT.EDU.UUCP
Newsgroups: comp.dcom.telecom
Subject: Error reporting by MCI
Message-ID: <12338634437.12.S.PAE@DEEP-THOUGHT.MIT.EDU>
Date: Tue, 29-Sep-87 23:43:16 EDT
Article-I.D.: DEEP-THO.12338634437.12.S.PAE
Posted: Tue Sep 29 23:43:16 1987
Date-Received: Sat, 3-Oct-87 05:10:13 EDT
Sender: daemon@ucbvax.BERKELEY.EDU
Distribution: world
Organization: The ARPA Internet
Lines: 12
Approved: telecom@buit1.bu.edu

I recently attempted to make a long-distance call with MCI. The call did not
go through; the recording suggested that I call MCI and check on the status
of my account. The MCI account rep. didn't notice anything wrong with th
account. She did try the number I was calling and verified that it was just
a wrong number.

This seems an exceedingly cumbersome (and costly) mechanism for a LD carrier
to handle a wrong number. Is there some technical reason that MCI is doing
so badly, or is this broken for the normal reason?

--phil
-------