[asterisk-bugs] [JIRA] (ASTERISK-24687) Asterisk behind NAT sets wrong Contact Header

[Matt Jordan (JIRA)]

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

Matt Jordan commented on ASTERISK-24687:
----------------------------------------

Not really. Binding to an IPv6 wildcard is not really the same thing as binding to an IPv4 wildcard. In fact, the SIP settings even tell you that:
{quote}
{noformat}
     [::] may include IPv4 in addition to IPv6, if such a feature is enabled in the OS.
{noformat}
{quote}

How those addresses are represented when the OS hands them back to Asterisk are different, as typically using an IPv6 bind all address will hand back the IPv4 address as an IPv6 tunnelled address - which is why using an IPv4 mask for your localnet settings won't work.

As it is, this is expected in this case: if you are going to use IPv6 for your bind information, you need to use IPv6 mapped addresses elsewhere as well.


> Asterisk behind NAT sets wrong Contact Header
> ---------------------------------------------
>
>                 Key: ASTERISK-24687
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-24687
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: Channels/chan_sip/General
>    Affects Versions: 13.1.0
>         Environment: ubuntu 14.04.1
>            Reporter: Lukas Hauser
>            Assignee: Michael L. Young
>            Severity: Critical
>         Attachments: debug-asterisk11.15.log, debug.log, deubg-asterisk11.log, sip-settings.log
>
>
> If asterisk is behind a statically configured NAT (e.g. with iptables), the externaddr or localnet option does not work.
> The Contact Header still contains the private IP address.
> The media_address option works.
> It also works as defined with version 11.7.0~dfsg-1ubuntu1.
> The Contact Header does not get updated in version 13.1 and 13.1.0-rc2.
> Therefore, I guess it is a bug in 13?
> Thanks!



--
This message was sent by Atlassian JIRA
(v6.2#6252)