Path: utzoo!utgpu!news-server.csri.toronto.edu!mailrus!accuvax.nwu.edu!nucsrl!telecom-request
From: Harry Skelton <jando!tons61!hskelton@uunet.uu.net>
Newsgroups: comp.dcom.telecom
Subject: Re: More ANI Fun!
Message-ID: <10500@accuvax.nwu.edu>
Date: 6 Aug 90 10:35:47 GMT
Sender: news@accuvax.nwu.edu
Reply-To: Harry Skelton <tons61!harrys@uunet.uu.net>
Organization: U.S. Dept. of Transportation
Lines: 16
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 545, Message 5 of 15


In article <10425@accuvax.nwu.edu> davidb@pacer.uucp (David Barts)
writes:

>>Anyway, here it is:  1-800-666-6258.

I tried this from an FTS line and it reported a totally different
number than the one I was at. To see if the "other" number reported
would get to my phone I called it! Guess what ... got "This number is
not in service" (DOT message).

Great! Now the sales hounds can't locate me via 800# call back! 8-)

I wonder if this holds true for all other FTS accesses? Perhaps
someone could try it with caller ID!