[asterisk-bugs] [Asterisk 0012006]: [patch] chan_sip fails to set contact, via, and sdp headers correctly with outboundproxy set
Asterisk Bug Tracker
noreply at bugs.digium.com
Tue Dec 9 17:28:36 CST 2008
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-09 17:28 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.
======================================================================
----------------------------------------------------------------------
(0096054) otherwiseguy (administrator) - 2008-12-09 17:28
http://bugs.digium.com/view.php?id=12006#c96054
----------------------------------------------------------------------
Just a note, I *always* appreciate capture files and would never discourage
someone from posting them. I even have a tool that I wrote that allows you
to convert a capture file into sipp scenarios so that you can replay the
issue on a test box. Granted, getting the debug output is necessary, but
if I had the option I'd get both. :-) Especially since wireshark makes it
very easy to visualize what is happening.
Issue History
Date Modified Username Field Change
======================================================================
2008-12-09 17:28 otherwiseguy Note Added: 0096054
======================================================================
More information about the asterisk-bugs
mailing list