[Home]

Summary:ASTERISK-17120: Asterisk does not end call properly and stops reacting to following SETUP messages
Reporter:Jiri Pokorny (jpokorny)Labels:
Date Opened:2010-12-16 11:13:20.000-0600Date Closed:2011-04-04 11:18:03
Priority:MajorRegression?No
Status:Closed/CompleteComponents:Channels/chan_dahdi
Versions:Frequency of
Occurrence
Related
Issues:
Environment:Attachments:( 0) log.tar.gz
Description:Using libpri 1.4.11.4. About once in a week or two Asterisk stops reacting to SETUP messages with a certain call reference number. Message is completely ignored and it does not reply until Asterisk is restarted. As the PBX on the other side of ISDN reuses this call reference often, it almost completely disables making any call. I am adding the full log with pri intense debug. Call has reference number 2304, you can easily see the situation:

grep "reference 2304" log

In the last working call asterisk didn't reply to RELEASE message. Since this moment all messages with this reference number were ignored. It could be as well libpri issue but chan_dahdi seems to me more appropriate.
Comments:By: Leif Madsen (lmadsen) 2010-12-16 11:16:05.000-0600

Looks like you forgot to attach the log.
By: Jiri Pokorny (jpokorny) 2010-12-16 11:22:58.000-0600

I was just uploading it...
By: Digium Subversion (svnbot) 2011-04-04 10:49:35

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 ASTERISK-16964)
Reported by: destiny6628
Tested by: rmudgett
JIRA SWP-2620

(closes issue ASTERISK-16892)
Reported by: destiny6628
Tested by: rmudgett
JIRA SWP-2924

(closes issue ASTERISK-17120)
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
By: Digium Subversion (svnbot) 2011-04-04 11:00:06

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 ASTERISK-16964)
 Reported by: destiny6628
 Tested by: rmudgett
 JIRA SWP-2620
 
 (closes issue ASTERISK-16892)
 Reported by: destiny6628
 Tested by: rmudgett
 JIRA SWP-2924
 
 (closes issue ASTERISK-17120)
 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
By: Digium Subversion (svnbot) 2011-04-04 11:10:53

Repository: asterisk
Revision: 312575

_U  branches/1.8/
U   branches/1.8/channels/chan_dahdi.c
U   branches/1.8/channels/sig_pri.c
U   branches/1.8/channels/sig_pri.h

------------------------------------------------------------------------
r312575 | rmudgett | 2011-04-04 11:10:51 -0500 (Mon, 04 Apr 2011) | 52 lines

Merged revisions 312574 via svnmerge from
https://origsvn.digium.com/svn/asterisk/branches/1.6.2

................
 r312574 | rmudgett | 2011-04-04 11:00:02 -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 ASTERISK-16964)
   Reported by: destiny6628
   Tested by: rmudgett
   JIRA SWP-2620
   
   (closes issue ASTERISK-16892)
   Reported by: destiny6628
   Tested by: rmudgett
   JIRA SWP-2924
   
   (closes issue ASTERISK-17120)
   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=312575
By: Digium Subversion (svnbot) 2011-04-04 11:18:02

Repository: asterisk
Revision: 312579

_U  trunk/
U   trunk/channels/chan_dahdi.c
U   trunk/channels/sig_pri.c
U   trunk/channels/sig_pri.h

------------------------------------------------------------------------
r312579 | rmudgett | 2011-04-04 11:18:00 -0500 (Mon, 04 Apr 2011) | 59 lines

Merged revisions 312575 via svnmerge from
https://origsvn.digium.com/svn/asterisk/branches/1.8

................
 r312575 | rmudgett | 2011-04-04 11:10:50 -0500 (Mon, 04 Apr 2011) | 52 lines
 
 Merged revisions 312574 via svnmerge from
 https://origsvn.digium.com/svn/asterisk/branches/1.6.2
 
 ................
   r312574 | rmudgett | 2011-04-04 11:00:02 -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 ASTERISK-16964)
     Reported by: destiny6628
     Tested by: rmudgett
     JIRA SWP-2620
     
     (closes issue ASTERISK-16892)
     Reported by: destiny6628
     Tested by: rmudgett
     JIRA SWP-2924
     
     (closes issue ASTERISK-17120)
     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=312579