aboutsummaryrefslogtreecommitdiffstats
path: root/configs/queues.conf.sample
diff options
context:
space:
mode:
authormmichelson <mmichelson@f38db490-d61c-443f-a65b-d21fe96a405b>2008-08-18 20:23:11 +0000
committermmichelson <mmichelson@f38db490-d61c-443f-a65b-d21fe96a405b>2008-08-18 20:23:11 +0000
commitd4a3345cb16062ba44a7c15ccfc02e273e58e750 (patch)
treedb70fdac46017e5a1445ad8e312799b0b9f79c6b /configs/queues.conf.sample
parentcc38d4ed0093a8aebbf61a520e9e9ada7fde22ed (diff)
Change the queue timeout priority logic into less ugly
and confusing code pieces. Clarify the logic within queues.conf.sample. (closes issue #12690) Reported by: atis Patches: queue_timeoutpriority.patch uploaded by atis (license 242) git-svn-id: http://svn.digium.com/svn/asterisk/trunk@138694 f38db490-d61c-443f-a65b-d21fe96a405b
Diffstat (limited to 'configs/queues.conf.sample')
-rw-r--r--configs/queues.conf.sample18
1 files changed, 13 insertions, 5 deletions
diff --git a/configs/queues.conf.sample b/configs/queues.conf.sample
index e4f6dd3bd..8e3b96d2b 100644
--- a/configs/queues.conf.sample
+++ b/configs/queues.conf.sample
@@ -148,11 +148,19 @@ shared_lastcall=no
; Queue application is more important. In the scenario above, timeoutpriority=app
; would result in the second member's phone ringing for 1 second.
;
-; There are a few exceptions to the priority rules. For instance, if the configuration
-; file timeout is set to 0, but the application argument timeout is non-zero, then the
-; timeoutpriority is ignored and the application argument is used as the timeout. Furthermore,
-; if no application argument timeout is specified, then the timeoutpriority option is
-; ignored and the configuration file timeout is always used when calling queue members.
+; There are a few exceptions to the priority rules. For instance, if timeoutpriority=appp
+; and the configuration file timeout is set to 0, but the application argument timeout is
+; non-zero, then the timeoutpriority is ignored and the application argument is used as
+; the timeout. Furthermore, if no application argument timeout is specified, then the
+; timeoutpriority option is ignored and the configuration file timeout is always used
+; when calling queue members.
+;
+; In timeoutpriority=conf mode however timeout specified in config file will take higher
+; priority than timeout in application arguments, so if config file has timeout 0, each
+; queue member will be called indefineately and application timeout will be checked only
+; after this call attempt. This is useful for having queue members with custom timeouts
+; specified within Dial application of Local channel, and allows handling NO ANSWER which
+; would otherwise be interrupted by queue destroying child channel on timeout.
;
; The default value for timeoutpriority is "app" since this was how previous versions of
; Asterisk behaved.