[asterisk-bugs] [Asterisk 0015194]: [SIP realtime] "sip reload" makes UNREACHABLE users behind NAT
Asterisk Bug Tracker
noreply at bugs.digium.com
Tue May 26 08:28:22 CDT 2009
A NOTE has been added to this issue.
======================================================================
https://issues.asterisk.org/view.php?id=15194
======================================================================
Reported By: ibc
Assigned To:
======================================================================
Project: Asterisk
Issue ID: 15194
Category: Channels/chan_sip/Registration
Reproducibility: always
Severity: major
Priority: normal
Status: new
Target Version: 1.4.26
Asterisk Version: 1.4.25
Regression: Yes
SVN Branch (only for SVN checkouts, not tarball releases): N/A
SVN Revision (number only!):
Request Review:
======================================================================
Date Submitted: 2009-05-26 08:17 CDT
Last Modified: 2009-05-26 08:28 CDT
======================================================================
Summary: [SIP realtime] "sip reload" makes UNREACHABLE users
behind NAT
Description:
When a SIP dynamic realtime user is registered behind NAT (with "nat=yes"),
a "sip reload" command makes Asterisk "forgetting" the public location of
the peer, and instead uses the private address of Contact header to reach
it. Of course it fails and causes the user to be UNREACHABLE.
======================================================================
----------------------------------------------------------------------
(0105396) ibc (reporter) - 2009-05-26 08:28
https://issues.asterisk.org/view.php?id=15194#c105396
----------------------------------------------------------------------
I'm testing some older versions right now to check if it has worked fine
before the current version. I'll comment it here soon.
Issue History
Date Modified Username Field Change
======================================================================
2009-05-26 08:28 ibc Note Added: 0105396
======================================================================
More information about the asterisk-bugs
mailing list