Loading ...
Loading ...
Loading ...
AXIS Perimeter Defender
Advanced configuration
- SCENARIO_NAME is the name of the scenario that triggered the alarm, as dened in the conguration interface.
See Set up the intrusion/loitering scenario on page 26
- EXTRA_DATA carries the zone name (or list of zone names) involved with the alarm, like the intrusion zone.
- TIMESTAMP is the date and time of the alarm start, in the format YYYY-MM-DDTHH:mm:ss.zzz, where:
– YYYY is the year on 4 digits, like 2014.
– MM is the month number on 2 digits, like 01 for January.
– DD is the day number on 2 digits, like 03 for the 3rd.
– ‘T’ is a xed letter
– HH is the hour in 24-hour format, from 00 to 23
– mm are the minutes on 2 digits, from 00 to 59
– ss are the seconds on 2 digits, from 00 to 59
– zzz are the milliseconds on 3 digits, from 000 to 999.
AXIS Perimeter Defender uses the camera internal date and time for generating the alarm timestamp, thus it is
important to synchronize the camera with some kind of external clock.
- GUID is a unique identier that is constant for all messages related to the same alarm (so ALARM_START,
ALARM_IN_PROGRESS and ALARM_STOP)
This is the equivalent, in text format, of the ALARM_START message:
9999|192.168.1.40|0|ALARM_START|INTRUSION|Intrusion-0|2014-03-01T21:24:12.114
Example
An ALARM_IN_PROGRESS 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_IN_PROGRESS"
SENDER_IP="192.168.1.40"
SENDER_PORT="0">
<REFERENTIAL>0</REFERENTIAL>
<TYPE>INTRUSION</TYPE>
<SCENARIO_NAME>Intrusion-0</SCENARIO_NAME>
<GUID>77acddf9-e0d4-402e-a497-231aeee22788</GUID>
</KEENEO_MESSAGE>
• The message header is the same as the “CONNECTION_TEST” and “ALARM_START” message.
• The message type is “ALARM_IN_PROGRESS”, and has a set of sub-tags.
- REFERENTIAL is the numeric ID associated to the camera.
- TYPE is the type of the alarm triggered by AXIS Perimeter Defender the same of the corresponding ALARM_START.
- SCENARIO_NAME is the name of the scenario that triggered the alarm, the same of the corresponding
ALARM_START.
- The GUID is the same of the corresponding ALARM_START.
The corresponding ALARM_IN_PROGRESS message in TEXT format:
33
Loading ...
Loading ...
Loading ...