Security: Video

This article provides the Firmware  of the VJD-7513 is also suitable for the successor model VJD-7523.

This article shows where  to check how many blocks cameras can be used in VRM.

If the CPP6, 7 and 7.3 cameras no longer have a live image or there is a delay in the image, and the Internet connection has been tested and is within normal parameters, it would be good to check if the cameras have the latest current firmware version 7.86.0020. This firmware version solves a 100% CPU load issue for CPP6, 7, 7.3 from firmware 7.82 to 7.86.19

This article explains how is the storage capacity calculated for DSA E-Series E2800 12-bay (RAID 6).

When using ANR function in combination with 'alarm only' recording , recording 1 is with only the motion recorded.

Remote Connect service allows the Customer users to display cameras on Remote Portal Viewer on Video Security App and Video Security Client.

When login Remote Portal in Configuration Manager v7.20.0067, the following error message is displayed "The remote name could not be resolved: api.remote.boschsecurity.com"

This article explains step-by-step how to add and keep the purchased licenses in my Remote Portal account. Upon purchasing licensing, an email from Bosch provides the needed codes.

This article explains what you can do when the ‘Stream limits’ parameter set in the webpage of FLEXIDOME multi 7000i camera is not visible in BVMS Configuration Client.

Alarm Management has a split user management. The users are created in Alarm Management related to what they are allowed to access in the system.

The normal process is to enable Complete memory dump, this will capture in the event there is an Unhandled Exception.

Find out from this article how can you avoid the MIC Inteox & Starlight 7100i camera wipers getting stuck.

The Dashboard has a Maximum temperature that exceeds 80 Degrees C and the camera will display "Status 8" when the internal temperature is above 80 Deg C.

Follow this article to avoid getting the message: “Changing orientation is not possible because of the mounted illuminators”.

Question Why the Autodome 7000i INTEOX cannot connect to the S&ST Cloud services?   Answer Most likely, when you tried to connect to the S&ST ecosystem, you missed one of the steps explained in this article: How to connect a Bosch INTEOX camera to S&ST using Configuration Manager?   If you are sure that you have followed correctly the steps from the article above, please collect from camera: Diagnostics logs Config file with log in credentials Event logs How to collect logs from your Bosch IP Camera/Encoder? Please check if the the following message is displayed in the logs: ✅ Tip "Not connecting (CC enabled: true; Network connection: true; MQTT client ready: true; NTP enabled: false)" → this indicates that you didn't turn on the NTP which is a prerequisite to connect to the cloud back-end  Please enable the timeserver and make sure the time of the camera is synchronized with a public time-server when connecting to the S&ST cloud.   Note: NTP synchronization is necessary if the camera is going to be claimed in the portal. Please refer also to the Help & Support page:  Claiming cameras

Follow the steps below from this article to collect the configuration data file and the maintenance log file that might be requested by Central Technical Support team for troubleshoot & support purposes.  

According to the BVMS 11. Release notes > 2.2. Removed functionality chapter > The digital monitor wall functionality has been removed. This removal has impact on the BVMS Viewer → Decoders are not supported anymore in BVMS Viewer starting with version 11.0 Other devices and functions that have been removed to ensure software security: Map migration (removed Autodesk design review installation) SMS gateway Dibos/ BRS Note: The Monitor Group functionality is still available in BVMS Professional/ Plus/ Lite.

Check this article and find out the port of VideoJet X20/X40 XF that must be opened in the firewall for video stream transmission

This behavior was improved with the release of Video Security Client/App 3.2.3.

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.