[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
Wed Dec 10 16:06:58 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-10 16:06 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.
======================================================================
----------------------------------------------------------------------
(0096143) chris-mac (reporter) - 2008-12-10 16:06
http://bugs.digium.com/view.php?id=12006#c96143
----------------------------------------------------------------------
Tested sip_outboundproxy_trunk162622-1.diff and now I am getting:
-- Got SIP response 482 "Loop Detected" back from 0.0.0.0
(same error as described above
http://bugs.digium.com/view.php?id=12006#96018)
in both cases when I use outboundproxy=__domainaName__ or
outboundproxy=__ipAddress__.
Issue History
Date Modified Username Field Change
======================================================================
2008-12-10 16:06 chris-mac Note Added: 0096143
======================================================================
More information about the asterisk-bugs
mailing list