Add a non-Verkada camera to a Command Connector

Connect non-Verkada cameras to Command with a Command Connector

The Command Connector integrates non-Verkada cameras into Command. This allows you to view the camera live streams and access Verkada analytics and features.

---

Before you begin

Connecting a camera to multiple video security systems simultaneously can degrade streaming performance and lead to inconsistent video quality. Verkada recommends connecting each camera to a single system to maintain optimal performance and video integrity.

For ONVIF cameras

1. Verify the non-Verkada camera datasheet states ONVIF Profile S compatibility. Check the Command Connector hardware compatibility list to make sure your model is compatible.

   Note: Verkada Command only supports I-frames and P-frames. B-frames are not supported.
2. Verify the Command Connector and non-Verkada camera are on the same Local Area Network (LAN). Dynamic NAT or L3 translation is not supported between the devices.
3. Verify the non-Verkada camera IP address is configured with one of the following:

   1. Static IP
   2. DHCP reservation

   The Command Connector communicates with cameras using IP addresses. If a camera's IP address changes, it will stop streaming.
4. The Command Connector and non-Verkada camera need bidirectional traffic to communicate. Verify these ports are allowed on the network:

   1. TCP+UDP port 80 - needed for camera HTTP web server access. ​Note: If you are using a non-default port allow that port in TCP+UDP.
   2. TCP+UDP port 554 - needed for camera RTSP streams.
5. Ensure that the IP address, along with the admin username and password is available for each of the non-Verkada cameras that will be added to the Command Connector.

For Non-ONVIF cameras

1. Check the Command Connector hardware compatibility list to ensure your model is compatible.

   Note: Verkada Command only supports I-frames and P-frames. B-frames are not supported.
2. Verify the Command Connector and non-Verkada camera are on the same Local Area Network (LAN). Dynamic NAT or L3 translation is not supported between the devices.
3. Verify the non-Verkada camera IP address is configured with one of the following:

   1. Static IP
   2. DHCP reservation

   The Command Connector communicates with cameras using IP addresses. If a camera's IP address changes, it will stop streaming.
4. The Command Connector and non-Verkada camera need bidirectional traffic to communicate. Verify this port is allowed on the network:

   • TCP+UDP port 554 - needed for camera RTSP streams.
5. Ensure the IP address is available and part of the RTSP URL that will be used for each non-Verkada camera that will be added to the Command Connector. Credentials are only required if RTSP authentication is enabled on the camera.
6. Ensure that streaming configurations for the RTSP stream meet the following criteria for an optimal experience:

   1. Resolution: should be greater than 2MP and should not exceed 4K.
   2. GOV Length: 80.
   3. FPS: cameras must stream at a minimum of 5 FPS and a maximum of 20 FPS.
   4. The following bitrates are recommended based on resolution:

   

---

Add a camera to the Command Connector

You need Organization Admin and/or Site Admin permissions for your Verkada Command organization to complete these actions.

1

In Command, go to All Products > Devices.

2

Select a Command Connector.

3

Under Connected Channels, click + Add Cameras.

4

Cameras can be added in the following ways:

a. Network discovery b. CSV upload c. Manually add IP addresses

When using Avigilon cameras managed in Avigilon Control Center 7 with the Verkada Command Connector, the HQ (vkda-high) stream must be configured manually in ACC 7 before adding the camera.

• Required settings: H.264 or H.265, no B-frames, 2MP–4K resolution, GOV 80, 5–20 FPS
• If streaming to both NVR + Command Connector: enable Multicast and Dual Mode per camera

Missing these settings may prevent the HQ stream from working.

Network Discovery

If a non-Verkada camera is discoverable on the LAN, it can be added to the Command Connector via network discovery.

1

Select Network Discovery to view the list of cameras discoverable to the LAN.

2

Click the checkbox to select a camera. Then select + Credential and input the username and password.

3

Select Continue to view the list of cameras successfully added.

CSV upload

A CSV template can be used to add cameras in bulk to the Command Connector.

For ONVIF cameras, the IP address, username, and password fields are required, and all other fields are optional.

1

Select which CSV template to download. You can select IP Cameras with ONVIF or RTSP Cameras.

2

Fill out the template.

The HTTP Port field is required if the camera is configured on a non-standard port.

3

Select Upload CSV and upload your file.

Manually add cameras via IP address

1

Select Manually Add IPs Instead. Input the IP address range and click Verify.

2

Select the camera(s) you want to add and click Activate.

---

Verify non-Verkada camera configuration

The Command Connector configures non-Verkada cameras through HTTP requests. You can connect to the camera web server to validate the configuration.

1

The Command Connector will create one administrator user with the username verkada.

2

Two media profiles will be configured.

a. An HQ stream labeled vkda-high. b. An SQ stream labeled vkda-low.Note: A pair of media profiles will be created per channel if the device is a multi-sensor and has multiple channels.

The Command Connector creates the vkda-high and vkda-low profiles when Streaming Profile Selection is set to Optimal. In Manufacturer mode it uses the profiles already on the camera. See Configure streaming profile selection for non-Verkada channels.

The vkda-high profile will also be used for Verkada analytics and thumbnails.