Embedded Files
Knowledge base > Components > ONVIF
An ONVIF camera is an IP camera that supports the ONVIF (Open Network Video Interface Forum) standard, an industry standard for IP-based video surveillance products. ONVIF promotes interoperability between different surveillance devices, such as cameras, Video Management Systems (VMS), and other network equipment, regardless of the brand. This ensures that ONVIF cameras can be easily integrated and managed within a networked surveillance system, offering more flexibility and greater choice in selecting compatible devices.
To add an ONVIF camera to Banalytics VMS, follow these steps.
First, make sure the camera is plugged into a power source and connected to the internet via a wired or wireless connection. To confirm that the camera is correctly connected, ensure that it is on the same local network as the device running Banalytics VMS. The camera must have an assigned IP address and be reachable over the network.
To verify that the camera is accessible, you can use the Network device discovery component within Banalytics VMS. This tool scans your local network for connected devices, including ONVIF cameras, and helps confirm the camera’s connectivity.
Then, click the + button next to an ONVIF camera sub-menu under the Banalytics server.
Configuration options
Configuration options
Value
Required (Yes/No)
Description
Default
Restart on failure
Yes
Restart mode upon catching an error:
Stop on failure - not restarted until triggered manually.
Immediately - tries to restart automatically immediately after catching an error.
10 sec - tries to restart automatically with a 10-second delay after catching an error.
30 sec - tries to restart automatically with a 30-second delay after catching an error.
1 min - tries to restart automatically with a 1-minute delay after catching an error.
Default to 10 sec
MAC Address
No
The MAC address is a unique identifier for the camera's network interface. You can find it in the camera’s web interface or through Network device discovery in Banalytics VMS. In some cases, the MAC address is also printed on a sticker on the camera itself or its packaging. This unique address helps distinguish your camera from others on the network.
Title
Yes
Choose a name for the camera to easily identify it within your system (e.g., "Garage Camera").
Host and Port
Yes
The IP address (host) and port number are required to establish communication between Banalytics VMS and the camera. You can find the camera’s IP address in the camera’s documentation or use Network device discovery to locate it. The default ONVIF port for HTTP is 80, and for HTTPS, it’s 443, but these may vary based on the camera’s settings.
Username and Password
Yes
You’ll need the username and password for the camera’s web interface. If you don’t have these, check the camera’s documentation, look for a sticker on the camera itself, or check its packaging for default login credentials. If these options don’t work, you may need to reset the camera to its factory settings.
Transport protocol
Yes
This setting defines how the camera communicates with other devices:
HTTP: A standard protocol, typically with lower quality and higher latency.
RTSP (Real-Time Streaming Protocol): A popular option for high-quality streaming.
UDP (User Datagram Protocol): Low-latency, connectionless protocol suitable for real-time video.
TCP (Transmission Control Protocol): More reliable but introduces additional latency.
The available transport protocol options in Banalytics VMS depend on the ports supported by the camera’s web interface. If multiple ports are defined, you can choose the most suitable protocol based on your specific needs (e.g., RTSP for real-time streaming or TCP for reliable transmission). Below, we've provided some guidance for different use cases to help you decide which protocol to use.
Default to RTSP
Override RTSP Port
No
In some cases, you may need to change the default RTSP port (usually 554) if there’s a conflict or for security reasons. Ensure that the new port does not conflict with other services and that network devices are configured to allow traffic on the new port.
You can override the RTSP port in Banalytics VMS, allowing you to set a different RTSP port than the one defined in the camera’s web interface. Once you specify the new RTSP port in Banalytics VMS, make sure that the network devices (routers, firewalls) are configured to allow incoming traffic on that new port.
Transport protocol selection
Transport protocol selection
In the entire ONVIF camera setup, the transport protocol often appears to be the most complicated parameter to configure, especially considering that a camera can be used for various purposes. Selecting the right transport protocol is critical for achieving optimal performance, whether you're streaming live video, recording footage, or monitoring for motion.
To help with this, we have created a dedicated article offering advice on configuring media profiles based on your specific surveillance needs. In this section, we'll guide you on which transport protocol to use for each of the six media profiles you may choose for your system.
Recommended protocol: UDP or RTSP.
UDP: This protocol is ideal for environments where low latency is crucial. If you're monitoring areas with movement and need real-time updates, UDP ensures minimal delay, which is essential for quick detection of motion events.
RTSP: If you require a more reliable stream with a balance between quality and performance, RTSP can be used. It will provide steady video streaming, which is particularly useful when you need both motion detection and consistent video quality.
Recommended protocol: RTSP or UDP.
RTSP: For real-time remote monitoring, RTSP is the best choice as it provides high-quality video streaming with minimal buffering, ensuring a seamless viewing experience.
UDP: If your primary need is low latency and you can handle occasional packet loss, UDP works well for live monitoring, especially in high-demand environments where speed is more critical than error-free video.
Recommended protocol: TCP or RTSP.
TCP: TCP ensures that all video data is reliably transmitted without packet loss, which is critical when you need to record high-quality footage for evidence or analysis. It's the preferred protocol when data integrity is essential.
RTSP: If you don’t need the additional reliability of TCP, but still want a steady video stream for recording, RTSP can work well for ensuring video quality during recording.
Recommended protocol: HTTP or UDP.
HTTP: In environments with severely limited bandwidth, HTTP provides the most basic, low-bandwidth video stream, suitable for basic surveillance without high-quality requirements. It is especially useful when you don’t need real-time video but still need some level of monitoring.
UDP: If low latency is needed but the network can handle a minimal drop in quality, UDP can also be used for transmitting video with reduced bandwidth consumption.
Recommended protocol: RTSP or UDP.
RTSP: RTSP is best for low-light surveillance where stable streaming is important, as it ensures consistent video quality even under challenging lighting conditions.
UDP: For environments where low-latency is crucial (e.g., live video monitoring of low-light areas), UDP is a good alternative if occasional loss of video quality is acceptable.
Recommended protocol: RTSP or UDP.
RTSP: Since PTZ cameras need smooth video streaming during movement, RTSP ensures high video quality and supports PTZ control without significant latency.
UDP: If minimizing delay is critical, UDP is a good option for real-time interaction with the PTZ camera, though the quality may degrade slightly compared to RTSP.
Each media profile serves a different purpose depending on the specific needs of your surveillance system. The transport protocol you select (HTTP, RTSP, UDP, or TCP) should be aligned with the use case to ensure optimal performance.
UDP or RTSP
UDP for low-latency, real-time monitoring.
RTSP for reliable streaming with balanced quality.
RTSP or UDP
RTSP for high-quality, low-latency streaming.
UDP for minimal delay, less reliability.
TCP or RTSP
TCP for error-free, reliable streaming.
RTSP for stable, high-quality streaming during recording.
HTTP or UDP
HTTP for basic, low-bandwidth streaming.
UDP for minimal latency in low-bandwidth settings.
RTSP or UDP
RTSP for stable, high-quality video in low light.
UDP for real-time streaming with slight quality loss.
RTSP or UDP
RTSP for smooth video and PTZ control with stable quality.
UDP for minimal delay with some quality trade-offs.
Page updated
Report abuse