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

The BVMS 11.1.1 Configuration Manual contains the lists for all components of BVMS, the ports that must be open within a LAN. You can find the used ports list starting with page 346 from the BVMS Configuration Manual.

This article explains how you can change the codec for your DINION IP 3000I IR via web GUI

Have a look in this article to learn how you can add ONVIF cameras to Configuration Manager through VSG managed by VRM.

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 this article we are going to show you how to add DIVAR IP 5000 EZ in My devices (Configuration Manager) and configure max & min retention time.

Find out from this article where you can find the sample audio files for the cameras added in the Alarm Management for the "Play audio on device" Action.

Find out from this article how you can get customized audio files to be used in the "play audio" action from Bosch Alarm Management

This article presents causes and solution regarding NTCIP control of Auto focus, Auto iris and wiper functions.

This article provides solutions regarding how to resolve SD Card Recording Issues with the MIC-7100i IP starlight and Inteox Cameras

AI Alarm Verification is applicable to Bosch Remote Portal cameras and 3rd party cameras**, for sites in Alarm Management which support alarm clip upload. 

This article answer to the question: "Why the ‘SD card Status’ is missing in GUI of MIC IP starlight/ultra/inteox 7100i camera?"

This article presents solution regarding how to stop "rtp.p_type 97" (OSD or Video Authetication packet) on a CPP4 and CPP7.3  

This article contains possible causes and solutions regarding  the recording error (stream 1) on the Remote Portal when camera records on its SD card on alarms only.

This article explains step by step how to load BIOS Optimized defaults on my DIVAR IP 5000 AIO unit.

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

This article explains what does the color of the led in the front view of the DIVAR IP AIO 5000 indicate.

This article explain what is the difference between ‘Operator Logon- off’ & ‘Operator Client Logon- off’ events in BVMS.

This article explain what is the meaning of each button on the KBD Universal XF.

This article explains step by step how to remotely connect to DIVAR Network or Hybrid via Divar Mobile Viewer App

All Bosch IP cameras that are equipped with a Micro SD can record at the edge. While video recorded via Bosch’s proprietary iSCSI format is none readable, many sites require any type of recorded video to be encrypted.