[asterisk-bugs] [Asterisk 0015014]: [patch] Asterisk loses SIP phones, possible deadlock, 1.6.1.0

[Asterisk Bug Tracker]

A NOTE has been added to this issue. 
====================================================================== 
http://bugs.digium.com/view.php?id=15014 
====================================================================== 
Reported By:                madkins
Assigned To:                
====================================================================== 
Project:                    Asterisk
Issue ID:                   15014
Category:                   Resources/res_timing_pthread
Reproducibility:            always
Severity:                   major
Priority:                   normal
Status:                     new
Asterisk Version:           1.6.1.0 
Regression:                 No 
SVN Branch (only for SVN checkouts, not tarball releases): N/A 
SVN Revision (number only!):  
Request Review:              
====================================================================== 
Date Submitted:             2009-05-01 11:03 CDT
Last Modified:              2009-05-05 12:18 CDT
====================================================================== 
Summary:                    [patch] Asterisk loses SIP phones, possible
deadlock, 1.6.1.0
Description: 
I have two Cisco 7905g SIP phones connected to an Asterisk 1.6.1.0 instance
running on a 64 bit Xen instance of Debian 4.0.  My initial configuration
was more complex, but I've removed a lot of the complexity searching for
the problem.

Basically, I can start the Asterisk server and pick up a SIP phone and
call either a test extension or the other phone.  Works fine.  If I leave
it alone for a time ... say over a long lunch or overnight ... I come back
and the phones won't connect to Asterisk.

This repeats reliably but at unknown intervals.

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

---------------------------------------------------------------------- 
 (0104236) madkins (reporter) - 2009-05-05 12:18
 http://bugs.digium.com/view.php?id=15014#c104236 
---------------------------------------------------------------------- 
of course the code should never actually depend on the directory traversal
order ;-)

so there may be two issues here:

1) some modules depend on others and that relationship isn't (afaik)
clearly documented anywhere (please correct me if i'm wrong, love to have
that as a resource) and the appearance of issues is in some cases dependent
on the directory traversal order which is unpredictable

2) the res_timing_pthread code will eventually lockup if the pipe is not
periodically cleared or read from and there appears to be no fallback for
this situation in cases such as this, which may occur when a module is
loaded and creates a timer object and then never calls an _ack or
_disable_continuous on it

both of these appear to be existing problems and may require separate
solutions, as it appears that the chan_iax2.so module may not properly
configure itself without a hint in the modules.conf

again ... i may have missed some key documentation ... i confess in
advance to ignorance as well as laziness, impatience, and hubris 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2009-05-05 12:18 madkins        Note Added: 0104236                          
======================================================================