Security: Video

This article explains how to connect an INTEOX camera to the S&ST ecosystem using Configuration Manager (7.20 and later).

When accessing the Operator Client from the Kiosk mode, the camera streams displayed on the cameos show a view that does not match the view from Operator Client running from desktop (Under the BVRAdmin account) or Remote Desktop.

Question   Why the Windows license key and System ID are the same on all my DIVAR IP 6000?   Answer   These units come pre-licensed from the factory and they have an OEM (Original Equipment Manufacturer) license activated. Please see more information about OEM on the Wikipedia link below:  https://en.wikipedia.org/wiki/Original_equipment_manufacturer According to its datasheet, all components relevant to the usage of DIVAR IP 6000 as storage array in a Bosch recording solution are pre-installed and preconfigured. Simply connect to the network and power the unit up — DIVAR IP 6000 is ready to begin recording straight out-of-the-box.

Let's suppose that the "Customer" user should see 3 cameras in the Video Security App. When logging to the App, he can see only 2 of them. Why?

Bosch Remote Portal connects you to your Bosch Security devices from anywhere and lets you perform remote administration and maintenance anytime

Depending on the 3rd party cameras’ capabilities, there are different ways of adding cameras to Bosch Alarm Management.

In Cloud-based Services, different 'Actions' can be configured for automatic processing as well as manual action for the operators (Alarm Agents). There are 2 different options how an action is processed: An 'Automatic Action' is processed automatically when the related Service Scenario is performed. An 'Intervention Action' is executed manually by an operator from the Cloud-based Service Operator Interface. This note shows available actions in Cloud-based Services and provides a step by step instruction to configure these actions.   Step-by-step guide   1. Send e-mail "Send e-mail" sends an e-mail notification to the configured recipient(s). The action can be used as manual action for the operators (Intervention Action). The content of the alarm email can be configured to the customer's needs.   To configure a "Send e-mail" action, perform the following steps: 1. Open Cloud-based Services Configuration website (/config), log in as Integrator or Config Agent. 2. Enter the related Account. 3. Click tab 'Actions'. 4. Click '+' button to add an action. 5. Give the action a descriptive name and select 'Email'. 6. Type recipients, CC's, mail subject and message. Use the pull down to enter environment variables to the e-mail text. 7. Click 'Create'. 8. Add the action to a Service Scenario for processing.   2. Execute PTZ Command "Execute PTZ Command" starts an auxiliary command on a Pan-Tilt-Zoom (PTZ) camera. The action can be used for automatic processing (Automatic Action) as well as manual action for the operators (Intervention Action). Note the available auxiliary commands in the camera’s manual. To configure an "Execute PTZ Command" action, perform the following steps: 1. Open Cloud-based Services Configuration website (/config), log in as Integrator or Config Agent. 2. Enter the related Account. 3. Click tab 'Actions'. 4. Click '+' button to add an action. 5. Give the action a descriptive name and select 'Execute PTZ Command'. 6. Select PTZ camera, select auxiliary command and type the command No. 7. Click 'Create'. 8. Add the action to a Service Scenario for processing   3. Go to PTZ Preposition "Go to PTZ Preposition" moves a Pan-Tilt-Zoom (PTZ) camera to a preposition. The action can be used for automatic processing (Automatic Action) as well as manual action for the operators (Intervention Action). The prepositions (shots) need to be configured via the Device Page upfront. To configure a "Go to PTZ Preposition" action, perform the following steps: 1. Open Cloud-based Services Configuration website (/config), log in as Integrator or Config Agent. 2. Enter the related Account. 3. Click tab 'Actions'. 4. Click '+' button to add an action. 5. Give the action a descriptive name and select 'Go to PTZ preposition'. 6. Select PTZ camera and type the preposition No. 7. Click 'Create'. 8. Add the action to a Service Scenario for processing.   4. Play Audio on Device "Play Audio on Device" replays an audio file directly from the device's loudspeaker. The action is intended to perform standard audio interventions without the need for the operator (alarm agent) to talk. "Play Audio on Device" can be used for automatic processing (Automatic Action) as well as manual action for the operators (Intervention Action). Audio files need to be prepared and installed by CBS development. If you want to use your own audio files, please get in contact with technical support. To configure a "Play Audio on Device" action, perform the following steps: 1. Open Cloud-based Services Configuration website (/config), log in as Integrator or Config Agent. 2. Enter the related Account. 3. Click tab 'Actions'. 4. Click '+' button to add an Action. 5. Give the Action a descriptive name and select 'Play audio on device'. 6. Select the audio device and select the audio file. 7. Click 'Create'. 8. Add the action to a Service Scenario for processing.   5. Switch Relay "Switch Relay" switches a relay of one or more IP devices. The action can be used for automatic processing (Automatic Action) as well as manual action for the operators (Intervention Action). To configure a "Switch Relay" action, perform the following steps: 1. Open Cloud-based Services Configuration website (/config), log in as Integrator or Config Agent. 2. Enter the related Account 3. Click tab 'Actions'. 4. Click '+' button to add an action. 5. Give the action a descriptive name and select 'Relay'. 6. Select activation mode and select one or more relays to switch. 7. Click 'Create'. 8. Add the action to a Service Scenario for processing.   6. Notify Monitoring Center and Log Event Both action types "Notify Monitoring Center" and "Log Event" are obsolete and can not be used in a Service Scenario.  See also: How to add a user to Remote Alert service in Remote Portal?

This article lists the initial troubleshooting steps and concrete instructions for collecting logging for issues with ONVIF cameras, added to BVMS system. We will classify the different issue scenarios one can have using ONVIF cameras in BVMS system. Depending on the issue the article lists the required logging to start initial troubleshooting.

Follow the steps from this article to add a Bosch IP camera to the Alarm Management.

Possible causes and solution(s) Cameras which get connected from the customer's site to Bosch Remote Portal use an outgoing connection via TCP port 42000. Outgoing connections usually are not blocked by a router, however in a corporate network with proxy server, firewall, etc. involved, the IT department might open the needed ports. The troubleshooting steps below might help you to connect cameras to Bosch Remote Portal.   Known issues on camera commissioning In most cases when camera commissioning fails, the root cause is: No connection to Bosch Security Cloud from the customer’s site Blocked Internet connectivity (e.g. blocked ports by proxy or firewall) User belongs to more than one Company in Remote Portal The camera is already commissioned to a different cloud instance Known camera firmware issues Known camera date issue Further…  

To be able to deploy a camera with DHCP disabled to Bosch Remote Portal, please perform the steps from this article.

The Windows Storage Server operating system of DIVAR IP all-in-one 7000 is installed on a two SSD drives in redundant (mirrored) configuration. Health status of the mirrored OS drives can be monitored using a tool called Virtual RAID on CPU (formerly known as Rapid Storage Technology). Installation and configuration steps are described below. Step-by-step guide   1. Installation: Download the setup from here Copy the content to a USB drive When the BVMS default screen is shown, press CTRL + ALT + DEL Hold down the SHIFT key while clicking Log off Log in as BVRAdmin Transfer the IATA_CD.exe from the USB drive to the BVRAdmin desktop Double click the IATA_CD.exe executable Follow the installation procedure as shown in the screen shots     2. Email notification: Note: The E-mail notification feature is based on SMTP access without authentication. It is strongly suggested to use this functionality only with a dedicated server in the local network, which is specifically configured for this purpose and doesn’t handle any critical data.

The Clear button on the Configuration Manager is designed to clear the codes that are self-generated by the IP firmware or the Configuration Manager itself. Follow the steps below, if you want the "Clear" button from Configuration Manager to able to erase the Alarm task script that are self created by users themselves.

This article explains how you can collect VRM logs in different versions of it

The browser supported by Bosch cameras depends on the CPP that camera belongs to and on the Firmware version the camera has.. In web browsers that do not support MPEG-ActiveX, VCA configuration is only possible via Configuration Manager.

When you request to reset the DIVAR password, the Central Technical Support team provides you with the unlock codes. The unlock codes received from the CTS are valid only for 1 Day. Moreover, please make sure that the date displayed on the Live monitor matches the date you requested the password reset.

Before requesting a password reset, please note that you need to provide some important information to the Central Technical Support Team to get help from them.

This article gives an overview of CPPs that correspond to certain types of cameras, decoders and encoders.

⚠️ NOTE: This procedure is the same for all 2U and 3U systems and is also applicable for DIP 7000 AIO GEN3 , except 3108 FW might be different, depends on the exact model.

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.