[asterisk-dev] extensions.conf included contexts priorities

[Andrew Kohlsmith]

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 context, it needs to be separated from that context and included, 
or it will never get used.

> As far as overriding goes, I'd guess you put your most specific stuff in
> the highest-level context, and include more general sorts of stuff. Sort
> of inside-out, but still very workable...?

Yeah, I dunno... I'm kind of aggravated with this nonintuitive stuff and am 
trying to help get the system to a path of least surprise kind of operation.  
The "it's always been that way" type of arguments against change have never 
had much pull with me.  We all drove horse-drawn carriages before the 
motorcar, so why design the motorcar?  It's always been done that way!

... or something like that.   Cue the "I get 12 rods to the hogshead and 
that's the way I likes it" and the old welshmen competition about who had it 
harder.  :-)

"Back in my day, we had to dial with our fingers and hope that nobody else was 
using the party line!"

"Party line?  Heaven!  When I was a youngster we didn't have a telephone, all 
we could do were send smoke signals, and by gum we liked it, too!"

"Smoke signals?  We dinna even have FIRE!"

-A.