Path: utzoo!telecom-request Date: Thu, 25 Apr 1991 23:48:46 GMT From: Peter Creath Newsgroups: comp.dcom.telecom Subject: Re: Per Line Blocking? Message-ID: Organization: A small corner of Hell Sender: Telecom@eecs.nwu.edu 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 307, Message 2 of 12 Lines: 34 In article , herrickd@iccgcc.decnet.ab. com writes: > I also want them to stop LYING and calling it "caller id" when it is > CALLING STATION id. > But, then, the advocates here in this forum think of it as caller id > and describe a great variety of uses that work only when knowing the > calling station happens to identify the calling party. > I can imagine a product that reads the caller id (sic) data and looks > the number up in an internal directory and displays a caller name from > the directory. Because the directory was entered by the owner of the > product, it would show my son's name as the caller. Any time he was > persona non grata, I would have great difficulty getting through. According to the most recent issue of {Popular Science} (in the What's New - Electronics section), they said a new box for Caller ID is now available, one which displays the callers NAME as well as phone number. Now, it didn't specify whether the name was transmitted by the Caller ID system or whether the owner of the box had to program in names and numbers. peterc@taronga.hackercorp.com peterc@taronga.uucp.ferranti.com (same thing...) [Moderator's Note: Well I would rather suspect the owner of the box has to load the information matching certain numbers and names. How would telco know who was calling? All they can say for sure is the number. PAT]