How media server supports RTSPS?
For encrypted communication, RTSP can be tunneled over a secure transport layer, most commonly using TLS (Transport Layer Security). This secured version is often referred to as RTSPS and typically uses port 322.
The Happytime media server supports rtsps. Modify the configuration file mediaserver.cfg, set <enable> and <rtsps_enable> to 1, set <rtsps_port> to specify the rtsps service port, and set <rtsps_cert> and <rtsps_key> to specify the rtsps certificate and private key:
<rtsp>
<enable>1</enable>
<serverip></serverip>
<rtsp_port>554</rtsp_port>
<rtsps_enable>1</rtsps_enable>
<rtsps_port>322</rtsps_port>
<rtsps_cert>ssl.ca</rtsps_cert>
<rtsps_key>ssl.key</rtsps_key>
......
</rtsp>
Note: On Linux systems, ports below 1024 are reserved by the system and require root privileges to use.
Note: The certificate file ssl.ca and key file ssl.key provided by default are self signed local hosts certificates, only for testing purposes (browsers may pop up untrusted certificate warnings), and cannot be used in formal deployment environments.
Run the media server, and you will see the rtsps playback address in the output window of the media server.
To test rtsps streams, you can use ffplay, Happytime rtsp client, or Happytime media client for testing.