[asterisk-bugs] [JIRA] (ASTERISK-20572) Realtime Peers behind NAT are Set to RFC1918 private address after sip reload
Matt Jordan (JIRA)
noreply at issues.asterisk.org
Mon Dec 10 07:15:45 CST 2012
[ https://issues.asterisk.org/jira/browse/ASTERISK-20572?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Matt Jordan updated ASTERISK-20572:
-----------------------------------
Target Release Version/s: 11.1.0
10.11.0-digiumphones
10.11.0
1.8.19.0
> Realtime Peers behind NAT are Set to RFC1918 private address after sip reload
> -----------------------------------------------------------------------------
>
> Key: ASTERISK-20572
> URL: https://issues.asterisk.org/jira/browse/ASTERISK-20572
> Project: Asterisk
> Issue Type: Bug
> Security Level: None
> Components: Channels/chan_sip/General, PBX/pbx_realtime
> Affects Versions: 10.9.0
> Reporter: JoshE
> Severity: Critical
> Target Release: 1.8.19.0, 10.11.0, 10.11.0-digiumphones, 11.1.0
>
> Attachments: fix_nat_realtime.diff
>
>
> Repro steps:
> Realtime peer behind RFC1918 NAT.
> Register the peer and verify public IP address shows up under 'sip show peers'.
> Issue a SIP reload.
> Perform any dial action that will cause the peer reload process to happen.
> Check 'sip show peers'.
> The private IP address will be listed. If that peer is qualified, it will immediately go offline and remain so until it re-registers.
> Traced problem back to dynamic host detection nulling out the ast_sockaddr if it is in !found state.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
More information about the asterisk-bugs
mailing list