3 Commits

Author	SHA1	Message	Date
George Joseph	8fc3df467e	security_agreement.c: Always add the Require and Proxy-Require headers ... The `Require: mediasec` and `Proxy-Require: mediasec` headers need to be sent whenever we send `Security-Client` or `Security-Verify` headers but the logic to do that was only in add_security_headers() in res_pjsip_outbound_register. So while we were sending them on REGISTER requests, we weren't sending them on INVITE requests. This commit moves the logic to send the two headers out of res_pjsip_outbound_register:add_security_headers() and into security_agreement:ast_sip_add_security_headers(). This way they're always sent when we send `Security-Client` or `Security-Verify`. Resolves: #789 (cherry picked from commit 1d9f43b5a5)	2024-07-11 13:22:18 +00:00
Maximilian Fridrich	7140faf410	res_pjsip: mediasec: Add Security-Client headers after 401 ... When using mediasec, requests sent after a 401 must still contain the Security-Client header according to draft-dawes-sipcore-mediasec-parameter. Resolves: #48 (cherry picked from commit ecd5f91125)	2023-05-08 17:55:17 +00:00
Maximilian Fridrich	675bed5f2c	res_pjsip: Add mediasec capabilities. ... This patch adds support for mediasec SIP headers and SDP attributes. These are defined in RFC 3329, 3GPP TS 24.229 and draft-dawes-sipcore-mediasec-parameter. The new features are implemented so that a backbone for RFC 3329 is present to streamline future work on RFC 3329. With this patch, Asterisk can communicate with Deutsche Telekom trunks which require these fields. ASTERISK-30032 Change-Id: Ia7f5b5ba42db18074fdd5428c4e1838728586be2	2022-10-03 08:01:23 -05:00