First of all, check: http://www.ee.washington.edu/conselec/A95/projects/jjblome/links.htm Some info there on interfacing to the telephone line. Most of the other links are dead, but you can at least get a schematic there. If memory serves me correctly, CallerID is implemented by sending a burst of data after the first ring. The data is modulated like a Bell 202A. (Any of you old enough to remember using one of those? ;) Motorola has info on their chip (the same one used in the schematic above available. Point you browser at: http://motorola.com/SPS/MCTG/MDAD/voice_coders/caller_id.html . Also, MX-Com (www.mxcom.com) has a CallerID chip, the MX602A that you can compare with the Motorola part. They both have decent app notes and some sample schematics. The following is from the CallerID FAQ: -------------------------------- Phone gets first ring, duration 2 seconds Delay 0.5 seconds after first ring Send 30 bytes of '01010101', duration 250ms (channel seizure signal) Send 150ms of marks (carrier signal) Send an 8 bit "parameter word type" 00000100 = Caller ID 00001010 = message waiting indicator 10000001 = Test for caller ID Send an 8 bit number representing the number of WORDS in the message Now, the actual data: The first two digits are the month with a leading zero for JAN to SEPt. The next two digits are the day of the month w/leading zero for 1 to 9. The next two digits are the hour in local military time. The next two digits are the minutes in local time. The remaining digits (message length -8) are the telephone number of the calling party. The last field may include the 'P' or 'O' for blocked or out-of-area calls. The last 8 bits of the message are the checksum. The check sum is the two's complement of the modulo 256 sum of the other words in the data message. This sum does not include the channel seizure signal or the carrier signal. Total transmission duration = 718ms ------------------------ Hope this is of some use. I dont have any personal experience with this stuff, I just seem to be able to find the info :) Good luck with your project! Paul Besides what's there, At 10:04 AM 5/3/99 +1000, you wrote: >> Dave Vandenberg (dfv@PARADISE.NET.NZ) >> Sat, 1 May 1999 23:14:02 +1200 > >> Hi Guys >> Do you have any tips on implementing Caller ID? > >snip--- > >> 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). > >Here is a collection of info I have picked up. I am quoting several >messages that have been sent to me in an exchange on the subject, and it >may, or may not interest you, but it's basically everything I could find >out, and it gives you the alternative of possibly using an off the shelf >modem. Depends on you application and finances. > >Many 56k modems sold in Oz and no doubt NZ support caller ID. Just use a >terminal program to issue the command 'AT#CID=1' - this enables caller >ID info to be sent in the normal 'RING' message from the modem. Give it >a call and watch! > >One user told me he has a Netcomm 56k unit - AM3477 - and it works well. >The feature is not documented in the manual, though. It also works well >with the latest versions of 'Winfax Pro'. When a call is received, the >CLI is shown in Winfax's receive log. > >You may not even need to write any database software, unless it is for a >very specific application. There are quite a number of programs >available already. Here are some caller ID programs at winfiles.com in >the misc. telephony section......... > >http://www.winfiles.com/apps/98/phone-misc.html > >There are many more to be found if one searches the net. > >Also, before you buy a 56k modem, check that it supports the CLI >feature. Usually, it won't be in the manual (just like all of the fax >specific AT commands never are), so it's best to test the feature (or >get a friend to do it on their modem). > >Also see this FAQ for lots more details. UK biased, but most of the >principles are the same, and the software works everywhere more or less. >Computer Caller ID FAQ : http://www.cloud9.u-net.com/callerid.htm > >Caller ID units: >The EM924547 is in both the OMNI CA290 and the Uniden Caller ID unit >that are available in OZ. It is the FSK CLI decoder. The Data pin is the >same as the Motorola MC145447. > >Now if any of this helps you to get the 84 going as a caller ID monitor >great. It's all the info I have. >There are two caller ID units on the market in kit form. These are to US >standards however. One was from ITU Technologies (sadly, no longer >available), and the other I seem to have lost the link, but I'm sure a >search will pick it up. > >an a serial LCD? >http://www.dontronics.com/sli.html > >Don McKenzie mailto:don@dontronics.com http://www.dontronics.com > >Don's Download Dungeon: http://www.dontronics.com/download.html >Australian Electronics Ring http://www.dontronics.com/aering.html >Win $500USD Cash. Micro design contest: http://www.simmstick.com Paul Davis Sr. Systems Engineer OEM, Carrier Sales, Healthcare pdavis@nbase-xyplex.com www.nbase-xyplex.com 184 Shuman Blvd., Suite 200 Naperville, IL. 60563 Phone: 630-717-2960 x 3072 FAX: 630-357-4237