[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-19-2008 01:32 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-19-08 01:32  
---------------------------------------------------------------------- 
James, it seems, that your patch bug11972-5.diff.txt solved my crashes,
especially, when tls peer/client becomes unreacheble. 
today, I got same messages as before on console, but asterisk doesn't
crash. I will continue testing...
Shouldn't be this warnings moved to debug log level? 

[Feb 19 00:02:39] NOTICE[9887]: chan_sip.c:18626 sip_poke_noanswer: Peer
'726' is now UNREACHABLE!  Last qualify: 14
[Feb 19 00:02:49] WARNING[9887]: chan_sip.c:2531 __sip_xmit: sip_xmit of
0xb799716c (len 587) to 85.216.201.137:53612 returned -1: Success
[Feb 19 00:03:07] WARNING[9887]: chan_sip.c:2531 __sip_xmit: sip_xmit of
0xb799716c (len 587) to 85.216.201.137:53612 returned -1: Success
[Feb 19 00:03:25] WARNING[9887]: chan_sip.c:2531 __sip_xmit: sip_xmit of
0xb799716c (len 587) to 85.216.201.137:53612 returned -1: Success
[Feb 19 00:03:43] WARNING[9887]: chan_sip.c:2531 __sip_xmit: sip_xmit of
0xb799716c (len 587) to 85.216.201.137:53612 returned -1: Success
[Feb 19 00:04:01] WARNING[9887]: chan_sip.c:2531 __sip_xmit: sip_xmit of
0xb799716c (len 587) to 85.216.201.137:53612 returned -1: Success 

Issue History 
Date Modified   Username       Field                    Change               
====================================================================== 
02-19-08 01:32  pj             Note Added: 0082548                          
======================================================================