[asterisk-bugs] [Asterisk 0018313]: Asterisk does not send release message when channel requested during SETUP gets changed during Procedding Message from TELCO

Mon Apr 4 11:00:04 CDT 2011

A NOTE has been added to this issue. 
====================================================================== 
https://issues.asterisk.org/view.php?id=18313 
====================================================================== 
Reported By:                destiny6628
Assigned To:                rmudgett
====================================================================== 
Project:                    Asterisk
Issue ID:                   18313
Category:                   Channels/chan_dahdi
Reproducibility:            always
Severity:                   minor
Priority:                   normal
Status:                     closed
Asterisk Version:           1.4.37 
JIRA:                       SWP-2620 
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-11-16 01:47 CST
Last Modified:              2011-04-04 11:00 CDT
====================================================================== 
Summary:                    Asterisk does not send release message when channel
requested during SETUP gets changed during Procedding Message from TELCO
Description: 
Hi, 

We are using Asterisk 1.4.36 / dahdi-linux-2.3.0.1 / dahdi-tool-2.3.0 /
libpri 1.4.10 with Digium Pri cards 4 PORT and 2 PORT respectively with
hardware echo cancellation supported.

I will try to describe issue to the best of my ability out here so that we
can come to any sort of resolution on this, as I am sure there would many
others facing same issue.

Description :

I am working with a TELCO PROVIDER known as BT in UK where i have ISDN30e
lines from there where TEI is static.

During Call Initiation from Dialer Server Channel picked up from Server
would be X and sent across the ISDN LINE towards TELCO.

Now in return to that SETUP there would be a CALL PROCEDDING Message send
back by TELCO on a different channel which was there during the SET UP
MESSAGE.

Unfortunately when this happens the channel on which CALL PROCEDDING was
sent back, was already BUSY.

Now at this instant as per my understanding ideally Asterisk shall release
channel and call shall get hangup but instead of this Call remains ON and
gets established on a another channel which was in CALL PROCEDDING but as
CHANNEL has changed there would be no audio at all.

Please find the PRI LOGS ATTACHED in the description

======================================================================
Relationships       ID      Summary
----------------------------------------------------------------------
related to          0018231 [patch] Asterisk gets killed during the...
====================================================================== 

---------------------------------------------------------------------- 
 (0133343) svnbot (reporter) - 2011-04-04 11:00
 https://issues.asterisk.org/view.php?id=18313#c133343 
---------------------------------------------------------------------- 
Repository: asterisk
Revision: 312574

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

------------------------------------------------------------------------
r312574 | rmudgett | 2011-04-04 11:00:04 -0500 (Mon, 04 Apr 2011) | 45
lines

Merged revisions 312573 via svnmerge from 
https://origsvn.digium.com/svn/asterisk/branches/1.4

........
  r312573 | rmudgett | 2011-04-04 10:49:30 -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=312574 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2011-04-04 11:00 svnbot         Checkin                                      
2011-04-04 11:00 svnbot         Note Added: 0133343                          
======================================================================