Following screen will appear: Below explains license status: "OK": This online license works correctly. "NEW": This is a newly installed license. "BOUND": This is an offline (committed) license which works correctly. "UNKNOWN": This license is currently working (and is previously known working). But due to some factors (such as lacking Internet connection or exceeding maximum concurrent license), it might soon be invalidated. "FAIL": This license is invalidated, mostly likely due to license check failure, or license revoked at server-side. "INVALID": This license is invalidated, mostly likely due to computer system change. "SUSPEND": This license is suspended by user. Can be reinstated. “RESUME”: User has requested to reinstate this license. But licensing server has not granted yet. If you want to commit a online license to current computer, right-click on that license and bring up a context menu. Select "Commit..." to perform the commit operation. You'll need Internet connection to perform this operation. Backup/Restore License Sometimes if the whole system is overwritten for some reason (reinstallation of the OS) or accidentally purges the entire software installation, the license information could be gone permanently. To prevent this from happening, you need to backup the license and restore it when needed. Note: that you can only restore license to the same system (OS+computer hardware). Restoring to different system will render the license useless. This function is a relatively new feature. Please refer to following references: See also Starting the service Use the Tray Icon The color of the tray icon indicates the system status:
user misunderstanding. This can be illustrated in the following diagram. In this example there are two cameras both named "Cam001". As a result of name conflict, the CMS will only be able to access one of them, the "Cam001" inside "NVR server 1". The "Cam001" inside "NVR server 2" will not be accessible (hidden) from user. (Unless the first Cam001 is removed from "NVR server 1", or the "NVR server 1" is removed from the CMS) Obsecured channel Can I connect to yet another CMS (nestable CMS configuration)? Yes but not recommended. Our CMS architecture fully support nested configuration. (as illustrated below) Nested CMS configuration However such configuration is not recommended. As it would easily cause user misunderstanding. From previous Q&A, we know that each channel name must be unique throughout the domain. Configuring nested CMS structure could potentially extend the domain without the inner domain knowing. Does the network traffic of the child NVR go through the primary NVR server? No. Network traffic, such as live or playback video, goes directly from child NVR into the client. They do not consume any primary NVR server bandwidth. From this point of understanding, the child NVR must be in a network domain that is directly accessible by the client console, otherwise video could not be viewed. How to configure child NVR channels? Follow the instruction below: Firstly, invoke "Cfg. System" dialog and switch to the "NVR Connections" node. Select the target child NVR (in this example, the child NVR called ALEE), and click "Edit". After clicking "Edit" in previous screen, a second configuration dialog pops-up. This is the child NVR configuration window. Now click to the "Channels" node. You are now able to perform all channel configuration operations in this child NVR.
Edit function object properties. Restore the modified region configuration into last saved one. Save current region configuration. Add polygon region object. Add rectangular region object. Function Object Overview Function Object is a abstract object defines a IVS function. It contains parameters and can be associated with regions to define ROI or object size. The following function objects are available in the system: Motion detection (hardware) Software motion detection Object tracking Creating Function Objects Invoke Camera Setup dialog and select Video Analytics Setup tab, then click on one of the New Function Object button. Use context menu to configure Function Object. Define Regions Drag the endpoint of Function Object to define regions as extra parameter. Available regions depends on the type of the Function Object. A tag will be displayed on the connection to indicate what the region is used for the Function Object. In this case, it’s defined as ROI (region of interest).