[asterisk-bugs] [Asterisk 0018627]: sip call fails to hang up - asterisk uses 99% resources
Asterisk Bug Tracker
noreply at bugs.digium.com
Tue Feb 1 03:00:24 CST 2011
The following issue has been UPDATED.
======================================================================
https://issues.asterisk.org/view.php?id=18627
======================================================================
Reported By: John Fawcett
Assigned To:
======================================================================
Project: Asterisk
Issue ID: 18627
Category: Channels/chan_sip/General
Reproducibility: have not tried
Severity: major
Priority: normal
Status: new
Asterisk Version: 1.8.2
JIRA:
Regression: No
Reviewboard Link:
SVN Branch (only for SVN checkouts, not tarball releases): N/A
SVN Revision (number only!):
Request Review:
======================================================================
Date Submitted: 2011-01-16 11:23 CST
Last Modified: 2011-02-01 03:00 CST
======================================================================
Summary: sip call fails to hang up - asterisk uses 99%
resources
Description:
After upgrading to 1.8.2 (and also present in 1.8.1.1) asterisk is often
found to be consuming 99% of resources.
This has been traced to calls which have been hangup by the remote party
but are still show as active (in BYE state) in asterisk.
It does seem to be random but happens so frequently that I can easily
reproduce this state by doing test calls until it happens. I can do any
debugging or tracing that is needed, just point me in the direction of what
is needed.
======================================================================
----------------------------------------------------------------------
(0131326) John Fawcett (reporter) - 2011-02-01 03:00
https://issues.asterisk.org/view.php?id=18627#c131326
----------------------------------------------------------------------
I have managed to reproduce, (now with 1.8.2.3)
I am attaching backtrace and locks info as well as debug log output with
verbose and debug set to 15 and sip debug and sip history on.
As the log contains a lot of info, the call which triggered the problem
was a test call from SIP/203 extension to a test queue SIP/252.
At the end of the call asterisk is consuming 90+% resources and is
unresponsive (i.e. no calls can be made any more).
Issue History
Date Modified Username Field Change
======================================================================
2011-02-01 03:00 John Fawcett Note Added: 0131326
2011-02-01 03:00 John Fawcett Status closed => new
2011-02-01 03:00 John Fawcett Resolution unable to reproduce =>
reopened
======================================================================
More information about the asterisk-bugs
mailing list