[asterisk-bugs] [Asterisk 0016989]: When Answer is used for chan_local in Originate, the originate go crazy

[Asterisk Bug Tracker]

A NOTE has been added to this issue. 
====================================================================== 
https://issues.asterisk.org/view.php?id=16989 
====================================================================== 
Reported By:                ik_5
Assigned To:                
====================================================================== 
Project:                    Asterisk
Issue ID:                   16989
Category:                   Channels/chan_local
Reproducibility:            have not tried
Severity:                   major
Priority:                   normal
Status:                     feedback
Asterisk Version:           1.4.30-rc3 
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-03-08 12:25 CST
Last Modified:              2010-04-28 16:52 CDT
====================================================================== 
Summary:                    When Answer is used for chan_local in Originate, the
originate go crazy
Description: 
When I do the following Originate:

action: Originate
priority: 1
context: btest
exten: s
channel: Local/<test>@atest/n
timeout: 60000

On a dialplan:
[atest]
exten => _X.,1,NoOp(Test Case A)
exten => _X.,n,Answer()
exten => _X.,n,DumpChan()
exten => _X.,n,Dial(DAHDI/g1/<number>,120,L(100000:5000:1000))

[btest]
exten => s,1,NoOp(Test case A-b)
exten => s,n,Answer()
exten => s,n,Dial(DAHDI/g1/<number>,120,rmg)

If I do not remove the Answer function from atest, then Originate act
crazy in an unknown way to predict, it will not execute the dialplan
properly.
======================================================================
Relationships       ID      Summary
----------------------------------------------------------------------
duplicate of        0016637 [patch] Dial option 'L' does not work c...
====================================================================== 

---------------------------------------------------------------------- 
 (0121133) ik_5 (reporter) - 2010-04-28 16:52
 https://issues.asterisk.org/view.php?id=16989#c121133 
---------------------------------------------------------------------- 
But this behavior is not the same as old Asterisk versions, or as I
understand from newer (have not tested it myself) 1.6x versions.

Old Asterisk 1.2 and older 1.4 allowed the dial to remain blocking even
with Answer on a local channel.

The original goal of the Answer cmd is to make the Originate terminate
successfully as fast as it can.

Unless I'm missing something, the dial plan execution should not be
jumping to other context unless they have a direct goto request, or it was
finishing executing the first context. And on my test case, that are not
the cases at all.

So I do not think that it's proper behavior at all. 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2010-04-28 16:52 ik_5           Note Added: 0121133                          
======================================================================