Security: Video

When working with previous versions of BVMS, remote connectivity was cumbersome due to the amount of port mapping that needed to be configured. BVMS 7.5 provides a new method of remote connectivity utilizing Secure Shell (SSH) Tunnelling. SSH Tunnelling constructs an encrypted tunnel established by an SSH protocol/socket connection. This encrypted tunnel can provide transport to both encrypted and un-encrypted traffic. The Bosch SSH implementation also utilizes Omni-Path protocol, which is a high performance low latency communications protocol developed by Intel. Key management The BVMS SSH service generates a private and public key when it is started for the first time. Both keys are saved in an encrypted file. When the BVMS SSH service restarts this file is detected and the private key is read.   Step-by-step guide   1.Configuration   A. Installation There is little to no configuration required for this feature to function. The SSH Service must be installed and running. If deploying a BVMS Pro system, insure the SSH Service is part of the installation process. Recording Appliances that ship with BVMS 7.5 should have the service pre-installed. Check your “Services”. If the service has not been installed, the install package can be run from the BVMS 7.5 downloadable install package. If working with a DIVAR IP Recording Appliance, the appliance “Installer Package” must be used.   B. Port mapping entry The primary configuration step is to configure one (1) port forwarding for the BVMS Central Server to utilize port 5322 for both internal and external connections. This is the only port mapping entry that needs to be made for the entire system. The image below shows a sample configuration.   2. Operation   A. Login with the Operator Client After the basic configuration is done, logging in via Operator Client is very intuitive: From the log menu, select the “Connection” drop down menu, then Select <New…> You will be prompted to enter an IP address or DNS host name. You will also notice a cheat guide below the entry menu that will assist with address entry. Addressing must be in the following format: ssh://IP or servername:5322. In the example we used: ssh://49.49.49.49:5322. After entering a properly formatted address, enter a valid user name and password. SSH users MUST have a password associated with their BVMS account. User accounts without a password cannot log in utilizing an SSH Connection.   B. Verification After connection is established via an SSH Tunnel, all communications between the BVMS Server (192.168.1.19) and a remote client (49.49.49.48) are encrypted. Below is a Wireshark Capture taken from the BVMS Server after a connection is established. C. Changing the SSH port Locate the SSH service configuration file in "C:\Program Files\Bosch\BVMS\bin" Open the configuration file and find the section below. Edit the value of the BvmsSshServicePort (the port should be unused) and restart the system.

This article contains documents attached which describes the installation package for BVMS. Operating system support of the specific BVMS version is listed in the BVMS release notes.

The attached manual provides information for Mobile Video Service (MVS) within Bosch Video Management System. You can find:  - how to configure the router and Internet Information Service (IIS) - how to add MVS to BVMS - user guide - some troubleshooting tips   This document can also be found online here.

This article describes the different components that Bosch Video Management System offers to to establish a connection between Bosch Video Management System and a 3rd party management system. This description helps you in writing your own commands for controlling Bosch VMS from inside your management system.   

 This article shows the keyboard shortcuts that can be used by operators when operating the BVMS system. 

This article will provide a basic explanation and simple examples of the interfacing (scripting, calling functions by external applications) functionality in Bosch Video Management System.

Check this article and have a look at the attached documents which describe the settings you must perform after having installed BIS and BVMS on the different computers.

In many cases a minimum and maximum retention time needs to be defined in a video surveillance systems due to legal requirements. While the minimum retention time defines the time period for how long video recordings need to be stored, the maximum retention time defines after which period of time the recordings have to be deleted. Thus, the minimum retention time is going to influence the amount of storage needed. The higher the minimum retention time the more storage space is required.

In order to quickly offer a technical solution or to provide a professional advice for the next analysis steps, the technical support specialists need to get some general and basic information. Ticket content should always be in English and provided in a well summarized and structured way in order to be able to provide a quick and appropriate feedback. Not following the guideline will impact the processing time of the ticket.

This attached document describes how Bosch Building Technologies handles the life-cycle of the BVMS, BIS, AMS, and APE, and in which state a specific release can reside.

This article contains the LIF fie which will help you to activate the Activation Key from SLMS for BVMS Lite v10.0

VideoView+ for DIVAR IP allows you to remotely monitor video footage from cameras connected to your DIVAR IP. It’s ideal for multi-site facilities, from mid-to-larger quantities of cameras per site, in need of local high-retention time, or RAID recording requirements. This is compatible with DIVAR IP all-in-one 4000, 5000, 6000, and 7000. To use the VideoView+ online service, you must first have an account on Remote Portal.

In order to use VideoView+ for DIVAR IP, the Remote Portal account needs to utilize Single Sign-On (SSO) ID. Initially, a new Remote Portal account does not use this technology. Follow the process from this article to convert the account to SSO.

This article is a step-by-step guide on how to set focus position on MIC IP starlight 7100i camera (focus to a certain setpoint).  

This article explains what to do when ‘Authentication failed’ message appears in VSC 3.7.0.817 for CPP4 cameras: To resolve this issue, upgrade the Video Security Client to version 3.7.1.840. According to the Release Notes (page 2), this version fixes the authentication failure with legacy cameras (CPP4) . 

This article explains how to secure access and manage ports for Bosch IP video devices. General network port usage and video transmission: HTTP, HTTPS and video port usage: Video software and port selection: SSH tunneling

This article answers whether the FLEXIDOME Multi 7000i camera consumes 4 licenses in BVMS. From BVMS 11.1 and newer version, the FLEXIDOME Multi 7000i camera is using only 1 license (including 4 channels). For BVMS lower than 11.1, then it will consume you 4 channel licenses.  

This article explains how to control access to restricted video in the BVMS Operator Client. Only users with the correct permissions can view restricted content, and access is managed via standard user groups on the Management Server.

The SDK application should always be compiled with the SDK assembly from the same BVMS version it will work with. There is no guarantee that the operation with different versions would work smoothly.

Camera name is displayed 'Camera 1' in Video Security Client (App), not as it is in Alarm Management. Even that the camera name is changed in Alarm Management in the Device name from the Devices menu or in the Channel name from the Channels menu, the camera name remains displayed as "Camera 1" in the Video Security Client (App). See how you can solve this!