[asterisk-bugs] [Asterisk 0019205]: Using "loose" option for "joinempty" and/or "leavewhenempty" settings causes severe Asterisk issues

Asterisk Bug Tracker noreply at bugs.digium.com
Fri Apr 29 18:03:31 CDT 2011


A NOTE has been added to this issue. 
====================================================================== 
https://issues.asterisk.org/view.php?id=19205 
====================================================================== 
Reported By:                wrp
Assigned To:                
====================================================================== 
Project:                    Asterisk
Issue ID:                   19205
Category:                   Applications/app_queue
Reproducibility:            random
Severity:                   crash
Priority:                   normal
Status:                     new
Asterisk Version:           1.8.3.2 
JIRA:                        
Regression:                 No 
Reviewboard Link:            
SVN Branch (only for SVN checkouts, not tarball releases): N/A 
SVN Revision (number only!):  
Request Review:              
====================================================================== 
Date Submitted:             2011-04-29 16:08 CDT
Last Modified:              2011-04-29 18:03 CDT
====================================================================== 
Summary:                    Using "loose" option for "joinempty" and/or
"leavewhenempty" settings causes severe Asterisk issues
Description: 
We started using this option today and have run into two separate issues
when using it:

1) We received countless registration-related errors immediately upon
reloading our config such as the following:

[2011-04-29 12:11:54] NOTICE[2255]: chan_sip.c:23511
handle_request_register: Registration from '<sip:2143@[REMOVED]>' failed
for '192.168.202.79:5060' - No matching peer found
[2011-04-29 12:11:55] NOTICE[2255]: chan_sip.c:23511
handle_request_register: Registration from '<sip:2216@[REMOVED]>' failed
for '192.168.202.76:5060' - No matching peer found
[2011-04-29 12:11:55] NOTICE[2255]: chan_sip.c:23511
handle_request_register: Registration from '<sip:2216@[REMOVED]>' failed
for '192.168.202.76:5060' - No matching peer found

It appears as though parts of our config, such as sip_additional.conf,
wasn't loaded, causing registrations from remote devices to fail. Upon
reverting back to using the "no" option for joinempty and leavewhenempty,
these errors went away.

2) A second time that we tried changing these settings, we experienced an
Asterisk crash a little later. We aren't able to find much information in
terms of errors, but we did see a huge spike on our SNMP graphs that
monitor server load and we were dropped out of our "asterisk -r" sessions.


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

---------------------------------------------------------------------- 
 (0134283) davidw (reporter) - 2011-04-29 18:03
 https://issues.asterisk.org/view.php?id=19205#c134283 
---------------------------------------------------------------------- 
The background for this is in
http://forums.digium.com/viewtopic.php?f=1&t=78109&p=156849

wrp is being constrained by a GUI (FreePBX) that seems only able to access
the legacy modes of these options.

As they haven't provided the required debugging information, I can't tell
whether their problems are actually related to the use of these options,
although the mix of symptoms suggests a memory corruptions problem.  wrp:
please see https://wiki.asterisk.org/wiki/display/AST/Getting+a+Backtrace
for what you need to do to progress a crash report.  If this is memory
corruption related, you will also need
https://wiki.asterisk.org/wiki/display/AST/Valgrind

In terms of wrp's original problem, the following, historic, issue is
relevant: https://issues.asterisk.org/view.php?id=12451 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2011-04-29 18:03 davidw         Note Added: 0134283                          
======================================================================




More information about the asterisk-bugs mailing list