[asterisk-bugs] [Asterisk 0014309]: [patch] SIP/realtime problems => 100 % CPU

[Asterisk Bug Tracker]

A NOTE has been added to this issue. 
====================================================================== 
https://issues.asterisk.org/view.php?id=14309 
====================================================================== 
Reported By:                pkempgen
Assigned To:                tilghman
====================================================================== 
Project:                    Asterisk
Issue ID:                   14309
Category:                   Channels/chan_sip/General
Reproducibility:            always
Severity:                   block
Priority:                   normal
Status:                     ready for testing
Target Version:             1.4.27
Asterisk Version:           1.4.22 
Regression:                 Yes 
SVN Branch (only for SVN checkouts, not tarball releases): N/A 
SVN Revision (number only!):  
Request Review:              
====================================================================== 
Date Submitted:             2009-01-22 07:50 CST
Last Modified:              2009-05-27 15:15 CDT
====================================================================== 
Summary:                    [patch] SIP/realtime problems => 100 % CPU
Description: 
As reported on
http://lists.digium.com/pipermail/asterisk-users/2009-January/225274.html
:

> Carlos Chavez schrieb:
>> 	Since 1.4.22 realtime status for sip peers seems to be broken.  If I
do
>> a "sip show peers" from the CLI I get this:
>> 
>> 2001/2001                  192.168.2.234    D          5060    
UNKNOWN
>> Cached RT
>> 
>> 	It is arbitrary which peers will say OK and which will say UNKNOWN
and
>> it changes over time.
> 
>> This used to work fine until 1.4.21
>> so why did it break and why wasn't it fixed on 1.4.23?  This only
>> happens when using realtime peers, static peers will always show the
>> proper status. 
> 
> It might be related to this issue (thread in German)
>
http://www.mail-archive.com/gemeinschaft-users@lists.amooma.de/msg00083.html
>
http://www.mail-archive.com/gemeinschaft-users@lists.amooma.de/msg00152.html
>
http://www.mail-archive.com/gemeinschaft-users@lists.amooma.de/msg00153.html
> etc.
> 
> Several people, including me, have confirmed that since Asterisk
> 1.4.22 you get hundreds (probably depends on the number of SIP
> peers/users) of SQL queries per second and the CLI is being flooded
> with
> ---cut---
> [Oct  8 12:22:56] NOTICE[2487]: chan_sip.c:16223 sip_poke_noanswer:
Peer
> '8280' is now UNREACHABLE!  Last qualify: 0
> ---cut---
> leading to 100 % CPU usage.
> 
> 1.4.21.2 didn't have the problem.

======================================================================
Relationships       ID      Summary
----------------------------------------------------------------------
related to          0004362 [patch] new config option 'rtautoreg'
related to          0012921 Asterisk 1.4.21 breaks realtime sip on ...
====================================================================== 

---------------------------------------------------------------------- 
 (0105588) pkempgen (reporter) - 2009-05-27 15:15
 https://issues.asterisk.org/view.php?id=14309#c105588 
---------------------------------------------------------------------- 
> pkempgen: if the patch works, why are we suggesting reverting something
different?

Reverting the changeset which caused the regression seemed the
most obvious thing to me but never mind.

Your patch seems to work. I just think at least one or two other
people should test it because I have no idea what side effects it
might have. OTOH if it should break anything else somebody will
complain sooner or later. :-) 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2009-05-27 15:15 pkempgen       Note Added: 0105588                          
======================================================================