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

Rusty Newton (JIRA) noreply at issues.asterisk.org
Tue Apr 14 13:16:32 CDT 2015


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

Rusty Newton commented on ASTERISK-24282:
-----------------------------------------

Thanks. Unfortunately it isn't clear to me what is going on from the log. Also, your packet capture does not show all of the same traffic seen in your Asterisk log which is unhelpful in troubleshooting. I can see some SIP traffic originating from *.65, but it isn't clear why.

For us to investigate this further you will need to provide a complete reproduction plan including:

 * Including all necessary configuration files (that may be modified for our own test network).
 * An explanation of the steps required to reproduce the issue.

As it is right now, many people, including the Digium development team run Asterisk within virtual machines and we haven't seen this issue. That means that if you are experiencing a bug that there is something very specific to either your configuration or environment that is not obvious. We need your help to pinpoint what that factor is.

> 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
>            Assignee: Rusty Newton
>            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)



More information about the asterisk-bugs mailing list