1993-11-13 - Caller ID

Header Data

From: karn@qualcomm.com (Phil Karn)
To: 0811wksh@ties.k12.mn.us
Message Hash: 534399401d057e8b2af856a43afad5f276736580b9aa631e84e6e8ca11c73903
Message ID: <9311130152.AA29949@servo>
Reply To: <Pine.3.05.9311082016.D26586-9100000@tiesnet.ties.k12.mn.us>
UTC Datetime: 1993-11-13 01:53:45 UTC
Raw Date: Fri, 12 Nov 93 17:53:45 PST

Raw message

From: karn@qualcomm.com (Phil Karn)
Date: Fri, 12 Nov 93 17:53:45 PST
To: 0811wksh@ties.k12.mn.us
Subject: Caller ID
In-Reply-To: <Pine.3.05.9311082016.D26586-9100000@tiesnet.ties.k12.mn.us>
Message-ID: <9311130152.AA29949@servo>
MIME-Version: 1.0
Content-Type: text/plain


>I believe the frequencies used for Caller ID are per Bell 202, a straight
>FSK data standard.

This is correct. Before Caller ID came along, about the only group
backward enough to still be using Bell 202 are the amateur packet
radio folks. So if you happen to be a ham with a packet TNC and a lot
of spare time, you could consider reprogramming one to decode caller
ID. Of course, you still have to sign up for the service before the CO
will send you the data.

And if your time is worth anything to you, it'd be better to just buy one
of the modems that already has caller-ID built in.

Phil





Thread