[asterisk-bugs] [JIRA] (ASTERISK-30032) Support of mediasec SIP headers and SDP attributes

[Friendly Automation (JIRA)]

    [ https://issues.asterisk.org/jira/browse/ASTERISK-30032?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=260398#comment-260398 ] 

Friendly Automation commented on ASTERISK-30032:
------------------------------------------------

Change 19388 merged by Friendly Automation:
res_pjsip: Add mediasec capabilities.

[https://gerrit.asterisk.org/c/asterisk/+/19388|https://gerrit.asterisk.org/c/asterisk/+/19388]

> Support of mediasec SIP headers and SDP attributes
> --------------------------------------------------
>
>                 Key: ASTERISK-30032
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-30032
>             Project: Asterisk
>          Issue Type: New Feature
>      Security Level: None
>          Components: Resources/res_pjsip
>    Affects Versions: 18.11.0
>            Reporter: Maximilian Fridrich
>            Assignee: Maximilian Fridrich
>
> Some SIP UAs require the "mediasec" header field parameter in the SIP Security headers and the "3ge2ae" attribute in SDP to allow secure communication. These fields are not specified in any RFC but they are defined in the [3GPP specification 24.229|https://portal.3gpp.org/desktopmodules/Specifications/SpecificationDetails.aspx?specificationId=1055] (specifically sections 7.2A.7 and 6.1).
> In particular, the SIP headers "Security-Client", "Security-Server", and "Security-Verify" must be supported. Asterisk endpoints and outbound registrations must configurable to set these security mechanisms.
> Some large telecommunication providers require these fields, so it would be desirable to make Asterisk compatible with them and/or switch them on through configuration options (in pjsip). There are patchsets out there that implement this behavior (to some extent) in res_pjsip (see mailing list).



--
This message was sent by Atlassian JIRA
(v6.2#6252)