[asterisk-bugs] [Asterisk 0016113]: Auto-fallthrough when attempting to enter DTMF using Background() in a Macro()

[Asterisk Bug Tracker]

A NOTE has been added to this issue. 
====================================================================== 
https://issues.asterisk.org/view.php?id=16113 
====================================================================== 
Reported By:                OrNix
Assigned To:                tilghman
====================================================================== 
Project:                    Asterisk
Issue ID:                   16113
Category:                   General
Reproducibility:            always
Severity:                   minor
Priority:                   normal
Status:                     feedback
Target Version:             1.6.1.13
Asterisk Version:           SVN 
JIRA:                       SWP-440 
Regression:                 Yes 
Reviewboard Link:            
SVN Branch (only for SVN checkouts, not tarball releases): N/A 
SVN Revision (number only!):  
Request Review:              
====================================================================== 
Date Submitted:             2009-10-22 03:59 CDT
Last Modified:              2009-12-10 13:11 CST
====================================================================== 
Summary:                    Auto-fallthrough when attempting to enter DTMF using
Background() in a Macro()
Description: 
Hello, All.

Asterisk calls me using a call-file, then i make call with the following
macro:

[macro-internalcall-with-redirect-callback]
exten => s,1,Dial(SIP/${ARG1},20,jgtedH)
exten => s,n,Goto(s-${DIALSTATUS},1)
exten => s-BUSY,1,Background(busy-cycl0)
exten => s-BUSY,2,Goto(${CONTEXT},s,1)

In ${MACRO_CONTEXT} i have extensions:
exten => *,1,ResetCDR(w)
exten => *,n,Goto(${CONTEXT},s,5) 

I make a call to _XXX, recieve "BUSY". While busy-cycl0 is playing, i hit
the "*"-key.

1.6.1.7rc2 - Strange behavior:
[Oct 16 18:03:19] -- Executing
[s at macro-internalcall-with-redirect-callback:3] Goto("H323/sibirtelecom-1",
"s-BUSY,1") in new stack
[Oct 16 18:03:19] -- Goto
(macro-internalcall-with-redirect-callback,s-BUSY,1)
[Oct 16 18:03:19] -- Executing
[s-BUSY at macro-internalcall-with-redirect-callback:1]
BackGround("H323/sibirtelecom-1", "busy-cycl0") in new stack
[Oct 16 18:03:19] -- <H323/sibirtelecom-1> Playing 'busy-cycl0.alaw'
(language 'en')
[Oct 16 18:03:20] -- Auto fallthrough, channel 'H323/sibirtelecom-1'
status is 'BUSY'
[Oct 16 18:03:24] DEBUG[9435]: pbx_spool.c:405 scan_service: Delaying
retry since we're currently running
'/var/spool/asterisk/outgoing/32631.call'
[Oct 16 18:03:27] NOTICE[9475]: pbx_spool.c:348 attempt_thread: Call
completed to Local/2487305 at qqq


1.6.1.4 - Normal behavior:
[Oct 16 18:06:43] -- Executing
[s at macro-internalcall-with-redirect-callback:3] Goto("H323/sibirtelecom-1",
"s-BUSY,1") in new stack
[Oct 16 18:06:43] -- Goto
(macro-internalcall-with-redirect-callback,s-BUSY,1)
[Oct 16 18:06:43] -- Executing
[s-BUSY at macro-internalcall-with-redirect-callback:1]
BackGround("H323/sibirtelecom-1", "busy-cycl0") in new stack
[Oct 16 18:06:43] -- <H323/sibirtelecom-1> Playing 'busy-cycl0.alaw'
(language 'en')
[Oct 16 18:06:44] == CDR updated on H323/sibirtelecom-1
[Oct 16 18:06:44] -- Executing [*@callback:1]
ResetCDR("H323/sibirtelecom-1", "w") in new stack
[Oct 16 18:06:44] -- Executing [*@callback:2] Goto("H323/sibirtelecom-1",
"callback,s,5") in new stack
[Oct 16 18:06:44] -- Goto (callback,s,5)
[Oct 16 18:06:44] -- Executing [s at callback:5]
WaitExten("H323/sibirtelecom-1", "1") in new stack

This error occurs both with chan_h323 and with chan_ooh323.

P.S. I don't know, what category should i select in this case, please move
 the topic to the correct one.
====================================================================== 

---------------------------------------------------------------------- 
 (0115085) tilghman (administrator) - 2009-12-10 13:11
 https://issues.asterisk.org/view.php?id=16113#c115085 
---------------------------------------------------------------------- 
You're missing a critical part of your dialplan.  How is that macro even
getting executed?  It's not ever called from the part of the dialplan that
you posted. 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2009-12-10 13:11 tilghman       Note Added: 0115085                          
======================================================================