Skip to content

RTSP Ingestion & Restreaming Server ​

RUSEON Core features a dual-role RTSP engine (internal/stream/ and internal/rtsp/): it acts as a resilient client ingesting feeds from remote IP cameras, and as a high-concurrency RTSP Re-Streaming Server providing standardized RTSP access to downstream consumers.


1. RTSP Ingest Capabilities ​

  • Transport Modes: Auto-negotiates TCP (Interleaved) and UDP. TCP is recommended for lossy networks to guarantee frame completeness.
  • Dial Throttling: Implements dialSemaphore (max 10 concurrent in-flight handshakes) to prevent server socket starvation during site-wide camera reboots.
  • Dynamic Reconnection: Automatically retries dropped feeds with exponential backoff and jitter.

2. RTSP Restreaming Server ​

Downstream video management systems (VMS), external NVRs, or computer vision scripts can consume any active camera stream via standard RTSP:

text
rtsp://<ruseon-host>:8554/<camera_id>

Example Access via VLC / FFmpeg: ​

bash
# Stream camera via FFmpeg
ffmpeg -rtsp_transport tcp -i "rtsp://localhost:8554/cam_entrance" -c copy output.mp4

# Play stream in VLC
vlc "rtsp://localhost:8554/cam_entrance"

3. Configuration Reference ​

yaml
rtsp:
  # Enable RTSP restreaming server
  server_enabled: true
  port: 8554
  
  # Global ingest defaults
  default_transport: "tcp" # options: tcp, udp
  reconnect_interval_min: "1s"
  reconnect_interval_max: "30s"

Released under the MIT License.