[asterisk-bugs] [Asterisk 0014729]: [patch] Added ability to specify different SIP and media addresses

[Asterisk Bug Tracker]

A NOTE has been added to this issue. 
====================================================================== 
http://bugs.digium.com/view.php?id=14729 
====================================================================== 
Reported By:                _brent_
Assigned To:                
====================================================================== 
Project:                    Asterisk
Issue ID:                   14729
Category:                   Core/RTP
Reproducibility:            N/A
Severity:                   feature
Priority:                   normal
Status:                     new
Asterisk Version:           SVN 
Regression:                 No 
SVN Branch (only for SVN checkouts, not tarball releases):  trunk 
SVN Revision (number only!): 183832 
Request Review:              
====================================================================== 
Date Submitted:             2009-03-23 17:52 CDT
Last Modified:              2009-03-23 18:53 CDT
====================================================================== 
Summary:                    [patch] Added ability to specify different SIP and
media addresses
Description: 
Added rtp_bindaddr setting to chan_sip. Enabled by setting

rtp_bindaddr=x.x.x.x

in sip.conf. This should be particularly useful to anyone running Asterisk
behind a SIP proxy, like OpenSER/OpenSIPS/Kamailio. This patch allows
Asterisk to report its externip (again, set in sip.conf) as the proxy's IP
address, but its media address as its own to bypass the proxy.
====================================================================== 

---------------------------------------------------------------------- 
 (0102112) _brent_ (reporter) - 2009-03-23 18:53
 http://bugs.digium.com/view.php?id=14729#c102112 
---------------------------------------------------------------------- 
Hmmm... I chose rtp_bindaddr as the name of the configuration parameter
because that's what the other issue had named it. I'm having seconds
thoughts about that name, though, since it's not actually binding the
address, just inserting it in the SDP. Any thoughts on this? 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2009-03-23 18:53 _brent_        Note Added: 0102112                          
======================================================================