Security: Video

This article explains how to configure an alarm communication between BVMS and Gmail e-mail address.

This article contains a simplified and generalized example, that could be helpful in building a particular tailored script related to implementation of event receiver in BVMS SDK scriplet.

The digital monitor wall functionality was removed since BVMS v11.0, and this is also stated in the release notes.

If you add a decoder that has 2 monitors connected, you must display the Edit Decoder dialog box of the decoder and update the device capabilities of this decoder. For each monitor add a further monitor wall.

This article explains step by step how to play exported recording files from VRM eXporter Wizard in BVMS Export Player.

This article provides an answer to the question: Can I install Intelligent Insights into DIVAR IP all-in-one 5000?

There is an issue with VRM versions lower than 4.0 where the retention time for recordings from VSG instances is set incorrectly. There are a few things that usually cause the recording mode to be set incorrectly. Find out more details from this article!

This article presents where are the Transcoder Log settings and how to enable them for log collection.  

This article explains why the Live view shows ‘Authentication failed’ in Video Security App.

This article presents what symptoms appear in BVMS Operator Client if Time synchronization is wrongly set. Also provides some recommendations about what to do to avoid this symptoms. 

This articles explains what does the User Name column indicate in the BVMS Operator Client LogBook.

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.  

Check this article and find out how you can avoid displaying black image in Operator Client BVMS v11.0

Can I display more than 1 camera on a single Monitor of Decoder VJD-7513 in BVMS 11.0 when an alarm is triggered?   System Overview: BVMS 11 1 monitor connected to 1 x VJD-7513 that is part of a Monitor Group The monitor has a layout consisting of several image panes Desired status: when an alarm is triggered → pop up the image of the 4 cameras on the same decoder monitor

This article contains a step-by-step guide which explains how you can do the setup for the camera's live view image pane to be displayed in full screen in the Operator Client if a motion alarm is triggered on that camera,

Windows 11 Pro is now officially supported as OS for BVMS 11.1.1 Operator Client

BVMS Version 10.0: please note that, currently, the export mechanisms provided in the BVMS Configuration Client do not export the user-data.

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.

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