[asterisk-bugs] [Asterisk 0018231]: [patch] Asterisk gets killed during the live calling

[Asterisk Bug Tracker]

The following issue has been RESOLVED. 
====================================================================== 
https://issues.asterisk.org/view.php?id=18231 
====================================================================== 
Reported By:                destiny6628
Assigned To:                rmudgett
====================================================================== 
Project:                    Asterisk
Issue ID:                   18231
Category:                   Channels/chan_dahdi
Reproducibility:            always
Severity:                   crash
Priority:                   normal
Status:                     resolved
Asterisk Version:           1.4.36 
JIRA:                       SWP-2924 
Regression:                 No 
Reviewboard Link:            
SVN Branch (only for SVN checkouts, not tarball releases): N/A 
SVN Revision (number only!):  
Request Review:              
Resolution:                 fixed
Fixed in Version:           
====================================================================== 
Date Submitted:             2010-10-29 08:13 CDT
Last Modified:              2011-04-04 10:49 CDT
====================================================================== 
Summary:                    [patch] 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.


======================================================================
Relationships       ID      Summary
----------------------------------------------------------------------
related to          0018313 Asterisk does not send release message ...
====================================================================== 

---------------------------------------------------------------------- 
 (0133339) svnbot (reporter) - 2011-04-04 10:49
 https://issues.asterisk.org/view.php?id=18231#c133339 
---------------------------------------------------------------------- 
Repository: asterisk
Revision: 312573

U   branches/1.4/channels/chan_dahdi.c
U   branches/1.4/configure
U   branches/1.4/configure.ac
U   branches/1.4/include/asterisk/autoconfig.h.in

------------------------------------------------------------------------
r312573 | rmudgett | 2011-04-04 10:49:32 -0500 (Mon, 04 Apr 2011) | 38
lines

Issues with ISDN calls changing B channels during call negotiations.

The handling of the PROCEEDING message was not using the correct call
structure if the B channel was changed.  (The same for PROGRESS.) The call
was also not hungup if the new B channel is not provisioned or is busy.

* Made all call connection messages (SETUP_ACKNOWLEDGE, PROCEEDING,
PROGRESS, ALERTING, CONNECT, CONNECT_ACKNOWLEDGE) ensure that they are
using the correct structure and B channel.  If there is any problem with
the operations then the call is now hungup with an appropriate cause code.

* Made miscellaneous messages (INFORMATION, FACILITY, NOTIFY) find the
correct structure by looking for the call and not using the channel ID.
NOTIFY is an exception with versions of libpri before v1.4.11 because a
call pointer is not available for Asterisk to use.

* Made all hangup messages (DISCONNECT, RELEASE, RELEASE_COMPLETE) find
the correct structure by looking for the call and not using the channel
ID.

(closes issue https://issues.asterisk.org/view.php?id=18313)
Reported by: destiny6628
Tested by: rmudgett
JIRA SWP-2620

(closes issue https://issues.asterisk.org/view.php?id=18231)
Reported by: destiny6628
Tested by: rmudgett
JIRA SWP-2924

(closes issue https://issues.asterisk.org/view.php?id=18488)
Reported by: jpokorny
JIRA SWP-2929

JIRA AST-437 (The issues fixed here are most likely causing this JIRA
issue.)
JIRA DAHDI-406
JIRA LIBPRI-33 (Stuck resetting flag likely fixed)

------------------------------------------------------------------------

http://svn.digium.com/view/asterisk?view=rev&revision=312573 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2011-04-04 10:49 svnbot         Checkin                                      
2011-04-04 10:49 svnbot         Note Added: 0133339                          
2011-04-04 10:49 svnbot         Status                   assigned => resolved
2011-04-04 10:49 svnbot         Resolution               open => fixed       
======================================================================