Path: utzoo!utgpu!news-server.csri.toronto.edu!rutgers!cs.utexas.edu!mailrus!accuvax.nwu.edu!nucsrl!telecom-request
From: dave%westmark@uunet.uu.net (Dave Levenson)
Newsgroups: comp.dcom.telecom
Subject: Re: Using the "O" Operator to Defeat 800 ANI and Caller*ID
Message-ID: <9529@accuvax.nwu.edu>
Date: 9 Jul 90 01:13:09 GMT
Sender: news@accuvax.nwu.edu
Organization: Westmark, Inc., Warren, NJ, USA
Lines: 20
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 470, Message 1 of 10


In article <9481@accuvax.nwu.edu>, riot!slr@csvax.caltech.edu writes:

> On a related question: For those of you with Caller*ID, what happens
> when you get a call routed through the "O" operator ?  (the called
> party being someone that you would normally get a calling number from
> on your Caller*ID display).

Here in New Jersey, local calls placed through the operator are
displayed as "OUT OF AREA" on the Caller*ID display.  This makes them
indistinguishable from calls which originate out of the LATA or from
CO's which are not equipped with SS7.  This is also true of calls
dialed as 0+ and charged to a calling card, without any communication
with a human operator.


Dave Levenson			Voice: 201 647 0900  Fax: 201 647 6857
Westmark, Inc.			UUCP: {uunet | rutgers | att}!westmark!dave
Warren, NJ, USA			AT&T Mail: !westmark!dave
[The Man in the Mooney]