[asterisk-bugs] [Asterisk 0011970]: Usage of Goto() in an included context can cause unexpected behaviour

[noreply at bugs.digium.com]

A NOTE has been added to this issue. 
====================================================================== 
http://bugs.digium.com/view.php?id=11970 
====================================================================== 
Reported By:                blitzrage
Assigned To:                
====================================================================== 
Project:                    Asterisk
Issue ID:                   11970
Category:                   PBX/pbx_config
Reproducibility:            always
Severity:                   minor
Priority:                   normal
Status:                     new
Asterisk Version:           1.4.17 
SVN Branch (only for SVN checkouts, not tarball releases): N/A 
SVN Revision (number only!):  
Disclaimer on File?:        N/A 
Request Review:              
====================================================================== 
Date Submitted:             02-11-2008 08:49 CST
Last Modified:              02-11-2008 11:36 CST
====================================================================== 
Summary:                    Usage of Goto() in an included context can cause
unexpected behaviour
Description: 
I found this interesting little tidbit of usage behaviour yesterday when
writing some dialplan. Here is a simplified example of what I ran into:


[phones]

include => callControl
include => checkVoicemail

[callControl]
exten => preAuth,1,NoOp(well hello there)   ;   <-- this is what gets
matched when you do the Goto() from the checkVoicemail context.

[checkVoicemail]
exten => 8500,1,Goto(preAuth,1)

exten => preAuth,1,NoOp(this does not get hit as you might expect)
====================================================================== 

---------------------------------------------------------------------- 
 Corydon76 - 02-11-08 11:36  
---------------------------------------------------------------------- 
Well, this is working the way it is designed, and I can't think of any
steps we could take that won't massively slow down the dialplan.  The best
way to approach this is with a "Best Practices" document that describes
this situation and how to avoid it. 

Issue History 
Date Modified   Username       Field                    Change               
====================================================================== 
02-11-08 11:36  Corydon76      Note Added: 0082021                          
======================================================================