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

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

Hmm... that is a bummer since I specifically tested for that since that is what your original report was for.  I tested the reloading as reported in the other issue and I tested for the prune scenario, with: 

nat not set,
nat set to no,
with nat set with just force_rport,
with just comedia,
with force_rport and comedia,
with auto_force_rport,
with auto_comedia
and with auto_force_rport and auto_comedia.

Did you reload chan_sip.so module or asterisk after applying and compiling the patch?

In the [general] section of sip.conf, you still have "nat=" commented out?

I guess I will have to relook at this since basically what you are saying is that there is no change in behavior since auto_force and auto_comedia should be working without this patch at all.

I am just trying to figure out what I could be missing.

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