EasyManua.ls Logo

Honeywell MX8000 - Table 8-7: Call Message Components

Honeywell MX8000
192 pages
Print Icon
To Next Page IconTo Next Page
To Next Page IconTo Next Page
To Previous Page IconTo Previous Page
To Previous Page IconTo Previous Page
Loading...
Section 8 – Automation Communication Formats
8–5
Note: Caller ID to Automation – When enabled, Caller ID information is output to the automation system
only in the event that no alarm data is received from a security system control panel.
Example: <$26><“051697”><$22><“081356”><$22><“01”><$22><“0001”><$22><“004”><“01”>
<12h><“1-800-328-0103”><11h><“ADEMCO”><$05><“123456”><$22><“BA01”>
<$22><“DC2”><$22><“RP”><V-byteV-byte><$0D>
Table 8–7 describes what each component of the call message means.
Table 87: Call Message Components
Component Description
<$26> Call message indicator.
<051697> Date-May 16th, 1997
<$22> Separator
<081356> Time-8:13:56 am
<$22> Separator
<01> Receiver number-1.
<$22> Separator
<0001> Reference number-0001
<$22> Separator
<004> Expanded dialer format -SIA DCS
<01> Line Card number-01
<12h> Caller ID phone number indicator
<1-800-328-0103> Caller ID phone number
<11h> Caller ID name field indicator
<ADEMCO> Caller ID name
<$05> Account number field indicator
<123456> Account number-123456
<$22> Good data field indicator.
*<BA01> Call event code-Burglary alarm, Zone 01.
<$22> Good data field indicator.
*<DC2> Call event code-Access Closed, Door 2
<$22> Good data field indicator.
*<RP> Call event code-Automatic Test
<V-byte> Validation Byte (V-byte). See Section 8.4.5.
<$0D> End of message indicator
*Note: Refer to SIA publication “Digital Communication Standard, February 1995 Revision,” or later for
message syntax.
8.4.2.3 Listen-in Indicator
If message sent to the automation computer contains a <$2A> (Listen-In indicator) followed the 3-ASCII
digits, the control panel calling is requesting the receiver put the phone line into listen-in mode.
The MX8000 receiver uses the following standards to identify a listen-in account:
First, the receiver searches for an embedded listen-in event in the panel data, depending on whether or
not the reporting format supports listen-in.
Second, the receiver compares the account number to those stored in the “listen-in accounts” list. See
Section 5.5.2.4.
Third, the receiver scans the line card flash record to determine if the listen-in is enabled for the line
card.
Fourth, if the above standards have been satisfied, the receiver sends the automation computer the
listen-in indicator.

Table of Contents

Related product manuals