home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!usc!rpi!crdgw1!rdsunx.crd.ge.com!rdsunx.crd.ge.com!trsnyder
- From: trsnyder@mcs.drexel.edu (Bob Snyder)
- Newsgroups: alt.privacy
- Subject: Re: Op-ed piece on telephone Caller ID
- Message-ID: <TRSNYDER.93Jan22083545@vf0031.mcs.drexel.edu>
- Date: 22 Jan 93 13:35:45 GMT
- References: <9301131346.AA27534@gull.cs.rochester.edu>
- <1993Jan20.010456.20340@samba.oit.unc.edu> <C14sKI.I8n@cs.uiuc.edu>
- <k2_sn!f@dixie.com>
- Sender: usenet@crd.ge.com (Required for NNTP)
- Distribution: usa
- Organization: ASCI
- Lines: 16
- In-Reply-To: jgd@dixie.com's message of Thu, 21 Jan 93 05:56:53 GMT
- Nntp-Posting-Host: vf0031.astro.ge.com
-
- >>>>> "John" == John De Armond <jgd@dixie.com> writes:
-
- John> The only part missing is giving me the ability to automatically block
- John> incoming calls originating from caller*ID-blocked lines. Given
- John> that, we are in full agreement. I currently implement that policy
- John> administratively by observing the caller*ID box and not answering
- John> blocked calls. What I really want is for the ringer to never actuate
- John> if the caller*ID is blocked.
-
- Look in Sears' big catalog. They have a caller ID unit which will route all
- incoming blocked calls to a message stating that Blocked calls aren't accepted.
- Also has 50 number memory, does names if your telco supports it... I haven't
- used it myself, but it looks quite nice, and at apx. $80, not too much
- different than what Bell Atlantic sold me my puny little display for. :-)
-
- Bob
-