Path: utzoo!utgpu!news-server.csri.toronto.edu!mailrus!accuvax.nwu.edu!nucsrl!telecom-request From: john@bovine.ati.com (John Higdon) Newsgroups: comp.dcom.telecom Subject: Re: More ANI Fun! Message-ID: <10376@accuvax.nwu.edu> Date: 3 Aug 90 06:45:27 GMT Sender: news@accuvax.nwu.edu Reply-To: John Higdon Organization: Green Hills and Cows Lines: 22 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 538, Message 2 of 15 Thomas Lapp writes: > Did that also mean that it knew that my LD carrier was MCI or was it > that it gets its info from the same source that MCI does for my LD > billing? When you call an 800 number, it matters not what your default LD carrier is. The call is routed over the carrier that corresponds to the 800 prefix that you dialed. A complete list of carriers vs prefixes was published not long ago in the Digest. For instance, if you try to dial a 10XXX code in front of an 800 number, you will probably get a recording that says that it is not necessary to dial a long distance company code. The fact that you have MCI as a carrier and that this particular number is an MCI InWATS is purely coincidental. ANI is sent to the carrier on all calls from an FGD compliant office. Even from PA. John Higdon | P. O. Box 7648 | +1 408 723 1395 john@bovine.ati.com | San Jose, CA 95150 | M o o !