1993-11-17 - Re: modem taps/caller id

Header Data

From: Stanton McCandlish <mech@eff.org>
To: Martin.Greifer@f28.n125.z1.FIDONET.ORG (Martin Greifer)
Message Hash: 89c6900bf9a943284746306299d141715aa6c1b56a587447b22535d83cab737e
Message ID: <199311170122.UAA02039@eff.org>
Reply To: <4110.2CE1DFEC@shelter.FIDONET.ORG>
UTC Datetime: 1993-11-17 01:24:14 UTC
Raw Date: Tue, 16 Nov 93 17:24:14 PST

Raw message

From: Stanton McCandlish <mech@eff.org>
Date: Tue, 16 Nov 93 17:24:14 PST
To: Martin.Greifer@f28.n125.z1.FIDONET.ORG (Martin Greifer)
Subject: Re: modem taps/caller id
In-Reply-To: <4110.2CE1DFEC@shelter.FIDONET.ORG>
Message-ID: <199311170122.UAA02039@eff.org>
MIME-Version: 1.0
Content-Type: text/plain


> > Practical Peripherals sells a modem that also captures Caller ID info
> > and makes   it available to your comm program.  I've also seen devices
> > that do this for   sale in the back of BBS magazines.
> 
> The question is, how does a caller block this feature?

Depends on the locality, but generally you have 2 options: temporarily
disable it with a *code, or get all-call-blocking.  In most areas, as far
as I know all-call-blocking (so you don't have to enter the *code for
every call) is a "special service" or "extra feature" and costs you more. 
This is of course utterly ludicrous, but that's what you'd expect from
semi-monopolies.

-- 
Stanton  McCandlish  mech@eff.org  1:109/1103   EFF  Online  Activist & SysOp
O P E N  P L A T F O R M   C R Y P T O P O L I C Y   O N L I N E  R I G H T S
N  E  T  W  O  R  K  I  N  G      V  I  R  T  U  A  L     C  U  L  T  U  R  E
I   N   F  O :  M   E   M   B   E   R   S   H   I   P  @  E  F  F  .  O  R  G




Thread