Path: utzoo!utgpu!news-server.csri.toronto.edu!rutgers!ucsd!ucbvax!agate!bionet!hayes.ims.alaska.edu!accuvax.nwu.edu!nucsrl!telecom-request
From: werner@rascal.ics.utexas.edu (Werner Uhrig)
Newsgroups: comp.dcom.telecom
Subject: Re: Blocking of Long Distance Calls - Part I
Message-ID: <14319@accuvax.nwu.edu>
Date: 4 Nov 90 10:24:38 GMT
Sender: news@accuvax.nwu.edu
Reply-To: Werner Uhrig <werner@rascal.ics.utexas.edu>
Organization: TELECOM Digest
Lines: 13
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 789, Message 9 of 11


> Instead, I got a recorded voice message stating that the call was a local
> call from my location.  A second attempt got the same recorded message.

This is interesting. Just last month, I had a similar "experience"
dialing some number (I forget which) and, automatically, I switched to
AT&T (my primary is Metromedia ITT, formerly LDS) which completed
without a problem.  I will keep my eyes out for the next AT&T bill to
refresh my memory as to the number and then look into the matter a
little more closely. Gee, wouldn't that be a surprise to find more
instances of this happening. (I suspect I called a customer support
number of some software company, and I would be rather infuriated if
Metromedia kept me from obtaining a needed software update...)