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.
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.
GVUserManual.docx