docs/3-publish/08-rtsp-cameras-and-servers.md
| supported codecs | |
|---|---|
| video | AV1, VP9, VP8, H265, H264, MPEG-4 Video (H263, Xvid), MPEG-1/2 Video, MJPEG |
| audio | Opus, MPEG-4 Audio (AAC), MPEG-1/2 Audio (MP3), AC-3, G726, G722, G711 (PCMA, PCMU), LPCM |
| other | KLV, MPEG-TS, any RTP-compatible codec |
Most IP cameras expose their video stream by using a RTSP server that is embedded into the camera itself. In particular, cameras that are compliant with ONVIF profile S or T meet this requirement. You can use MediaMTX to connect to one or several existing RTSP servers and read their media streams:
paths:
proxied:
# Use rtsp:// for plain RTSP and rtsps:// for encrypted RTSP.
source: rtsp://user:pass@host:port/path
# If the source is RTSPS and the source TLS certificate is self-signed
# or invalid, you can provide the fingerprint of the certificate in order to
# validate it anyway. It can be obtained by running:
# openssl s_client -connect source_ip:source_port </dev/null 2>/dev/null | sed -n '/BEGIN/,/END/p' > server.crt
# openssl x509 -in server.crt -noout -fingerprint -sha256 | cut -d "=" -f2 | tr -d ':'
sourceFingerprint:
If username or password contain special characters (like ?, :, etc), they need to be url-encoded.
The resulting stream will be available on path /proxied.
It is possible to tune the connection by using several additional parameters, that are listed in the configuration file.
Advanced RTSP features and settings are described in RTSP-specific features.