[asterisk-bugs] [Asterisk 0011080]: SIP channel stops processing calls, but no apparent deadlock
noreply at bugs.digium.com
noreply at bugs.digium.com
Thu Dec 27 02:38:09 CST 2007
A NOTE has been added to this issue.
======================================================================
http://bugs.digium.com/view.php?id=11080
======================================================================
Reported By: callguy
Assigned To: russell
======================================================================
Project: Asterisk
Issue ID: 11080
Category: Channels/chan_sip/General
Reproducibility: always
Severity: block
Priority: normal
Status: assigned
Asterisk Version: 1.4.13
SVN Branch (only for SVN checkouts, not tarball releases): N/A
SVN Revision (number only!):
Disclaimer on File?: N/A
Request Review:
======================================================================
Date Submitted: 10-24-2007 15:58 CDT
Last Modified: 12-27-2007 02:38 CST
======================================================================
Summary: SIP channel stops processing calls, but no apparent
deadlock
Description:
Approximately once per week we are seeing asterisk stop processing SIP
calls. The behavior is the same as a deadlock, but core show locks does not
show any evidence that there is a deadlock.
The only way to resolve is to restart asterisk.
output of:
core show locks
info thread
thread apply all bt
from the running process is attached.
======================================================================
Relationships ID Summary
----------------------------------------------------------------------
related to 0011165 Deadlock in channel.c
======================================================================
----------------------------------------------------------------------
Ivan - 12-27-07 02:38
----------------------------------------------------------------------
callguy: I think that the problem was solved after last closing. I see,
that it not so. For New Year's holidays I will have enough time to look
this long-living problem. It looks like simple back-call locking with
complex conditions. Tell me please, do you have some specific addons under
Asterisk? If the problem repeated on our systems, it would be much easier.
Anything concrete I do not promise, but I shall try to help.
Issue History
Date Modified Username Field Change
======================================================================
12-27-07 02:38 Ivan Note Added: 0075999
======================================================================
More information about the asterisk-bugs
mailing list