[asterisk-bugs] [Asterisk 0017009]: Dialplan continues execution after transfer

Asterisk Bug Tracker noreply at bugs.digium.com
Fri Mar 19 07:32:31 CDT 2010


A NOTE has been added to this issue. 
====================================================================== 
https://issues.asterisk.org/view.php?id=17009 
====================================================================== 
Reported By:                mmurdock
Assigned To:                
====================================================================== 
Project:                    Asterisk
Issue ID:                   17009
Category:                   PBX/General
Reproducibility:            always
Severity:                   minor
Priority:                   normal
Status:                     acknowledged
Asterisk Version:           SVN 
JIRA:                       SWP-1074 
Regression:                 No 
Reviewboard Link:            
SVN Branch (only for SVN checkouts, not tarball releases): 1.6.1 
SVN Revision (number only!): 251819 
Request Review:              
====================================================================== 
Date Submitted:             2010-03-11 13:33 CST
Last Modified:              2010-03-19 07:32 CDT
====================================================================== 
Summary:                    Dialplan continues execution after transfer
Description: 
A Call B
B Answers
A does a dtmf attended transfer to 700
B is transfered
A hears parking slot and with the dialplan shown below hears weasels.

A should not hear weasels.  Dialplan execution should of ended after the
dial application ran.
====================================================================== 

---------------------------------------------------------------------- 
 (0119614) rsw686 (reporter) - 2010-03-19 07:32
 https://issues.asterisk.org/view.php?id=17009#c119614 
---------------------------------------------------------------------- 
This is related to 0016856. Since the behavior was changed at the end of
the 1.4 branch and looks to exist in 1.6.0, 1.6.1, and 1.6.2. If we keep
the behavior functionality is broken for those migration from 1.4. If we
change it back it breaks functionality for those running 1.6.x. Can we just
add a setting to turn this on or off. This would solve the problem for
everyone. 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2010-03-19 07:32 rsw686         Note Added: 0119614                          
======================================================================




More information about the asterisk-bugs mailing list