Security: Video

Bosch Remote Portal connects you to your Bosch Security devices from anywhere and lets you perform remote administration and maintenance anytime

In this article it is explained in a step-by-step guide how to activate the needed services in Remote Portal to be able to connect the cameras to Bosch Alarm Management.

Possible causes and solution(s) Cameras which get connected from the customer's site to Bosch Remote Portal use an outgoing connection via TCP port 42000. Outgoing connections usually are not blocked by a router, however in a corporate network with proxy server, firewall, etc. involved, the IT department might open the needed ports. The troubleshooting steps below might help you to connect cameras to Bosch Remote Portal.   Known issues on camera commissioning In most cases when camera commissioning fails, the root cause is: No connection to Bosch Security Cloud from the customer’s site Blocked Internet connectivity (e.g. blocked ports by proxy or firewall) User belongs to more than one Company in Remote Portal The camera is already commissioned to a different cloud instance Known camera firmware issues Known camera date issue Further…  

All multitenant cloud instance migrate to under SingleKey ID (SKID) access management. This means: - One single email/password for login all integrated applications - One digital id for your users - All existed email migrate under single Key id - If you have same email address for system users and company user, it will migrate as system user

For VRM (Video Recording Manager) stand-alone Systems and Servers with VSG (Video Streaming Gateway) installed, it is strongly recommended to check for Microsoft OS updates before the VRM Master Installer is installed/updated.

Log4j 1.2.17 is not actively used or called by the SQL Server or by the BVMS. This means that the vulnerabilities are not exploitable unless you install some additional components that refer to the vulnerable component. Therefore, there is no risk of exploitation within the SQL Server or BVMS environment.

We found that there was a change in the way intelligent tracking worked after CPP 7.3 firmware v7.62.0005. With these changes if an object triggered an alarm that turned on intelligent tracking, the camera would not track the object. It would wait for another object to trigger an alarm to track it.

This article explains what to do if buttons are not visible in Bosch Intelligent Insights

DIVAR network 5000 / DIVAR hybrid 5000   support configuration of 3rd party cameras through the ONVIF Profile S protocol.

The Axis cameras can be added to the DIVAR Hybrid system and the Live view can be seen for a moment, but when going back to the settings to see the cameras, they are no longer available and the live view is also paused. What to do?

You can try the steps explained in this article to create a Task using Task Scheduler from MS Windows

This document is specifically for DIP-71xx as it's the DIP which supports certain versions of BVMS (regular BVMS installer) and must be updated in a certain order. The document details how to upgrade from BVMS v8 to BVMS v12.0.1.

Regular BVMS 12.1 installer will not run on any DIVAR IP all-in-one platform. The upgrade shall be performed via DIVAR IP System Manager application.

The Image Stabilization cannot be used in combination with VCA tasks, with the various MIC-7100i models. Turning Off the image stabilization will solve this behavior.

Follow the steps below and find out how you can perform the Firmware Upgrade for multiple cameras in bulk

This article describes how to configure a generic Microsoft Windows Server (2012 R2, 2016 or 2019) based server to serve as an iSCSI target for a Bosch video surveillance environment. SCSI (Small Computer System Interface) is most commonly used for the communication between computers and peripheral devices, such as hard drives. iSCSI enables devices to use SCSI over a network interface, therefore it makes a lot of sense for cameras to use iSCSI to record video. The camera is a small computer that needs a (network) connection to a "hard drive" to store video footage. In other systems this job is performed by the network video recorder (NVR).

External processes can be started within server scriptlets. Check details on C#  System.Diagnostics, Process Class.

The internal logs are directly located in the folder C:\ProgramData\Bosch\VMS\Log and then are named like "CameoSdkLog_Instance1.txt.0".  To activate the Cameo SDK logging, the "Init" button has to be pressed after setting the checkbox "Internal logging" and entering an instance name - then logging is activated with the given instance name (e.g. "Instance1").

The choice of the tool depends on the way the camera and recording are managed.

White cameo in BVMS Operator Client or "device failed" message may be caused by the NVIDIA graphic card driver that might not be compatible.