[asterisk-bugs] [Asterisk 0017352]: Asterisk deadlock

[Asterisk Bug Tracker]

A NOTE has been added to this issue. 
====================================================================== 
https://issues.asterisk.org/view.php?id=17352 
====================================================================== 
Reported By:                aleksey2000
Assigned To:                
====================================================================== 
Project:                    Asterisk
Issue ID:                   17352
Category:                   Channels/chan_sip/General
Reproducibility:            random
Severity:                   major
Priority:                   normal
Status:                     acknowledged
Asterisk Version:           1.6.2.7 
JIRA:                       SWP-1508 
Regression:                 No 
Reviewboard Link:            
SVN Branch (only for SVN checkouts, not tarball releases): N/A 
SVN Revision (number only!):  
Request Review:              
====================================================================== 
Date Submitted:             2010-05-18 05:11 CDT
Last Modified:              2010-05-18 13:06 CDT
====================================================================== 
Summary:                    Asterisk deadlock
Description: 
This asterisk used for transit traffic between MERA and unknown Cisco
device. Protocol: SIP Full proxy. Accept alaw, g729 than convert to alaw.
Timing: dahdi.
Usually,  after 2-3 hours asterisk going to deadlock. Average channels: 20
- 40.

Deadlock happened on 1.6.1.18, 1.6.1.19, 1.6.2.7. (with AGI (a2billing)
and without)


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

---------------------------------------------------------------------- 
 (0122064) lmadsen (administrator) - 2010-05-18 13:06
 https://issues.asterisk.org/view.php?id=17352#c122064 
---------------------------------------------------------------------- 
We're proceeding on this issue, however if you wish to test the latest
1.6.2.8-rc1 (or 1.6.2 branch directly) then that may be useful just to
verify it has not already been resolved. Thanks for the info! 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2010-05-18 13:06 lmadsen        Note Added: 0122064                          
======================================================================