Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!usc!apple!agate!telecom-request From: kaufman@Neon.Stanford.EDU (Marc T. Kaufman) Newsgroups: comp.dcom.telecom Subject: Re: Caller*ID Operation in Ottawa, Ontario Message-ID: Date: 24 Feb 91 02:40:02 GMT Sender: usenet@agate.berkeley.edu (USENET Administrator) Organization: Computer Science Department, Stanford University Lines: 15 Approved: Telecom@eecs.nwu.edu X-Telecom-Digest: Volume 11, Issue 154, Message 8 of 12 X-Submissions-To: telecom@eecs.nwu.edu X-Administrivia-To: telecom-request@eecs.nwu.edu In article fred@aficom.ocunix.on.ca (Fred Ennis) writes: > Someone was also asking earlier about the means of encoding the > Caller*ID string. It's in ASCII and passed by a Bell 202 modem. Most > of the computer modems around now are Bell 212 at 1200 baud, which > doesn't help in decoding Caller*ID. That's OK. The standard modem for amateur packet radio is a Bell 202 (or equivalent). Packet TNCs (Terminal Node Controllers) could probably be converted quite easily for Caller*ID use. Marc Kaufman (kaufman@Neon.stanford.edu)