[asterisk-bugs] [Asterisk 0018036]: Incoming SIP UDP packets are ignored.

[Asterisk Bug Tracker]

A NOTE has been added to this issue. 
====================================================================== 
https://issues.asterisk.org/view.php?id=18036 
====================================================================== 
Reported By:                dtryba
Assigned To:                
====================================================================== 
Project:                    Asterisk
Issue ID:                   18036
Category:                   Channels/chan_sip/General
Reproducibility:            random
Severity:                   minor
Priority:                   normal
Status:                     feedback
Asterisk Version:           1.6.2.13 
JIRA:                        
Regression:                 No 
Reviewboard Link:            
SVN Branch (only for SVN checkouts, not tarball releases): N/A 
SVN Revision (number only!):  
Request Review:              
====================================================================== 
Date Submitted:             2010-09-23 07:53 CDT
Last Modified:              2010-11-11 05:19 CST
====================================================================== 
Summary:                    Incoming SIP UDP packets are ignored.
Description: 
UDP SIP datagrams are not processed by Asterisk. tcpdump shows them
arriving on the network interface but they don't show up in Asterisk. This
lasts for about 10m (RTP and SIP/TCP or IAX functions just fine in this
period), Asterisk then starts to "Really destroying SIP dialog" (100+ in
1s) and suddenly all is well again. Outbound UDP packets are being send and
the other side replies (but obviously gets ignored).

Last UDP datagram received:
[2010-09-22 18:49:20] VERBOSE[17369] chan_sip.c:
<--- SIP read from UDP:213.247.xxx.xxx:1024 --->

next datagram arrives 9m and 11s later:
[2010-09-22 18:58:31] VERBOSE[17369] chan_sip.c:
<--- SIP read from UDP:84.246.xxx.xxx:1042 --->

Versions affected are 1.6.2.9 (backported from Debian/unstable to
Debian/stable) and 1.6.2.13 (Debian 1.6.2.9-2 with patches applied to get
to version 1.6.2.13). This suddenly started happening 1 weeks ago, before
this machine had been running in the same configuration since 1.6.2.9 was
released by the Debian team (uptime was about 115 days before rebooting
this machine to fix a kernel issue) without any problems.

The only thing changed that week was the installation of fail2ban to block
bruteforce attempts. But removing this (and rebooting the machine) didn't
solve the problem. 

The problem happends at random times, during the day with active calls or
during the night whitout any usage.

====================================================================== 

---------------------------------------------------------------------- 
 (0128776) dtryba (reporter) - 2010-11-11 05:19
 https://issues.asterisk.org/view.php?id=18036#c128776 
---------------------------------------------------------------------- 
I took some time, but finally I have a "core show locks" from the moment
asterisk stopped responding to UDP requests. It's from an 1.6.2.13
machine.

The last time this happened the work around of changing bindaddr and
reloading didn't solve the problem (needed a restart).

I made asterisk dump core, it's a 64bit machine but the core file is
3551223808 bytes, might be a coincidence but this looks pretty close to the
max memory usage of 32bit binaries. Still have to examine the stack trace,
but am a bit weary about running "gdb /usr/sbin/asterisk core" on the
machine that is running an active asterisk. Will this cause problems for
the running asterisk? 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2010-11-11 05:19 dtryba         Note Added: 0128776                          
======================================================================