The ONVIF-Server module supports filtering of messages and events transmitted in the metadata stream according to the ONVIF standard: Topic Filter and Message Content Filter.
You can configure the correspondence of messages for Topic Filter and the Axxon PSIM events. These are the ONVIF-Server events that start with tns and tmk in the examples below on this page. Axxon PSIM transmits only those events for which the correspondence is configured. The remaining events and messages are sent automatically according to the specification (for example, when changing the settings of the server, profile, or MotionAlarm, and so on).
Profile S and Profile T are implemented for event transmission. These profiles include standard events described in the ONVIF documentation. You can get a full list of supported events by a corresponding request to the server or using the Onvif Device Test Tool utility.
tns1:VideoSource/MotionAlarm (MD_START/MD_STOP in Axxon PSIM terms)
tns1:RecordingConfig/JobState (RECORDER_ON/RECORDER_OFF in Axxon PSIM terms)
tt:VideoAnalyticsStream (only BoundingBox for the tracker is transmitted inside the events, this is MD_INFO in Axxon PSIM terms)
tns1:Device/Trigger/Relay
tns1:Device/Trigger/DigitalInput
tns1:Configuration/Profile
tns1:Media/ProfileChanged
The correspondence of messages for Topic Filter and the Axxon PSIM events is configured in the following order:
From the drop-down list in the ONVIF-server event column (1), select the ONVIF server event. See the event description in the table at the bottom of the page.
To add a row to the table, press the "down" button on the keyboard; to delete a row, use the Ctrl+Del key combination. |
In the Event parameter name column (5), it is necessary to specify the parameter value or the parameter names of the Axxon PSIM event. Event parameters can be found in the Debug window, and some of them are described in Description of events and reactions of system objects (see Guide for creating scripts (programming)).
You can check the message and event filtering in the third-party software, for example, in the ONVIF Device Manager utility.
To do this, go to the Events or Metadata page, depending on what messages you want to see, set the filtering conditions (1) that are displayed in the list (2), and then click Apply (3). As a result, only the events that match the filter must be displayed.
Examples of filters used in the ONVIF Device Manager utility:
When you restart the ONVIF server, the filters are reset, and they need to be set again. Before changing the filter in the Events section, it is necessary to click the Refresh button for the camera in ODM. All events from the filter of the tns1:Device type are configurable and created for a specific integration. You can configure and use them with the restriction that the list of parameters and the format of the event are fixed. |
Event | Event description | Parameters | Configuration required |
---|---|---|---|
tns1:Device/AccessControl/Accident | Access Control System incident | Name Comment Place | Yes |
tns1:Device/AccessControl/Fault | Access Control System failure | ||
tns1:Device/FireAlarm/Alarm | Fire Alarm System alarm | Category Zone Comment | Yes |
tns1:Device/FireAlarm/Fire | Fire message from Fire Alarm System | ||
tns1:Device/FireAlarm/Fault | Fire Alarm System failure | ||
tns1:Device/GasAnalysis/ConcentrationExceeded | Increased concentration of hazardous gases | Place ConcentrationLimit GasType Concentration Comment | Yes |
tns1:Device/Introscopy/LimitExceeded | Detection of metal objects and organic matter | Account Picture Result | Yes |
tns1:Device/NeutronProbing/Detect | Detection of explosives | Place ExplosiveType Location Comment | Yes |
tns1:Device/RadiationMonitoring/Detect | Increased radiation | Picture Category Measures Account | Yes |
tns1:Device/SteamDetector/Detect | Detection of vapors and trace amounts of explosives that exceed the established threshold values | Measures Picture Account | Yes |
tns1:Device/MetalDetector/Detect | Detection of metal objects that exceed the specified values. | Picture Account | Yes |
tns1:Device/VideoSurveillanceSystem/ChannelDisconnect | Video channel disconnection | Category Comment Priority | Yes |
tns1:Device/VideoSurveillanceSystem/ChannelConnect | Video channel connection | ||
tns1:Device/VideoSurveillanceSystem/RecordTurnOff | Recording turned off | ||
tns1:Device/VideoSurveillanceSystem/RecordTurnOn | Recording turned on | ||
tns1:Device/VideoSurveillanceSystem/MotionDetectorTrigger | Motion detector triggering | ||
tns1:Device/VideoSurveillanceSystem/ReadRecordRequest | Request for the record reading | ||
tns1:Device/VideoSurveillanceSystem/DeleteRecordRequest | Request for the record deletion | ||
tns1:Device/VideoSurveillanceSystem/EditDbRecordRequest | Request for the event database editing | ||
tns1:Device/VideoSurveillanceSystem/CopyDbRecordRequest | Request for the event database copying | ||
tns1:Device/VideoSurveillanceSystem/Authorization | System user authorization | ||
tns1:Device/VideoSurveillanceSystem/ServerPowerOn | Server switched on | ||
tns1:Device/VideoSurveillanceSystem/ServerPowerOff | Server switched off | ||
axn:HDDrive/axn:Fault | Hard disk error (hard disk missing) | - | No |
axn:HDDrive/axn:RecordingFault | Hard disk failure | - | No |
axn:HDDrive/axn:DriveFull | Hard disk full (if overwriting on a loop is not enabled) | - | No |
axn:VideoSurveillanceSystem/axn:ChannelDisconnect | Video camera disconnection | - | No |
axn:VideoSurveillanceSystem/axn:ChannelConnect | Video camera connection | - | No |
axn:VideoSurveillanceSystem/axn:ServerPowerOn | Connection of any Axxon PSIM servers in a distributed architecture | - | No |
axn:VideoSurveillanceSystem/ServerPowerOff | Disconnection of any Axxon PSIM servers in a distributed architecture | - | No |
tns1:VideoSource | All events of the video system with a comment containing an Axxon PSIM event in its original form (for examples, see The Debug window) | - | No |