Post by thread:RES: [EE] Alarm Reporting

Can anyone tell me where I can find the specifications for having an alarm panel report to a central monitoring station? I am looking for the Contact ID protocol to be exact. Any help is appreciated. Thanks Shawn CONFIDENTIALITY NOTICE: This message, including any attachments, is for the sole use of the intended recipients and may contain confidential and privileged information. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient, please contact the sender by reply e-mail and destroy all copies of the original message. To learn more about Lifeline Systems, Inc. please visit us at http://www.lifelinesys.com or Lifeline Systems Canada, Inc. at http://www.lifelinecanada.com

On Tue, 2006-01-17 at 08:57 -0500, Shawn Yates wrote: > Can anyone tell me where I can find the specifications for having an > alarm panel report to a central monitoring station? I am looking for > the Contact ID protocol to be exact. Any help is appreciated. I may be wrong, but considering how competitive that market is, I'm quite certain that the protocols are all proprietary and not compatible with each other, and are surely not something you are meant to be able to find in the public domain. TTYL ----------------------------- Herbert's PIC Stuff: http://repatch.dyndns.org:8383/pic_stuff/

www.siaonline.org/response.asp?c=store&l=2&r=1024 In the Industry Standards dropdown look for SIA DC-05-1999.09 - DCS Ademco Contact ID Standard Randy Shawn Yates wrote: {Quote hidden}>Can anyone tell me where I can find the specifications for having an >alarm panel report to a central monitoring station? I am looking for >the Contact ID protocol to be exact. Any help is appreciated. > >Thanks >Shawn > >CONFIDENTIALITY NOTICE: >This message, including any attachments, is for the sole use of the intended recipients and may contain confidential and privileged information. >Any unauthorized review, use, disclosure or distribution is prohibited. >If you are not the intended recipient, please contact the sender by reply e-mail and destroy all copies of the original message. > > > >To learn more about Lifeline Systems, Inc. please visit us at http://www.lifelinesys.com or Lifeline Systems Canada, Inc. at http://www.lifelinecanada.com > > > > > > >

On Tue, 17 Jan 2006, Herbert Graf wrote: > On Tue, 2006-01-17 at 08:57 -0500, Shawn Yates wrote: >> Can anyone tell me where I can find the specifications for having an >> alarm panel report to a central monitoring station? I am looking for >> the Contact ID protocol to be exact. Any help is appreciated. > > I may be wrong, but considering how competitive that market is, I'm > quite certain that the protocols are all proprietary and not compatible > with each other, and are surely not something you are meant to be able > to find in the public domain. Most simpler systems dial into the center and send DTMF codes. One can program just about anything to be sent. Peter

Peter wrote: {Quote hidden}>On Tue, 17 Jan 2006, Herbert Graf wrote: > > > >>On Tue, 2006-01-17 at 08:57 -0500, Shawn Yates wrote: >> >> >>>Can anyone tell me where I can find the specifications for having an >>>alarm panel report to a central monitoring station? I am looking for >>>the Contact ID protocol to be exact. Any help is appreciated. >>> >>> >>I may be wrong, but considering how competitive that market is, I'm >>quite certain that the protocols are all proprietary and not compatible >>with each other, and are surely not something you are meant to be able >>to find in the public domain. >> >> > >Most simpler systems dial into the center and send DTMF codes. One can >program just about anything to be sent. > >Peter > > Although many proprietary alarm protocols have come and mostly gone, the three most popular remaining are 4x2, Ademco Contact ID and SIA protocols. 4x2 uses pulsed tones to send 4 (account number) and 2 (alarm signal) hex digits at 10, 20 or 40 pps. Ademco Contact ID sends 15 (information) and 1(checksum) DTMF digits representing account number, event code and zone number etc. SIA sends info using half duplex 300 or 1200 baud FSK the information it send can be quite diverse including the capability of being bidirectional. Most alarm panels on the market today have the capability of being programmed to send at least two and sometimes all three of these formats. Randy

Wow - it's only $5.00???? Are you sure this is a _real_ standards organization? -Adam On 1/17/06, piclist <spam_OUTpiclistTakeThisOuTcritical-mass.homelinux.org> wrote: {Quote hidden}> http://www.siaonline.org/response.asp?c=store&l=2&r=1024 > > In the Industry Standards dropdown look for > SIA DC-05-1999.09 - DCS Ademco Contact ID Standard > > Randy > > > Shawn Yates wrote: > > >Can anyone tell me where I can find the specifications for having an > >alarm panel report to a central monitoring station? I am looking for > >the Contact ID protocol to be exact. Any help is appreciated. > > > >Thanks > >Shawn

If you check the price of the other documents you can feel a little better about it. You do have a point though, using "security industry" and "standards" in the same sentence takes a great leap of faith. Randy M. Adam Davis wrote: {Quote hidden}>Wow - it's only $5.00???? > >Are you sure this is a _real_ standards organization? > >-Adam > >On 1/17/06, piclist <.....piclistKILLspam@spam@critical-mass.homelinux.org> wrote: > > >>www.siaonline.org/response.asp?c=store&l=2&r=1024 >> >>In the Industry Standards dropdown look for >>SIA DC-05-1999.09 - DCS Ademco Contact ID Standard >> >>Randy >> >>

On Tue, 17 Jan 2006, piclist wrote: {Quote hidden}> Peter wrote: > >> On Tue, 17 Jan 2006, Herbert Graf wrote: >> >> >>> On Tue, 2006-01-17 at 08:57 -0500, Shawn Yates wrote: >>> >>>> Can anyone tell me where I can find the specifications for having an >>>> alarm panel report to a central monitoring station? I am looking for >>>> the Contact ID protocol to be exact. Any help is appreciated. >>>> >>> I may be wrong, but considering how competitive that market is, I'm >>> quite certain that the protocols are all proprietary and not compatible >>> with each other, and are surely not something you are meant to be able >>> to find in the public domain. >>> >> >> Most simpler systems dial into the center and send DTMF codes. One can >> program just about anything to be sent. >> >> Peter >> > Although many proprietary alarm protocols have come and mostly gone, the > three most popular remaining are 4x2, Ademco Contact ID and SIA protocols. > > 4x2 uses pulsed tones to send 4 (account number) and 2 (alarm signal) hex > digits at 10, 20 or 40 pps. > Ademco Contact ID sends 15 (information) and 1(checksum) DTMF digits > representing account number, event code and zone number etc. What I meant was, you get to calculate the messages yourself, and store them if you want it to be compatible. I also think that the Contact ID requires some special tones which cannot be made with a regular DTMF (and which are not issued by the cheap alarm dialers I alluded to). Peter

{Quote hidden}> > >>>Most simpler systems dial into the center and send DTMF codes. One can >>>program just about anything to be sent. >>> >>>Peter >>> >>> >>> >>Although many proprietary alarm protocols have come and mostly gone, the >>three most popular remaining are 4x2, Ademco Contact ID and SIA protocols. >> >>4x2 uses pulsed tones to send 4 (account number) and 2 (alarm signal) hex >>digits at 10, 20 or 40 pps. >>Ademco Contact ID sends 15 (information) and 1(checksum) DTMF digits >>representing account number, event code and zone number etc. >> >> > >What I meant was, you get to calculate the messages yourself, and store >them if you want it to be compatible. I also think that the Contact ID >requires some special tones which cannot be made with a regular DTMF >(and which are not issued by the cheap alarm dialers I alluded to). > >Peter > > Calculating the message yourself is one of the greatest errors you can make with a security system. That was the greatest downfall of the 4x2 format, 2 hex digits available to identify alarm type (burg, fire etc) and zone (front door, hall way etc). Since there was only a pseudo standard for what hex digits mean what, communication of meanings at the time of install between the installer of the security system and the central station doing the monitoring was of tantamount importance. Unfortunately this didn't happen in a large amount of cases. The industry eventually realized this and created contact id and sia standards. Each of these standards send a unique signal type (Burg, Fire etc.) and Zone Number for the zones that are violated at the time of the alarm. When sending Contact ID, the alarm transmitter does listen for a particular handshake tone (that is not DTMF) from the receiver, once it is detected all transmittion from the sender to receiver is in standard "DTMF" that any receiver that adheres to telco DTMF will understand. I can send a properly formatted Contact ID signal to a regular Central Station Alarm Receiver using a normal modem. No special tones involved other than the tones the CS receiver sends for handshake/kissoff. The CS Receiver will not know the difference if it received an alarm from an alarm system or from my modem. Randy

On Wed, 18 Jan 2006, Dave Lag wrote: {Quote hidden}> Peter wrote: > >> What I meant was, you get to calculate the messages yourself, and store >> them if you want it to be compatible. I also think that the Contact ID >> requires some special tones which cannot be made with a regular DTMF (and >> which are not issued by the cheap alarm dialers I alluded to). >> >> Peter > > MF or the "extra row" of DTMF? > D Afaik the Contact ID uses non-dtmf start and stop tones. The simple alarms cannot use these. Peter