[asterisk-bugs] [Asterisk 0013972]: including same dial plan into 2 different contexts, produces different priorities

[Asterisk Bug Tracker]

A NOTE has been added to this issue. 
====================================================================== 
http://bugs.digium.com/view.php?id=13972 
====================================================================== 
Reported By:                pabelanger
Assigned To:                
====================================================================== 
Project:                    Asterisk
Issue ID:                   13972
Category:                   PBX/General
Reproducibility:            always
Severity:                   minor
Priority:                   normal
Status:                     new
Asterisk Version:           1.6.0.1 
SVN Branch (only for SVN checkouts, not tarball releases): N/A 
SVN Revision (number only!):  
Disclaimer on File?:        N/A 
Request Review:              
====================================================================== 
Date Submitted:             2008-11-25 22:19 CST
Last Modified:              2008-12-11 09:21 CST
====================================================================== 
Summary:                    including same dial plan into 2 different contexts,
produces different priorities
Description: 
I'll try my best to explain.

We are trying to create a context [Global1] that we reuse it a few other
contexts.  The problem is, when included in the first context, the
priorities are created properly.

However, when we call the next context including [Global1], the priorities
from [Global1] are dropped and over written by the context that included
it.
====================================================================== 

---------------------------------------------------------------------- 
 (0096197) file (administrator) - 2008-12-11 09:21
 http://bugs.digium.com/view.php?id=13972#c96197 
---------------------------------------------------------------------- 
After confirming with Jared Smith I am closing this out as this was a
dialplan configuration issue. 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2008-12-11 09:21 file           Note Added: 0096197                          
======================================================================