Security: Video

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

This article explains how to enable or disable audio recording for specific camera in BVMS, on action of BVMS Operator Client user.   Follow the step-by-step guide from this article.

This article presents which are  the supported Bosch extensions with the Forensic Search.

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

This article provides causes and solutions if the Security Center crashes and is no longer operational - this may happen directly at launch or when you try to enable one of the plugins' tasks.

The "User Manual Bosch AI Alarm Verification Plug-in for Milestone XProtect" is a comprehensive guide designed to assist users in integrating and utilizing the Bosch AI Alarm Verification Plug-in with the Milestone XProtect video management system.

Are AMD CPUs / GPUs supported by the Bosch Dewarping plugin for Milestone XProtect?

This article provides solution for Bosch PTZ camera & Genetec VMS when camera's image does not follow the correct field of view on the map.

For Scriplets (because they are process of BVMS): .NET 4.8.  For SDK App: BVMS SDK .dll is compiled in .NET 3.5; .NET 4.8 can be used because it is backward compatible

The way to get Metadata in Milestone is through the Bosch Enhanced Metadata Plug-in

During the troubleshooting process, the Central Technical Support team often needs to run several different loggers to gain a more complete understanding of the problem.  You can use custom console traces to regroup and run different loggers that are not combined in the default Server Admin list. To create and run custom console traces for Security Center, follow the steps from this article.

The error message "Couldn't find a compatible Webview2 Runtime installation to host WebViews" might occur after installing the AI Alarm Verification Plug-in on a Milestone Husky system and attempting to log into Remote Portal in the Plug-in.

This article contains the scriplet that on Input sends a RCPP command on Input to another camera to close its Relay 1.

Milestone search tools (People & Vehicles) find results for other cameras. But the Bosch Forensic Search Agent finds zero results for DINION IP starlight 7000 FW v7.89. Why?

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 article describes how to ensure the delivery of the IVA events to Genetec Security Center via Hybrid Driver ( Other ( CPP13 or newer) driver )

By default the maximum number of shown results in the forensic search execution is 1000 and after 200 found results a warning message is shown. This article describes how to change those values.

When doing a pull point subscription, at the Start of the events Rule Engine/LineDetector/Crossed is missing, even though the rule is configured, and is given in the GetEventProperties response. The topic name space for RuleEngine/ FieldDetector/ ObjectInside works as expected.

In order to determine the Time Zone values, perform the bit mask operation of the flag value with the combined bit mask value 0x1F800000 as shown below. Bits 23-28 correspond to the Time Zone bits in the Flags.

The Cameo SDK is only backwards compatible, same as the Operator Client. According to the BVMS - Upgrade and Migration guides (boschsecurity.com)