Which is the VSG preparation to support ONVIF Profile T in BVMS 10.0?
Additionally to ONVIF profile S, BVMS 10.0 supports ONVIF profile T.
Profile S concentrates on basic video streaming and configuration
Profile T focuses on advanced video streaming like use of H.264, H265 encoding formats, HTTPS streaming and event definition is more precise there
Profile T functionality is only supported for devices that are added over VSG
For conditional and optional features please refer to the BVMS - ONVIF Device compatibility article.
Functionalities available for all devices added over VSG (BVMS 10.0):
The ONVIF relays are scanned automatically
Relays can be added to the Logical Tree by drag& drop and triggered from there
Thee relay status is automatically updated and signaled with an appropriate icon in Operator Client
Status and triggering is possible over BVMS scripts
Once ONVIF camera is added to VSG, its capabilities are automatically scanned
In the “Add ONVIF encoder” dialog it was added a new device properties entry that shows weather AUX is supported by device. The AUX commands are sent to camera vis VSG and can be triggered for an ONVIF device on alarm.
Note: most of the ONVIF cameras do not support all in Configuration Client available events
ONVIF vendor mapping:
ONVIF camera connection to VSG and BVMS Operator Client:
Live video from ONVIF camera to VSG or Operator Client can be secured with a Secure connection check box in the Add/ Edit ONVIF Encoder dialog. The secure connection is not chosen by default. (Default HTTPS port is 443)
If the live video does not have to be secured, it is possible to choose what protocol should be used: TCP, UDP, Multicast, UDP Unicast.
Note: The protocol automatically is switched to TCP if Secure connection is chosen:
Ports used between ONVIF camera and VSG:
RTP/RTSP/TCP (secured 😞 443
HTTPS: 443/ customizable (requires TCP)
RTP/RTSP/TCP (unsecured 😞 80
HTTPS: 80/ customizable (requires TCP)
Unicast/ Multicast UDP:
has to be configured in a camera first
control connection via http port (default port 80 or customizable/ RTSP port: 554)
Nice to know:
For a better understanding of the BVMS 10.0 - ONVIF camera integration with VSG , we encourage you to join our online Trainings from Bosch Building Technologies Academy!
This article describes the different components that Bosch Video Management System offers to to establish a connection between Bosch Video Management System and a 3rd party management system.
This description helps you in writing your own commands for controlling Bosch VMS from inside your management system.
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
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
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.
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?
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?
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.)
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.
Provide a little sample application that illustrates the BVMS SDK issue and list the reproduction steps.
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