Article 30785 of comp.dcom.telecom.tech: From: "Jennifer \"Jassyfer\" Martino" Newsgroups: comp.dcom.telecom.tech Subject: Re: Need tech info caller ID Date: Fri, 24 Apr 1998 22:46:00 -0500 Organization: Ameritech.Net http://www.ameritech.net/ Lines: 248 Message-ID: <35415C78.8B9B03E1@ameritech.net> References: Reply-To: jmartino@ameritech.net NNTP-Posting-Host: dyn1-tnt6-82.chicago.il.ameritech.net Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="------------9B4E9CDC0FFCC20C9354269E" X-Mailer: Mozilla 4.04 [en] (Win95; I) Path: news1.meer.net!nntp2.ba.best.com!news1.best.com!nntprelay.mathworks.com!ais.net!ameritech.net!not-for-mail This is a multi-part message in MIME format. --------------9B4E9CDC0FFCC20C9354269E Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit TechBook wrote: -- NOTE: E-mail address ROT-13 encypted to foil evil spammers. "The Web Page You Have Reached" http://www.ameritech.net/users/jmartino/index.html Telephone sounds/recordings No annoying ads, banners or pop-ups! Who is that guy Archangel whose name is all over alt.2600? http://newbie.darkridge.com/ --------------9B4E9CDC0FFCC20C9354269E Content-Type: text/plain; charset=us-ascii; name="A Basic CND (Caller ID) Specification 1.txt" Content-Transfer-Encoding: 7bit Content-Disposition: inline; filename="A Basic CND (Caller ID) Specification 1.txt" Newsgroups: alt.2600 Distribution: world X-Comment-To: All From: Tommy Date: Tue, 24 Mar 98 09:30:56 -0800 Subject: A Basic CND (Caller ID) Specification. Message-ID: <890731878@f26.n340.z1.ftn> Organization: Tommy's 250-361-4549 V.34 35000 Textfiles X-FTN-FLAGS: PVT TRN X-FTN-AREA: ALT.2600 X-FTN-Tearline: GoldED 2.40 X-FTN-Origin: Tommy's 250-361-4549 V.34 35000 Textfiles (1:340/26) X-FTN-SEEN-BY: 340/13 26 X-FTN-PATH: 340/26 X-FTN-PATH: 340/13 Path: mil.ameritech.net!ameritech.net!ais.net!newsfeed.direct.ca!news.bctel.net!news.pinc.com!news.spydernet.com!f13.n340!f303.n340!not-for-mail Xref: mil.ameritech.net alt.2600:196407 If my previous posts including live CID data proving that *67 does block number and name transmission won't put this stupidity to bed, then maybe this will. Standard Disclaimer: I didn't write this, I didn't even go to Comdex '91. ------------------------8<-------------------------------------------------- This is a copy of the data sheet picked up at the Rockwell booth at the COMDEX show (1991?). INTRODUCTION Calling Number Delivery (CND), better known as Caller ID, is a telephone service intended for residential and small business customers. It allows the called Customer Premises Equipment (CPE) to receive a calling party's directory number and the date and time of the call during the first 4 second silent interval in the ringing cycle. The customer must contact a Bellcore Client Company to initiate CND service. According to Pacific Bell representatives, the following states and district currently support CND service: Delaware, District of Columbia, Florida, Georgia, Idaho, Kentucky, Louisiana, Maine, Maryland, Nebraska, Nevada, New Jersey, Oklahoma, Tennessee, Vermont, Virginia, and West Virginia. The following states are scheduled to support CND service by April, 1992: Alaska, Arizona, California, Colorado, Illinois, Indiana, Iowa, Massachusetts, Mississippi, New Hampshire, New York, North Carolina, North Dakota, Ohio, Oregon, Rhode Island, and South Carolina. PARAMETERS The data signalling interface has the following characteristics: Link Type: 2-wire, simplex Transmission Scheme: Analog, phase-coherent FSK Logical 1 (mark) 1200 +/- 12 Hz Logical 0 (space) 2200 +/- 22 Hz Transmission Rate: 1200 bps Transmission Level: 13.5 +/- dBm into 900 ohm load (I have copied this data as presented. I believe the transmission level is meant to be -13.5 dBm.) PROTOCOL The protocol uses 8-bit data words (bytes), each bounded by a start bit and a stop bit. The CND message uses the Single Data Message format shown below. Channel Carrier Message Message Data Checksum Seizure Signal Type Length Word(s) Word Signal Word Word CHANNEL SEIZURE SIGNAL The channel seizure is 30 continuous bytes of 55h (01010101) providing a detectable alternating function to the CPE (i.e. the modem data pump). CARRIER SIGNAL The carrier signal consists of 130 +/- 25 mS of mark (1200 Hz) to condition the receiver for data. MESSAGE TYPE WORD The message type word indicates the service and capability associated with the data message. The message type word for CND is 04h (00000100). MESSAGE LENGTH WORD The message length word specifies the total number of data words to follow. DATA WORDS The data words are encoded in ASCII and represent the following information: o The first two words represent the month o The next two words represent the day of the month o The next two words represent the hour in local military time o The next two words represent the minute after the hour o The calling party's directory number is represented by the remaining words in the data word field If the calling party's directory number is not available to the terminating central office, the data word field contains an ASCII "O". If the calling party invokes the privacy capability, the data word field contains an ASCII "P". CHECKSUM WORD The Checksum Word contains the twos complement of the modulo 256 sum of the other words in the data message (i.e., message type, message length, and data words). The receiving equipment may calculate the modulo 256 sum of the received words and add this sum to the reveived checksum word. A result of zero generally indicates that the message was correctly received. Message retransmission is not supported. EXAMPLE CND SINGLE DATA MESSAGE An example of a received CND message, beginning with the message type word, follows: 04 12 30 39 33 30 31 32 32 34 36 30 39 35 35 35 31 32 31 32 51 04h= Calling number delivery information code (message type word) 12h= 18 decimal; Number of data words (date,time, and directory number words) ASCII 30,39= 09; September ASCII 33,30= 30; 30th day ASCII 31,32= 12; 12:00 PM ASCII 32,34= 24; 24 minutes (i.e., 12:24 PM) ASCII 36,30,39,35,35,35,31,32,31,32= (609) 555-1212; calling party's directory number 51h= Checksum Word DATA ACCESS ARRANGEMENT (DAA) REQUIREMENTS To receive CND information, the modem monitors the phone line between the first and second ring bursts without causing the DAA to go off hook in the conventional sense, which would inhibit the transmission of CND by the local central office. A simple modification to an existing DAA circuit easily accomplishes the task. (I will mail the Rockwell data sheet, which includes the suggested schematic diagram.) MODEM REQUIREMENTS Although the data signalling interface parameters match those of a Bell 202 modem, the receiving CPE need not be a Bell 202 modem. A V.23 1200 bps modem receiver may be used to demodulate the Bell 202 signal. The ring indicate bit (RI) may be used on a modem to indicate when to monitor the phone line for CND information. After the RI bit sets, indicating the first ring burst, the host waits for the RI bit to reset. The host then configures the modem to monitor the phone line for CND information. (I'm skipping some Rockwell-specific information here.) According to Bellcore specifications, CND signalling starts as early as 300 mS after the first ring burst and ends at least 475 mS before the second ring burst APPLICATIONS Modem manufacturers will soon be implementing new modem features based on CND information as this service becomes widely available. Once CND information is received the user may process the information in a number of ways. 1. The date, time, and calling party's directory number can be displayed. 2. Using a look-up table, the calling party's directory number can be correlated with his or her name and the name displayed. 3. CND information can also be used in additional ways such as for: a. Bulletin board applications b. Black-listing applications c. Keeping logs of system user calls, or d. Implementing a telemarketing data base REFERENCES For more information on Calling Number Delivery (CND), refer to Bellcore publications TR-TSY-000030 and TR-TSY-000031. To obtain Bellcore documents contact: Bellcore Customer Service 60 New England Avenue, Room 1B252 Piscataway, NJ 08834-4196 (908) 699-5800 ---------------------8<----------------------------------------------------- Note: At the very beginning it is stated that Caller ID is meant for "residential and small business" customers. Which means it's NOT meant for law enforcement, big business, the telco itself, 800 subscribers, yada yada. THOSE guys have realtime ANI which looks, walks, talks, and quacks like Caller ID but which uses a different (older) system called ANI (automated number identification) which is unaware of, and unaffected by, Caller ID privacy features like *67 and per-line blocking. THAT is why 911 operators know where you are already, not because of what would amount to a major flaw in the Caller ID system... -=( T )=- www.vvv.com/~tommy --------------9B4E9CDC0FFCC20C9354269E-- Article 30786 of comp.dcom.telecom.tech: From: "Jennifer \"Jassyfer\" Martino" Newsgroups: comp.dcom.telecom.tech Subject: Re: Need tech info caller ID Date: Fri, 24 Apr 1998 22:46:41 -0500 Organization: Ameritech.Net http://www.ameritech.net/ Lines: 113 Message-ID: <35415CA1.26C4D244@ameritech.net> References: Reply-To: jmartino@ameritech.net NNTP-Posting-Host: dyn1-tnt6-82.chicago.il.ameritech.net Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="------------595BED9E8CC547ECEB8C2A7A" X-Mailer: Mozilla 4.04 [en] (Win95; I) Path: news1.meer.net!nntp2.ba.best.com!news1.best.com!nntprelay.mathworks.com!ais.net!ameritech.net!not-for-mail This is a multi-part message in MIME format. --------------595BED9E8CC547ECEB8C2A7A Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit TechBook wrote: -- NOTE: E-mail address ROT-13 encypted to foil evil spammers. "The Web Page You Have Reached" http://www.ameritech.net/users/jmartino/index.html Telephone sounds/recordings No annoying ads, banners or pop-ups! Who is that guy Archangel whose name is all over alt.2600? http://newbie.darkridge.com/ --------------595BED9E8CC547ECEB8C2A7A Content-Type: text/plain; charset=iso-8859-1; name="Caller ID and 67 - The Facts 1.txt" Content-Transfer-Encoding: 8bit Content-Disposition: inline; filename="Caller ID and 67 - The Facts 1.txt" Newsgroups: alt.2600 Distribution: world X-Comment-To: All From: Tommy Date: Tue, 24 Mar 98 16:12:58 -0800 Subject: Caller ID and *67 - The Facts Message-ID: <890755994@f26.n340.z1.ftn> Organization: A BBS Somewhere, with a phone number. X-FTN-FLAGS: PVT TRN X-FTN-AREA: ALT.2600 X-FTN-Tearline: GoldED 2.40 X-FTN-Origin: A BBS Somewhere, with a phone number. (1:340/26) X-FTN-SEEN-BY: 340/13 26 X-FTN-PATH: 340/26 X-FTN-PATH: 340/13 Path: mil.ameritech.net!ameritech.net!ais.net!newsfeed.direct.ca!news.bctel.net!news.pinc.com!news.spydernet.com!f13.n340!f303.n340!not-for-mail Xref: mil.ameritech.net alt.2600:196404 OK, it's time to shovel the bullshit which is piling up in this newsgroup about Caller ID. A few people are saying that when you block your Caller ID with *67, the switch sends your number anyway along with a so-called "private bit" that tells the Caller ID display unit to suppress display of the number. That is pure undeodorized BULLSHIT, and in order to squelch those who'd rather flame back with "show me proof" than just read a FAQ, here is the proof. These are actual raw data captures from a Bell 202 demodulator (better known as a serial port Caller ID) which I captured myself today. They prove conclusively that the "Private Bit" is a myth. Here is what I got in my raw data stream when I called my voice line from one of my BBS lines (which is unlisted, hence the PRIVATE string in the name field): UUUUUUUUUUUUUUUUUUUUUUUUUUUUUU€'^A^H03241512^A2503806467^G^OPRIVATE x This is what I got when I did the same thing with *67: UUUUUUUUUUUUUUUUUUUUUUUUUUUUUU€^P^A^H03241512^D^AO^H^AP(˙ The number I was calling from was 250-380-6467. That string is clearly displayed in the first (non *67) call. In the number field of the second call, only the letter "O" is transmitted. In the name field, only the letter "P" is transmitted. In both calls, the date and time (03/24, 15:12) is transmitted, but transmission of the calling telephone number is suppressed in the second call. There is no "private flag" suppressing display of the number by the display unit; the calling number is not transmitted at all! For those of you unfamiliar with the CID raw data stream, the U's are actually sync pulses (an ASCII "U" is 01010101 binary). The control characters are field delimiters. The first 8-digit number is the date and time in MMDDHHSS format. The second number in the first call is the phone number, in NPANXXXXXX format. That is followed by the name (for those of us with name & number CID). The ^O (0Fh) just before the name indicates how many characters are in the name - in this case "PRIVATE" is padded out with 8 spaces (20h) to make 15 characters. At the very end is an 8-bit checksum. By the way, BC Tel apparently incorrectly sends an "O" in the number field, which would explain why my regular Caller ID device displays blocked calls as "Out of Area." Grrr. -=( T )=- Tommy, Sysop, THC BBS +1 250 361 4549, +1 250 380 6467, +1 250 360 0628 www.vvv.com/~tommy/hp.htm --------------595BED9E8CC547ECEB8C2A7A--