[asterisk-bugs] [Asterisk 0017454]: [patch] valid IP address in RTP offer when Asterisk is attached to several networks

Asterisk Bug Tracker noreply at bugs.digium.com
Fri Jun 11 19:47:24 CDT 2010


The following issue has been set as RELATED TO issue 0012685. 
====================================================================== 
https://issues.asterisk.org/view.php?id=17454 
====================================================================== 
Reported By:                under
Assigned To:                
====================================================================== 
Project:                    Asterisk
Issue ID:                   17454
Category:                   Channels/chan_h323
Reproducibility:            always
Severity:                   feature
Priority:                   normal
Status:                     ready for testing
Asterisk Version:           1.6.0 - SECURITY ONLY! Test 1.6.2 
JIRA:                       SWP-1634 
Regression:                 No 
Reviewboard Link:            
SVN Branch (only for SVN checkouts, not tarball releases): N/A 
SVN Revision (number only!):  
Request Review:              
====================================================================== 
Date Submitted:             2010-06-03 09:38 CDT
Last Modified:              2010-06-11 19:47 CDT
====================================================================== 
Summary:                    [patch] valid IP address in RTP offer when Asterisk
is attached to several networks
Description: 
Currently Asterisk sends host IP address (the one that is get from
/etc/hosts or via DNS, function ast_find_ourip()) in RTP media offer of
H225.

This is not acceptable when Asterisk is attached to several networks (for
example, via several NICs, or IP aliases), because this leads to no voice
in worst cases (depends on network setup).

For this case Asterisk should be bind to 0.0.0.0 and should place correct
media IP address in media offer that corresponds to the IP address of
NIC/network the call is sent from.

SIP channel already handles this case correctly.
What we need is the same handling in H323 channel.
======================================================================
Relationships       ID      Summary
----------------------------------------------------------------------
related to          0012685 [patch] enable chan_h323 to bind addr 0...
====================================================================== 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2010-06-11 19:47 pabelanger     Relationship added       related to 0012685  
======================================================================




More information about the asterisk-bugs mailing list