diff options
author | murf <murf@f38db490-d61c-443f-a65b-d21fe96a405b> | 2007-05-02 17:10:50 +0000 |
---|---|---|
committer | murf <murf@f38db490-d61c-443f-a65b-d21fe96a405b> | 2007-05-02 17:10:50 +0000 |
commit | 64c47fc59d08227e402cd2177d8ea8a23064f289 (patch) | |
tree | 8fef696a254988ddb7ce5e5ba9414a130635b739 /configs | |
parent | 47d7b5c6e6f748cdf9696b5441d4c18baf3b5d4a (diff) |
a)In chan_zap, set the clid, src fields in channel_alloc call. b)in the channel_alloc func, set the cid_num and name fields from the arglist[blush]. c) don't update the channel app & app data fields if you are in the 'h' extension. d)the load_module func in cdr_radius needs to return DECLINE, SUCCESS.
git-svn-id: http://svn.digium.com/svn/asterisk/branches/1.4@62689 f38db490-d61c-443f-a65b-d21fe96a405b
Diffstat (limited to 'configs')
-rw-r--r-- | configs/extensions.conf.sample | 41 |
1 files changed, 37 insertions, 4 deletions
diff --git a/configs/extensions.conf.sample b/configs/extensions.conf.sample index e50837cde..aa382f52d 100644 --- a/configs/extensions.conf.sample +++ b/configs/extensions.conf.sample @@ -140,15 +140,48 @@ TRUNKMSD=1 ; MSD digits to strip (usually 1 or 0) ; ; Contexts contain several lines, one for each step of each ; extension, which can take one of two forms as listed below, -; with the first form being preferred. 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. +; with the first form being preferred. ; ;[context] ;exten => someexten,{priority|label{+|-}offset}[(alias)],application(arg1,arg2,...) ;exten => someexten,{priority|label{+|-}offset}[(alias)],application,arg1|arg2... ; +; Included Contexts +; +; 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. +; The reason a context would include other contexts is for their +; extensions. +; The algorithm to find an extension is recursive, and works in this +; fashion: +; first, given a stack on which to store context references, +; push the context to find the extension onto the stack... +; a) Try to find a matching extension in the context at the top of +; the stack, and, if found, begin executing the priorities +; there in sequence. +; b) If not found, Search the switches, if any declared, in +; sequence. +; c) If still not found, for each include, push that context onto +; the top of the context stack, and recurse to a). +; d) If still not found, pop the entry from the top of the stack; +; if the stack is empty, the search has failed. If it's not, +; continue with the next context in c). +; This is a depth-first traversal, and stops with the first context +; that provides a matching extension. As usual, if more than one +; pattern in a context will match, the 'best' match will win. +; Please note that that extensions found in an included context are +; treated as if they were in the context from which the search began. +; The PBX's notion of the "current context" is not changed. +; Please note that in a context, it does not matter where an include +; directive occurs. Whether at the top, or near the bottom, the effect +; will be the same. The only thing that matters is that if there is +; more than one include directive, they will be searched for extensions +; in order, first to last. +; Also please note that pattern matches (like _9XX) are not treated +; any differently than exact matches (like 987). Also note that the +; order of extensions in a context have no affect on the outcome. +; ; Timing list for includes is ; ; <time range>|<days of week>|<days of month>|<months> |