Security: Video

Have a look at this article and learn how to fix the Add Scriptlet button which does not become active. It stays grayed out. Same happens with ClientScript and ServerScript.

If you want to be able to replay the recording for the complete retention time, you should use VRM replay. VRM should be accessible and added to the VSC

  Important note Currently, the VRM is itself very seldom used in combination with Genetec. Starting with 2022, Genetec developed a new driver for Bosch cameras “Hybrid driver for CPP13/14+”. With this, the VRM is not considered anymore. With the old “Legacy (CPP7.3 and older) the VRM is still supported.      Related Products: VRM, Genetec Security Center Overview: It is possible to use VRM free of charge (no extra VRM license is required) within Genetec Security Center. Genetec is sending encrypted secret to the VRM server with the number of the licensed channels. When VRM receives and validates this, it can be used for that number of channels for 24 h. A periodic license update is send by Genetec, so the VRM licensing is guaranteed as long as it is used with Genetec Security Center. Default settings, if not extra configuration is needed or done. -License for 1000 Cameras - License update is done every hour   How to license more than 1000 cameras or change the license update period for VRM within Genetec Security Center: Open the Config Tool and Launch a Video Task Select the Archiver Go to the Resource Tab and click on Extensions From the Tab Installed extensions select Bosch. In the Tab VRM add a new VRM and/or select already configured VRM. Click on Advanced settings and add the following parameters If you need to license the system with more than the default 1000 licenses – create the parameter with Name VrmLicenseRequestCount and as value put the required number of licenses. The parameter name is case sensitive If you need to change the duration of the period between each license request (there is always one license request when the archiver starts) – create the parameter with Name VrmLicenseRequestPeriod. The duration of the period is in milliseconds. The default value is one hour. If the value is set to 0, the license request are disabled. The parameter name is case sensitive     Press Enter to confirm the entry and then Close Press Apply and then OK. At the webpage of the VRM one can check if the number of licenses is changed. If you would like to know how to replay the recordings from a Bosch camera managed by Bosch Video Recording Manager (VRM) in Genetec Security Center software, please follow this video: How to use VRM recording in Genetec Security Center   Note:  To support customer needs and to leverage the most important features of Bosch cameras (like data security, Video Analytics, and intelligent bitrate management), the agreed focus of Bosch and Genetec is on the Genetec Archiver Recording Solution. Current and future developments are focused on this recording solution and the VRM in Genetec will only be supported to maintain existing and upcoming projects where a VRM solution is selected. There will be no development of new features. In this maintenance mode, the following is possible: • Certification of new VRM versions (for projects)* • Certification of new DIVAR IP’s* *Requirement: stable API on VRM side Note: The VRM itself might offer more functionality not covered with the integration in Genetec.

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.  

License expansions missing after upgrade to BVMS 11 in Remote Portal. Only 1 x MBV-XCHANPLU license activated instead of 16 x MBV-XCHANPLU. What to do?

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

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?

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.

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

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.