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

Michael L. Young (JIRA) noreply at issues.asterisk.org
Wed Feb 27 16:19:18 CST 2013


     [ https://issues.asterisk.org/jira/browse/ASTERISK-20904?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Michael L. Young updated ASTERISK-20904:
----------------------------------------

    Attachment: asterisk-20904-nat-auto-and-rt-peers.diff

Mark, thanks for reviewing that last patch.  I was getting ready to post a review since it has been in use for a few months now without any issues.

In bringing the patch up to the latest revision and reviewing it one more time, I made two changes that I would like you to confirm that is correct.

If the "useglobal_nat" is turned on, currently we are only copying the SIP_NAT_FORCE_RPORT flag.  I think we need to also copy SIP_PAGE3_NAT_AUTO_RPORT as well.  Can you confirm if that is correct?  I have been testing this for the past week+ and haven't seen any problems occur do to adding this.

Attaching my latest patch which included changes to the other realtime schemas.

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: Michael L. Young
>         Attachments: asterisk-20904-auto-nat-prune_v1.diff, asterisk-20904-nat-auto-and-rt-peers.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



More information about the asterisk-bugs mailing list