SOFTWARE RELEASE NOTES ====================== Application: AXIS Perimeter Defender Bridge to Genetec Security Center Release date: 2020-02-14 Release type: Production Software version: 2.5.0 File name: AXIS Perimeter Defender Bridge to Genetec Security Center.exe Preceding Release: 2.3.0 ------------------------------------------------------------------------------- Contact Information =================== Please contact Axis Communications for product information, updates and support at http://www.axis.com ------------------------------------------------------------------------------- Installation instructions ========================= AXIS Perimeter Defender integrates with Genetec Video Management Systems (VMS) from Genetec providing operators with immediate and informative feedback on potential security incidents. For more instructions see the User Manual "AXIS Perimeter Defender with Genetec VMS" for this plugin. Supported Security Center Versions ================================== • Genetec Security Center 5.5 SR5, 5.6 SR4, 5.7 SR6 and 5.8.1, editions “Pro” and “Enterprise”a. a: Using a different version of Security Center might lead to unexpected behaviours. Always install all the available Cumulative Updates for the targeted version • Genetec SV16 and SV32 running one of the aforementioned versions. Features in 2.5.0 ============================ * Support for Security Center Directory Role failover server * Much faster retrieval of camera list from Security Center for very large systems (with more than > 1000 cameras connected) * Devices running Axis Perimeter Defender application and configured to be used but off-line at bridge start-up are automatically and regularly checked to be added as alarm and metadata sources when they are back online again Changes in 2.5.0 from 2.3.0 ============================ F01: Fixed an issue when a camera running Axis Perimeter Defender goes temporary offline or is disconnected from the system, the metadata stream does not come back even if the camera is online again F02: Fixed an issue under specific conditions, when the bridge gets disconnected from Security Center, it does not connect back anymore F03: When the logoff operation from the Security Center Directory blocks forever, the bridge is now able to restart itself Changes in 2.3.0 from 2.2.2 ============================ F01: Bridge initialization phase greatly speed-up, especially for large Security Center systems with hundreds of cameras. F02: Progression bars and progression messages added on lengthy operations. F03: GSC cameras to be associated to SafeZone server channels are now ordered in alphabetical order. F04: Log files reorganized to increase readability Changes in 2.2.2 from 2.2.0 ============================ F01: Corrected an issue that let the Bridge Configuration Tool become unresponsive when there are cameras in the Security Center system whose “Manufacturer” field is reported as NULL by the SDK. Known Bugs/Limitations ====================== L01: Sometimes the Alarm & Metadata bridge service refuses to stop. The workaround, when this happens, is to kill the Windows process manually and then stop the service using the Service Control Panel. L02: Multiple monitoring of the same video device (a camera or encoder) can affect the analytics results. L03: Version 2.0.0 or later of APD must be used.