Page History

...

You can configure the correspondence of messages for Topic Filter and the Intellect events. These are the ONVIF-Server events that start with tns and tmk in the examples below on this page. Intellect will transmit 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 server, profile or MotionAlarm settings, etc.).

...

1. Go to the Event settings tab on the settings panel of the ONVIF-Server object.
   

2. From the drop-down list of the ONVIF-server event column, select the ONVIF-Server event (1). See the events description in the table at the bottom of the page.

   Info
   title Note
   To add a row to the table, press the "down" button on the keyboard; to delete a row, use the Ctrl+Del keyboard shortcut.

   
   

3. In the Computer, Type and Number columns specify the parameters of the required object, from which the corresponding event comes (2). The Name field will be filled in automatically when you left-click it. If any column parameter is empty, it means that the message will be sent for any value of the corresponding parameter.
4. From the Event drop-down list, select an event which comes from the selected object and corresponds to the specified ONVIF-Server message (3).
5. If the specification requires that the event should contain certain parameters (see the table at the bottom of the page), it is necessary to set specify their values or the correspondence to the Intellect event parameters in the Transfer parameters table:
   1. The ONVIF-event parameter name column contains the required parameters of the ONVIF-Server event (4). They are set according to the specification.

   2. In the Event parameter name column, it is necessary to specify the parameter value or the Intellect event parameter names (5). Event parameters can be found in the Debug window, and some of them are described in the Description of events and reactions of system object reactionsobjects section (see Programming Guide ).

      Info
      title Note
      The following non-standard events can also be used: 1. Failure or hard disk error axn:HDDrive/axn:Fault axn:HDDrive/axn:RecordingFault 2. Hard disk full (if overwriting on a loop is not enabled) axn:HDDrive/axn:DriveFull 3. Video camera disconnection/connection axn:VideoSurveillanceSystem/axn:ChannelDisconnect axn:VideoSurveillanceSystem/axn:ChannelConnect 4. Any Intellect Servers disconnection/connection in a distributed architecture axn:VideoSurveillanceSystem/axn:ServerPowerOn axn:VideoSurveillanceSystem/ServerPowerOff

      for creating scripts (programming)).

6. Repeat steps 2-5 for all required events.
7. Click the Apply button (6).

...

To do this, go to the Events or Metadata page, depending on what messages you want to see, set the filtering conditions (1) that will be displayed in the list (2), and then click Apply (3). As a result, only the events that match the filter should be displayed.

Image Modified 

Image Modified

Examples of filters used in the ONVIF Device Manager utility:

1. Topic Filter
   1. tmktns1:VideoSurveillanceSystem//.
      Events where the topic starts with tmktns1:VideoSurveillanceSystem/
   2. tns1:VideoSource/MotionAlarmMotionDetectorTrigger
      MotionAlarm events MotionDetectorTrigger events only
   3. tmktns1:VideoSurveillanceSystem//.|tns1:VideoSourceFireAlarm/MotionAlarmAlarm
      Events where the topic starts with tmktns1:VideoSurveillanceSystem/, as well as MotionAlarm eventsFireAlarm/Alarm events
   4. tns1:VideoSource/
      All events of the video system, they contain a comment in Intellect format
2. Message Content Filter
   1. //tt:SimpleItem[@Name="Source" and @Value="{DFC2A44E-7CE4-E711-8A5F-54E6FC817BD7}{CAM.1}"]
      Events only from the source with the {DFC2A44E-7CE4-E711-8A5F-54E6FC817BD7}{CAM.1} identifier