Make stream compatibility testable
Inspect DESCRIBE, SDP, SETUP, PLAY, RTP, RTCP, H.264, and H.265 evidence from the same run instead of relying on one tolerant player.
IP camera vendor QA
Validate RTSP, SDP, RTP, and H.264/H.265 behavior before shipping camera firmware
A camera firmware build can pass basic playback and still ship broken SDP, RTP continuity, UDP behavior, or codec parameter-set handling.
Field problems
What this page is built to solve
- DESCRIBE succeeds but SDP exposes missing tracks, bad control URLs, or codec parameters.
- UDP and TCP behavior diverge after SETUP.
- RTP sequence gaps, timestamp drift, or SSRC changes break downstream clients.
- H.264/H.265 streams miss parameter sets or advertise profiles the target VMS rejects.
- QA needs an artifact that shows exactly what regressed between firmware builds.
Why RTSP Inspector
The output is a failure boundary.
Compare working and failing sessions
Saved .risession cases and report exports make firmware regressions reviewable without reconnecting to the original lab device.
Produce vendor-readable failure notes
Reports summarize the likely failure boundary, protocol evidence, codec readiness, and recommended fix for firmware, QA, and support teams.
Workflow
From stream URL to handoff report
-
1
Run smoke checks for each camera profile: main stream, substream, TCP, and UDP where supported.
-
2
Confirm SDP track declarations, control URLs, payload types, and codec parameters.
-
3
Measure RTP/RTCP continuity and timing under normal and stressed network paths.
-
4
Save reports for firmware regressions, VMS compatibility issues, and customer-facing support cases.
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.