About Central-Support

Question   What to do when ‘Authentication failed’ message appears in VSC 3.7.0.817 for CPP4 cameras?    Answer   After upgrading the Video Security Client (VSC) to 3.7.0.817 version, CPP4 cameras could no longer be accessible in VSC, displaying the 'Authentication Failed' error.  To resolve this issue, upgrade the Video Security Client to version 3.7.1.840. According to the Release Notes (page 2), this version fixes the authentication failure with legacy cameras (CPP4) .    Nice to know:  Why the Live view shows ‘Authentication failed’ in Video Security App?    ... View more

Required programming for RPS remote connection to the FPD-7024 via Cellular or Ethernet. Press 0 Enter 9876 to enter programming Press 6 Program Accounts Press 7 Alternate Communication – Select (0) Network *(See note below) Press * / Back key once Press 4 Ring Count to set it to (02) Press # Press (* / BACK) key once – The display should read Program Modes on the top line Next Enable Remote Programming - Press (3) Program System Press (7) Remote Program Press (1) Enable Press (* / BACK) key once Update the Option Buss - Press (3) Program System Press (4) Option Buss Press (1) Update Buss – The keypad will display “Updating . . .  TOT BUS DEVS: XX”. XX is the total number of devices on the Option bus. If it displays (00) check wiring and addressing of each device on the Option bus. Each device needs to have its own unique address.  Repeat the steps above until all the devices are learned to the Option bus of the panel.\Press (* / BACK) key 3 Times to exit programming 14   Press (* / BACK) key 3 Times to exit programming   Note: RPS Connects to the Cellular or Ethernet device addressed as 250 only, it will never connect to a device addressed 134. ... View more

Question   How can you secure access and manage ports for Bosch IP video devices?   Overview: General network port usage and video transmission: HTTP, HTTPS and video port usage: Video software and port selection: SSH tunneling:   Answer    All Bosch IP video devices come with built-in multi-purpose web pages. The device-specific web pages support both live and playback video functions, as well as some specific configuration settings that may not be accessible via a video management system. The built-in user accounts act as the access to the different sections of the dedicated web pages. While the web page access cannot be completely disabled via the web page itself - the Configuration Manager could be used for -, there are several methods to cloak the presence of the device, restrict access, and manage video port usage.   General network port usage and video transmission: All Bosch IP video devices utilize Remote Control Protocol Plus (RCP+) for detection, control, and communications. RCP+ is a proprietary Bosch protocol which uses specific static ports to detect and communicate with Bosch IP video devices - 1756, 1757, and 1758. When working with BVMS, or another 3rd-party vendor video management system that has integrated Bosch IP video devices via the Bosch VideoSDK, the listed ports must be accessible on the network for the IP video devices to function correctly.  Video can be streamed from the devices in several ways: UDP (Dynamic), HTTP (80), or HTTPS (443).  The HTTP and HTTPS port usage can be modified (see HTTP, HTTPS and video port usage, page 17). Prior to making any port modifications, the desired form of communication to a device must be configured. The Communication menu can be accessed using Configuration Manager.  1. In the Configuration Manager, select the desired device. 2. Select the General tab, then select Unit Access. 3. Locate the Device access portion of the page. 4. In the Protocol list, select the desired protocol: – RCP+ – HTTP (default) – HTTPS If selecting HTTPS communications, communication between Configuration Manager and video devices will utilize HTTPS (TLS) to encrypt the payload with an AES encryption key up to 256 bits in length. This is a free basic feature. When utilizing TLS, all HTTPS control communications and video payload is encrypted via the encryption engine in the device.    HTTP, HTTPS and video port usage: HTTP and HTTPS port usage on all devices can be altered or turned off. Encrypted communication can be enforced by disabling RCP+ port as well as the HTTP port, forcing all communication to use encryption. If HTTP port usage is turned off, HTTPS will remain on and any attempts to turn it off will fail.  1. In the Configuration Manager, select the desired device. 2. Select the Network tab, then select Network Access. 3. Locate the Details portion of the page. 4. In the Details portion, modify the HTTP and HTTPS browser ports and RCP+ port using the drop down menu: – HTTP browser port modification: 80 or ports 10000 to 10100 – HTTPS browser port modification: 443 or ports 10443 to 10543 – RCP+ port 1756: On or Off   Video software and port selection: Adjusting these settings will also affect what port is utilized for video transmission when using video management software in your LAN.  If all IP video devices are set to HTTP port 10000, as an example, and the BVMS Operator Client is configured for "TCP tunneling", then all video transmissions on the network will be made across HTTP port 10000.   SSH tunneling: For a remote device access with BVMS Operator Client via public networks, BVMS provides Secure Shell (SSH) tunneling to ensure secure (encrypted) communication.  SSH tunnelling constructs an encrypted tunnel established by an SSH protocol/socket connection. This encrypted tunnel can provide transport to both, encrypted and un-encrypted traffic. The Bosch SSH implementation also utilizes Omni-Path protocol, which is a high performance low latency communications protocol developed by Intel.  For more information on how to configure the SSH service in BVMS, refer to the BVMS documentation. For more information on how to configure DIVAR IP systems for a secure remote access with BVMS Operator Client, refer to the DIVAR IP documentation.    Nice to know: Cybersecurity guidebook for Bosch IP video products Secure by default - Increasing the default level of IP camera security  ... View more

Question   Does the FLEXIDOME Multi 7000i camera consume 4 licenses in BVMS?   Answer   The FLEXIDOME Multi 7000i camera is a 4-imager camera which in BVMS translates into 4 channels. Each channel in BVMS requires a license for it to be integrated into the system.  However, each FLEXIDOME Multi 7000i camera comes with 3 free BVMS licenses.  Please note that starting with BVMS version 11.1.1, the device-based licensing feature was introduced for cameras >= CPP7.3, including FLEXIDOME Multi 7000i cameras (4camera sensor model), MIC IP fusion 9000i (2 camera sensor model) and also the ONVIF multichannel cameras.   This feature applies for standard VRM, VSG, Live only and Local Storage channels as well as for Failover and Secondary VRM channels. 🛈 If a multichannel camera was already connected in BVMS 11.0, after the upgrade to 11.1.1, three channel licenses will become "unused" again. ⚠️  Note: Bosch analog encoder devices, e.g. VIDEOJET multi 4000 is not affected by this feature, each channel counts as one channel license.   So, in conclusion: From BVMS 11.1 and newer version, the FLEXIDOME Multi 7000i camera is using only 1 license (including 4 channels). If you are using BVMS lower than 11.1, then it will consume you 4 channel licenses.       ... View more

Question   Can any user view the restricted video in BVMS Operator Client?     Answer   The restricted video can only be viewed by users that have this permission. You can use the standard user group for managing the access to the Management Server. The Operator Feature page/tab allows you to configure various permissions for the selected user group. Select the check box to allow restricting video data, Save & Activate your changes: An user that has the Restrict video permission enabled, can see restricted video in the timeline of the Operator Client. For more info, please check the BVMS 12.1 Configuration Manual, page 325: Configuration Manual ... View more