The VMS is the central component for video integrations. Here, all recordings are managed, and you can configure which movements trigger a recording and else. The following components are needed on the VMS to enable communication between VMS and Siveillance Control:
- Video API
- VMS Provider
- Furthermore, cameras are attached to the VMS. Thus, the VMS is the only component that directly communicates to the cameras. All other components including Siveillance Control need to be connected to the VMS in order to communicate to the cameras. In the typical workflow, Siveillance Control issues commands to the VMS.
- Videos can be viewed either in an internal or in an external player. For the external player you need to install the Video client on every machine where an external player is desired.
The following picture shows a scenario with external player.
The following installation and configuration steps are necessary:
VMS Tasks | Video Client Tasks | Siveillance Control Tasks |
---|---|---|
First, you have to create the Video API service account. For more information refer to: Creating the User Account for the Video API Service (1) The Video API service account needs VMS permissions. For more information refer to: Configuring VMS Permissions for the Video API Service User Account. (2) | In order to utilize the Video Control functionality for the external player, the Video Control plugin must be installed on the machine where the Video Client is installed. For more information refer to: Installing and Configuring the Video Control Plugin for the Video Client. (5) | For a secure communication you have to transfer a trusted certificate from the Video API server to Siveillance Control. For more information refer to: Importing the Video API Certificate to the Siveillance Control Servers. (6) |
You have to install the VMS Provider. For more information refer to: Installing the VMS Provider on the VMS Server. (3) | In order to utilize the Video Control functionality for the internal player, the VMS Provider and Video API must be installed on the machine where the video streams should be shown. For more information refer to: Installing VMS Provider and Video API for the Internal Player (not shown in the picture) | You have to configure the VMS connection in Siveillance Control. For more information refer to: Configuring the VMS Integration. (7) |
You have to install the Video API. For more information refer to: Installing the Video API on the VMS Server. (4) |
|
|