[asterisk-bugs] [Asterisk 0012006]: [patch] chan_sip fails to set contact, via, and sdp headers correctly with outboundproxy set

[Asterisk Bug Tracker]

A NOTE has been added to this issue. 
====================================================================== 
http://bugs.digium.com/view.php?id=12006 
====================================================================== 
Reported By:                mnicholson
Assigned To:                oej
====================================================================== 
Project:                    Asterisk
Issue ID:                   12006
Category:                   Channels/chan_sip/General
Reproducibility:            always
Severity:                   minor
Priority:                   normal
Status:                     feedback
Asterisk Version:           SVN 
SVN Branch (only for SVN checkouts, not tarball releases):  trunk 
SVN Revision (number only!): 103725 
Disclaimer on File?:        N/A 
Request Review:              
====================================================================== 
Date Submitted:             2008-02-15 12:45 CST
Last Modified:              2008-12-10 16:35 CST
====================================================================== 
Summary:                    [patch] chan_sip fails to set contact, via, and sdp
headers correctly with outboundproxy set
Description: 
Setting outboundproxy in sip.conf causes asterisk to fail to properly set
contact, via, and sdp headers (they get set to 127.0.0.1).  This is because
when outboundproxy is set, we don't fill in the sa struct of the sip_pvt
for that dialog which is used to generate the ourip member of the sip_pvt
struct which is used to generate the contact, via, and sdp headers that are
faulty.  I don't know what the reasoning was for not populating the
sip_pvt.sa member originally, but it breaks stuff.
====================================================================== 

---------------------------------------------------------------------- 
 (0096148) jtodd (administrator) - 2008-12-10 16:35
 http://bugs.digium.com/view.php?id=12006#c96148 
---------------------------------------------------------------------- 
chris-mac:  If you run "tcpdump -i lo0" do you see these packets going to
127.0.0.1 or 0.0.0.0?  This error message looks like it's sending the
proxied requests to the wrong location.   The patch (I believe) fixes a
problem where proxied requests are sent to 127.0.0.1 instead of the
outboundproxy= setting.  (Am I wrong with this?)  Can you show a packet
trace on some interface that shows where these bogus outbound packets are
headed?  Might be on loopback, or it might be on your "real" interface that
is handling your default route. 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2008-12-10 16:35 jtodd          Note Added: 0096148                          
======================================================================