[asterisk-bugs] [Asterisk 0018674]: [patch] Unable to choose which SRTP suite to offer

[Asterisk Bug Tracker]

A NOTE has been added to this issue. 
====================================================================== 
https://issues.asterisk.org/view.php?id=18674 
====================================================================== 
Reported By:                bbeers
Assigned To:                
====================================================================== 
Project:                    Asterisk
Issue ID:                   18674
Category:                   Channels/chan_sip/SRTP
Reproducibility:            always
Severity:                   minor
Priority:                   normal
Status:                     new
Asterisk Version:           SVN 
JIRA:                        
Regression:                 No 
Reviewboard Link:            
SVN Branch (only for SVN checkouts, not tarball releases):  trunk 
SVN Revision (number only!): 303637 
Request Review:              
====================================================================== 
Date Submitted:             2011-01-25 09:56 CST
Last Modified:              2011-01-31 13:34 CST
====================================================================== 
Summary:                    [patch] Unable to choose which SRTP suite to offer
Description: 
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.

====================================================================== 

---------------------------------------------------------------------- 
 (0131283) lmadsen (administrator) - 2011-01-31 13:34
 https://issues.asterisk.org/view.php?id=18674#c131283 
---------------------------------------------------------------------- 
bbeers: why not allow you to specify the type of encryption with
encryption=... and then just letting encryption=yes default to the same as
it is now. That way you're backwards compatible while at the same time not
having a separate option (which makes the existing encryption= option
confusing). 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2011-01-31 13:34 lmadsen        Note Added: 0131283                          
======================================================================