Path: utzoo!attcan!uunet!cs.utexas.edu!yale!mintaka!ogicse!decwrl!hayes!accuvax.nwu.edu!nucsrl!telecom-request From: asuvax!gtephx!mothra!bakerj@ncar.ucar.edu (Jon Baker) Newsgroups: comp.dcom.telecom Subject: Re: Caller-ID Theory and Operation Message-ID: <8578@accuvax.nwu.edu> Date: 1 Jun 90 17:21:41 GMT Sender: news@accuvax.nwu.edu Organization: gte Lines: 28 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 409, Message 9 of 14 In article <8448@accuvax.nwu.edu>, ssid@mtuxo.att.com (Sameer Siddiqui) writes: > - Is it a propriatary service/product? Do you mean is only AT&T allowed to manufacture equipment that offers it, or is only Bell allowed to offer it? No. Anyone can manufacture equipment that provides CID, and any telco can offer it. > - Is it available or going to be available nationwide? The capability to offer it will be available nationwide (i.e. nationwide deployment of SS7). It may not be available in some areas due to regulatory or judicial intervention. Certainly some backwater areas will be slower to acquire the technology ... > - Is it part of ISDN service? No. > - Do you need the decoder/display box or can you get a PC to do the work? With the proper interfacing equipment, you could get a PC to do it. Redcom in Rochester, N.Y., markets an interface that connects to lines, trunks, T1, etc., and reports activity on such devices through an RS-232. This device does detect FSK tones, so could be used to detect and report Caller ID.