Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!tut.cis.ohio-state.edu!att!att!westmark!dave
From: dave@westmark.WESTMARK.COM (Dave Levenson)
Newsgroups: comp.dcom.modems
Subject: Re: Modems capturing caller-ID?
Message-ID: <2194@westmark.WESTMARK.COM>
Date: 30 Dec 90 00:44:44 GMT
References: <6562.2772E8C7@zswamp.fidonet.org> <1822@blackbird.afit.af.mil> <3709.277b6b4e@hayes.uucp>
Organization: Westmark, Inc., Warren, NJ, USA
Lines: 25

In article <3709.277b6b4e@hayes.uucp>, tnixon@hayes.uucp writes:
> My understanding is that it is possible to have an outgoing trunk 
> group set up to ANI/Caller-ID to a single number -- that is, for 
> Caller-ID purposes, they'd all  display the same number, which could 
> be the main INCOMING number of the company.  Certainly makes a lot 
> more sense than having it ID as a number that you can't even call 
> back!

Here in NJ we have had Caller*ID service for a couple of years.  The
number you receive is sometimes the main inbound number, sometimes a
fictitious 'billing number' which you cannot call back, sometimes
the actual trunk number of the outbound trunk (sometimes you can
call it and reach the PBX attendant, sometimes no answer), and
sometimes the actual extension number (if the caller is using
Centrex).  What it comes down to is that with Caller*ID, there are
lots of options, and you can't design a system that expects only one
of them to work.

Also, at least for the present time, any call from outside your LATA
is displayed only as "OUT OF AREA".
-- 
Dave Levenson			Internet: dave@westmark.com
Westmark, Inc.			UUCP: {uunet | rutgers | att}!westmark!dave
Warren, NJ, USA			AT&T Mail: !westmark!dave
[The Man in the Mooney]		Voice: 908 647 0900  Fax: 908 647 6857