[asterisk-bugs] [Asterisk 0017012]: [patch] endless wait for RTP when both legs have a=direction:passive in SDP

[Asterisk Bug Tracker]

A NOTE has been added to this issue. 
====================================================================== 
https://issues.asterisk.org/view.php?id=17012 
====================================================================== 
Reported By:                wdoekes
Assigned To:                
====================================================================== 
Project:                    Asterisk
Issue ID:                   17012
Category:                   Channels/chan_sip/General
Reproducibility:            always
Severity:                   feature
Priority:                   normal
Status:                     new
Asterisk Version:           1.4.30-rc3 
JIRA:                        
Regression:                 No 
Reviewboard Link:            
SVN Branch (only for SVN checkouts, not tarball releases): N/A 
SVN Revision (number only!):  
Request Review:              
====================================================================== 
Date Submitted:             2010-03-12 02:34 CST
Last Modified:              2010-03-12 03:52 CST
====================================================================== 
Summary:                    [patch] endless wait for RTP when both legs have
a=direction:passive in SDP
Description: 
A Dialogic machine that I'm peering with has the ability to go into passive
mode for RTP traffic (adding a=direction:passive to the SDP body). I
haven't figured out why/when it does so, but when it does -- and it always
does in my current setup -- everyone ends up waiting for data and no RTP
stream gets set up.
====================================================================== 

---------------------------------------------------------------------- 
 (0119300) wdoekes (reporter) - 2010-03-12 03:52
 https://issues.asterisk.org/view.php?id=17012#c119300 
---------------------------------------------------------------------- 
And indeed, the problem occurs with 1.4.30rc3 as well. And the
proof-of-concept fix still works.

(Unrelated, but worthwhile mentioning: 1.4.29.1 does not work in my test
setup. It could be that 302 handling is broken somehow because after
setting up the second call it doesn't 200 OK the first.) 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2010-03-12 03:52 wdoekes        Note Added: 0119300                          
======================================================================