[asterisk-bugs] [Asterisk 0018899]: no native bridging when more than one crypto offer in SRTP
Asterisk Bug Tracker
noreply at bugs.digium.com
Mon Feb 28 13:54:57 CST 2011
A NOTE has been added to this issue.
======================================================================
https://issues.asterisk.org/view.php?id=18899
======================================================================
Reported By: gersonsm
Assigned To:
======================================================================
Project: Asterisk
Issue ID: 18899
Category: Channels/chan_sip/SRTP
Reproducibility: always
Severity: major
Priority: normal
Status: new
Asterisk Version: 1.8.2.4
JIRA:
Regression: No
Reviewboard Link:
SVN Branch (only for SVN checkouts, not tarball releases): N/A
SVN Revision (number only!):
Request Review:
======================================================================
Date Submitted: 2011-02-28 11:57 CST
Last Modified: 2011-02-28 13:54 CST
======================================================================
Summary: no native bridging when more than one crypto offer
in SRTP
Description:
When using phones (ie Yealink T22p) that send more than one crypto offers
Asterisk does not establish a native bridging between the phones anymore,
meaning that the asterisk server stays in the media path and all the
traffic flows from phone A to Asterisk and from Asterisk further on to
phone B. When using softphone (Phonerlite) i can use SRTP with no issue.
======================================================================
----------------------------------------------------------------------
(0132446) gersonsm (reporter) - 2011-02-28 13:54
https://issues.asterisk.org/view.php?id=18899#c132446
----------------------------------------------------------------------
The same problem appear with Polycom IP-650 Phone.
Issue History
Date Modified Username Field Change
======================================================================
2011-02-28 13:54 gersonsm Note Added: 0132446
======================================================================
More information about the asterisk-bugs
mailing list