[asterisk-bugs] [Asterisk 0011972]: tls transport often causes asterisk to lock

[noreply at bugs.digium.com]

A NOTE has been added to this issue. 
====================================================================== 
http://bugs.digium.com/view.php?id=11972 
====================================================================== 
Reported By:                pj
Assigned To:                jamesgolovich
====================================================================== 
Project:                    Asterisk
Issue ID:                   11972
Category:                   Channels/chan_sip/General
Reproducibility:            random
Severity:                   block
Priority:                   normal
Status:                     assigned
Asterisk Version:           SVN 
SVN Branch (only for SVN checkouts, not tarball releases):  trunk 
SVN Revision (number only!): 103313 
Disclaimer on File?:        N/A 
Request Review:              
====================================================================== 
Date Submitted:             02-11-2008 11:04 CST
Last Modified:              02-26-2008 01:54 CST
====================================================================== 
Summary:                    tls transport often causes asterisk to lock
Description: 
when asterisk is locked, no call or registration is processed,
this happened several times today and yesterday (tried several trunk
revisions)
currently haven't found thing, what causes the locking situation, 
it seems, that locking problem start appearing, after more peers start
using tls transport
my tls only peers are: asterisk trunk, asterisk beta2 and eyebeam
sofphone
+several udp clients.



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

---------------------------------------------------------------------- 
 pj - 02-26-08 01:54  
---------------------------------------------------------------------- 
what should I find in coredebug to supply usefull informations? log is very
big, so I can't upload all file. coredebug2.txt was catched around time,
when some call was not established successfully (looking to cli), so I
issue 'core show locks' and saw some locking state and posted coredebug2
from this time, maybe locks happened before I catch this. but I have log
stored, so if you tell me, what should I find, I can post it.
Right now, I'm uploading coredebug3.txt, where you can also see some weird
states.
(it was not locked today, 'core show locks' shows only tried and failed
entries) 

Issue History 
Date Modified   Username       Field                    Change               
====================================================================== 
02-26-08 01:54  pj             Note Added: 0082946                          
======================================================================