SilentKnight VisorAlarm Plus 2U - Manual (Page 9)

VISORALARM - Introduction
I - 7
Doc.DM374-I
Ver. 1.0
different polling time with the center, the VisorALARM PLUS 2U checks the status of each
mIP/IPDACT starting with the polling time value for all of them.
In order to prevent the Teldat VisorALARM PLUS 2U from sending hundreds or thousands of
communication failure alarms when faced with a situation of general failure of IP traffic reception, the
device itself monitors the network access through ICMP echo packets (ping) to a known address: if the
echo packets towards this address fail then a code 356 alarm is generated from the Contact-ID protocol
(Loss of central polling). From release 10.1.27 onwards, the event code is configurable. Default is
356.
Apart from the previous codes, the Teldat VisorALARM PLUS 2U with network backup functionality
generates other codes that do not directly correspond with those pre-established by the CONTACT-ID
protocol. These have default values which can be changed via the console.
A series of these codes are grouped indicating the states the VisorALARM PLUS 2U passes through.
The device configured as main on startup sends a 396 restore code indicating that the device is active.
The device configured as backup must send code 398 restore code indicating that the device is active.
Once the main and backup VisorALARM are connected by polling, the main device sends a 358
restore code to indicate the backup device is up and the backup device sends a 399 restore code to
indicate the main device is up. Both the main and the backup VisorALARM PLUS 2U can have
communication problems (Loss of central polling) and consequently pass to a down state sending code
event 396 for main and 398 for backup. If the backup device detects communication failure with the
main device it will assume that as it cannot communicate with the VisorALARM PLUS 2U then nor
will the mIP/IPDACTs. The backup will then activate sending a 399 event code (Primary
VisorALARM is down) and the mIP/IPDACT polls should go to this device. Lastly, the main
VisorALARM PLUS 2U can detect and indicate through a 358 code that the polls from the backup
VisorALARM PLUS 2U are not reaching it and consequently there is a problem either with
communications with the backup or with the main VisorALARM PLUS 2U device itself.
In addition to the above codes, we need to add a further two which provide information over particular
cases. If in the mIP/IPDACT configuration there is an error where the main address is in fact the
backup address, all communications from this mIP/IPDACT will be routing to the backup. The
backup device, through a 395 code, will indicate this error by sending the code after each two
programmed keep-alives have been executed. The second case indicates a situation where an
mIP/IPDACT in backup is polling the backup device but this latter is not active, consequently there is
a communication error between the mIP/IPDACT and the main VisorALARM PLUS 2U. This
problem is indicated with a 394 code.
3.2. Sending of Alarms
When the mIP/IPDACT has connectivity with the Teldat VisorALARM PLUS 2U, the former
intercepts the telephone line and processes all the incoming and outgoing calls taking place from the
alarm panel.
The supported alarm sending protocol is Contact-ID. This format sends alarms through DTMF digits
complying with the following format:
AAAA MM QEEE GG CCC S
where AAA is the client number, MM the type of message, Q an event qualifier, EEE the type of alarm,
GG the group or partition number, CCC the zone number and lastly S is the frame validation digit.
When the panel opens to send an alarm, the mIP/IPDACT provides power and emits the dialing tone.
When the control panel dials the alarm center telephone number, it issues the Contact-ID handshake
and receives the alarm frame. From this point, the mIP/IPDACT sends this alarm to the
VisorALARM PLUS 2U.