Forsight specializes in advanced safety and security video analytics for construction sites and offers seamless integration with Meraki MV cameras using Meraki RTSP streams, Webhooks, and MV Sense MQTT.

Meraki RTSP streams

Forsight deploys powerful and robust (IP67 rated) edge devices that process the RTSP streams from Meraki cameras and stream the footage along with the analytics metadata to the cloud.

The only requirements are that:

  • the Meraki RTSP stream is enabled for each camera that you want to analyze and stream through Forsight’s Construction Autonomous Monitoring System (CAMS)
  • the cameras and edge devices are on the same subnet

Meraki RTSP streams must be enabled per-camera which can be done through the Meraki Dashboard:

  1. Select Cameras → Monitor → Cameras and select a camera from the list.
  2. Select Settings → Video Settings.
  3. Under External RTSP select “Yes” and use the provided stream link to access the camera.

[Enable RTSP.mp4]

Forsight’s tech support will help you with any question or problem you might have.

How do we guarantee the security of the RTSP Stream?

First, you should always follow Meraki best practices to secure the cameras by:

Forsight’s CAMS system does not use port forwarding in order to increase security and guarantee the privacy of your streams. Instead, we conform to the highest standards of Amazon Web Services network security procedures by using Transport Layer Security (TLS) 1.2 and cipher suites with perfect forward secrecy (PFS) such as Ephemeral Diffie-Hellman (DHE) or Elliptic Curve Ephemeral Diffie-Hellman (ECDHE) when streaming the video to the CAMS cloud.


RTSP is only supported on second-generation cameras (MV*2 cameras only). It is not supported on the MV21 and MV71.

RTSP is only available on MV 4.2 firmware and newer. Please refer to Managing Firmware Upgrades for steps on scheduling this firmware upgrade for your network.

Meraki Webhooks

Forsight also utilizes Meraki Webhooks, which offer a powerful and lightweight way to subscribe to alerts sent from the Meraki Cloud when something happens, in order to monitor the health of the cameras and the edge devices and provides a detailed activity log and alerting system in the Forsight CAMS dashboard.

Webhooks support all configurable alert types available in the dashboard under Network-wide → Alerts. This includes a variety of alerts for all product types that you own or operate. This tool is helpful for service providers and other organizations who need around-the-clock monitoring of their networks. With webhooks, you can receive updates within minutes for outages, network changes, new configurations, and many other events in your environments.

Webhooks – setup and configuration

You’ll need to add a Forsight HTTP server.

In order to do that, you’ll need to input:

  1. Arbitrary name (Webhook ID)
  2. Unique HTTPS (TLS) URL – provided by Forsight in the onboarding process
  3. Shared secret – provided by Forsight in the onboarding process
  4. (See image)

After successfully adding Forsight’s HTTP server, you can now select it as the default recipient (destination) for any alert within the Meraki dashboard.


Securing data in transport

Webhook HTTP server URLs must use a TLS-enabled HTTPS URL located on a public server with a valid SSL certificate. The sharedSecret parameter is defined when configuring the HTTP server on the Meraki Dashboard. The value of the sharedSecret can be evaluated by the webhook receiving service before saving the information.

Meraki MV Sense MQTT

Another level of Forsight/Meraki integration is by utilizing Meraki’s MV Sense in order to send the Meraki analytics metadata into Forsight’s CAMS dashboard.

In order to setup MV Sense MQTT, you’ll need to create a Meraki Dashboard API key. For security reasons, we recommend that you create a new admin user to manage only the cameras. This way, Forsight will only have access to a specific network and cameras within that specific network.  Please DO NOT SHARE your entire organization.  Please read Create New Organization in Meraki tutorial.

1.  Go to Organization → Configure → Administrators and click on Create Admin.

2.  To generate a new API Key, navigate to My Profilein the top right corner then scroll down to the API access section.

  1. Start by navigating to Cameras → Monitor → Cameras and selecting the camera you would like to enable MV Sense on.
  2. Once the camera is selected, go to Settings → Sense.
  3. Click Enabled.*
  4. To enable MQTT on your camera and create a new MQTT broker configuration click Add or edit MQTT Brokers.

* If this is your organization’s first time using MV Sense, you will have 10 free perpetual licenses available to use. If you have exceeded this 10 free license count, you must activate more licenses by navigating to Organization → Configure → License info and claiming more licenses.

Enter the following information for Forsight broker – provided in the onboarding process:

  1. Broker Name – Name of the broker.
  2. Host – IP address or hostname.
  3. Port – TCP port number for MQTT.
  4. Security – Enable or disable TLS. When enabling TLS, upload a CA-signed cert for the broker and choose hostname verification.
  5. Test the connection between the camera and the broker to ensure communication.