[asterisk-bugs] [Asterisk 0013777]: crash or dialing isn't possible

[Asterisk Bug Tracker]

A NOTE has been added to this issue. 
====================================================================== 
http://bugs.digium.com/view.php?id=13777 
====================================================================== 
Reported By:                pj
Assigned To:                Corydon76
====================================================================== 
Project:                    Asterisk
Issue ID:                   13777
Category:                   Channels/chan_skinny
Reproducibility:            random
Severity:                   crash
Priority:                   normal
Status:                     feedback
Asterisk Version:           1.6.1-beta3 
Regression:                 No 
SVN Branch (only for SVN checkouts, not tarball releases): 1.6.0 
SVN Revision (number only!): 151765 
Request Review:              
====================================================================== 
Date Submitted:             2008-10-24 14:24 CDT
Last Modified:              2009-01-21 17:37 CST
====================================================================== 
Summary:                    crash or dialing isn't possible
Description: 
asterisk sometimes crashes, when attempt to dial from skinny phone (cisco
7920) or if asterisk doesn't crash, after some successfull skinny calls,
more calls are not possible: I type number on phone, then press 'dial'
button, after that, number disappears from phone display (skinny debug
shows nothing in this case), restarting phone doesn't solve this problem, I
must restart asterisk to restore functionality, asterisk isn't locked in
this situation ('core show locks' is empty)
it seems, that svn-trunk isn't affected by this issue
====================================================================== 

---------------------------------------------------------------------- 
 (0098385) wedhorn (reporter) - 2009-01-21 17:37
 http://bugs.digium.com/view.php?id=13777#c98385 
---------------------------------------------------------------------- 
Actually, my guess is that it's a locking issue. It appears that a call
continues being processed while the session with the device is torn down.
Of course, this will lead to memory corruption as the call will happily
write to areas of memory that have been freed by another thread.

I've changed the locking on a rewrite I'm doing that will hopefully either
fix this or make it easier to fix. 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2009-01-21 17:37 wedhorn        Note Added: 0098385                          
======================================================================