Loading ...
Loading ...
Loading ...
AXIS Perimeter Defender
Advanced configuration
9999|192.168.1.40|0|ALARM_IN_PROGRESS|INTRUSION|Intrusion-0|-
Example
An ALARM_STOP message in XML format looks like this example:
<?xml version="1.0"?>
<KEENEO_MESSAGE xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:xsd="http://www.w3.org/2001/XMLSchema"
VERSION="5.0.0"
ID="9999"
TYPE="ALARM_STOP"
SENDER_IP="192.168.1.40"
SENDER_PORT="0">
<REFERENTIAL>0</REFERENTIAL>
<TYPE>INTRUSION</TYPE>
<SCENARIO_NAME>Intrusion-0</SCENARIO_NAME>
<EXTRA_DATA>zone=testzone</EXTRA_DATA>
<TIMESTAMP>2014-03-01T21:24:26.304</TIMESTAMP>
<GUID>77acddf9-e0d4-402e-a497-231aeee22788</GUID>
</KEENEO_MESSAGE>
• The message header is the same as the previous messages.
• The message type is “ALARM_STOP”, and has the same set of subtypes of the ALARM_START message.
The corresponding ALARM_IN_PROGRESS message in TEXT format:
9999|192.168.1.40|0|ALARM_STOP|INTRUSION|Intrusion-0|2014-03-01T21:24:26.304
The TCP/IP connection is always closed after each message. Therefore, the recipient has to keep the listening socket always open
for being able to receive further notications.
Communication errors
If the remote recipient of XML notications is not reachable, for example because of a network disconnection, AXIS Perimeter Defender
starts buffering the non-delivered alarms internally and periodically (at least every 10 seconds) tries to deliver them again. After a
consecutive number of failures in delivering new messages (failures while trying to deliver again a message from the buffer does not
account for that), AXIS Perimeter Defender declares the recipient as “permanently ofine” and stops sending XML notications to
the recipient. The number of consecutive failures is xed to 20, roughly corresponding to 4 or 5 intrusion alarms of an average
duration of 40 seconds each. AXIS Perimeter Defender starts sending notications to the same recipient again if one of the following
events occurs:
• AXIS Perimeter Defender is restarted.
• The same value of the parameter “Alarm streaming url” is saved again.
Post-alarm time
AXIS Perimeter Defender implements the notion of “post-alarm time”. This is dened as the time interval after an alarm stops, during
which, if another alarm is triggered, both alarms are merged into a unique one.
34
Loading ...
Loading ...
Loading ...