From: dan@milliways.org (Dan Bailey)
To: SudduthLM@SecureC2.com
Message Hash: 161087ac85957eaa2d1b28c58916f959b188666e60b312258ed91ae193800a9b
Message ID: <199601131511.PAA06506@pop01.ny.us.ibm.net>
Reply To: N/A
UTC Datetime: 1996-01-13 15:22:11 UTC
Raw Date: Sat, 13 Jan 1996 23:22:11 +0800
From: dan@milliways.org (Dan Bailey)
Date: Sat, 13 Jan 1996 23:22:11 +0800
To: SudduthLM@SecureC2.com
Subject: Re: Reach out! Update 01 (CypherPurists trash this)
Message-ID: <199601131511.PAA06506@pop01.ny.us.ibm.net>
MIME-Version: 1.0
Content-Type: text/plain
Regarding the *67 feature to disable Caller ID:
This does not stop your ANI information from travelling with your
call. It just sets the "privacy bit" to on. So standard
consumer-grade Caller ID systems won't see your number. But if the
user on the other end is receiving your call over a T1, they can use a
Dialogic voice processing card to yield your ANI, even with the
privacy bit set.
A *much* better way to do this is the following:
Dial the Operator.
Ask him/her to dial the 800 number for you.
This will result in your ANI being (000) 000-5555 (or at least that's
what it does in Bell Atlantic land). I tested this a couple months
ago using AT&T's 1-800-MY-ANI-IS service. I directly dialed
1-800-MY-ANI-IS and it read back my phone number. Then I had the
operator dial it for me and got (000) 000-5555. This service doesn't
work anymore, YMMV.
Dan
***************************************************************
#define private public dan@milliways.org
Worcester Polytechnic Institute and The Restaurant at the End of the
Universe
***************************************************************
Return to January 1996
Return to “dan@milliways.org (Dan Bailey)”
1996-01-13 (Sat, 13 Jan 1996 23:22:11 +0800) - Re: Reach out! Update 01 (CypherPurists trash this) - dan@milliways.org (Dan Bailey)