Meraki MV external RTSP: verify the camera generation

Supported generations and firmware

The external RTSP page lists second-generation MV2, MV12, MV22, MV32, MV52 and MV72; third-generation MV13, MV23, MV33, MV53, MV63, MV73 and MV93; and fourth-generation MV84X. It does not include first-generation MV21 or MV71. Check the current list for your exact camera instead of assuming all MV-branded devices behave alike.

The documentation specifies MV firmware 4.2 or later as a baseline for the feature. Firmware availability and current support should be checked in Dashboard for the selected device. These prerequisites describe the documented feature, not a guarantee that any particular third-party decoder accepts every camera configuration.

Turn on External RTSP in Dashboard

1. Identify the exact MV model and installed firmware in the authorized Meraki Dashboard organization.
2. Open Cameras > Monitor > Cameras, select the camera, then open Settings > Video Settings.
3. Set External RTSP to Yes using the official instructions and copy the link supplied for that camera.
4. Test the copied link from a client with direct permitted network reachability to the camera, then document the approved viewing client and intended stream use.

One stream and live video only

The documented limit is one external RTSP stream per camera, with MV84X allowing one per imager. Account for an existing recorder or viewer before opening another session. A concurrency limit can look like an intermittent connection problem if multiple applications compete for the same camera.

External RTSP carries live video, not the associated Meraki analytics metadata. MV Sense and other Dashboard or API capabilities are separate interfaces. Do not promise camera events, historical footage, ONVIF discovery or PTZ control merely because the RTSP image can be viewed.

Quality and privacy settings still apply

The stream respects the configured video quality, privacy windows and sensor crop. Inspect those Dashboard settings when the picture differs from expectations; do not assume a missing area can be recovered by changing the player. Set an appropriate quality for the receiving application and test decoding before relying on the connection for routine monitoring.

Protect the unencrypted network connection

Meraki documents TCP port 9000 for external RTSP and states that the stream is unencrypted. Keep camera access restricted to trusted, authorized clients and do not expose the port publicly. A generated local URI is not a public sharing link. Reviewed on 2026-10-18 against the official External RTSP page and MV FAQ; model coverage and prerequisites are documentation-based and are not a physical-device certification.

Check each feature independently

Start on the same local network with the exact model, firmware and account permissions. A working video stream does not prove support for ONVIF discovery, pan or tilt, two-way audio, events, or every recording feature. Test the features you need in your installed SmartRTSP app.

Keep camera credentials private. Do not expose camera ports to the public internet just to test local viewing. Manufacturer cloud accounts, device accounts and generated sharing links are not interchangeable.

Official sources and scope

Read the documentation for the exact model before changing settings. Manufacturer menus, firmware and service availability can change. These sources explain the published connection conditions, not independently verified SmartRTSP hardware compatibility.

• Cisco Meraki external RTSP configuration
• Cisco Meraki MV Smart Camera FAQ