[asterisk-bugs] [JIRA] (ASTERISK-18203) Problems with NAT on realtime peers (and maybe static ones)
JoshE (JIRA)
noreply at issues.asterisk.org
Tue Oct 16 22:25:34 CDT 2012
[ https://issues.asterisk.org/jira/browse/ASTERISK-18203?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=198503#comment-198503 ]
JoshE commented on ASTERISK-18203:
----------------------------------
I can confirm this behavior also persists on Asterisk 10.9.0 as well.
Register a realtime peer with a fullcontact that is behind NAT with rtcachefriends=yes and do a 'sip reload'. Make a call and Asterisk will query the database for the realtime peer. It will return the private address and so a 'sip show peers' shows the private IP address. If that peer is qualified, as many of them are, it will now go and stay unreachable until the peer re-registers, which resolves the issue.
> Problems with NAT on realtime peers (and maybe static ones)
> -----------------------------------------------------------
>
> Key: ASTERISK-18203
> URL: https://issues.asterisk.org/jira/browse/ASTERISK-18203
> Project: Asterisk
> Issue Type: Bug
> Security Level: None
> Components: Channels/chan_sip/General
> Affects Versions: 1.8.5.0
> Reporter: daren ferreira
>
> I just upgraded from 1.8.4.2 to 1.8.5.0 because of ASTERISK-17964 and related issues, to see if the leak was corrected, it was, but now i get NAT problems.
> My peers are set to nat=yes but asterisk send packets to their private IPs (fullcontact) instead of public IP (ipaddr).
> I didn't change anything else rtcachefriends from "yes" to "no" to test the leak i had on 1.8.4.2
--
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