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

[Asterisk Bug Tracker]

The following issue has been CLOSED 
====================================================================== 
https://issues.asterisk.org/view.php?id=14309 
====================================================================== 
Reported By:                pkempgen
Assigned To:                lmadsen
====================================================================== 
Project:                    Asterisk
Issue ID:                   14309
Category:                   Channels/chan_sip/General
Reproducibility:            always
Severity:                   block
Priority:                   normal
Status:                     closed
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:              
Resolution:                 open
Fixed in Version:           
====================================================================== 
Date Submitted:             2009-01-22 07:50 CST
Last Modified:              2009-07-29 11:13 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 ...
====================================================================== 

---------------------------------------------------------------------- 
 (0108349) lmadsen (administrator) - 2009-07-29 11:13
 https://issues.asterisk.org/view.php?id=14309#c108349 
---------------------------------------------------------------------- 
OK, I'm closing this issue because the people who were affected by it seem
to be unresponsive, which means I can only come to the conclusion this
issue has been resolved in a later version of Asterisk.

I attempted to reproduce as I explained in my note, and have been unable
to come up with anything other than what I expected to see.

The original reporter of the issue is more than welcome to reopen this
issue if he has additional information which can lead to this issue being
reproduced, and thus moved towards resolution.

If anyone else experiences this issue, please open a new issue, and report
exact how to reproduce this on the latest 1.4 branch.

Thanks!
Leif. 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2009-07-29 11:13 lmadsen        Note Added: 0108349                          
2009-07-29 11:13 lmadsen        Status                   ready for testing =>
closed
======================================================================