Direct answer
Measure the exact time to failure. A consistent interval suggests session expiry, battery sleep or a configured idle timeout; variable stalls point more often to Wi-Fi loss, congestion or decoder pressure.
Why this happens
Without timing evidence, all disconnects look alike. RTSP session state, camera power policy and the media path can fail independently after successful startup.
Separate stream availability, media description, transport, decoding and timing before changing camera settings.
A controlled test
Run one stream for at least twice the usual failure interval while logging reachability, RTSP responses and packet or decode errors.
Change one variable at a time. Keep the camera model, firmware, endpoint and account recorded; then test network reachability, protocol response, media transport and decoding as separate layers.
Use a dedicated view-only account and a trusted local diagnostic tool. Redact credentials, private addresses and identifying data before sharing output.
Diagnostic sequence
| Check | Action | Evidence of progress |
|---|---|---|
| Interval | Time three failures from successful PLAY. | A stable or variable pattern is established. |
| Session | Check supported keep-alive behavior and timeout values. | The client maintains or renews the session correctly. |
| Power | Verify whether the camera or hub sleeps without activity. | Continuous powered operation is confirmed. |
| Network | Inspect Wi-Fi signal, switch counters and address changes. | The path remains stable across the failure window. |
Evidence to keep
A small timeline showing connection, last good frame, RTSP error and recovery attempt is more useful than a screenshot of a frozen tile.
Boundary and safety note
Do not treat a battery camera as a continuous RTSP source unless the manufacturer explicitly documents that mode.
For remote viewing, use a managed VPN instead of exposing RTSP or camera administration ports directly to the public internet.
SmartRTSP
SmartRTSP is a camera-focused RTSP and ONVIF viewer for Apple devices, Windows and Android. It fits direct viewing, discovery and multi-camera checks; keep a dedicated NVR or VMS when continuous recording, evidence export or centralized enterprise controls are required.
Frequently asked questions
Why does my stream stop at nearly the same time?
A repeatable interval often maps to session timeout, idle policy or battery sleep.
Should a viewer reconnect automatically?
Yes, but with bounded backoff and visible state so it does not hide the underlying fault or overload the camera.
Could another app disconnect this viewer?
Some cameras limit concurrent sessions, so test with other viewers and NVR connections closed.
Primary references
- IETF RFC 7826 — Real-Time Streaming Protocol 2.0
- FFmpeg — RTSP protocol options and examples
- SmartRTSP — official platform and product information
Related SmartRTSP guide
Open related guideUse the repeatable failure interval to identify keep-alive, battery sleep, Wi-Fi and concurrent-session limits.