March Networks Command Version 2.3 January 2018 Introduction March Networks Command provides a single interface for managing your video surveillance infrastructure. As the industry s most comprehensive, end-to-end video surveillance solution, it allows you to discover, monitor, manage, and configure your video surveillance assets more quickly and easily than ever before. These release notes provide the version information, system requirements, and known issues in this release for the following products: Command Enterprise Command Professional Command Lite Command Enterprise March Networks Command Enterprise is a fully distributed solution, designed for large multi-site and multiple recording server or recorder installations. Command Enterprise offers edge device support from various vendors, as well as offering seamless support with March Networks edge devices. Command Enterprise consists of the following main components: Command Enterprise Server () Software Command Recording Server (CRS) Software Command Config Software Command Client Software Command Player Software SiteManager Software Command Enterprise is engineered to manage and support large enterprise applications with tens of thousands cameras or thousands of servers/recorders. Deployment and management of video surveillance systems can be complex. Using Command Enterprise s Mass Management capabilities allows your organization to manage complex solutions with ease. Note: All of the following Command Professional features are also available for Command Enterprise. Command Solution 2.3 Copyright 2008-2018 March Networks Corporation, An Infinova Company. All rights reserved. Information in this document is subject to change without notice. MARCH NETWORKS, March Networks Command, March Networks Searchlight, March Networks RideSafe, and the MARCH NETWORKS logo are trademarks of March Networks Corporation. Infinova is a trademark of Infinova Corporation. All other trademarks are the property of their respective owners. 35958 Revision 2.0, January 2018.
Command Professional March Networks Command Professional offers organizations with single-server environments a set of powerful video management tools that scale simply and are priced effectively. The software delivers video protection functionality, including redundancy, Shadow Archiving, and Shadow Archive synchronization, to ensure that the video you rely upon is available when you need it. It is designed to support up to 128 channels. Command Professional consists of the following main components: Command Recording Server (CRS) Software Command Config Software Command Client Software Command Player Software SiteManager Software Command Lite March Networks Command Lite is a simplified and free edition of Command Professional (not recommended for commercial use). With Command Lite, you can record up to 6 IP cameras and retain the video archive for up to seven days. The application also allows you to configure user profiles and use a basic set of Command features. Command Lite consists of the following main components: Command Recording Server (CRS) Software, simplified edition Command Config Software Command Client Software Command Player Software Note: Command Lite can be licensed and upgraded to Command Professional or to a Command Enterprise recording server. What s New in Version 2.3? Command Client 2.3 Traditional Chinese: Command Client now allows you to set the interface language to Traditional Chinese. Command Enterprise 2.3 Privacy Masks Based on User Profiles: System administrators can now configure the system for certain user profiles to see video without privacy masks. Command Professional 2.3 Improved Redundancy Shadow Archiving: Video recorded to a redundant server can now automatically transfer back to a primary server once the primary server is back online. Options to push data automatically or on a schedule are available. Improved Redundancy Server Switchover time: Any switchover between a primary-toredundant server or a redundant-to-primary server now occurs in less than 30 seconds. 2
Duplicate User Preferences: When duplicating users, all associated Command Client resources are also duplicated. This includes map configurations, views, private topology, language, and time preferences. Axis VMD3: Cameras and encoders using AXIS Video Motion Detection 3 (VMD3) are now supported. Edge 16e and 4e Encoder Licensing: March Networks Edge 16e and 4e encoders now only require 1 license to enable all analog channels present on the encoder. NAS Performance: When connected to network attached storage (NAS), writing and recovery performance have been greatly improved. RTSP Support: CRS is now able to provide an RTSP stream sent from the recorder by specific video channel and encoder channel (primary or secondary). The compression format of the video stream is standard H.264 and up to 16 RTSP streams can be sent concurrently. Statistics Dashboard: The Statistics Dashboard page allows you to access useful charts and data related to the system performance, recording performance, and incoming and outgoing bitrate. The data can also be exported to an excel file and the charts can be downloaded for offline view, allowing you to send them to March Networks Technical Support for analysis in case of performance problems. Upgrade Paths Command Enterprise Server If you have a previous version installed, first upgrade the to 2.3. Only after that upgrade is complete, upgrade all the managed CRS servers and recorders to a version compatible with 2.3. Command Client and Command Player Installers Command Client and Command Player installers are available from the Partner Portal in two different file extensions:.exe and.msi. Important: When upgrading Command Client and Command Player, you must use an installer with the same file extension as used to originally install. For example: it is not possible use the.msi installer to upgrade a Command Client originally installed using the.exe installer. You must first uninstall the previous version, then install the latest one using the preferred installer. The.EXE installer includes the Command software and automatically checks whether the software components (such as Microsoft.NET Framework 4.5.2 and Visual C++ 2015 Redistributable) required to run Command Client and Command Player are present in the system. If the components are not present, the.exe installers automatically trigger their installation: an internet connection is required. The.MSI installers only include the Command software. Before using these installers, ensure that the target computers meet the system requirements. In particular, Command Client and Command Player require the following software components: Microsoft.NET Framework 4.5.2 Microsoft Visual C++ 2015 Redistributable UCRT library * * Note: If Microsoft Visual C++ 2015 Redistributable is installed, and the UCRT library is NOT installed, uninstall Visual C++ 2015 Redistributable, then download and re-install the component. 3
Release Line-Up Software Package Version Changed Command Enterprise (includes Command Client) 2.3 Yes Command Client 2.3 Yes Command Transportation 2.3 Yes Command Media Archiver 2.3 No Command Player 2.3 Yes Discovery Browser 4.1.2 No Site Manager 3.9.6 No Decode Station VX 2.3.4 No Edge Decode Station 1.3.14 No Administrator Console (8000 Series, RideSafe, Gen4 4000 Series) 5.11 Yes Recorder Firmware (9000 Series) 5.11 Yes Recorder Firmware (8000 Series, RideSafe) 5.11 Yes Recorder Firmware (Gen4 4000 Series) 5.8.1 SP2 No DVR Configuration Tool (5000 Series) 4.9.3 No Recorder Firmware (5000 Series) 4.9.5 SP2 No Command Config (CRS) 2.3 Yes Command Recording Server 2.3 Yes Command Config (6700) 2.5.0 No Recorder Firmware (6700 Series) 2.5.0 No Authentication Tool 1.11.1 No Client SDK 2.1.2 No CRS Active X SDK 2.1.0 No Visual Intelligence ESM 5.11 Yes Visual Intelligence Clients 5.11 Yes Visual Intelligence Active X SDK 5.11 Yes For the list of supported cameras and encoders, please visit the March Networks official website at: https://www.marchnetworks.com/partners/integrations/nvr-integrations/ 4
Notes: Command Client 2.3 is supported on Windows systems only. For MAC OS X-based client workstations, it is possible to virtualize within a Windows environment. Command Config, the configuration interface for Command Recording Servers, is a browserbased interface that requires the installation of Silverlight, Command Client Plug-In, and the March Networks Root Certificate. Command Client 2.3 currently does not support direct connection to March Networks edge devices. To connect to these devices using Command Client 2.3, you must first add them to a Command Enterprise Server or a recording platform. For detailed information about the software versions, insert your Command Software DVD into the DVD-ROM drive or extract the installation package and double-click the Autorun.exe file. On the DVD main menu, click Documentation, navigate to the last page of the menu, and click Version Information to open the text file. 5
Supported Edge Devices CamPX H264 (VCS-IFC) 1 CamPX MiniDome (VCS-EFD-B-N) 1 CamPX MicroDome (CAMPXMICRODE) 1 CamPX PTZ (30670) CamPX WDR MiniDome (28050) 1 MegaPX 720p (MEGAPX720P) 1 MegaPX 1080p (MEGAPX1080P) 1 MegaPX 720p MiniDome (MEGAPX720P-D) 1 MegaPX 1080p MiniDome (MEGAPX1080P-D) 1 MegaPX NanoDome (MEGAPXNANOD4) 1 MegaPX WDR NanoDome (27816) MegaPX WDR (25552) 1 MegaPX 5MP (25551) 1 MegaPX WDR MiniDome (MEGAPXMINIWDRI) 1 MegaPX WDR MiniDome Z (28051-29965) 1 MegaPX WDR MiniDome Z 2 & Z2 1MP (31571 31571-SD) MegaPX MicroDome (27027) 1 MegaPX MicroDome 2 (30824) MegaPX DPoC MicroDome (31800) MegaPX 360 Indoor Dome (29253) MegaPX PTZ (30665, 30666, 30667, 30668) MegaPX Indoor Analytics Dome (29703) MegaPX ATM Camera (31763, 32044) MegaPX Integrated PTZ (30669) MegaPX Indoor IR Dome (30671) MegaPX Outdoor IR Bullet (30672, 30673) MegaPX HDR Forward Facing Camera (32049, 32111) MegaPX HDR Wedge Camera (33134-101, 33134-102, 33134-103, 33134-104) MegaDome (VC2-EPD-16, NETMEGADOME2) 2 MegaPX 2 (NETMEGAPX2) 2 MDome HD PTZ (MDOME10XHD) 1 XDome PTZ (XDOME series) 1 MiniDome PTZ (VCS-EPD-10-N) 1 MicroDome PTZ (NETMICROD10-N, NETMICROD10EXT-N) 1 Edge 1 (VE801) 1 Edge 4 (both standalone and blade version) (VE804, VE804B) 1 Edge 1 MicroEncoder (VE801-MICRO) 1 Edge 4e (30161) Edge 16e (32628, 32628-101) ME4 Outdoor IR Bullet (33166-101, 33166-102) ME4 IR MicDome (33164-101, 33164-102) ME4 Outdoor IR Dome (32459-101) ME4 Box Camera (33168-101) ME4 Discreet IR Dome (33208-101) ONVIF 1.02 compliant devices Third-party IP cameras and encoders listed on the March Networks website: http://www.marchnetworks.com/partners/integrations/integration-partners.aspx?p=command - sc Notes: 1. Legacy devices. 2. The MegaDome PTZ and MegaPX 2M cameras are not supported in Command Client and Command Config when configured on an 8000 Series NVR; also they are not supported when forwarded through the E-Pass feature from a 8000 Series NVR. 6
Recommended System Requirements Server Applications Command Enterprise Server Command Enterprise Server application requires a dedicated server or VM. These specifications are recommended for the Operating System and application without Searchlight. Please contact your March Networks Sales Engineer for specific project sizing with Searchlight or for systems with greater than 2500 CRS or NVRs. The HDD Space listed is the amount of space recommended for the OS, application, and free space necessary for backups and install files. Command Enterprise Servers Small Less than 10 CRS or recorders Mid 10-100 CRS or recorders Large Up to 2500 CRS or recorders Operating system (OS) Windows Server 2008 R2 SP1 Windows Server 2008 R2 SP1 Windows Server 2008 R2 SP1 R2 R2 R2 Processor (CPU) Quad Core Intel Xeon Quad Core Intel Xeon Eight Core Intel Xeon HDD Space 50 GB 50 GB 80 GB Infrastructure If you are integrating LDAP with the Command Enterprise Server, a Microsoft Active Directory Server is required (provided with Windows Server). If your system is managing more than 250 CRSs/recorders, March Networks recommends that you use a Microsoft SQL Server 2008, 2012, or 2014 as the external database, instead of the pre-configured Microsoft SQL Server Express 2012 included with Command Enterprise. Network interface Gigabit Ethernet 2 x Gigabit Ethernet 2 x Gigabit Ethernet Memory 6 GB 6 GB 1333 MHz 12 GB 1333 MHz 7
Command Recording Server Command Recording Server application requires a dedicated workstation, server or VM. These specifications are recommended for the Operating System and CRS. The recommended system requirements are estimated for a typical usage, under the assumption that the cameras are configured to consume 2-4 Mb/s of bandwidth each. The HDD Space listed is the amount of space recommended for the OS, CRS application, and free space necessary for config backups and install files. Video Storage requires a dedicated storage volume, not on the C drive. Command Recording Servers Operating system (OS) Processor (CPU) Small Less than 32 cameras Windows Server 2008 R2 R2 Windows 7 Windows 8 Windows 8.1 Windows 10 Mid 32-64 cameras Windows Server 2008 R2 R2 Windows 7 (64-bit) Windows 8 (64-bit) Windows 8.1 (64-bit) Windows 10 (64-bit) Large Up to 128 cameras Windows Server 2008 R2 R2 Windows 7 (64-bit) Windows 8 (64-bit) Windows 8.1 (64-bit) Windows 10 (64-bit) Dual Core Intel i5 Quad Core Intel i7 Quad Core Intel Xeon HDD Space 25 GB 25 GB 25 GB Storage for Video Archive Network interface Storage volumes for video recording must be exclusive to the CRS and managed by the CRS server s Operating System. Consider RAID volumes for optimal performance and resilience. For external storage, consider DAS (Direct Attached Storage) or Block Level SAN technologies such as iscsi or virtual disks. SMB/CIF storage is not recommended because of inconsistent performance. Use the March Networks System Design Tool (or an appropriate third-party camera calculator) to calculate the required storage size to meet retention needs. It is extremely important that the Video Storage volume and its connection to the CRS can indefinitely sustain recording on all cameras simultaneously (consistent write speed is greater than the total camera aggregated bit rate). Consult your March Networks Sales Engineer for any questions or concerns. Gigabit Ethernet 2 x Gigabit Ethernet (dedicated NIC for camera network) 2 to 4 x Gigabit Ethernet (One or more dedicated NICs for camera networks) Memory 4 GB Minimum 6 GB 8 GB 1333 MHz 8
Client Applications Command Config, SiteManager, and DecodeStation VX Command Config SiteManager DecodeStation VX Operating system (OS) Windows 7, Windows 8, Windows 8.1, and Windows 10 Windows 7, Windows 8, and Windows 8.1 Windows 7 SP1, Windows 8, Windows 8.1, and Windows 10 64- bit Processor (CPU) Intel i3 or equivalent (minimum) Intel i3 or equivalent (minimum) Intel i7 or equivalent Intel i7 64-bit or equivalent (recommended) HDD space for Clients Network interface 50 MB 150 MB 150 MB Gigabit Ethernet Gigabit Ethernet Gigabit Ethernet Memory 2 GB (minimum) 2 GB (minimum) 4 GB (minimum) 4 GB (recommended) 6 GB (recommended for 64- bit systems) Web Browser Microsoft Internet Explorer 9 (or later, Windows OS only), Firefox (up to version 29.0), Safari 8 (Mac OS X 10.10 Yosemite), with Microsoft Silverlight 5.x installed. N/A N/A Video card Any video card (128 MB per monitor minimum) capable of 24-bit color depth (true color). Any video card (256 MB per monitor minimum) capable of 24-bit color depth (true color), compatible with Microsoft DirectX 11 (or later) and Direct3D. 1GB dedicated video card for every monitor. Microsoft DirectX 11 and Direct3D Other N/A N/A 1 USB port (required for the licensing dongle) 9
Command Client Task Operating system (OS) Processor (CPU) Command Client Minimum Specs Minimum video access, one or two simultaneous stream playback and export. Windows 7, Windows 8, Windows 8.1, and Windows 10 2 with Microsoft.NET Framework 4.5.2 installed 3 Intel i3 or equivalent (minimum) Command Client 1 Optimal Performance Dedicated Command Client workstation with up to four monitors for many simultaneous live streams, playback and export. Max number of simultaneous streams depends on total FPS and bit rate of all viewed cameras 1. Windows 10 64-bit 2 with Microsoft.NET Framework 4.5.2 installed 3 Intel i7 with 8 Cores HDD space for Clients 200 MB 200 MB Network interface Ethernet Gigabit Ethernet Memory 2 GB (minimum) 8 GB Video card Intel HD 4000 video card 4 (minimum) or an equivalent video card compatible with Microsoft DirectX 11 and Direct3D 1GB Dedicated video card for every monitor. Microsoft DirectX 11 and Direct3D Notes: 1. March Networks recommends that installations with a high number of megapixel cameras and live viewing enable multi-streaming (high and low resolution streams) for all cameras. This helps to limit CPU overhead for live monitoring on Command Client, Site Manager, and Decode Station VX workstations. 2. A 64-bit Operating System is required for smooth reverse playback in Command Client and Command Player. 3. For Windows 8.1 users, it is required to download and install the following updates from the Microsoft website. The updates must also be applied in the following order: 1- KB2919442 2- KB2919355 For more information about the updates, please click the following links: https://support.microsoft.com/en-us/kb/2919442 https://support.microsoft.com/en-us/kb/2919355 4. March Networks does not support Command Client in Virtual Desktop Infrastructure (VDI). VDI is not ideal for CCTV clients because its architecture shares a pool of resources between multiple simultaneous clients. This means that client performance is dependent on available hardware resources, backend software and configuration, number of concurrent sessions, the number of simultaneous streams viewed, and their profiles. 5. If.NET Framework 4.5.2 is not installed on the Client PC, the Command Client and the Command Player installers automatically trigger the installation of the component (an internet connection is required). See Command Client and Command Player Installers for details. To use the Command Player Portable application (if not present), you must manually install the.net Framework 4.5.2 from the Command Software DVD or from the official Microsoft website. For the.net system requirements, consult the official Microsoft website. 10
Known Issues and Limitations Command Solution Issue ID 2849 3303 3814 4870 6652 6976 7067 7273 8996 10418 24141 11 Description When exporting video from 3000, 4000 C, or 8000 Series NVRs, if you select time parameters that are in the future, Command continues the export operation as new video frames are received. It does not stop the export at the end of the recorded archive. Workaround: Limit your time parameters to the times of the recorded archive video. If your Command Recording Server is disconnected from the Command Enterprise Server for more than 15 days, its license expires. Workaround: Restart the Command Recording Server service to reclaim licenses. If you change the time on the OS hosting by more than two minutes, the connection status of your recorders may not display properly. In addition, if you change the time zone on the OS, the does not reflect this change. Workaround: Restart the. Immediately after a device registration, sometimes the channel state update for the device tab is lost. If this happens, the tab shows a default state for the streaming, configuration, and recording status which may be different from the real one. The device only sends another update if the channel state changes again. Workaround: Close and relaunch Command Client. An upgrade from a 1.3.x or 1.4.x version to a 1.5.x or later version may generate network configuration alerts from CRS, 7532, and 8000 series devices. Workaround: Delete the alerts. When an Edge 4 encoder is added to the CRS, the server duplicates the four switches for all of the channels, listing a total of 16 different switches. Workaround: We recommend that you disable the duplicate switches to avoid unexpected behavior, especially after an upgrade from a previous CRS version. When an address zone from the "Edit Addresses" box is deleted, a health alert of Network category is raised, but the description is blank. Workaround: If you see a Network category health alert after performing the above action, expect to find a blank description. The issue does not have other side effects. The Command Client Plug-in does not apply changes to the Interpolation Method or the De-interlacing Method after you press the Save button in the Settings tab changes are applied only when you restart the plug-in. Workaround: Close (Exit) and restart the Command Client Plug-in after you apply changes to either the Interpolation Method or the De-interlacing Method settings. If you start multiple exports from the CRS, some of the export actions may fail. Workaround: Use the Restart or Resume button in the Export inbox to restart or resume the Export process. If a user with full access to the system tree moves a root device into the territory of another user, with limited access to the system tree, the associated alert entries are not automatically added to the device s health dashboard, or to the health summary. Workaround: Log out and log in again. If a user acknowledges a camera obstruction or field of view alarm in, it is not automatically acknowledged in the Administration Console as well, which prevents notification of subsequent alarms to. Workaround: Acknowledge these alarms in the Administration Console. Affects 3000 4000 8000 CRS All CRS 3000 4000 8000
Issue ID Description Affects 24239 25744 26089 27946 28121 28364 28888 29634 29696 29790 29852 30313 Deleting a device may cause some health alerts associated with other devices to disappear from the health alert inbox. Workaround: Log out and log in again, and the health alerts are restored. If you install and do not use the default install path, the Windows firewall rules have the wrong path (default install path) and the Command Client is not accessible. Workaround: Manually update the path of each firewall rule created by the installer, using the correct install path (your non-default path). CME files exported from a newer version of Command cannot be opened with an older version of Command Player. Workaround: Update the Command Player to the latest version. When a Media Archiver is registered to a, trying to register it to a different returns the wrong warning message - "Failed: Invalid username or password". When more than 1500 devices are registered on a, memory leaks may happen and the watchdog may restart multiple times. Workaround: Open the consoler and set the "jvm_maxheap" parameter to 4096. Also, navigate to the configuration folder, open the "domains.xml" file with an appropriate editor, and set the "MaxPermSize" value to 400m. Command Enterprise may fail to upgrade R5 recorders, triggering an "Upgrade failed" error. Workaround: Access the Admin Console interface and reboot the recorder to restore the automatic upgrade procedure. If the upgrade procedure is not restored, open the Mass Management tab, set the software release for the recorder to none, then set it back to the software version required. When a newly imported configuration has a different user name, LDAP settings that are already present are changed by, making CRS inaccessible for LDAP users. Workaround: Avoid the forward slash character in the LDAP user name and be aware that user names are changed by importing configuration. The Operation failed error message displays when a user right-clicks the camera list inside the Device tab, then clicks again to the System navigation panel. Workaround: If this happens, log out and log in again. When the ESM has a large number of devices, the ESM migration may take a long time and can cause a timeout. Workaround: In case of a timeout, reconnect to see the ESM device list. Some devices cannot register a device to a that is set to use a TLS version higher than 1.0. Workaround: Change the minimum supported TLS version to 1.0 in Enterprise Console, or register the device from the..net Command Client installation: the first time a user accesses the latest version of a device using the web, they may be prompted to download the plugin. Workaround: Clear the cache to eliminate this prompt. The list of Open Tabs only shows docked tabs. Undocked (floating) windows are missing from the list. Workaround: Avoid overlapping windows while undocking from the main window, so that undocked windows are not hidden. All CMD Client All All All All 12
Issue ID Description Affects 30727 31044 31117 31447 31862 31916 32961 35319 Reopening a saved layout of undocked views with the Global resolution set to high shows cameras at the lowest frame rate. Workaround: When you click on the Global resolution setting in each view, HIGH is selected. Click HIGH again, and all cameras refresh to their high settings. Command Enterprise requires Service Pack 3 if using SQL Server 2008 R2. If a smart card PIN request and a drag & drop tooltip are displayed at the same time, the Client can become unresponsive. The working icon spins and you cannot click the button to submit the entry. Workaround: Use the Enter key after you have provided the PIN to submit the entry. Command Client login takes up to 5 minutes after server reboot of with 1500 devices. Workaround: 1. Increase the start time in C:\Program Files\MarchNetworks\Command Enterprise \server\management\watchdog\watchdog.xml. Modify the parameter <starttimeout> in <process type="executable"> to 3 mins = 180000 <process type="executable"><name></name> <starttimeout>120000</starttimeout> 2. Add a parameter in the Advanced tab of the Console: jvm_maxheap = 4096 A with 2500 registered devices takes a long time (approx. 50 mins) to return to an up and running state after it is offline for more than an hour. Workaround: 1. Increase the start time in C:\Program Files\MarchNetworks\Command Enterprise \server\management\watchdog\watchdog.xml Modify the parameter <starttimeout> in <process type="executable"> to 3 mins = 180000 <process type="executable"><name></name> <starttimeout>120000</starttimeout> 2. Add a parameter in the Advanced tab of the Console: jvm_maxheap = 4096 When registering a CRS for the first time (in Lite Mode), it does not return the alarms capability at registration. As a result, the does not obtain the Alarms list. Workaround: Unregister the CRS and register it again, or force the CRS offline (disconnect for more than 4 minutes) and reconnect. Command Client may stop functioning and exit after running for a long period of time (over 6 hours). Workaround: Open a new client session. The 32-bit Command Player stops working when a 20 camera grid view file is opened with 16 or more of the 20 cells in the grid populated. If only 15 or less of the cells in the grid are populated, the file plays correctly. Workaround: For the 32-bit Command Player, export smaller camera grid views with fewer cameras in a single file. Or, if possible, use the 64-bit Command Player instead. CMD Client CMD Client CRS / CRS / CMD Player 13
Third party devices Issue ID Description 3484 5147 5620 Arecont AV 1300 does not provide a valid stream if the resolution options are set and the Motion JPEG transport layer is selected. Arecont AV 1305 does not provide a valid stream if the resolution options are set to 2592 x 1944 and the RTSP transport layer is selected. Arecont cameras cannot be discovered when multiple NICs are in use and are configured on different subnets. If using Samsung cameras, ensure that the Use timeout flag is disabled (in the Network Port section) to prevent the cameras from disconnecting from the CRS or the 7532 Hybrid NVR. 5742 When G726 codec is configured, audio from Panasonic devices does not play in SiteManager. 7052 7186 Audio output on Infinova cameras is not properly reproduced when the audio output quality on the cameras is set to 44 KHz. Workaround: Set the audio output quality to 8 KHz. SiteManager does not correctly display the croma component of Sentry360 cameras, when configured at 10 Mpixel. 7194 Live and playback video streams from VideoIQ cameras are not fluid. 7216 The configuration page for Pelco cameras cannot be loaded from Command Client. 9253 23893 Pelco Spectra IV may disconnect if the TCP transport layer is used. Workaround: Configure the camera to use the UDP transport layer. Sony cameras (generation 1 and 2) may disconnect if the native transport layer is used. Workaround: Configure the camera to use the RTSP transport layer. 14