[asterisk-bugs] [JIRA] (ASTERISK-20805) SIP Notify message has incorrect IP address in FROM field

[Tim Irvin (JIRA)]

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

Tim Irvin commented on ASTERISK-20805:
--------------------------------------

A workaround for this issue is to deactivate IPv6 on the system, notice the From address in the SIP NOTIFY header is Unknown@[::1] (IPV6 localhost address (a bug no doubt), but if IPv6 is deactivated then this address can't be used and asterisk goes back to the correct method of using the IPv4 address of the egress interface.

To deactivate IPv6 add the following lines to /etc/sysctl.conf and reboot:

net.ipv6.conf.default.disable_ipv6=1
net.ipv6.conf.all.disable_ipv6=1
                
> SIP Notify message has incorrect IP address in FROM field
> ---------------------------------------------------------
>
>                 Key: ASTERISK-20805
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-20805
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: Channels/chan_sip/General
>    Affects Versions: 1.8.11.1, 11.1.0
>         Environment: Centos 6.2 - 32bit
> PIAF Purple
> Freepbx 2.10.1.2
> EPM 
> Polycom IP331
>            Reporter: Bryan Hunt
>            Assignee: Bryan Hunt
>         Attachments: asterisk-20805-notify-ip.diff, full.txt
>
>
> When sending a SIP Notify 'check-sync' to our IP331 phones, the FROM portion of the Notify message does not contain the IPv4 address of the Asterisk server's interface (to which the phone is registered).  The FROM instead contains something that looks like an IPV6 localhost address: 
>    From: "Unknown" <sip:Unknown@[::1]>;tag=as567b56ba
> The phones will not reboot, as the from message is not giving the server that the phone is registered to.
> This can be worked-around by putting in the interface's IPV4 address in the bindaddress field.  The FROM then looks like this:
>     From: "Unknown" <sip:Unknown at 172.16.99.218>;tag=as60768d2a
> This message does cause the phone to be rebooted.
> Unfortunately, setting the bindaddress will break any environment where SIP is used on two or more NIC interfaces.
> I believe that the Asterisk server should determine the IP address of the egress NIC interface (or the IP address that the phone is registered to) and place that in the FROM field in the SIP Notify message.
> http://forums.digium.com/viewtopic.php?f=1&t=85080
> http://lists.digium.com/pipermail/asterisk-dev/2011-July/050271.html

--
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