Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!usc!zaphod.mps.ohio-state.edu!rpi!bu.edu!telecom-request
From: larson@snmp.sri.com (Alan Larson)
Newsgroups: comp.dcom.telecom
Subject: Caller-ID Technical Question
Message-ID: <74363@bu.edu.bu.edu>
Date: 8 Feb 91 23:49:17 GMT
Sender: news@bu.edu.bu.edu
Organization: TELECOM Digest
Lines: 25
Approved: Telecom@eecs.nwu.edu
X-Submissions-To: telecom@eecs.nwu.edu
X-Administrivia-To: telecom-request@eecs.nwu.edu
X-Telecom-Digest: Volume 11, Issue 104, Message 6 of 9


  As I understand it, Caller-ID works by sending the information out
after the first or second ring.  Why doesn't it send it out before the
first ring, so the phone could know if it was to ring at all.

  That would leave a great market for pre-programmed boxes to modify
the ring signal to indicate when selected numbers were calling, to
selectively ignore numbers, or to automatically route the calls to fax
or modem equipment.

  It seems kind of obvious, why wouldn't it be done that way?

	Alan


[Moderator's Note: I do not think the intent of Caller*ID is to tell
folks what calls NOT to accept (Call Screening is intended for that).
I think its purpose is merely to *identify* the origin of the call in
the event you wish to know that information. In other words, do not
choose to answer or not based on what the Caller*ID box displays --
remember the many examples of someone you want to talk to calling from
a different phone than usual -- but instead, answer the phone as you
normally would and use the identification provided for recourse to the
caller if desired.  PAT]