Tag: Event Linking

Description

This issue was discovered when we implemented additional shock analytic event support for the Axis plugin. The event linking items were not assigned an unique id but rely on the next item in the list. So if additional analytic event applications are loaded, the initial ID assigned to the analytic event linking item would be invalid depends on the order it is loaded. The fix would be to assign an unique id to each analytic event supported by Axis so any new analytic event added to the system would not invalid or replace the existing ones.

<br>

Version Introduced

r88921 (7.3.20.88942/7.4.0.89235)

<br>

Platform

All

<br>

Steps to reproduce

1. load cross line application from the camera page(P1364 AC-CC-8E-02-A8-BB was used for this example)
2. connect to server and add cross line analytic in event linking list.
3. load VMD3 application in the camera.
4. disable/enable the axis camera from server.
5. this Axis should have both cross line and VMD3 in the analytic event linking list.

<br>

Expected result

the existing cross line analytic event should stay valid.

Actual result

the existing cross line analytic event is invalid.

<br>

Work Around

manually replace the invalid event linking item

<br>

Version Fixed

none

<br>

Keywords

Axis Analytic