RTSP video diagnostics

RTSP Inspector RTSP software for proving why an IP camera stream fails.

Turn camera black screens, VLC-vs-VMS mismatches, ONVIF handoff failures, blocked UDP media, RTP loss, and H.264/H.265 codec problems into a report a customer, vendor, or support team can act on.

RTSP diagnostic workbench

Workflow paths

Enter by the job, not by the protocol acronym.

RTSP Inspector is useful when a team needs to prove whether the camera, network, NVR, VMS, player, codec path, device, file, or local workflow owns the failure.

Sample reports

See what the handoff looks like.

Public examples show how the product turns failure symptoms, local evidence, and next actions into something a customer, vendor, teammate, or clinic operator can read.

Field evidence, not player guesswork

Find the exact camera-stream failure boundary before the blame loop starts.

RTSP Inspector is the focused local desktop workbench for teams that need to explain CCTV and IP camera failures across RTSP/RTP/RTCP/SDP, H.264/H.265 structure, transport choice, and reportable evidence.

01

Control plane answers first

  • RTSP OPTIONS, DESCRIBE, SETUP, and PLAY stay in one timeline with status codes, CSeq behavior, headers, and redacted authentication evidence.
  • SDP track inspection exposes codecs, payload types, clock rates, control URLs, and missing media declarations before you blame the decoder.
  • Bad paths, 401 loops, unsupported transport replies, ONVIF handoff mistakes, and server-side failures become visible protocol events instead of vague black-screen symptoms.
02

Media flow gets measured

  • RTP continuity, packet loss, duplicates, reordering, jitter, malformed packets, and SSRC changes are surfaced beside the RTSP session that produced them.
  • RTCP sender reports, packet counts, timing evidence, and CNAME context help separate network delivery problems from camera timing problems.
  • H264/H265 structural inspection helps prove whether the stream is missing parameter sets, fragmenting badly, or advertising a codec it does not deliver cleanly.
03

Built for cases, not screenshots

  • .risession save/open, Case Library, and replay workflows keep the normalized evidence reusable when a customer, vendor, or field team needs the same diagnosis later.
  • Professional reports export as PDF, HTML, Markdown, and saved JSON so the answer can leave the app without rewriting notes by hand.
  • The app stays local on the desktop and focused on evidence handoff, not NVR playback, generic packet browsing, or cloud upload flows.
04

A focused field report beats another hour on site

  • Community is enough to preview a single RTSP-over-TCP case; Professional unlocks UDP unicast receive, advanced H264/H265 checks, reports, and saved sessions.
  • No subscription, no account dashboard to keep alive, and no improvised VLC/Wireshark/ONVIF toolchain just to explain one broken camera stream.
  • Use it when a repeatable diagnostic report is worth more than another hour of arguing between RTSP control, RTP delivery, RTCP timing, SDP metadata, codec readiness, and network ownership.

Free

Single-stream live RTSP-over-TCP diagnosis and JSON report preview.

  • Live RTSP-over-TCP inspection
  • RTSP/RTP/RTCP/H264 evidence tables
  • Diagnostics cockpit
  • JSON report preview

Professional

One-time lifetime license that unlocks every paid desktop capability.

  • PDF, HTML, Markdown, and saved JSON diagnostic reports
  • .risession save/open
  • RTP/RTCP over UDP unicast live receive
  • Advanced H264/H265 structural inspection
  • Case Library
License details

Compare

RTSP Inspector vs Wireshark for Camera Stream Diagnostics

The blue-marked column is the product on this page. The other names are comparison context for buyers who are deciding between focused desktop workflow, cloud accounts, subscriptions, and broader tools. Read why Hannes wins.

RTSP Inspector logo
RTSP Inspector This product
Capability RTSP Inspector
This product
Wireshark VLC ONVIF Device Manager
RTSP request/response timelineBuilt-in timeline with status, sequencing, and next-action contextFull packet detail, but manual correlationMinimal playback logsDevice/profile workflow, not request diagnosis
SDP and transport explanationFocused stream, codec, payload, transport, and control URL reviewRaw protocol decode that still needs interpretationMostly hiddenProfile discovery, not media-path proof
RTP/RTCP evidenceLoss, jitter, SSRC, timestamp, sender-report, and continuity evidence in one flowDeep packet view, overbuilt for a single stream casePlayback symptoms onlyNot a packet diagnostics tool
Replay and exportSimple evidence/export path for handoffPCAP and screenshots require manual narrativeScreenshots/logs onlyDevice profile screenshots/logs
Account or cloud dependencyLocal desktop workflow, no subscriptionLocal tool, broad workflowLocal playerWindows utility workflow

Before you choose RTSP Inspector

No. It is a diagnostic and reporting workbench for RTSP/RTP/RTCP/H.264/H.265 evidence. It does not replace VLC, an NVR, or an ONVIF manager.

Compare

RTSP Inspector

Turn camera black screens, VLC-vs-VMS mismatches, ONVIF handoff failures, blocked UDP media, RTP loss, and H.264/H.265 codec problems into a report a customer, vendor, or support team can act on.

Use cases and boundaries

When RTSP Inspector is the right tool.

Product boundary

RTSP control, RTP delivery, SDP tracks, and codec readiness

Workflow

Turn an RTSP URL test into a failure report that explains whether setup, transport, RTP, or codec readiness owns the problem.

Workflow

  1. When the camera opens in one tool but fails in another

    Start with the authorized RTSP URL, inspect DESCRIBE, SETUP, PLAY, SDP tracks, RTP continuity, RTCP timing, and codec readiness, then export a report that explains where the stream fails.

    Reference: RTSP Inspector vs Wireshark for Camera Stream Diagnostics
  2. When the site network is blamed too early

    Compare TCP and UDP transport behavior, packet gaps, timeouts, and firewall symptoms before deciding whether the camera, client, or network owns the problem.

    Reference: RTSP 461 Unsupported Transport Fix: SETUP Failed, UDP vs TCP, ffmpeg Camera Transport Error
  3. When support needs evidence instead of screenshots

    Save the RTSP session with request logs, track details, transport decisions, packet timing, and decoder notes so another engineer can review the same case.

    Reference: Export RTSP Diagnostic Reports for RTSP Inspector: Setup and Workflow Guide
  4. When H.264 or H.265 playback depends on the client

    Check payload types, parameter sets, keyframes, and decoder readiness so the report explains why one player is tolerant and another one rejects the stream.

    Reference: RTSP Diagnostics FAQ for Camera Teams Debugging Stream Failures
  5. When a VMS integration stalls

    Use the product to prove the boundary between camera output, RTSP negotiation, RTP delivery, and VMS expectations before changing camera or server settings.

    Reference: RTSP Inspector vs VLC for Camera Debugging: Player or Evidence?
  6. When the issue must be handed to a vendor

    Turn the stream test into a concise diagnostic package: failure boundary, observed evidence, likely cause, and the next action for firmware, QA, or support.

    Reference: RTSP Main Stream Not Working but Sub Stream Works: What the Difference Proves