[asterisk-users] priority problem

[unplug]

Thanks.  Could you tell me how useful it is?  As I think if the
priority is reset in every context.  I can design something like this.
 My default context is myflow and your default context is yrflow.  So
I can easy to delete a context in the context myflow if necessary.

[myflow]
include => testflow1
include => testflow2
include => testflow3

[yrflow]
include => testflow1
include => testflow3

[testflow1]
exten => _X.,1,NoOp(testflow1,1=${CALLERID(NUM)})

[testflow2]
exten => _X.,1,NoOp(testflow2,1=${CALLERID(NUM)})
exten => _X.,2,NoOp(testflow2,2=${CALLERID(NUM)})

[testflow3]
exten => _X.,1,NoOp(testflow3,1=${CALLERID(NUM)})
exten => _X.,2,NoOp(testflow3,2=${CALLERID(NUM)})
exten => _X.,3,NoOp(testflow3,3=${CALLERID(NUM)})

On 7/13/06, Steve Davies <davies147 at gmail.com> wrote:
> On 7/13/06, unplug <maillisting at gmail.com> wrote:
> > In dial plan, we can set the priority.  However, I find that the
> > priority count is a global value.  It will continue to increment no
> > matter in different context.  Below is what I have tried.
>
> This is exactly how it is designed, and is a very useful feature.
>
> You need to understand the matching order properly to appreciate to
> power of this type of evaluation, but I believe the solution to your
> particular question is Goto, and not include.
>
>  [testflow]
> exten => _X.,1,NoOp(testflow,1=${CALLERID(NUM)})
> exten => _X.,2,NoOp(testflow,2=${CALLERID(NUM)})
> exten => _X.,3,Goto(testflow1,${EXTEN},1)
> ...
>
> Each context has its own "exten =>" lines checked first, and then each
> "include =>" is checked in the order specified after that. Consider
> using Macros too, they will often shorten a dialplan.
>
> Cheers,
> Steve
> _______________________________________________
> --Bandwidth and Colocation provided by Easynews.com --
>
> asterisk-users mailing list
> To UNSUBSCRIBE or update options visit:
>    http://lists.digium.com/mailman/listinfo/asterisk-users
>