Path: utzoo!utgpu!news-server.csri.toronto.edu!mailrus!cs.utexas.edu!samsung!zaphod.mps.ohio-state.edu!sdd.hp.com!decwrl!hayes.fai.alaska.edu!accuvax.nwu.edu!nucsrl!telecom-request
From: yilmazer@suns01.UUCP (Sedat Yilmazer)
Newsgroups: comp.dcom.telecom
Subject: Re: Caller-ID Again
Message-ID: <10848@accuvax.nwu.edu>
Date: 14 Aug 90 05:58:30 GMT
Sender: news@accuvax.nwu.edu
Reply-To: yilmazer@suns01.Nowhere (Sedat Yilmazer)
Organization: Alcatel Austria, Vienna
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 10, Issue 569, Message 11 of 12


In article <10793@accuvax.nwu.edu> dave%westmark@uunet.uu.net (Dave
Levenson) writes:

>With the introduction of Caller*ID service, however, crank calls have
>all but disappeared in this area.

At the cost of the callers privacy!  Here in Vienna I got, up to
now, no crank calls. So if you implement this feature in here, at least
for me, it would mean the violation of the callers privacy.

So if you are receiving crank calls , let there be a feature to trace
back that call.


Sedat Yilmazer   | Tel:  277222465
Alcatel Austria  | telex 277222146
Scheydg 41 A-1211| Home  2679825  


[Moderator's Note: Yes! I said in the last issue that the Caller ID
discussion was concluded in the Digest for the time being. This
message arrived as the last issue was going out. Our correspondent
from Austria could not have known, so his item is appearing. But this
is it for now!  Please no more Caller ID for a couple months.   PAT]