On Tuesday 24 April 2007 4:38 pm, Steve Murphy wrote:
You only need one such 'catchall' in the include hierarchy. They will
all be searched. The first matching exact-match or pattern match will
take the prize.
That's my point, exactly. If I want a different catchall action in a
particular
On Wed, 2007-04-25 at 08:18 -0400, Andrew Kohlsmith wrote:
On Tuesday 24 April 2007 8:26 pm, Jared Smith wrote:
Here's just one example of the many ways I use the current behavior.
[long-distance]
exten = _1NXXNXX,1,Dial(IAX2/${UPSTREAM}/${EXTEN})
include = local
[local]
exten
On Tuesday 24 April 2007 20:26:25 Jared Smith wrote:
On 4/24/07, Steve Murphy [EMAIL PROTECTED] wrote:
Trouble is, is this desired behavior? Or is having the contexts checked
level by level until a match of any kind is found, the better procedure?
Well, I for one desire the current
On Wednesday 25 April 2007 10:04 am, Steve Murphy wrote:
Well, I guess the magic of putting the _1NXXNXX exten in the local
context wouldn't be useful until you define an untrusted context:
I generally build my contexts as small and modular blocks, and then
build grouping contexts which
On Wednesday 25 April 2007 10:37 am, Leif Madsen wrote:
[long_distance]
exten = _1NXXNXX,1,Dial(IAX2/${UPSTEAM}/${EXTEN})
exten = h,1,Verbose(1|This would actually get hit, and not the _. pattern)
include = match_all
[match_all]
exten = _.,1,NoOp()
exten =
On Wed, 2007-04-25 at 10:37 -0400, Leif Madsen wrote:
On Tuesday 24 April 2007 20:26:25 Jared Smith wrote:
On 4/24/07, Steve Murphy [EMAIL PROTECTED] wrote:
Trouble is, is this desired behavior? Or is having the contexts checked
level by level until a match of any kind is found, the
On Wednesday 25 April 2007 11:47 am, Steve Murphy wrote:
I do propose that we make the following change to the
extensions.conf.sample file to minimize user
misunderstanding/frustration over include directives the reason this
thread began...
Do you think this might help? Is the English
