RTSP over HTTP / HTTPS (Media Transport)
Overview
RTSP over HTTP / HTTPS allows audio and video streams to be transported over standard web ports instead of the default RTSP port.
This mode is designed for restricted network environments where RTSP or UDP traffic is blocked.
RTSP over HTTP/HTTPS affects media transport only.
Use this mode only when direct RTSP or UDP transport is not possible.
Why RTSP over HTTP Is Used
RTSP over HTTP/HTTPS is useful when:
- Port 554 is blocked
- UDP traffic is restricted
- Only HTTP (80) or HTTPS (443) is allowed
- Streaming must work behind firewalls or proxies
How It Works
RTSP over HTTP uses HTTP/HTTPS as a tunnel for RTSP commands and RTP data.
- RTSP commands are sent via HTTP POST
- RTSP responses and media are received via HTTP GET
- The RTSP protocol logic remains unchanged
HTTP is used only as a transport wrapper.
ITVDesk Stream URL Examples
RTSP over HTTP
http://<ITVDESK_IP>:80/ipc1-stream1/screenlive
RTSP over HTTPS
https://<ITVDESK_IP>:443/ipc1-stream1/screenlive
The stream path is identical to standard RTSP URLs. Only the protocol and port differ.
Relationship to ONVIF
RTSP over HTTP/HTTPS:
- Does not require ONVIF
- Can be used directly by media players
- Works independently of ONVIF HTTP/HTTPS settings
ONVIF and RTSP transport are separate layers.
Performance Notes
- RTSP over HTTP/HTTPS uses TCP
- Slightly higher latency than UDP
- More reliable in restricted networks
- Not suitable for multicast streaming
Typical Use Cases
- Firewall-restricted networks
- Corporate and public environments
- Remote access without port forwarding
- Secure video transport using HTTPS
Summary
RTSP over HTTP / HTTPS in ITVDesk provides:
- Reliable streaming through web ports
- Compatibility with restricted networks
- Optional HTTPS encryption for media
- Independent operation from ONVIF
This option controls how media is transported, not how devices are managed.