[asterisk-bugs] [JIRA] (ASTERISK-20904) RFC1918 NAT Issue On Prune
JoshE (JIRA)
noreply at issues.asterisk.org
Thu Jan 10 13:52:45 CST 2013
[ https://issues.asterisk.org/jira/browse/ASTERISK-20904?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=201326#comment-201326 ]
JoshE commented on ASTERISK-20904:
----------------------------------
Correct. Rtcachefriends is enabled.
You won't reproduce by reregistering, but if you prune and then just have the UA execute a dial event, Asterisk attempts to repopulate the peer. It does using the private IP address and then the peer goes unreachable until it registers again.
> RFC1918 NAT Issue On Prune
> --------------------------
>
> Key: ASTERISK-20904
> URL: https://issues.asterisk.org/jira/browse/ASTERISK-20904
> Project: Asterisk
> Issue Type: Bug
> Security Level: None
> Reporter: JoshE
> Assignee: JoshE
> Attachments: rfc1918_patch.diff
>
>
> Issue is related to ASTERISK-20572, but appears to have been reintroduced in Asterisk 11.x.
> Bring up a realtime peer behind separated from the Asterisk server behind NAT. When the peer is pruned and brought back up, the peer's external NAT address is replaced with the private IP from the contact header, if that address was present.
--
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