Path: utzoo!utgpu!jarvis.csri.toronto.edu!clyde.concordia.ca!uunet!cs.utexas.edu!mailrus!accuvax.nwu.edu!nucsrl!telecom-request
From: claris!netcom!onymouse@ames.arc.nasa.gov (John Debert)
Newsgroups: comp.dcom.telecom
Subject: Re: Speaking of Security Codes
Message-ID: <4520@accuvax.nwu.edu>
Date: 28 Feb 90 04:32:40 GMT
Sender: news@accuvax.nwu.edu
Organization: NetCom- The Bay Area's Public Access Unix System {408 249-0290}
Lines: 27
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 132, Message 6 of 12


In article <4416@accuvax.nwu.edu>, john@bovine.ati.com (John Higdon) says:
X-Telecom-Digest: Volume 10, Issue 129, Message 6 of 9
 
> John G Dobnick <jgd@csd4.csd.uwm.edu> writes:
 
>> My question to you good folks on this list is: Can remote access be
>> totally supressed on this beastie?  I see no way to do so.  If this
>> _is_ mentioned in the manual, it isn't obvious to me.
 
> There is no way, short of tampering with the unit's firmware, to
> defeat the remote feature. This is a major shortcoming with this
> otherwise good product. The only suggestion would be to change the
> code daily :-)

This is reference to an answering machine, no?

One way is to open it up and remove the tone decoder chip - whichever
one is used in your particular machine.

I've noted a comment in misc.security about the ability to make an
answering machine make "untraceable" calls. I tried this on my machine
without success. It mutes all DTMF tones.


jd
onymouse@netcom.UUCP