[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:                mvanbaak
====================================================================== 
Project:                    Asterisk
Issue ID:                   13777
Category:                   Channels/chan_skinny
Reproducibility:            random
Severity:                   crash
Priority:                   normal
Status:                     assigned
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-03-30 12:12 CDT
====================================================================== 
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
====================================================================== 

---------------------------------------------------------------------- 
 (0102407) tilghman (administrator) - 2009-03-30 12:12
 http://bugs.digium.com/view.php?id=13777#c102407 
---------------------------------------------------------------------- 
pj:  It may or may not be, but as stated previously, the ONLY debug that's
going to help on this issue is valgrind output.  gdb output at this point
is gratuitous and useless. 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2009-03-30 12:12 tilghman       Note Added: 0102407                          
======================================================================