RTSP Inspector sample reports
Evidence you can inspect before trusting the workflow.
These examples show the output buyers actually need: a failure boundary, evidence table, recommended fix, and a file that can leave the app.
- CCTV field handoffCamera connects but video is black Sample RTSP Inspector report for an IP camera that accepts RTSP control but never provides usable H.264 video evidence. Failure boundary RTSP control succeeded. SDP advertised H.264. RTP packets arrived. Codec readiness failed because the stream did not provide stable SPS/PPS evidence before video payloads. Likely cause The camera, relay, or NVR path is sending media before required H.264 parameter sets are available to downstream clients. HTML preview PDF sample
- Firewall or NAT boundaryRTSP works over TCP but UDP media is blocked Sample RTSP Inspector report for a camera that negotiates UDP transport but delivers no RTP media to the client. Failure boundary RTSP control and transport negotiation succeeded. UDP media did not arrive. TCP interleaved media is the working workaround. Likely cause A firewall, NAT rule, VLAN boundary, VPN path, or host policy is blocking or misrouting UDP RTP/RTCP ports. HTML preview PDF sample
- Installer URL handoffONVIF works but the RTSP URL fails Sample RTSP Inspector report for a camera that appears in ONVIF discovery but fails when the installer or VMS opens the RTSP media URL. Failure boundary Device discovery succeeded outside the app, but RTSP DESCRIBE/SETUP did not reach a usable media session for the selected stream profile. Likely cause The VMS or installer is using a stale RTSP URL, wrong stream profile, missing channel suffix, credential mismatch, or ONVIF-provided path that does not match the camera firmware's current media endpoint. HTML preview PDF sample
- Vendor support evidenceVLC plays but the VMS cannot decode H.265 Sample RTSP Inspector report for a camera stream that plays in VLC but fails in a VMS due to H.265 and SDP compatibility details. Failure boundary RTSP control succeeded and RTP media arrived. The failure is at the H.265 compatibility and decoder-readiness boundary used by the VMS. Likely cause The camera profile advertises or delivers H.265 in a way accepted by VLC but rejected by the target VMS decoder or ingest profile. HTML preview PDF sample