Summary: | ASTERISK-13123: including same dial plan into 2 different contexts, produces different priorities | ||
Reporter: | Paul Belanger (pabelanger) | Labels: | |
Date Opened: | 2008-11-25 22:19:30.000-0600 | Date Closed: | 2011-06-07 14:08:27 |
Priority: | Minor | Regression? | No |
Status: | Closed/Complete | Components: | PBX/General |
Versions: | Frequency of Occurrence | ||
Related Issues: | |||
Environment: | Attachments: | ( 0) asterisk_v2.log ( 1) asterisk.log ( 2) dialplan_show_v2.txt ( 3) dialplan_show.txt ( 4) expected-asterisk.log ( 5) extensions_v2.conf ( 6) extensions.conf | |
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. ****** ADDITIONAL INFORMATION ****** I've attached the asterisk.log(CLI output), extensions.conf(syntax for dial plans) and dial show.txt(output from asterisk CLI of priorities) | ||
Comments: | By: Paul Belanger (pabelanger) 2008-11-25 22:23:44.000-0600 I've also uploaded expected-asterisk.log (hand created) of what we would expect asterisk to do. By: Miguel Molina (coolmig) 2008-11-27 16:31:34.000-0600 Well, a workaround could be using another extension on the Goto's (s,start to <another extension>,1). I think that using the same extension on a context and an included context is what is causing you problems. However, including the same dialplan into 2 contexts that look the same should produce the same priorities. By: Paul Belanger (pabelanger) 2008-11-27 23:39:18.000-0600 coolmig: Thanks for the suggestion, but same problem :( Attached is v2 reproducing the issue. By: Miguel Molina (coolmig) 2008-11-28 08:11:04.000-0600 Well I think that in [Menu1] and [Menu2] contexts, to use 'n' extensions you should start them with the '1' priority, as in any dialplan. That would take you to this: [Menu1] include => Global1 exten => s,1(start),Answer exten => s,n(restart),Background(digits/6) exten => s,n,Background(digits/7) exten => s,n,Background(digits/8) exten => s,n,WaitExten(3) exten => 1,1,Goto(Menu2,go,1) [Menu2] include => Global1 exten => s,1(start),Background(digits/5) exten => s,n(restart),Background(digits/6) exten => s,n,Background(digits/7) exten => s,n,Background(digits/8) exten => s,n,WaitExten(3) If you put the extensions that way, the issue should be gone. By: Paul Belanger (pabelanger) 2008-11-28 08:30:05.000-0600 coolmig: Thanks, just retested with your logic and asterisk now works as expected. I'll continue to monitor this issue in case patch is submitted on this. By: Joshua C. Colp (jcolp) 2008-12-11 09:21:35.000-0600 After confirming with Jared Smith I am closing this out as this was a dialplan configuration issue. |