On 21.12.22 at 09:17 Michael Maier wrote:
On 21.12.22 at 08:21 Fridrich Maximilian wrote:
Security-Client: sdes-srtp;mediasec
^^^^^^^^^
The ",mediasec" is missing.
Yes, the security_mechanisms option is a comma separated list of the
literal security_mechanisms that should be used. I.e. you have to
specify security_mechanisms=sdes-srtp\;mediasec,dtls-srtp\;mediasec
(don't forget to escape the semicolon).
I got it working now with (order has been important if I remember correctly)
security_mechanisms=msrp-tls\;mediasec,sdes-srtp\;mediasec,dtls-srtp\;mediasec
I think this should be part of the documentation.
But:
The Invite has to many headers - those are not needed (or is it Telekom
specific?):
Security-Client: msrp-tls;mediasec
Security-Client: sdes-srtp;mediasec
Security-Client: dtls-srtp;mediasec
Maybe remove them?
Just detected some more eventually unneeded headers in Invite:
Require: mediasec
Proxy-Require: mediasec
Those three headers in Invite seem to be enough (besides the a=3ge2ae:requested in
SDP) - couldn't see any problem during ~ 3 years until now.
Security-Verify: msrp-tls;mediasec
Security-Verify: sdes-srtp;mediasec
Security-Verify: dtls-srtp;mediasec
Thanks
Michael
--
_____________________________________________________________________
-- Bandwidth and Colocation Provided by http://www.api-digital.com --
asterisk-dev mailing list
To UNSUBSCRIBE or update options visit:
http://lists.digium.com/mailman/listinfo/asterisk-dev
