[asterisk-bugs] [JIRA] Closed: (ASTERISK-17282) [patch] Unable to choose which SRTP suite to offer

[Matt Jordan (JIRA)]

     [ https://issues.asterisk.org/jira/browse/ASTERISK-17282?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Matt Jordan closed ASTERISK-17282.
----------------------------------

    Resolution: Fixed

> [patch] Unable to choose which SRTP suite to offer
> --------------------------------------------------
>
>                 Key: ASTERISK-17282
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-17282
>             Project: Asterisk
>          Issue Type: Bug
>          Components: Channels/chan_sip/SRTP
>            Reporter: Bob Beers
>            Severity: Minor
>         Attachments: configurable-srtp-crypto-suite-offer-bbeers01.patch, configurable-srtp-crypto-suite-offer-bbeers02.patch, configurable-srtp-crypto-suite-offer-bbeers03.patch, configurable-srtp-crypto-suite-offer-bbeers04.patch, configurable-srtp-crypto-suite-offer-bbeers05.patch, srtp-cryptosuite-bbeers22.patch
>
>
> Setting encryption=yes in sip.conf will cause asterisk to
>  generate a line in SIP INVITE SDP:
>  a=crypto: AES_CM_128_HMAC_SHA1_80 ...
> There is no way to specify that asterisk should offer
>  AES_CM_128_HMAC_SHA1_32 instead of
>  AES_CM_128_HMAC_SHA1_80.
> ****** ADDITIONAL INFORMATION ******
> RFC 3711 and RFC 4568 are relevant.
> I have patched asterisk's sdp_crypto.c function sdp_crypto_offer()
>  to offer _32 vs. _80 and it correctly establishes an SRTP connection.
> I would rather have a configuration parameter to select
>  which suite will be offered.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira