Separate control success from media failure
RTSP Inspector keeps OPTIONS, DESCRIBE, SETUP, PLAY, status codes, CSeq, headers, and redacted auth evidence in one timeline so a reachable camera is not mistaken for a usable stream.
CCTV installers and security integrators
RTSP troubleshooting reports for CCTV installers
When a customer says the camera is black, you need more than VLC. You need a field report that shows where the stream actually failed.
Field problems
What this page is built to solve
- The camera is reachable but the NVR shows black video.
- ONVIF discovery works but the RTSP URL fails or points to the wrong stream.
- VLC plays the stream but the VMS cannot decode or ingest it.
- UDP media is blocked across VLANs, VPNs, firewalls, or NAT.
- A customer wants proof before replacing the camera, NVR, switch, or cable.
Why RTSP Inspector
The output is a failure boundary.
Show where packets stop
UDP/TCP transport negotiation, RTP sequence continuity, RTCP timing, jitter, loss, and SSRC changes make firewall and network ownership visible.
Hand off a customer-ready answer
Export PDF, HTML, Markdown, JSON, or a saved .risession case instead of rewriting notes after the site visit.
Workflow
From stream URL to handoff report
-
1
Run RTSP Inspector against the camera or NVR stream URL.
-
2
Save the RTSP control transcript, SDP tracks, transport negotiation, and RTP/RTCP evidence.
-
3
Check codec readiness for H.264/H.265 parameter-set or compatibility failures.
-
4
Export a report with likely cause and recommended fix before leaving the site.
Stop sending screenshots as evidence.
RTSP Inspector connects RTSP control, SDP, transport, RTP, RTCP, codec readiness, likely cause, recommended fix, and exportable evidence in one report path.