fred@aficom.ocunix.on.ca (Fred Ennis) (02/23/91)
We have Caller*ID operating here in Ottawa, ON and I can answer a couple of the questions that have been posted about the number passed to the subscriber when calls originate from PBX locations. It has been my experience that individual trunks are identified and occasionally these are "phantom" numbers that don't allow you to call back. On key systems, individual CO lines are identified. Cellular calls generate an UNKNOWN NUMBER. Most interestingly, telemarketing calls from Bell's OWN telemarketing centre also trigger an UNKNOWN NUMBER display! (sneaky, eh?) 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.
kaufman@Neon.Stanford.EDU (Marc T. Kaufman) (02/24/91)
In article <telecom11.153.3@eecs.nwu.edu> 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)
faunt@cisco.com (Doug Faunt N6TQS 415-688-8269) (02/25/91)
The newest AMRAD newsletter had a homebrew Caller*ID demonstration circuit.