At 23:14 1/05/99 +1200, you wrote:
>Hi Guys
>Do you have any tips on implementing Caller ID?
>
>There's a few features I feel are missing from current CID units which I
>personally want to build. Also my NZCE Electronics (polytech) course
>requires a project soon, so I thought I'd kill two birds with one stone. Who
>knows, someone else may need one too.
>
>Questions:
>- What are the code requirements to I/F to a CID chip?
>I don't know what protocol the CID-chip spits the data out in,
>is it relatively simple serial-type data, or real messy to bit-bang?
>
>- Is the CID format [date,time,number...] standard, or could the US standard
>I've read a few things on be different than implemented here in New Zealand?
>
>Also..
>- Lcd display (I saw a PICListers website do this serially)
>- I'll need to store number/name... data - i2c eeprom?
>- Audio caller announcement (I have ISD1020 ChipCorder).
>
>- What should I be aware of when interfacing several devices...
>ie. parallel data & address decoding vs. several SIPO shift reg's,
>timing and co-ordination seems a not too tall order here on the surface
>(famous last words :) etc... (Oh, & will this fit in an 'F84?)
>
>Thanks in advance for any help/advice/suggestions,
>David Vandenberg
>
>dfv@paradise.net.nz
>
>

There are several possible formats for CID, it seems that NZ may have
followed the Aust format. Check to see if NZ is using ALCATEL type 12
exchanges (If so then signaling will be the same). Mitel have a very good
CID chip that handles the BA, US and Aust formats for signaling (Formats
are also supplied), however if you need more information on the exact
contents (Some extra goodies that many be included in the undocumented
area) then you will have to contact the carrier.

You will also find that some modems eg. Netcoms 56K have CID in-built the
AT command I don't know, but may provide some help.

Dennis