[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=202544#comment-202544 ] 

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

JoshE... sorry to keep asking but with this patch in place I tried the following:

I have "nat" commented out in the sip.conf in the general context (unconfigured, using the default setting), localnet and externaddr commented out as well.  For the realtime peer I have nat=yes.  The realtime peer (behind NAT) registers.  Everything looks good.  I then do "sip prune realtime peer <peername>".  I then attempt to dial a number from the peer that was just pruned.  The peer is able to complete the call and the "ipaddr" is populated with the external IP address even though the fullcontact field contains a private ip.

Can you attach a debug log that perhaps can help show what is happening?  In sip.conf, do you have localnet set?  Is externaddr set?  I am just trying to figure out the difference between our two environments.

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
>          Components: Channels/chan_sip/General
>    Affects Versions: 11.2.0
>            Reporter: JoshE
>            Assignee: JoshE
>         Attachments: asterisk-20904-auto-nat-prune_v1.diff, 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