[asterisk-bugs] [JIRA] (ASTERISK-24282) Asterisk listening/communicating on undefined IP

[Joshua Colp (JIRA)]

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

Joshua Colp commented on ASTERISK-24282:
----------------------------------------

Actually, it appears as though you set it to Waiting For Feedback from yourself after asking for an update. I've moved it back.

There has been no change in this issue. If there is it will be reflected here and updated.

> Asterisk listening/communicating on undefined IP
> ------------------------------------------------
>
>                 Key: ASTERISK-24282
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-24282
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: Channels/chan_sip/Interoperability
>    Affects Versions: 11.3.0
>         Environment: Vmware Esxi / Centos 6 
>            Reporter: Zohair Raza
>            Severity: Critical
>         Attachments: 7may.pcapng, ast.pcap, issue24282, mylog.log, s1.pcap
>
>
> Hi,
> I am running asterisk on VMs with standby heartbeat configuration, Heartbeat assigns a virtual IP 172.20.255.40 on machine afterwards asterisk is started. In the sip.conf, I have explicitly define bindaddr=172.20.255.40 but sometimes I see packets coming from physical IP 172.20.255.41
> I have both tcp and udp transport enabled 
> Here is the lsof -ni :5060 output 
> asterisk 2878 asterisk  613r  IPv4 40060683      0t0  TCP 172.20.255.41:52381->10.100.210.110:sip (ESTABLISHED)
> asterisk 2878 asterisk  528u  IPv4 29757779      0t0  TCP 172.20.255.41:55627->10.200.14.29:sip (ESTABLISHED)
> asterisk 2878 asterisk  530u  IPv4 19211854      0t0  TCP 172.20.255.40:sip->10.100.157.32:49227 (ESTABLISHED)
>  sip show settings
> Global Settings:
> ----------------
>   UDP Bindaddress:        172.20.255.40:5060
>   TCP SIP Bindaddress:    172.20.255.40:5060



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