UltraView Security Center 5.0 SP1 Release Notes

Transcription

1 UltraView Security Center 5.0 SP1 Release Notes ISS Table of contents Introduction 1 Description of new features 1 Recommendations 8 Installation instructions 8 Upgrade instructions 8 Known limitations 8 Legacy issues fixed in 5.0 SP1 release 11 Documents 13 Introduction These release notes contain a summary of the new features as well as issues fixed in UltraView Security Center 5.0 SP1. For the latest information on the UltraView Video Security Center, please visit: Americas: EMEA: Australia: Description of new features UltraView Security Center 5.0 SP1 (build number for Config Panel, for Security Center client, and for Multivision) delivers the following modifications: 2017 United Technologies Corporation. UltraView is a registered trademark of UTC Fire & Security Americas Corporation, Inc.

2 TruVision camera support: List of supported TruVision cameras has been extended to include: TruVision Series 3 - TVB TVB TVB TVB TVD TVD TVD TVD TVW TVW TVW TVW TVW TVT TVT TVT TVT TVT TVT-5306 TruVision Series 4 - TVC TVC TVC TVB TVB TVB TVB TVB UltraView Video Security Center Release Notes

3 - TVD TVD TVD TVD TVD TVD TVD TVD-5408 RTSP input This modification allows UltraView Security Center user to configure any RTSP stream as an NVR video input. Requirements addressed: VSC-RQ In Config Panel there will be a possibility to configure the video input providing link to RTSP session, user name and password instead of IP camera address. VSC-RQ There should be a new camera type RTSP Link next to the existing cameras layers in Config Panel VSC-RQ Camera model for RTSP link should be Not Applicable. VSC-RQ In UltraView Security Center video input based on RTSP link should be treated as every video channel. Improvements of user experience Requirements addressed: VSC-RQ Filtering mechanism should be added to health monitoring panel in UltraView Security Center allowing user to display only faulty components of the system: cameras, encoders, recorders, Multivision. VSC-RQ Filter by device name should be added to history log allowing user of the system to retrieve only actions done for single entity, e.g. camera: configuration changes, requesting for live, playback, PTZ, configuring, deleting, requesting for presets. VSC-RQ Upper and lower thresholds for playback speed in Digital Recorder should be changed to higher values, e.g. 10 for forward and -5 for backward playback. UltraView Video Security Center Release Notes 3

4 VSC-RQ Additional option should be added to Multivision tile allowing user to take snapshot from single video feed and whole Multivision screen. TruVision cameras hallway view This modification adds support for hallway view for TruVision camera models. Requirements addressed: VSC-RQ Option Hallway View should be added to relevant TruVision cameras in video channel configuration. VSC-RQ Hallway View should be respected by Security Center, video image should be presented in alternated aspect ratio (e.g. 9:16 or 3:4 instead 16:9 or 4:3 respectively). Active Directory support This modification allows UltraView system administrator to use Active Directory for user authentication in UltraView Security Center and Config Panel. It also supports the importing of FCWnx users defined in Active Directory. Requirements addressed: VSC-RQ It should be possible to define Active Directory Password Authentication per user in Config Panel. That means that we can have mixed authentication mechanism in UltraView Security Center: password authentication against SC database and Active Directory Password Authentication against Active Directory. VSC-RQ It should be possible to define Active Directory Domain Server using IPv4 address, NetBIOS name and Fully Qualified Domain Name per user of UltraView Security Center. VSC-RQ Security Center and Config Panel should check user credentials against Active Directory when AD password authentication is defined for that user. VSC-RQ Security Center and Config Panel should check user credentials against SC database when password authentication is used. VSC-RQ Administrator of the system is responsible for ensuring consistency between user name in VC database and user name in the Active Directory. That means that user added to UltraView Security Center must be a valid user in the domain directory. 4 UltraView Video Security Center Release Notes

5 VSC-RQ Active Directory Domain Server name or address should be imported to SC database from FCWnx database if Active Directory Password Authentication is defined for that user in FCWnx (FCWnx 7.7.SP5 Patch 132 needed). VSC-RQ Security Center and Config Panel should check user credentials against SC database when FCWnx user authentication is defined for that user in FCWnx. VSC-RQ Security Center and Config Panel called from FCWnx should check user credentials against Active Directory when AD password authentication is defined for that user in FCWnx. VSC-RQ VSCController should pass active user credentials used for current FCWnx session when calling Security Center or Config Panel in case of FCWnx password authentication and Active Directory password authentication. Alarm recording modifications Requirements addressed: VSC-RQ It should be possible to choose same storage parameters (storage space and recording fps) to configure recording for different alarms. VSC-RQ Storage size and time parameter are common for all alarms that trigger given recording. VSC-RQ VSCFCWnxDBSync service should update UltraView Security Center database with alarms FC_ALARM_EquipmentName_VideoChanneIndex for each Video Event Trigger action that has assigned camera or camera presets. VSC-RQ User should be able to define following actions based on FC_ALARM event: video switches, video recording, relay switches, , and time schedules. UltraView Security Center integration with Event Proxy + Requirements addressed: VSC-RQ OnGuard event should be translated to UltraView event. VSC-RQ The OnGuard alarm acknowledgement, sent from OnGuard server to Event Proxy should be distributed to UltraView Security Center Event Manager. UltraView Video Security Center Release Notes 5

6 VSC-RQ The OnGuard alarm acknowledgement, sent from video system to Event Proxy, should be distributed to OnGuard Server. VSC-RQ Event Proxy alarms configuration should be sent to video system when user confirms that configuration is ready. VSC-RQ Event Proxy should put the newly prepared configuration to system queue. Service on Master Station should read the configuration from system queue. VSC-RQ Config Panel should expose option to start / stop reading the alarms configuration from system queue. VSC-RQ Event Proxy should send whole alarm configuration each time configuration upload is triggered by the user (no incremental configuration changes). VSC-RQ Video system user shouldn t be allowed to change OnGuard alarm s codes imported from Event Proxy. VSC-RQ It should be possible to use the same Event Proxy with PRISM or UltraView Security Center depending on installation mode. VSC-RQ Only one target system (PRISM or UltraView Security Center) should be allowed to work at given time with Event Proxy. VSC-RQ It should be possible to send set of test events from Event Proxy to UltraView system. VSC-RQ UltraView Security Center alarm s panel should present additional information associated with OnGuard Events. VSC-RQ UltraView Security Center alarm s panel should allow user for selective alarm acknowledgment. VSC-RQ Maximum size of UltraView events and OnGuard event should match each other. VSC-RQ UltraView database should be extended to store stateful list of alarms VSC-RQ Security Center client should load current alarm status from DB on application start or application refresh. VSC-RQ OnGuard alarm, passed by Event Proxy to UltraView system, should be received by new RK service and stored in UltraView database on stateful alarm list. VSC-RQ OnGuard alarm and acknowledgement received by new RK service should be stored in history log. 6 UltraView Video Security Center Release Notes

7 VSC-RQ The stateful list of alarms in UltraView database should contain only active alarms. Alarm record should be removed from that list after receiving alarm acknowledgment. VSC-RQ If video alarm is received in OnGuard through OAAP integration, it shouldn t be sent back to video system by EventProxy. VSC-RQ Event Proxy user interface should allow user configuration of parameters allowing connection to video system. UltraView Video Security Center Release Notes 7

8 Recommendations System administrator cannot use UltraView Security Center Config Panel and CCS applications simultaneously to configure video equipment. System administrator cannot configure multicast for video equipment with redundant definition. Installation instructions Please follow the installation instructions provided in B UltraView Security Center 5.0 SP1 Installation Guide to install ULTRAVIEW SECURITY CENTER (also with FCWnx integration). Upgrade instructions Please follow the upgrade instructions provided in B UltraView Security Center 5.0 SP1 SWUpgrade_from_5.0 _to_5.1. Note: UltraView Security Services 5.0 SP1 needs to be running on all video devices managed by UltraView Security Center 5.0 SP1. Known limitations [QC #1258] [SC] Audio is not played and authenticated if there is a gap on the timeline and exported files span over the gap. [QC #1431] Multi-selection is not allowed when mixing main streams and sub-streams for TruVision encoders or cameras. [QC #1449] Wrong settings of the slave streams for TruVision cameras: while configuring slave cameras to TruVision cameras, you may experience a situation where a no board icon appears instead of video. In such a case, you must configure a slave camera once again, modify/correct the streaming FPS value and again apply the configuration. [QC #1507] Security Center limitation: camera s technical name remains in the timeline of the Digital recorder no matter what the user has set, whether using technical or functional names. 8 UltraView Video Security Center Release Notes

9 [QC #1526] [Multivision] By selecting the fastback icon, the fastback feature can be used for playback. Additionally, the operator can use then Digital Recorder for playback. [QC #1601] [SC] For PTZ cameras that are based on the same IP address (dual stream, slave), wrong status is serviced. Then the PTZ cameras telemetry is locked and then automatically unlocked, the status is still serviced as locked by UltraView Security Center client. [QC #1606] [SC] Wrong status of Multivision is displayed in the Video Security Center application if there was Multivision application restart. Refresh application to display correct status. [QC #1610] [Multivision] Dual stream of PTZ camera s status appears operational while the PTZ camera based on the same IP address is shown as locked. [QC #1622] [SC][Multivision] Using the drag and drop feature for the first time between Security Center and Multivision (when both applications are on the same machine), will cause the operator to lose control of the monitors moved onto Multivision. [QC #1624] [SC] Dual stream of PTZ camera s status appears operational while the PTZ camera based on the same IP address is shown as locked. [QC #1670] [CP] Cameras hosted on NVR's with redundant definition cannot be used to define alarms with alerts. [QC #1712] [CP] Video alarms are not backed up if their definition is based on specific FPS settings of the IP TruVision camera alarms. [QC #1730] [SC] For cameras with redundant definition, when there are multiple alarms with recordings assigned to a single camera, the Digital Recorder incorrectly displays information about alarms with the lower FPS. Only highest FPS alarm is displayed in the Digital Recorder. [QC #1732] [SC] For cameras with redundant definition, access to the alarm storages from the Digital Recorder may not be possible, although the recordings have been stored. UltraView Video Security Center Release Notes 9

10 [QC #1736] [CP] System administrator must not define remote storage on equipment with redundant definition for audio equipment also being hosted on equipment with redundant definition. [QC #1737] [CP] System administrator must not define remote storage on equipment with redundant definition for a camera also being hosted on equipment with redundant definition. [QC #1738] [CP] System administrator must not change the camera s host, when the host and remote storage have a redundant definition. This issue concerns a situation when a camera s storage is configured on the NVR that is not hosting it. [QC #1739] [CP] System administrator must not change the IP address of an event manager, to an IP address which was assigned to equipment that was not configured as an event manager. In this situation the system will display a message that the event manager is not reachable. [QC #1743] [CP] System administrator must not change the definition of the secondary IP camera with the audio option active. Administrator must delete and recreate that definition if it has to be changed. [QC #1782] [Multivision, UltraView Security Center application] - Number of video streams that can be simultaneously displayed on Client Station with Multivision is the lowest from two values: feed number configured for user groups and Max simultaneous video setting in Security Center. Additionally Multivision has its own capacity. When a view is redirected to local Multivision, number of videos that can be display is limited only by Multivision Capacity and Max simultaneous video setting. Feed number that the operator can display is taken into account while dragging and dropping cameras to Multivision or redirecting single cameras. [QC #1783] [CP][Users groups] It is not possible to add users group with the same name as users group imported from FCWnx. [QC #1785] Live and playback access rights need to be imported from FCWnX and taken into account by UltraView Security Center. Limitation: Global import doesn't import permission for Security Center to ULTRAVIEW SECURITY CENTER database. Playback permission is given to 10 UltraView Video Security Center Release Notes

11 every user group synchronized during that process. Does not affect user imported by incremental import. [QC #1798] Improper information about quantity of monitors while changing Multivision configuration. [QC # 1824] [Multivision, UltraView Security Center application] - Cannot redirect View when maximum number of video channels on local Multivision has been reached. User is given a message: Maximum video feeds is reached on Multivision. After this situation it is still possible to redirect single camera or drag & drop camera on Multivision. To be able to redirect view, the user has to select Clear option from Multivision context Menu. [QC #1831] [Users groups] FCWnx 'Create Evidence CD' permission in not taken into account when a user is added to additional user group created in the ConfigPanel. Workaround: Does not apply to a user assigned to Administrators user group in UltraView Security Center. [QC #1836] Zooming with Security Center telemetry panel and joystick is not smooth for PTZ cameras configured by PSIA layer. Affected cameras: TVP-110X series, TVP- 310X series, and Panasonic SC384. [UVOS QC #2010] For NVRs that host TruVision cameras with embedded TruVision analytics plugins, redundant NVRs cannot be configured. Legacy issues fixed in UltraView Security Center 5.0 SP1 release [QC #2027] Cannot save alarm for camera with very long technical name (128 characters) [QC #2441] Performance of events processing degrades when part of the video equipment in configuration is not available in the network. The problem was related to alarm panel that refreshing status for each incoming event. [QC #2444] UltraView Video Security Center Release Notes 11

12 It is impossible to configure more than 10 presets for PTZ camera hosted on NVR having enabled redundancy. [QC #2445] Config Panel crashes while importing database from Security Center 4.6 version. [QC #2446] Incorrect multicast configuration on redundant NVR. Video port on redundant NVR uses the same multicast group and port as corresponding video port on primary NVR. [QC #2457 ticket 51157] Video tiles in Multivision support only 4x3 image proportions. Views that is configured as 16x9 should consist of 16x9 video tiles. [QC #2468 ticket 50980] MAX_TIME storage parameter for alarm storage is overwritten with incorrect value when user uses graphical Storage Distribution manager to adjust storage size. [QC #2474 ticket 50981] Sorting does not work correctly for cameras having defined call numbers. [QC #2475 ticket 50979] Duplicated TCP ports are configured for image processors when user edit group of cameras. [QC #2477 ticket 51062] Duplicate Wizard does not work correctly for cameras having sub-streams in configuration [QC #2477 ticket 51066] There is not enough space in Camera s video recording tab to see full alarm code while configuring event recording. [QC #2489 ticket 51152] Retrieving storage from cameras tree in main UltraView Security Center window not always shows alarm recording configured for video input. All recording for given video inputs (permanent and alarm) should be retrieved. 12 UltraView Video Security Center Release Notes

13 Documents The following important documents are available: Filename B UltraView Security Center 5.0 SP1 Administrator Manual B UltraView Security Center 5.0 SP1 Installation Guide B UltraView Security Center 5.0 SP1 Multivision Guide B UltraView Security Center 5.0 SP1SWUpgrade_from_5.0_to_ B UltraView Security Center 5.0 SP1 User Manual B UltraView Security Center 5.0 SP1 Vector Tool User Manual B UltraView Security Center Quick Installation Guide UltraView Security Center 5.0 SP1 Datasheet B Cameras and encoders supported by UltraView OS 5.0 SP1 and earlier versions This document includes an overview of the product and detailed instructions explaining how to configure and use the Config Panel. This document explains how to install and register UltraView Security Center and how to configure the network. This document includes an overview of the Multivision and detailed instructions explaining how to configure and use Multivision. This document explains how to upgrade UltraView Master and Client Station. This document includes an overview of the product and detailed instructions explaining how to use the UltraView 5.0 SP1 Security Center. This document explains how to use VECTOR (VECtorial Editor) software. It is a tool for drawing or recording maps that can be used in UltraView Security Center software. This document explains how to quickly install UltraView Security Center. This document provides general information about UltraView Security Center features and specifications. Supported cameras and encoders by UltraView OS 5.0 SP1 and earlier versions of the system. Provides general camera/encoder specifications, such as FW and resolutions. Also provides information about UltraView Security Center supported cameras. Used by UltraView Video Security Center Release Notes 13