[asterisk-bugs] [Asterisk 0013777]: crash or dialing isn't possible
Asterisk Bug Tracker
noreply at bugs.digium.com
Sat Jan 24 08:05:18 CST 2009
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-24 08:05 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
======================================================================
----------------------------------------------------------------------
(0098665) Corydon76 (administrator) - 2009-01-24 08:05
http://bugs.digium.com/view.php?id=13777#c98665
----------------------------------------------------------------------
pj: At this point, only the valgrind is going to help. Please note that
even if when running valgrind, Asterisk does not crash, the output provided
by that utility should be helpful in tracking this down. Your gdb output
only serves to reinforce the idea that this is a memory corruption issue
and provides no further useful information.
Issue History
Date Modified Username Field Change
======================================================================
2009-01-24 08:05 Corydon76 Note Added: 0098665
======================================================================
More information about the asterisk-bugs
mailing list