Security: Video

  Question   Which .NET Framework version is required for Configuration Manager v7.30?   Answer   .NET Framework is the original implementation of .NET. It supports running websites, services, desktop apps, and more on Windows. The system requirements for Configuration Manager state .NET 4.7.2 as necessary to be installed. .NET 4.7.2 is considered an operating system component under responsibility of Microsoft. If you operate in an offline CCTV network environment, please make sure that you have the .NET Framework 4.7.2 downloaded with the Configuration Manager v7.30 installer. Otherwise, the message below might appear and if you don’t have internet access you will be not able to use CM v7.30 WARNING: Configuration Manager v7.30 installation package does not provide .NET Framework 4.7.2.

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

From this article you will find out how to set up the IP Matrix configuration on the VIDEOJET decoder 7000 (VJD-7513) using Configuration Manager.   The built-in IP Matrix functionality, together with a connected keyboard, allows VIDEOJET decoder 7000 to run as a stand-alone system. An operator can manage up to 32 cameras via the keyboard without any PC or management system required. System setup is quickly done with Configuration Manager. After that, no PC is required to run the IP Matrix   Note: According to the Release letter (Firmware 9.51) of VJD-7513, VIDEOJET decoder 7000 supports IP Matrix application as built-in feature. According to the Release letter (Firmware 54.8.02) of VJD-7000, IP matrix remote monitor is only possible with UDP. TCP not supported. ** VJD-7000 can be used as an extended monitor to IP Matrix in single and quad view. Please check also the following article and find out: Which are the system requirements for configuration/ operation of VIDEOJET decoder 3000/ 7000/ 8000?   A single system can support: 2 physical monitor displays One KBD-Universal XF keyboard 32 cameras 32 camera sequences 9 favorite views

Perhaps you are wondering how to set the maximum retention time on a Divar Network? Some of our customers asked about this option. Well, in DIVAR Network and Hybrid there is not retention time. But you can set the automatically deleting time, that is more or less the same.   Step-by-step guide:   Open one Browser and type your device IP address Login with the administrator account Go to Settings > Storage > Recording Fill in the box with the desired automatic deletion time   Another option is to make this change directly in the local interface of the unit.

Short intro and related topics: This article will review the settings required to configure Windows as a NTP time server. Note: If you are running VRM and have the Time Server enabled, you must disable the Time Server before performing the following. Article requirements: Windows Server 2016/ Windows 10

Find below Gmail SMTP settings which you have to set in your EMAIL screen of DIVAR Menu. SMTP Server address: smtp.gmail.com Username: Your Gmail e-mail adress Password: Your Gmail password Port (TLS 😞 587 Port (SSL 😞 465 TLS / SSL required: Yes TLS : Transport Layer Security         SSL: Secure Sockets Layer What happens if you do not select either one? If neither SSL nor TLS is used , then the communication line can easily become a party line for eavesdroppers, all data transmitted between DIVAR and e-mail account for anyone to see.

It is possible to add ONVIF compliant cameras to Bosch Video Management System as live only devices or as VSG devices (then the cameras will also record). This article explains how to add an ONVIF camera as VSG device in full Bosch Video Management System (BVMS 10.1). We recommend using Bosch Workstations and Servers. They are fully tested and optimized for Bosch Video Management System.   Article requirements: BVMS installed ONVIF camera. Please refer to BVMS - ONVIF Device compatibility for additional information. PC/ Server/ Workstation

Question   Which is the VSG preparation to support ONVIF Profile T in BVMS 10.0?   Answer   Additionally to ONVIF profile S, BVMS 10.0 supports ONVIF profile T. Profile S concentrates on basic video streaming and configuration Profile T focuses on advanced video streaming like use of H.264, H265 encoding formats, HTTPS streaming and event definition is more precise there Profile T functionality is only supported for devices that are added over VSG For conditional and optional features please refer to the BVMS - ONVIF Device compatibility article. Functionalities available for all devices added over VSG (BVMS 10.0): The ONVIF relays are scanned automatically Relays can be added to the Logical Tree by drag& drop and triggered from there Thee relay status is automatically updated and signaled with an appropriate icon in Operator Client Status and triggering is possible over BVMS scripts Once ONVIF camera is added to VSG, its capabilities are automatically scanned In the “Add ONVIF encoder” dialog it was added a new device properties entry that shows weather AUX is supported by device. The AUX commands are sent to camera vis VSG and can be triggered for an ONVIF device on alarm. Note: most of the ONVIF cameras do not support all in Configuration Client available events   ONVIF vendor mapping:   ONVIF camera connection to VSG and BVMS Operator Client: Live video from ONVIF camera to VSG or Operator Client can be secured with a Secure connection check box in the Add/ Edit ONVIF Encoder dialog. The secure connection is not chosen by default. (Default HTTPS port is 443) If the live video does not have to be secured, it is possible to choose what protocol should be used: TCP, UDP, Multicast, UDP Unicast. Note: The protocol automatically is switched to TCP if Secure connection is chosen:   Ports used between ONVIF camera and VSG: RTP/RTSP/TCP (secured 😞 443 HTTPS: 443/ customizable (requires TCP)   RTP/RTSP/TCP (unsecured 😞 80 HTTPS: 80/ customizable (requires TCP)   Unicast/ Multicast UDP: has to be configured in a camera first control connection via http port (default port 80 or customizable/ RTSP port: 554)   Nice to know: For a better understanding of the  BVMS 10.0 - ONVIF camera integration with VSG , we   encourage  you to join our online Trainings from  Bosch Building Technologies Academy!

This article explains how to connect an INTEOX camera to the S&ST ecosystem using Configuration Manager (7.20 and later). Nice to know: For a better understanding of using the  Bosch Remote Portal, S&ST ecosystem and INTEOX cameras , we encourage you to join our   online Inteox product line introduction training  from Bosch Building Technologies Academy!

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.

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 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.  

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 This article describes the initial information needed to start troubleshooting Operator Client Crash.   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   Symptom specific Information Problem Description   Note down the events that lead to crash Classify the crash reproducible crashes that trigger Windows Error Reporting crashes/ hangs/ freezes that are hard to reproduce, or take long before repeating   Logging Information   Dump file from the crash – refer to the following article How To create BVMS memory dump?  ConfigCollection from the machine where the crashing Operator Client is running.

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

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 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

This article lists the initial troubleshooting steps and concrete instructions for collecting logging for issues with ONVIF cameras, added to BVMS system. We will classify the different issue scenarios one can have using ONVIF cameras in BVMS system. Depending on the issue the article lists the required logging to start initial troubleshooting.

  Causes   DIVAR mobile viewer is not able to connect to DIVAR AN and/or DIVAR Hybrid/Network because some ISP’s  (Internet Service Provider) only support IPV6. This issue occurs on: iOS 14.4 DIVAR Mobile Viewer 3.1.4 DIVAR AN and/or DIVAR Hybrid/Network    Solution New app  3.1.5 version is released and available on the App Store.  Please download the new App version and fix this behavior. We encourage you to always use the latest version of the App. Latest versions contain the newest features and bug fixes.

Possible causes and solution(s) Causes   DIVAR IP all-in-one 5000 (DIP-5244IG-4HD) without the video card: When accessing the Operator Client from the Kiosk mode, the camera streams displayed on the cameos show a view that does not match the view from Operator Client running from desktop (Under the BVRAdmin account) or Remote Desktop. The scaling seems to be off. Note: The   DIVAR IP all-in-one 5000   (DIP-5244IG-4HD) is the model without the added video card. The production units of the DIP 5k AiO can run Operator Client locally on the DIP5k AIO without the higher end graphics card and display at least 4 1080p cameras @ 15fps as long as the I-frame distance was well over 30. The units   without a graphic   card   (like   DIP-5244IG-4HD) should not run the Operator Client locally; only remote viewing, with the Operator Client running on a Workstation or suitable PC, is recommended. Doing it any other way may produce inconsistent results, see attached pictures. ✓   You can run the Configuration Client from the Kiosk. ✓   If you logon to the desktop with the BVRAdmin account, you can run the Operator Client from the console (desktop) on the unit. On this unit this is only supported for diagnostics/ testing purposes. This falls under the same category as the Remote Access to the unit.                 ✓   The Central GUI should be used for "configuration and operation management." It does not mention watching videos from the same GUI.                   ✓   You can attach a single monitor to the AiO, in order to run the Configuration Client from the Kiosk (Management purposes).   ⚠️   When using a remote workstation/ computer, to run the BVMS Operator Client remotely, the workstation / computer should  meet the hardware and OS (Operating System) requirements  for such use.  ◦ The hardware and OS (Operating System) requirements can be found in the datasheet of each version of BVMS Operator Client you use. Select the product family from the official Bosch Security and Safety Systems   page, go to Downloads area and download the data sheet. ◦ Bosch strongly urges customers to use the driver versions mentioned in the following   BVMS Release notes. This ensures that the software can perform its task reliably and the specified performance. On the units   with Graphics Cards   you can run both: Operator Client and Configuration Client from the Kiosk and get consistent results, without any changes. ◦ Please also refer to the following   Datasheet  for the Models with and without Graphic Cards.   Solution   The attached .zip file contains a script to check for the credentials to run the script and set the proper scaling on the desktop, for the current user (even for the limited user).

Question   Why the Windows license key and System ID are the same on all my DIVAR IP 6000?   Answer   These units come pre-licensed from the factory and they have an OEM (Original Equipment Manufacturer) license activated. Please see more information about OEM on the Wikipedia link below:  https://en.wikipedia.org/wiki/Original_equipment_manufacturer According to its   datasheet, all components relevant to the usage of DIVAR IP 6000 as storage array in a Bosch recording solution are pre-installed and preconfigured. Simply connect to the network and power the unit up — DIVAR IP 6000 is ready to begin recording straight out-of-the-box.

Question   Why the "Customer" user from the Bosch Remote Portal can see only few cameras in Video Security App?   Answer   Let's suppose that the "Customer" user should see 3 cameras in the Video Security App. When logging to the App, he can see only 2 of them. Why? This is because the "Administrator" user didn't grant rights to the "Customer" user to see the 3rd camera. Follow the steps from this article and find out how you can solve this issue.

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 you can add Bosch cameras to Bosch Remote Portal.    Nice to know: For a better understanding of using the  Bosch Remote Portal , we encourage you to join our   online Training from Bosch Building Technologies Academy!