Understanding IP Camera Streaming Technology

What is RTSP?

Real Time Streaming Protocol (RTSP) is a network protocol that enables streaming of video and audio data over a network. It is commonly used for IP surveillance cameras, professional video production, and real-time streaming media applications. The RTSP protocol allows you to control the stream, including pausing, rewinding, and fast-forwarding, making it ideal for live video monitoring and broadcast applications.

ONVIF Standard for IP Cameras

ONVIF (Open Network Video Interface Forum) is an international standard that specifies how IP-based physical security products shall communicate. Most modern IP surveillance cameras support ONVIF, ensuring broad compatibility with video management systems and streaming software like IPVTL. ONVIF profile support indicates which video codecs and features your camera provides.

RTSP Server Support Ecosystem

RTSP is widely supported by most streaming servers and applications, such as Wowza Streaming Engine, GStreamer, LIVE555, Helix, Nimble Streamer, and MediaMTX. This broad ecosystem support ensures you can stream from any IP camera to virtually any streaming platform or recording system. Professional video management systems and surveillance platforms universally support RTSP input.

IP Camera Source Configuration

Stream from RTSP Service and ONVIF IP Cameras

In IPVTL channel source, select either rtsp (over UDP) or rtspt (over TCP) as appropriate, and enter the RTSP address from your IP camera or video management system.

RTSP vs RTSPT: When to Use Each Protocol

rtsp (RTSP over UDP) is faster and ideal for reliable local area networks where packet loss is minimal. rtspt (RTSP over TCP) provides better reliability and firewall-friendliness by tunneling over reliable TCP connections. rtspt is recommended in unreliable network environments if the source server supports it, or when streaming across the public internet with variable latency.

IP Camera RTSP Address Format

The RTSP address format varies by camera manufacturer. Common examples include:
rtsp://192.168.1.100:554/stream1 (Hikvision)
rtsp://192.168.1.100:554/Streaming/Channels/101 (ONVIF Profile)
rtsp://192.168.1.100:554/live1 (Dahua)
Consult your camera documentation for the exact RTSP URL pattern. Many modern cameras provide this information in the web interface under Network Settings or RTSP Server configuration.

RTSP Authentication with Credentials

If RTSP authentication is required on the source camera, enter the username and password in the following format:
rtsp://<username>:<password>@<server_ip>:<port>/stream
Use the camera's default credentials (often admin/admin or admin/password) unless you have configured custom authentication. For production deployments, change default credentials immediately after installation.

Network Connectivity and Firewall

Ensure your system has network connectivity to all IP cameras. Verify firewall rules allow RTSP traffic on port 554 (or custom ports). For production environments, isolate camera networks on a separate VLAN and implement strict firewall rules limiting access to authorized systems only.

RTSP Output and Stream Publishing

Publishing a Stream to Third-Party RTSP Services

IPVTL can also publish video streams to third-party RTSP servers for centralized media management, recording, or multi-viewer distribution. This is useful when aggregating streams from multiple IP cameras or creating a unified streaming platform.

Install and Configure MediaMTX Server

First, ensure you have a third-party RTSP server installed and running. We recommend MediaMTX, a lightweight open-source RTSP server ideal for streaming applications. Download the latest version from MediaMTX GitHub Releases. MediaMTX supports multiple input and output formats and integrates seamlessly with IPVTL for professional streaming workflows.

Configure IPVTL RTSP Output

IPVTL supports H.264/AVC and H.265/HEVC video encodings in RTSP format. Once MediaMTX is running, set the IPVTL target URL to rtsp://<mediamtx_ip>:8554/ipvt_ch1 and start the channel. RTSP clients will then be able to view the stream at the same address from any compatible media player.

Stream Naming and Multi-Camera Setup

For multiple IP cameras, configure separate IPVTL channels with unique RTSP stream names, for example: rtsp://mediamtx-server:8554/camera1, rtsp://mediamtx-server:8554/camera2, etc. This allows centralized management of multiple camera streams on a single RTSP server.

IP Camera Video Processing and Distribution

Video Codec Selection for IP Cameras

IPVTL supports both H.264 (AVC) and H.265 (HEVC) video encoding for IP camera streams. H.264 is universally supported and recommended for maximum compatibility. H.265 offers 40-50% better compression efficiency, reducing bandwidth and storage requirements while maintaining quality. Select the codec based on your downstream player/server compatibility requirements.

Multi-Protocol Publishing

In addition to RTSP output, IP camera streams can be published to:

• HLS streaming for web browser and mobile device playback
• MPEG-DASH for adaptive bitrate surveillance delivery
• RTMP protocol for legacy broadcast systems
• Multi-bitrate streaming for flexible viewer support

Hardware Acceleration for IP Camera Encoding

For high-volume IP camera deployments, hardware acceleration significantly reduces CPU overhead:

• NVIDIA GPU acceleration for multi-camera real-time encoding
• Intel GPU integration for energy-efficient IP camera transcoding
• NETINT VPU hardware for data center surveillance solutions

Advanced Video Processing Features

Enhance IP camera streams with additional processing:

• Video overlay and graphics for timestamp, camera ID, or branding overlays
• Seamless streaming transitions for multicam switching
• Professional video codecs optimization for different camera types