Summary:ASTERISK-01413: with current cvs head _1NXX beats _18[00|88|77|66|55] even when in separate included contexts
Reporter:cloos (cloos)Labels:
Date Opened:2004-04-15 10:25:35Date Closed:2011-06-07 14:05:21
Versions:Frequency of
Description:Given this siplified plan

exten => _18[00|88|77|66|55]XXXXXXX,1,Playback(digits/1)

exten => _1NXXXXXXXXX,1,Playback(digits/2)

include => tf
include => toll

The order of including tf and toll no longer changes which pattern 18005551212 matches.

I tried re-ordering w/in the including context and also re-ordering the placement of the contexts w/in the file.
In all cases the calls went to the more general pattern
rather than the more specific one.

Comments:By: Mark Spencer (markster) 2004-04-15 10:31:03

Find me on IRC, i'm sure this is a configuration issue.

By: Mark Spencer (markster) 2004-04-15 11:40:43

I'm looking at pbx.c and it doesn't look like:


Is a valid pattern.  Is your file patched somehow?

By: Mark Spencer (markster) 2004-04-15 11:51:53

The pattern being tested wasn't valid.  Sorry it took me so long to figure that out.

By: cloos (cloos) 2004-04-15 11:53:28

mea culpa

i thought I had confirmed that [11|22|33] was kosher to select either 11 or 22 or 33 but that is not the case.

bug should be not just closed but erased; it is getting hard to breathe in this paper bag.... :-/