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

JoshE (JIRA) noreply at issues.asterisk.org
Tue Jan 8 02:19:45 CST 2013


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

JoshE commented on ASTERISK-20904:
----------------------------------

Sample patch attached. Not sure this is really reflective of the best approach, but it solved the problem for me.

For additional information, I tested this with nat=yes (deprecated in 11) and nat=force_rport,comedia

Seems to work in both cases.
                
> 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 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