RTSPS client uses default crypto parameters for generated SRTCP packets
Describe your issue
RTSPS client uses default crypto parameters for generated SRTCP packets.
SRTP Decoder uses parameters sent by RTSP server in MIKEY message:
/GstPipeline:pipeline0/GstRTSPSrc:rtspsrc0/GstUDPSrc:udpsrc1: caps = application/x-srtp, media=(string)video, payload=(int)96, clock-rate=(int)90000, encoding-name=(string)H264, packetization-mode=(string)1, srtp-key=(buffer)75ad989e7fc8e2795168c1b5721c69cdc79684ba259e9dab930e13344c9f, srtp-cipher=(string)aes-128-icm, srtp-auth=(string)hmac-sha1-32, srtcp-cipher=(string)aes-128-icm, srtcp-auth=(string)hmac-sha1-32
SRTP Encoder uses default ones:
0:00:06.788757717 1496360 0x7f32bc007aa0 DEBUG srtpenc gstsrtpenc.c:913:gst_srtp_enc_sink_setcaps:<srtpenc_0:rtcp_sink_0> Source caps: application/x-srtcp, srtp-key=(buffer)ff4e6022d50b455405ecc2a0f2ac4edd0e44fd9fe3a92bf751c6afe18e7a, srtp-cipher=(string)aes-128-icm, srtp-auth=(string)hmac-sha1-80, srtcp-cipher=(string)aes-128-icm, srtcp-auth=(string)hmac-sha1-80
Setup
- Operating System: Ubuntu 22.04.3
- Device: Computer
- GStreamer Version: 1.20.3
- Command line: gst-launch-1.0 -v rtspsrc tls-validation-flags=0 'location=rtsps://localhost/something' ! decodebin ! autovideosink