[asterisk-bugs] [Asterisk 0018674]: [patch] Unable to choose which SRTP suite to offer
Asterisk Bug Tracker
noreply at bugs.digium.com
Wed Apr 20 05:09:00 CDT 2011
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: acknowledged
Asterisk Version: SVN
JIRA: SWP-3142
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-04-20 05:08 CDT
======================================================================
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.
======================================================================
Relationships ID Summary
----------------------------------------------------------------------
has duplicate 0018893 Can't provide secure audio requested in...
related to 0018187 Indicate SRTP + Feature reqest
======================================================================
----------------------------------------------------------------------
(0133976) keys (reporter) - 2011-04-20 05:08
https://issues.asterisk.org/view.php?id=18674#c133976
----------------------------------------------------------------------
bbeers: any updates?
FYI your patches do not affect IAX2 encryption.
The unprotect errors that you say are related to libsrtp functions, do
they in any way mean that there is a fallback to standard RTP during a
call, or at the start of a call?
Using Wireshark everything looks correct with srtp packets but of course
its harder to tell when TLS is also enabled.
Issue History
Date Modified Username Field Change
======================================================================
2011-04-20 05:08 keys Note Added: 0133976
======================================================================
More information about the asterisk-bugs
mailing list