[asterisk-bugs] [Asterisk 0017563]: [patch] SRTP (SRTP unprotect: authentication failure)

[Asterisk Bug Tracker]

A NOTE has been added to this issue. 
====================================================================== 
https://issues.asterisk.org/view.php?id=17563 
====================================================================== 
Reported By:                Alexcr
Assigned To:                twilson
====================================================================== 
Project:                    Asterisk
Issue ID:                   17563
Category:                   Resources/res_srtp
Reproducibility:            always
Severity:                   minor
Priority:                   normal
Status:                     acknowledged
Target Version:             1.8.0
Asterisk Version:           SVN 
JIRA:                       SWP-1795 
Regression:                 No 
Reviewboard Link:            
SVN Branch (only for SVN checkouts, not tarball releases):  trunk 
SVN Revision (number only!):  
Request Review:              
====================================================================== 
Date Submitted:             2010-06-29 04:04 CDT
Last Modified:              2010-07-28 10:29 CDT
====================================================================== 
Summary:                    [patch] SRTP (SRTP unprotect: authentication
failure)
Description: 
I setup asterisk-trunk with res_srtp 

Test with Snom320 and Eyalink T26P is failed with error

[Jun 24 17:08:08] DEBUG[629] res_srtp.c: SRTP unprotect: authentication
failure
[Jun 24 17:08:08] WARNING[629] res_rtp_asterisk.c: RTCP Read error:
Success.  Hanging up.

with eyebeam-1.5 all work fine if add TLS support on both.
====================================================================== 

---------------------------------------------------------------------- 
 (0125198) sfritsch (reporter) - 2010-07-28 10:29
 https://issues.asterisk.org/view.php?id=17563#c125198 
---------------------------------------------------------------------- 
(to Alekstom)

You could test sdp_crypto.c.patch which removes accepting .._32 crypto
suite on asterisk the side.

After applying the patch and using .._32 crypto suite asterisk replies
with SIP "488 Not acceptable here". In your case asterisk should accept the
second offered crypto line. 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2010-07-28 10:29 sfritsch       Note Added: 0125198                          
======================================================================