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

Asterisk Bug Tracker noreply at bugs.digium.com
Fri May 1 18:19:45 CDT 2009


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:                   Channels/chan_sip/Interoperability
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-01 18:19 CDT
====================================================================== 
Summary:                    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.

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

---------------------------------------------------------------------- 
 (0104050) madkins (reporter) - 2009-05-01 18:19
 http://bugs.digium.com/view.php?id=15014#c104050 
---------------------------------------------------------------------- 
in the meantime, i instrumented res_timing_pthread.c...

i added code to track how many bytes were written to and read from each
pipe inside of res_timing_pthread.c, adding code to read_pipe and
write_byte

there's one FD (11 on my box) that only seems to be written to, never read
from, and when it hits 65536 all debug statements stop, this seems like a
problem, like there's nothing setup to read from that pipe

i also instrumented the pthread_timer_xxx functions (e.g.
pthread_timer_open), but they don't get called until an actual phone call
is made ... which begs the question ... why is write_byte being called so
many times if the pthread_timer_open initialization is never called?

still exploring that 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2009-05-01 18:19 madkins        Note Added: 0104050                          
======================================================================




More information about the asterisk-bugs mailing list