[asterisk-bugs] [Asterisk 0012782]: no native bridging with SIP over TLS enabled

[Asterisk Bug Tracker]

The following issue has been UPDATED. 
====================================================================== 
https://issues.asterisk.org/view.php?id=12782 
====================================================================== 
Reported By:                lukas
Assigned To:                file
====================================================================== 
Project:                    Asterisk
Issue ID:                   12782
Category:                   Channels/chan_sip/General
Reproducibility:            always
Severity:                   minor
Priority:                   normal
Status:                     closed
Asterisk Version:           1.6.0-beta9 
Regression:                 No 
SVN Branch (only for SVN checkouts, not tarball releases): N/A 
SVN Revision (number only!):  
Request Review:              
Resolution:                 no change required
Fixed in Version:           
====================================================================== 
Date Submitted:             2008-06-04 02:58 CDT
Last Modified:              2009-05-20 10:27 CDT
====================================================================== 
Summary:                    no native bridging with SIP over TLS enabled
Description: 
As soon as you enable SIP over TLS, 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. (see wireshark capture
tls_no-native-bridging.pcap)

As soon as you deactivate TLS again, the traffic is routed directly
between the two phones. (see wireshark capture
no-tls_native-bridging.pcap)

Mailing list:
http://lists.digium.com/pipermail/asterisk-dev/2008-June/033330.html


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

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2009-05-20 10:27 file           Status                   resolved => closed  
======================================================================