[asterisk-bugs] [Asterisk 0018231]: Asterisk gets killed during the live calling
Asterisk Bug Tracker
noreply at bugs.digium.com
Tue Nov 16 01:24:02 CST 2010
A NOTE has been added to this issue.
======================================================================
https://issues.asterisk.org/view.php?id=18231
======================================================================
Reported By: destiny6628
Assigned To:
======================================================================
Project: Asterisk
Issue ID: 18231
Category: Channels/chan_dahdi
Reproducibility: always
Severity: crash
Priority: normal
Status: feedback
Asterisk Version: 1.4.36
JIRA:
Regression: No
Reviewboard Link:
SVN Branch (only for SVN checkouts, not tarball releases): N/A
SVN Revision (number only!):
Request Review:
======================================================================
Date Submitted: 2010-10-29 08:13 CDT
Last Modified: 2010-11-16 01:24 CST
======================================================================
Summary: Asterisk gets killed during the live calling
Description:
We are using Asterisk 1.4.36 / Dahdi 1.4.0 / Dahdi-tool as 1.4.0 / Libpri
as 1.4.11.4 and Wanpipe Drivers as wanpipe-3.5.17.
We are using Sangoma 2 Port E1 Card with hardware echo cancellation
supported.
Problem which is being faced during the calls twice in a day every day
asterisk gets stopped and due to which all our calls gets disconnected
which has been a daily issues.
======================================================================
----------------------------------------------------------------------
(0128879) abhay_avis (reporter) - 2010-11-16 01:24
https://issues.asterisk.org/view.php?id=18231#c128879
----------------------------------------------------------------------
My view is from your logs and code is that while on any message say during
ringing if the channel asked is 5 instead of 17 as you see in log and it is
found busy , asterisk is not sending the hangup. The call proceeds receives
a ANSWER and again the same message moving call from 17 to 5 and 5 is busy
.
So certainly the call is not going in BUSY state and is proceeding though
structures are neither cleared nor locked . This seems to be a sure bug
which needs to be resolved .
Issue History
Date Modified Username Field Change
======================================================================
2010-11-16 01:24 abhay_avis Note Added: 0128879
======================================================================
More information about the asterisk-bugs
mailing list