CCTV field handoff
Camera 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.
HTML preview
Evidence handoff preview
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. Raw evidence excerpt
DESCRIBE 200 OK; SETUP 200 OK; PLAY 200 OK; RTP video packets observed; H.264 SPS/PPS not stable before key payloads.- Summary The camera accepted DESCRIBE, SETUP, and PLAY, but the media stream did not provide a complete decoder-ready H.264 baseline. This is not a generic player failure; the evidence points to an incomplete codec handoff.
- Confidence High
Evidence screenshots
Evidence table
| Layer | Finding | Implication |
|---|---|---|
| RTSP control | OPTIONS, DESCRIBE, SETUP, and PLAY returned success. | The URL, credentials, and basic RTSP session setup are not the primary failure. |
| SDP | The video track advertised H.264 payload type and control URL. | The server claims a usable video track, so the next boundary is RTP and codec readiness. |
| RTP | RTP video packets arrived after PLAY, but continuity alone did not prove decodability. | Network delivery is present; black video is more likely codec initialization or payload structure. |
| H.264 readiness | SPS/PPS evidence was missing or unstable before key video payloads. | A VMS or stricter decoder can show black video even when a tolerant player appears to connect. |
Recommended fix
- Change the camera profile to send SPS/PPS with IDR frames or enable a more compatible H.264 profile.
- Test the camera's substream and main stream separately; compare whether parameter sets appear before payload.
- If the path goes through an NVR or relay, test direct camera RTSP to separate camera behavior from relay rewriting.
- Attach this report to the vendor ticket as codec-readiness evidence, not a generic playback complaint.
RTSP Inspector turns RTSP control, SDP, RTP, RTCP, codec readiness, and transport findings into local PDF, HTML, Markdown, JSON, and saved .risession evidence.