The Ava Aware Video Management System (VMS) allows integrations with several third party cameras and encoders. These integrations revolve primarily around the support of Open Network Video Interface Forum (ONVIF) within the device but there are other methods Ava aware can use as well. This document will describe the capabilities Ava Aware supports, Its methods for managing third party devices, and troubleshooting the most common issues when adding these devices.
TABLE OF CONTENTS
- Supported Methods For Cameras
- Tools To Help Integrations
- Most Common Issues Adding Cameras
Supported Methods For Cameras
Ava aware supports the following methods for communicating with third party cameras:
- Onvif profile S
If a camera does not support one of these methods, they will not be directly compatible with Ava Aware.
Tools To Help Integrations
Ava Aware includes some built tools to help third party cameras have a smooth transition to the VMS:
- Media Configuration
- Manual Stream Mode
Media configuration is set at the device level on cameras once they have been added to Aware. This can be found in the Devices tool, clicking Edit Settings and navigating to the Connection tab of the device.
There are two settings available for media configuration:
- Ava Aware (Active)
- Camera (Passive)
Ave Active will request all the profile information from the device that has been added. Aware will then attempt to push the settings configured manually or automatically.
Passive configuration mode will read all the profile information from the camera as well, however it will not push any configurations to the camera for automatic or manual stream settings.
Manual Stream Mode
Manual stream mode allows a user to configure the streams that Aware will use to communicate with the camera. This can be used in conjunction with Media Configuration settings to optimize the streams being received by aware. Below is a stable that summarizes these options
|Media Configuration||Stream Mode||Outcome|
|Active Mode||Automatic||Aware requests all profile information from the camera. Selects the best streams, pushes settings to camera, requests streams we just configured.|
|Active Mode||Manual||Aware requests all profile information from camera, User sets stream parameters, Aware then pushes these settings to the camera and requests these streams once set.|
|Passive Mode||Automatic||Aware requests current profile information. Aware then attempts to automatically allocate the received streams for its own use.|
|Passive Mode||Manual||Aware requests current profile information from camera. User then manually sets the stream parameters. (There is no push to the camera)|
Most Common Issues Adding Cameras
Cameras show video "Tearing" in streams
In cases where tearing is observed in streams, the best course of action would be to:
- Investigate the stream to verify it has the appropriate values being received on Ava Aware.
- Test the stream using a tool like ONVIF device manager or VLC if an RTSP stream to see if the issue is seen there as well
- Verify if there is any packet loss or latency being observed or reported via aware.
GOP too long
When the error message "GOP too long" appears on cameras, this indicates that the Group of Pictures (GOP) received from the camera is not an an optimal value for analytics. Depending on how the camera has been added (active or passive) we can use the above chart to best tune the camera to bring these values to an optimal state. This may include using manual stream mode and configuring appropriate values for the analytics stream.