Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!sdd.hp.com!uakari.primate.wisc.edu!dali!ogicse!decwrl!hayes!accuvax.nwu.edu!nucsrl!telecom-request
From: asuvax!gtephx!mothra!bakerj@ncar.ucar.edu (Jon Baker)
Newsgroups: comp.dcom.telecom
Subject: Re: Defeating 800 ANI & Caller*ID Using the "O" Operator
Message-ID: <8573@accuvax.nwu.edu>
Date: 1 Jun 90 19:09:01 GMT
Sender: news@accuvax.nwu.edu
Organization: gte
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 409, Message 5 of 14


In article <8427@accuvax.nwu.edu>, slr@dhw68k.cts.com (Steve L.
Rhoades) writes:

> My question: Is this just a fluke ?  Is there some type of convention
> for TOPS to pass the calling number to the 800 service provider ?  Has
> anyone else tried this ?  Does it work elsewhere ?

Your number is being passed (via ANI) to TOPS.  TOPS *should* pass the
caller's number back to the originating CO via ANI.  If the
originating CO has SS7 or ANI trunks to the 800 carrier, then the
originating CO *should* forward your number to the 800 carrier.

Possible causes :

  1. TOPS is not passing the digits back to the CO;
  2. the originating CO does not have ANI/SS7 trunks to the 800 carrier;
  3. the originating CO does have such trunks, but for some reason is not
     forwarding your number.

Since your number does usually get passed on, that should rule out #2.
Someone who knows more about TOPS could address #1.  If you know what
type of CO you are served by, we might be able to address #3.  --