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

[Asterisk Bug Tracker]

The following issue requires your FEEDBACK. 
====================================================================== 
https://issues.asterisk.org/view.php?id=17563 
====================================================================== 
Reported By:                Alexcr
Assigned To:                
====================================================================== 
Project:                    Asterisk
Issue ID:                   17563
Category:                   Resources/NewFeature
Reproducibility:            always
Severity:                   minor
Priority:                   normal
Status:                     feedback
Asterisk Version:           SVN 
JIRA:                        
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-06-29 14:16 CDT
====================================================================== 
Summary:                    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.
====================================================================== 

---------------------------------------------------------------------- 
 (0124039) lmadsen (administrator) - 2010-06-29 14:16
 https://issues.asterisk.org/view.php?id=17563#c124039 
---------------------------------------------------------------------- 
Could you provide a pcap packet capture with all the packet information?
Terry is saying it looks like something to do with the RTCP possibly not
getting encrypted and would need to see all of that information.

You can capture it with something like wireshark and upload the resulting
file here. 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2010-06-29 14:16 lmadsen        Note Added: 0124039                          
2010-06-29 14:16 lmadsen        Status                   acknowledged =>
feedback
======================================================================