[asterisk-bugs] [Asterisk 0013823]: [patch] Response to REGISTER is sent to wrong address when using rport
Asterisk Bug Tracker
noreply at bugs.digium.com
Tue Oct 12 10:37:30 CDT 2010
A NOTE has been added to this issue.
======================================================================
https://issues.asterisk.org/view.php?id=13823
======================================================================
Reported By: dimas
Assigned To:
======================================================================
Project: Asterisk
Issue ID: 13823
Category: Channels/chan_sip/General
Reproducibility: always
Severity: minor
Priority: normal
Status: acknowledged
Asterisk Version: SVN
JIRA: SWP-1114
Regression: No
Reviewboard Link:
SVN Branch (only for SVN checkouts, not tarball releases): N/A
SVN Revision (number only!):
Request Review:
======================================================================
Date Submitted: 2008-11-02 12:08 CST
Last Modified: 2010-10-12 10:37 CDT
======================================================================
Summary: [patch] Response to REGISTER is sent to wrong
address when using rport
Description:
I have client behind NAT.
when client (10.0.0.17) sends REGISTER request, it puts rport into Via
header. check_via notices that and sets SIP_NAT_ROUTE to the &p->flags[0] -
note the log line:
Sending to 192.168.7.211 : 5079 (NAT)
however the register_verify function later does
ast_copy_flags(&p->flags[0], &peer->flags[0], SIP_NAT);
effectively overwritting the value with SIP_NAT_RFC3581. And finally,
check_auth send response back to client to the wrong address which is
visible from the log line
<--- Transmitting (no NAT) to 10.0.0.17:5079 --->
======================================================================
Relationships ID Summary
----------------------------------------------------------------------
related to 0017044 [regression][patch] SDP c and o lines c...
======================================================================
----------------------------------------------------------------------
(0127873) lmadsen (administrator) - 2010-10-12 10:37
https://issues.asterisk.org/view.php?id=13823#c127873
----------------------------------------------------------------------
This issue has been triaged and imported and will be worked on as soon as
development resources and priority warrant.
With that being said, it has a high priority and I would expect it to get
fixed perhaps in the next sprint session.
Issue History
Date Modified Username Field Change
======================================================================
2010-10-12 10:37 lmadsen Note Added: 0127873
======================================================================
More information about the asterisk-bugs
mailing list