; Contexts contain several lines, one for each step of each extension. One may
; include another context in the current one as well, optionally with a date
; and time. Included contexts are included in the order they are listed.
; Switches may also be included within a context. The order of matching within
; a context is always exact extensions, pattern match extensions, includes, and
; switches. Includes are always processed depth-first. So for example, if you
; would like a switch "A" to match before context "B",
simply put switch "A" in
; an included context "C", where "C" is included in your
original context
; before "B".
Note that if the pattern match is actually in another include (which it does
not seem to be, given that you didn't imply that it was), then the order of
includes matters - so you would want to include your parkinglots context first.
This is also one way that I believe you could define the behavior you want:
[call_extension]
exten => 100,1,NoOp()
same => n,Verbose(Do stuff to a call)
same => n,Hangup()
include => parkedcalls
include => catch_all
[catch_all]
exten => _X.,1,Noop(22 - Running in ${CONTEXT} at ${EXTEN})
exten => _X.,n,Set(AGISIGHUP=no)
exten => _X.,n,AGI(/var/lib/asterisk/hash3/bin/exten2.py)
exten => _X.,n,HangUp
--
Matthew Jordan
Digium, Inc. | Engineering Manager
445 Jan Davis Drive NW - Huntsville, AL 35806 - USA
Check us out at: http://digium.com & http://asterisk.org