[asterisk-bugs] [JIRA] (ASTERISK-20904) RFC1918 NAT Issue On Prune

[Michael L. Young (JIRA)]

    [ https://issues.asterisk.org/jira/browse/ASTERISK-20904?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=201325#comment-201325 ] 

Michael L. Young commented on ASTERISK-20904:
---------------------------------------------

I would like to confirm some things.

Do you have "rtcachefriends" enabled?  I am pretty sure that you do based on looking at the code path and based on your report.

I was not able to reproduce by pruning a realtime peer and then having the peer register again.  But, I was able to reproduce by issuing "sip reload" (as was done in the prior issue related to this) and then have the peer register after the reload.

Can you confirm the above and the exact steps you did to reproduce this?

Thanks
                
> 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
>         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