Security: Video

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. Related Products: BVMS Operator Client Overview: This article describes the initial steps one can take for   troubleshooting BVMS display   issues (during   live view   or   playback). It also summarizes what initial information and logs are needed for support in order to start the issue investigation.   General Information   SMA validity How to retrieve the Hardware ID for BVMS and check the Software Maintenance Agreement (SMA) status? BVMS stand alone or appliance Detailed problem description Check and eventually update the version of your Graphic Card driver. During BVMS system tests there were documented cases of display issues related with out of date Graphic card divers. ❗   It is important that the Graphic Card driver of the client is up to date. Find the supported version of the Graphic Card driver in the corresponding to your BVMS version Release Notes (https://downloadstore.boschsecurity.com), in the section Hardware drivers.   Symptom specific Information   Problem Description   Is the issue camera type / FW dependent? Are all the devices in the system affected? Is the issue existent for all BVMS Operator Clients in the system? Is the issue existent for hardware decoders, for camera Web Interface or other display Clients? Is the recording, the playback or are both affected?   Logging Information   BVMS ConfigCollector logs keeping the following conditions: From the machine that shows the issue VSDK logging – please follow the steps from the article: How to collect Video SDK log files  VRM logs (in case VRM runs on the same machine like the BVMS MS, then BVMS ConfigCollector logs from the server) for VRM version 3.82 and onwards use VRM Monitor.   The following articles will help you out:    How to access VRM monitor from BVMS Configuration Client? How to collect VRM logs with VRM Monitor (v3.82/ v3.83)? Screenshot of the Dashboard of the VRM for VRM version till 3.81 - contact support to receive BVIP Log collector tool and use it to collect VRM logs Movie showing the display artefacts can be helpful

Related Products: BVMS / MVS / VSDK Overview: On request from development to provide a dump file from MVS system please follow the steps in the solution section.   Step-by-step guide   Reproduce the issue Download the Microsoft debugger procdump (https://technet.microsoft.com/en-us/sysinternals/dd996900.aspx). The procdump tool is also attaced to the article :How To create BVMS memory dump?  When application is crashing, do not click any buttons on the appeared error window that will change the program state. Run the procdump.exe from the directory where you copied the tool with following command line (Start - cmd): procdump.exe –ma <name of the programm exe> <dump file name>.dmp   In the case of MVS you need to do that for all 4 MVS services: - Bosch.MVS.SourceProvider.BVMS.Service.exe - Bosch.MVS.DataStorage.Service.exe - Bosch.MVS.SourceProvider.MobileCamera.Service.exe - Bosch.MVS.Transcoder.Service.exe

In order to start to analyze and optimize Video Analytics settings for particular customer set up, we need initial information and export of example video. This article describes the absolute minimum information we need in order to start analyzing and optimizing Video Analytics performance. Video Analytics (VA) task performance optimization Please provide the following details:   Symptom specific Information   Problem Description   Describe the expected result from the VA task. It is important to get detailed information of the results VA should provide. Define what is the customer’s priority: High sensitivity - miss as few true alarms as possible, but increases the likelihood of more false alarms! High precision – have less false alarms, but accept the risk to miss true alarm! Using VA is always based on balancing between sensitivity and precision. It is not always possible to get high sensitivity and high precision at the same time.   Provide an export of recorded video that should contain: Meta data: for basic understanding of meta data, please read the latest Software Manual Video Content Analytics for instructions about doing a video export with meta data, please read the article: How to export video including meta data (Export video including Video Analytics meta data).   Couple of examples of false alarms (in case false alarms are the issue) Provide the number of false alarms per time span (per day, per week, etc.) What would be acceptable as a number of false alarms per time span   Couple of   examples of situation that should have caused alarm, but VA did not generate the alarm as expected. In this case please provide the time stamp of the event and short description   Screenshot from the Camera Calibration Verification page - only in case calibration is needed for the particular VA functionality  access the Calibration Verification page of the camera (via the Configuration Manager or Web Interface)  provide screenshot from the verification of each parameter used for camera calibration     Note:  For more information on Camera Calibration and Calibration Verification, please check: How To calibrate camera for Video Analytics?

Related Products: BVMS SDK, BVMS    Overview: Analyzing BVMS systems with SDK components is a challenging task, because the functionality and the runtime behavior of those systems are harder to determine than for a BVMS systems without SDK functionality. In order to troubleshoot BVMS systems with SDK components support needs the following information and logging.   Please prove the following information to support:   Symptom specific Information   Problem Description SMA validity How to retrieve the Hardware ID for BVMS and check the Software Maintenance Agreement (SMA) status? BVMS stand alone or appliance Detailed description of the expected behavior of the SDK functionality. Detailed description of the actual behavior of the SDK functionality.   SDK Components What type is the standalone SDK application (based on ClientSDK, ServerSDK, or CameoSDK) and on which machine is it running? Are there additionally client scripts, server scripts or workstation startup scripts?   SDK Interactions Do SDK components interact with remote Operator Clients? Do SDK components interact with the Operator Client UI? Do SDK components control devices? How often are client scripts triggered? How often are scripts triggered by BVMS event?   Environment Which shared resources are accessed by SDK actions? (Dome cameras, AMG, Operator Client UI) Do SDK components interact with an unreliable environment? (Unstable network, offline devices, offline PCs, etc.) Do SDK components properly handle offline situations? (offline devices, configuration changes, etc.)    Logging Information Please provide the Scriplet and/or Log files The optimal approach is to provide both the scriplet and logging. ClientScript logfiles: can be found in the ConfigCollection of Operator Client machines. ServerScript logfiles: can be found in the ConfigColletion of Management Server machines.   Make sure that logging is implemented in the script and that logging is activated in the configuration.  

Related Products: Video SDK Overview: Analyzing issues with Video SDK based application is a challenging task. One needs to determine if the issue is based on wrong implementation of the Video SDK functionality, wrong programming practices, functionality and runtime behavior of the system with SDK functionality or Video SDK issues. In order to start troubleshoot Video SDK application support needs the following initial information and logging. Please prove the following information to support:   Symptom specific Information   Problem Description VideoSDK version VideoSDK issue description What is the expected behavior? What is the issue?   Environment Which shared resources are accessed by SDK actions? (Dome cameras, decoders, etc.) Do SDK components interact with an unreliable environment? (Unstable network, offline devices, offline PCs,  etc.) Do SDK components properly handle offline situations? (offline devices, configuration changes, etc.)    Logging Information The optimal approach is to provide both source code and logging for the problematic Video SDK application. Try to reproduce the issue with one of the  Video SDK samples (Advanced C# Sample, Complete C# Sample, Simple C# Sample) and provide the result from the test. Source Code Provide a little sample application that illustrates the Video SDK issue and list the reproduction steps. Logfiles Enable VideoSDK backdoor logging, reproduce the issue (note the date and time) and provide the Video SDK logs. How to collect Video SDK log files 

Related Products: BVMS SDK, Cameo SDK, BVMS  Overview: Analyzing BVMS systems interaction with BVMS SDK based application is a challenging task. One needs to determine if the issue is based on wrong implementation of the BVMS SDK functionality, wrong programming practices, functionality and runtime behavior of BVMS system with SDK functionality or BVMS SDK issues. In order to troubleshoot BVMS SDK or Cameo SDK application support needs the following information and logging. Please prove the following information to support:   Symptom specific Information   Problem Description SMA validity How to retrieve the Hardware ID for BVMS and check the Software Maintenance Agreement (SMA) status? BVMS stand alone or appliance Detailed description of the expected behavior of the SDK functionality. Detailed description of the actual behavior of the SDK functionality.   SDK Components What type is the standalone SDK application (based on ClientSDK, ServerSDK, or CameoSDK) and on which machine is it running? Are there additionally client scripts, server scripts or workstation startup scripts?   SDK Interactions Do SDK components interact with remote Operator Clients? Do SDK components interact with the Operator Client UI? Do SDK components control devices? Do SDK components link to 3rdParty devices or applications?   Environment Which shared resources are accessed by SDK actions? (Dome cameras, AMG, Operator Client UI) Do SDK components interact with an unreliable environment? (Unstable network, offline devices, offline PCs, etc.) Do SDK components properly handle offline situations? (offline devices, configuration changes, etc.)    Logging Information   Please provide source code and/or Log files The optimal approach is to provide both source code and logging for the problematic BVMS SDK application. If it is not possible to provide the code, we will start the troubleshooting process based only on the logging. Source Code Provide a little sample application that illustrates the BVMS SDK issue and list the reproduction steps. Logfiles Add log outputs to the SDK application functionality. The logs should illustrate which BVMS SDK functionality was called at which time. Provide the logs to support. How to collect Video SDK log files?   List of Typical Mistakes that are often seen when troubleshooting BVMS / Cameo SDK based applications   Use of Thread. Sleep() in event handlers - Consequence: loss of events in customer SDK application. Implementations that are not thread safe - Consequence: unexpected SDK application effects Unintentional introduction of multithreading issues by using timers - Consequence: unexpected SDK application effects Application without "speed control" - Consequence: operator overload in case of high event frequency Lack of configuration change handling - Consequence: data inconsistencies in SDK application (access to no longer existing devices) Lack of traces/logging in SDK code - Consequence: not detected malfunctions and troubleshooting difficulties Lack of error tolerance in SDK code - Consequence: unhandled exceptions in SDK application / script Lack of exception handling - Consequence: SDK application crashes

⚠️  CAUTION! If a computer on which VRM Server is starte d is simultaneously accessed by multiple  Configuration Manager programs, this can result  in an inconsistent VR M configuration. Ensure  that different people do not make chang es to the configuration at the same time.   Step-by-step guide Open one browser and type in the IP address of the VRM server you are pulling the log from. This will take you to the VRM Monitor web page. Log in with the VRM credentials (default user name is srvadmin); by default, there is no password   3.82 version: Go to Monitoring > System > Logbook The Export  Log bock page allows you to export all or only selected system  log s as a .zip file. Export system  log s Select the desired export  log book options. Export as ZIP  – Click to create a .ZIP file with selected   log  files, for example to send them to the Central  Technical Support Team.   3.83 version: Please note that the interface for VRM v3.83 has changed on the log collection. Therefore, the VRM log collection will be done by accessing Monitoring > System > Export Logbook Export system  log s Select the desired export  log book options. Export as ZIP  – Click to create a .ZIP file with selected   log  files, for example to send them to the Central  Technical Support Team. You can also collect the device maintenance logs from the VRM monitor (for VRM 3.50 or newer) Open the   VRM monitor   and log in with the VRM credentials Go to   Monitoring->   Devices   -> click on the   download icon   next to the camera

  Related Products: VRM, Genetec Security Center Overview: It is possible to use VRM free of charge (no extra VRM license is required) within Genetec Security Center. Genetec is sending encrypted secret to the VRM server with the number of the licensed channels. When VRM receives and validates this, it can be used for that number of channels for 24 h. A periodic license update is send by Genetec, so the VRM licensing is guaranteed as long as it is used with Genetec Security Center. Default settings, if not extra configuration is needed or done. -License for 1000 Cameras - License update is done every hour   How to license more than 1000 cameras or change the license update period for VRM within Genetec Security Center: Open the Config Tool and Launch a Video Task Select the Archiver Go to the Resource Tab and click on Extensions From the Tab Installed extensions select Bosch. In the Tab VRM add a new VRM and/or select already configured VRM. Click on Advanced settings and add the following parameters If you need to license the system with more than the default 1000 licenses – create the parameter with Name VrmLicenseRequestCount and as value put the required number of licenses. The parameter name is case sensitive If you need to change the duration of the period between each license request (there is always one license request when the archiver starts) – create the parameter with Name VrmLicenseRequestPeriod. The duration of the period is in milliseconds. The default value is one hour. If the value is set to 0, the license request are disabled. The parameter name is case sensitive     Press Enter to confirm the entry and then Close Press Apply and then OK. At the webpage of the VRM one can check if the number of licenses is changed.                    

The   Clear   button on the   Configuration Manager   is designed to clear the codes that are self-generated by the IP firmware or the Configuration Manager itself. Follow the steps below, if you want the "Clear" button from Configuration Manager to able to erase the Alarm task script that are self created by users themselves.   Step-by-step guide   When you create your alarm task script, add it within an opening quotes which then the   Clear   button will be able to erase all those codes within the quotes. Alternatively, create your own quotes within your script by following the below rules. In the  Below example,   //{{MyScript_start   is inserted before any script and   //}}Myscript_end   is inserted at the end of the script. By doing this, the   Clear   button will now be able to recognize and detect the manual scripts created by user and erase them.   Example: //{{Myscript_start ControlCode auxon1:={Operation(AuxOn)Number(1)}; if(Motion(1))then auxon1; //r1_o1 //}}Myscript_end

Compared to hardware, in which it is relatively easy to define an end-of-support concept based on the expected lifetime, software behaves totally different. In theory, when the environment does not change, software can still be running ten years after it has been installed. As new versions of the software are released regularly, it is important for customers to know what they can expect from Bosch Building Technologies when the software is purchased. This 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. Additionally this document lists the up-to-date situation for all of those software packages.

When Central Support Team provide assistance on a specific topic, at some point, customers may be asked to enable the VSG debug logging option. This article answers the question: Where can you find the "VSG debug logging" option in Configuration Client to enable/ disable it?

Operator Client helps you display the original full image circle of a panoramic camera, its image dewarped or you can select a point of interest of the image. Cropping and using ePTZ in a cropped image is possible in Live and Playback Mode. The Image window allows a flexible resizing of the Image pane that displays a panoramic camera or any other camera. This article provides you information on how you can switch the view mode of panoramic camera in Operator Client. Article requirements: Operator Client Panoramic camera PC/ Server/ Workstation

Intelligent Insights support controlling Bosch IP cameras by  Common Gateway Interface  (CGI) commands over HTTP or HTTPS when a threshold of the area fill level, area fill level traffic light or occupancy use case is reached. Follow the step-by-step guide below and find how you can to setup the threshold actions in Intelligent Insights.

Currently, most of the cameras are using profiles that are wrong created or profiles that actually belong to legacy cameras like the "excellent" profile. Therefore, the bitrates to the storage could be exceeded and probably will exceed during match when lot of motion is created. This article is focused on a method of creating a new profile with own parameters and make this new profile active.

This guide is meant to help you adding new cameras in VRM in Configuration Client and display their images in Operator Client. Before adding a new camera there are a few things that need to be taken into consideration: You are not exceeding the maximum number of channels allowed. Each unit has a maximum number of channels. For example: DIP 5000 AIO the maximum number of channels is 42 DIP 6000/ 7000 AIO the maximum number of channels is 128 You have the neccesarry number of licenses installed on the system The units come with 8 channels pre-licensed. If you want to add more cameras or encoders/ decoders, you need first to make sure that licenses have been purchased. The system has enough storage to cover the retention time of the cameras. If there is no storage available,   there is a risk that your system will stop recording. The bandwidth available of the unit is not exceeded. For example: Bandwidth   DIP 5000 AIO: 170   Mbit/s Bandwidth   6000/ 7000 AIO: 550   Mbit/s Article requirements: Operator Client Configuration Client Camera PC/ Server/ Workstation

Check if your system is performing correctly! The VRM Monitor is one of the best options to check if the system is recording correctly, providing a quick overview as well as detailed information about all the cameras and storage added to VRM. In this article you are going to see how to access VRM Monitor from Bosch Video Management System (BVMS) Configuration Client.   Furthermore, you will find here some useful information about each section on the Dashboard page.

Learn more about virtualization!

Do you want to know more about designing a BVMS system?

The attached documents should help you to make the upgrade process as smooth as possible. The upgrade itself is not restricted to BVMS software only. The supported software and firmware versions can be found in the release notes of the related BVMS version. An attachment is added to this article for each BVMS version. Currently the upgrade guides for BVMS 8.0 and 9.0 are attached to this article. From BVMS 10.0 onwards a description on how to migrate systems has been included as well.

CPP: Combined firmware package – applicable to all platforms The Release Letter for CPP 7.72.1118 provides information about the dependencies between firmware versions for a better understanding of the upgrade process of devices with older firmware. To find a combined firmware file in the downloadstore you can use the following URL syntax: https://downloadstore.boschsecurity.com/index.php?type=fw&filter=CPP CCP4 and CPP6 devices: Due to an internal file system being introduced to CPP4 and CPP6 since firmware 6.10 and architectural changes thereof, a direct upgrade from firmware below version 6.10 to latest firmware is only possible via intermediate firmware 6.1x. CPP4 cameras upgrade from FW < 6.10 to intermediate FW 6.11 upgrade from FW < 6.50 to intermediate FW 6.50 upgrade EXTEGRA from FW 6.10 or newer to latest FW 6.32 upgrade from FW 6.50 (<6.51) to latest FW 7.10   CPP6 cameras  upgrade from FW < 6.50 to intermediate FW 6.50 upgrade from FW 6.50 (<6.51) to latest FW 7.70  CPP5 devices: This combined firmware cannot be applied to CPP5 products with firmware version older than 5.91. It is required to upgrade to intermediate firmware 5.91 first This means that intermediate firmware version 5.91 for CPP5 needs to be requested from your technical support. Only after receiving and uploading firmware 5.91, you can upload the latest version CPP5 specific firmware  available on the Download Store (currently 6.31.0010). To find a combined firmware file in the downloadstore you can use the following URL syntax: https://downloadstore.boschsecurity.com/index.php?type=fw&filter=CPP if needed for some reason, the older CPP 6.50 combined file is available here: https://downloadstore.boschsecurity.com/FILES/KnowledgeBase/CPP_FW_6.50.0620.fw and Releaseletter of that combined firmware package: https://downloadstore.boschsecurity.com/FILES/KnowledgeBase/Bosch_Releaseletter_CPP_FW_6.50.0620.pdf Note: Upgrading from versions lower than 5.5x To upgrade to a newer firmware version using this combined firmware package, firmware versions before 5.5x require an intermediate update cycle using the respective platform firmware version mentioned above. Restrictions: This firmware and its included platform firmware builds are not applicable to MPEG-4 products. The final firmware version for VIP-X1600-XFM4 modules is FW 5.53. No newer firmware will be provided for these modules. Configuration Manager cannot upload this Combined Firmware file to VIP-X1600-XFM4 modules. Use the module’s web page instead for uploading; or use the separate firmware file. The final firmware version for CPP3 devices is FW 5.75. No newer firmware will be provided for these products. The Combined Firmware file does not load onto VG4 AUTODOME or AUTODOME Easy II via the browser when running a firmware version before 5.52.0017. The specific platform file should be used instead. (Note: In case any link might not work to the current DownloadStore, see attached a copy PDF of the Release Letter.) How to get and request a BOSCH Legacy Firmware: The procedure to request and get an legacy firmware that is no longer online in the web is as follows: Customers are kindly requested to reach out to the local BOSCH Support (Central Solutions and Support Group teams). Bosch Support Group will ask for the exact BOSCH Commercial Type Number (CTN). The local BOSCH team can check the Global End of service date. The project background (How many of these devices/cameras) need to be collected.  The relevant BOSCH Technical Support can explain and check if there is the chance to update the project and included management software in order to be able to use the latest BOSCH device firmware as the goal is to have a non-vulnerable product in productive environments. In case there is no newer firmware available (hardware was discontinued), a commercial hardware upsell can be recommended. In general all firmware that is not available on the product catalog, and for all firmware files that are ranked to have vulnerabilities, this need to be documented in a Technical Support case. In case legacy firmware is anyhow needed and requested by our customers, the Bosch Technical support will start an approval flow. The BOSCH Level 3 Technical Support will provide a form/document that must be signed by the installer/customer. See an example PDF (empty) "Example_Aged_Software_Release_form.pdf" attached to this article. Such a form will be prepared by the BOSCH Level 3 Technical support team and provided to our customer/installer in order to confirm that legacy firmware is then used on the risk of the installer and customer (See text and legal note in the PDF). In the future BOSCH plan to introduce and setup a self-service portal for all customers to simplify this process. ___________________________________________________________________________ The above mentioned combined firmware 6.50 supports: CPP7.3 HD and UHD cameras update from FW 6.40 or newer to latest FW 6.50 CPP7 UHD cameras update from FW 6.30 or newer to latest FW 6.50 CPP6 UHD cameras update from FW 6.10 or newer to latest FW 6.50 CPP5 encoders update from FW 5.91 or newer to latest FW 6.30 CPP4 HD cameras update from FW < 6.10 to intermediate FW 6.11 update from FW 6.10 or newer to latest FW 6.50 CPP3 cameras and encoders update from FW 4.54.0026 or newer to latest FW 5.74 CPP-ENC VIP-X1600-XFM4 encoders: update from FW 4.2x or newer to latest FW 5.53 VJT XF and VJD-3000 update to latest FW 5.97 The combined firmware package includes the following build versions: CPP7.3 FW 6.50.0128 CPP7 H.264 6.50.0128 CPP6 H.264 6.50.0128 CPP5 H.264 6.30.0059 CPP4 H.264 6.50.0128 CPP4 H.264 6.11.0021 CPP3 H.264 5.74.0010 CPP-ENC H.264 5.97.0005 for VJT XF family, VJD-3000 and VJC-7000 CPP-ENC H.264 5.53.0004 for VIP X1600 XFM4 For detailed description please refer to the separate release letters. Customers can upload such combined firmware packages by using multi-select in the Configuration tool "BOSCH Configuration Manager" (currently available in version 06.01.0157 at the BOSCH DownloadStore or Product catalog > Video Software > Video Management Systems > Configuration Manager) When using the multi-select option in Configuration Manager, please make sure this combined firmware package for all platforms can be uploaded to all the devices selected and there are no additional requirements or intermediate steps needed for any of the devices in question. This article has status of 24th of March 2021 and changes in this procedure might be introduced. When changes are done, then this article will be updated. Therefore check this article from time to time.