Security: Video

This article is focused on a method of creating a new profile with own parameters and make this new profile active.

This article contains videos which explain the usage of Bosch cameras integrated in Genetec Security Center.

If BVMS and VRM are installed on the same machine, it is needed to change the TCP Port of the VRM Monitor.

Related Products: BVMS SDK, BVMS    Overview: BVMS Scriptlets can be debugged via logging to a logger file or messaging to the Operator workstation. This article describes how to enable BVMS Scriplet logging. You can log to the Server Script log or the Client Script log. Logs are default send to C:\ProgramData\Bosch\VMS\Log   1.Creating Log files ClientScriptLogger – automatically created Creates file “ClientScriptLog.txt” ServerScriptLogger - automatically created  Creates file “ServerScriptLog.txt”   2.Log information to the log files There are 3 methods to log information: Log Info Log Error Log Debug   Examples: [Scriptlet("59c4d66e-9395-4dcc-8d27-90dc2b7a00c4")] public void DemoLogger() { //use refence:C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727 MessageBox.Show("Hello World"); Logger.Info("Hello World script started"); Logger.Error("Hello World script started"); Logger.Debug("Hello World script started"); // Not writing to ClientScriptLog.txt ! }   3.Logging Location - C:\ProgramData\Bosch\VMS\Log. The logs are automatically collected by the BVMS Configuration Collection Tool. 4.Changing the location of the BVMS Scriplet Logging.   Server Scripts : Logging Directory can be found in the file: C:\Program Files (x86)\Bosch\VMS\AppData\Server\CentralServer\BvmsLogCfg.xml and is defined by the ServerScriptLogAppender path: Default: </appender> <appender name="ServerScriptLogAppender" type="Bosch.Vms.Shared.Logging.Imp.RollingFileAppender, Bosch.Vms.Shared.Logging.Imp"> <file value="%CommonApplicationData%\\Bosch\\VMS\\Log\\ServerScriptLog.txt"/>   Client Scripts : Logging Directory can be found in the file: C:\Program Files (x86)\Bosch\VMS\AppData\Client\OpClient\ApplicationWiring\Nvr\LogCfg.xml and is defined by the ClientScriptLogAppender path: Default: </appender> <appender name=“ClientScriptLogAppender" type="Bosch.Vms.Shared.Logging.Imp.RollingFileAppender, Bosch.Vms.Shared.Logging.Imp"> <file value="%CommonApplicationData%\\Bosch\\VMS\\Log\\ClientScriptLog.txt"/>

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

In this solution article a questionnaire for a first basic analysis of a reported issue is described. This checklist is intended to help to identify and resolve known issues immediately and to collect relevant data in case of an unknown issue. 

FW 11.50.2 must be used for Single Controllers and 11.60.2 for Dual Controllers and then updated to latest version.

A password prevents unauthorized access to the device. You can use different authorization levels to limit access. Proper password protection is only guaranteed when all higher authorization levels are also protected with a password. Therefore, you must always start from the highest authorization level when assigning passwords. This article will guide you step by step to set the destination password for decoders.

Starting with BVMS 10.0, ONVIF encoder events can be retrieved from VSG or ONVIF encoder directly. Additionally to ONVIF profile S, BVMS 10.0 supports ONVIF profile T.

This article contains 2 options describing the way you can find the Firmware version of your DSA unit, in case the Central Technical Support team is asking you about it or if you simply want to find it by yourself. Check out this article!

If your VIDEOJET decoder does not seem to work properly, most likely it is because the software (SW) version used is not compatible with the firmware (FW) version of your device.

If one of DIVARs IP 5000 AIO is selected on a user profile, the Operator Client opens the site and works fine. One message is displayed when two or more DIVARs are added into the same Enterprise system.   If you already have a DIP 5000 AIO into your Enterprise system and you want to add additional units but you receive the following message, you can solve this by using the steps below: "Server of configuration database is already in the server list. Remove either the server that is twice in the list or make sure that the configuration database is not cloned between servers."

The IEEE standards in computer networks ensure communication between various devices; it also helps to make sure that the network service, i.e., the Internet and its related technologies, must follow a set of guidelines and practices so that all the networking devices can communicate and work smoothly. Depending on the camera model, the PoE IEEE standard used could be different. 

This article lists different ways to connect to cameras Live/Playback using the Video Security Client/App: to DIVAR IP AIO/BVMS system or to Camera directly, bypassing DIVAR IP AIO/BVMS system.  

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 explains how to fix the behavior of MIC IP 7000i/9000i Bosch camera when is out of focus during a rapid zoom

Find out from this article what is the domain name used to connect your DIVAR to the Remote Portal

 This article shows the keyboard shortcuts that can be used by operators when operating the BVMS system. 

The RCP documentation can be found in the Firmware .zip file on the product page.

This guide is meant to explain how to enable the appropriate debug commands for logging during random reboot situations, and which logging to collect for troubleshooting, as in general there are multiple triggers that can cause a device to reboot. The information gathered will help to analyze the root cause.  Please make sure that all of the logs collected cover the same time period.