Test RTSP session survival across firewalls and idle periods

Bottom line: an RTSP stream that starts successfully may still fail after an idle interval, firewall-state change, endpoint restart, or transport fallback. Commission session survival and recovery, not just the first PLAY request.

Source fact: RTSP controls stateful media sessions

RFC 7826 specifies RTSP 2.0 for setting up and controlling real-time media delivery. It describes transport choices that can include UDP, multicast, and TCP, and it defines stateful sessions with timeout behavior. The specification describes a normal session timeout of 60 seconds unless a server indicates another value and recommends SET_PARAMETER as a keepalive method. It also states that RTSP 2.0 is not wire compatible with RTSP 1.0.

These are protocol facts, not a claim that any camera uses RTSP 2.0. Many surveillance devices implement a documented subset or a different version, so observed and vendor-documented behavior governs the deployment.

Source boundary and applicability

The RFC does not certify camera/VMS interoperability, dictate firewall timers, or guarantee recovery from network loss. Products may use RTSP 1.0, vendor extensions, HTTP tunneling, or another media workflow. Consult the exact vendor documentation and applicable RFC version before forming a test expectation.

Applicability questions

• Which RTSP version and methods do both endpoints document and negotiate?
• Is RTP delivered over UDP, multicast, interleaved TCP, or another supported path?
• What timeout does the server advertise, and what keepalive does the client send?
• Which firewall, proxy, NAT, or load balancer has a shorter state timer?
• Does recovery preserve timestamps, credentials, stream profile, and recording continuity?

DSE recommendation: test start, idle, interruption, and recovery

The following steps are DSE recommendations based on the cited source.

Record a sanitized session trace or product log showing the actual version, Session header, timeout, transport, ports, and keepalive method. Allow the connection to remain in each production idle state beyond the shortest configured timer. Then test a dropped media path, dropped control path, firewall-state expiration, camera restart, and client restart in an approved environment.

Measure detection and reconnection time and inspect the recorder timeline around every event. Align firewall policy with the supported transport and least access necessary; do not broadly expose RTSP or weaken controls merely to mask an ununderstood timeout.

Verification and evidence

Retain the endpoint/version inventory, vendor support references, sanitized negotiation trace, firewall rule and timer record, test timestamps, native clips, reconnect logs, alert evidence, and approved exception for any unresolved gap. Protect traces because URLs or headers can contain credentials or sensitive addresses.

Official references

• RFC 7826 – Real-Time Streaming Protocol Version 2.0 – RFC Editor