queues.conf.sample 24 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180181182183184185186187188189190191192193194195196197198199200201202203204205206207208209210211212213214215216217218219220221222223224225226227228229230231232233234235236237238239240241242243244245246247248249250251252253254255256257258259260261262263264265266267268269270271272273274275276277278279280281282283284285286287288289290291292293294295296297298299300301302303304305306307308309310311312313314315316317318319320321322323324325326327328329330331332333334335336337338339340341342343344345346347348349350351352353354355356357358359360361362363364365366367368369370371372373374375376377378379380381382383384385386387388389390391392393394395396397398399400401402403404405406407408409410411412413414415416417418419420421422423424425426427428429430431432433434435436437438439440441442443444445446447448449450451452453454455456457458459460461462463464465466467468469470471472473474475476477478479480481482483484485486487488489490491492493494495496497498499500501502503504505506507508509510511512513514515516517518519520521522523524525526527528529530531532533534535536537538539540541542543544545546547548549550
  1. [general]
  2. ;
  3. ; Global settings for call queues
  4. ;
  5. ; Persistent Members
  6. ; Store each dynamic member in each queue in the astdb so that
  7. ; when asterisk is restarted, each member will be automatically
  8. ; read into their recorded queues. Default is 'no'.
  9. ;
  10. persistentmembers = yes
  11. ;
  12. ; AutoFill Behavior
  13. ; The old behavior of the queue (autofill=no) is to have a serial type behavior
  14. ; in that the queue will make all waiting callers wait in the queue
  15. ; even if there is more than one available member ready to take
  16. ; calls until the head caller is connected with the member they
  17. ; were trying to get to. The next waiting caller in line then
  18. ; becomes the head caller, and they are then connected with the
  19. ; next available member and all available members and waiting callers
  20. ; waits while this happens. The new behavior, enabled by setting
  21. ; autofill=yes makes sure that when the waiting callers are connecting
  22. ; with available members in a parallel fashion until there are
  23. ; no more available members or no more waiting callers. This is
  24. ; probably more along the lines of how a queue should work and
  25. ; in most cases, you will want to enable this behavior. If you
  26. ; do not specify or comment out this option, it will default to yes.
  27. ;
  28. ;autofill = no
  29. ;
  30. ; Monitor Type
  31. ; By setting monitor-type = MixMonitor, when specifying monitor-format
  32. ; to enable recording of queue member conversations, app_queue will
  33. ; now use the new MixMonitor application instead of Monitor so
  34. ; the concept of "joining/mixing" the in/out files now goes away
  35. ; when this is enabled. You can set the default type for all queues
  36. ; here, and then also change monitor-type for individual queues within
  37. ; queue by using the same configuration parameter within a queue
  38. ; configuration block. If you do not specify or comment out this option,
  39. ; it will default to the old 'Monitor' behavior to keep backward
  40. ; compatibility.
  41. ;
  42. monitor-type = MixMonitor
  43. ;
  44. ; UpdateCDR behavior.
  45. ; This option is implemented to mimic chan_agents behavior of populating
  46. ; CDR dstchannel field of a call with an agent name, which you can set
  47. ; at the login time with AddQueueMember membername parameter.
  48. ;
  49. ; updatecdr = no
  50. ;
  51. ; Note that a timeout to fail out of a queue may be passed as part of
  52. ; an application call from extensions.conf:
  53. ; Queue(queuename,[options],[optionalurl],[announceoverride],[timeout])
  54. ; example: Queue(dave,t,,,45)
  55. ; shared_lastcall will make the lastcall and calls received be the same in
  56. ; members logged in more than one queue. This is useful to make the queue
  57. ; respect the wrapuptime of another queue for a shared member.
  58. ; The default value is no.
  59. ;
  60. ;shared_lastcall=no
  61. ;
  62. ; Negative_penalty_invalid will treat members with a negative penalty as logged off
  63. ;
  64. ;negative_penalty_invalid = no
  65. ;
  66. ; log_membername_as_agent will cause app_queue to log the membername rather than
  67. ; the interface for the ADDMEMBER and REMOVEMEMBER events when a state_interface
  68. ; is set. The default value (no) maintains backward compatibility.
  69. ;
  70. ;log_membername_as_agent = no
  71. ;
  72. ;[markq]
  73. ;
  74. ; A sample call queue
  75. ;
  76. ; Musicclass sets which music applies for this particular call queue.
  77. ; The only class which can override this one is if the MOH class is set
  78. ; directly on the channel using Set(CHANNEL(musicclass)=whatever) in the
  79. ; dialplan.
  80. ;
  81. ;musicclass = default
  82. ;
  83. ; An announcement may be specified which is played for the member as
  84. ; soon as they answer a call, typically to indicate to them which queue
  85. ; this call should be answered as, so that agents or members who are
  86. ; listening to more than one queue can differentiated how they should
  87. ; engage the customer
  88. ;
  89. ;announce = queue-markq
  90. ;
  91. ; A strategy may be specified. Valid strategies include:
  92. ;
  93. ; ringall - ring all available channels until one answers (default)
  94. ; leastrecent - ring interface which was least recently hung up by this queue
  95. ; fewestcalls - ring the one with fewest completed calls from this queue
  96. ; random - ring random interface
  97. ; rrmemory - round robin with memory, remember where we left off last ring pass
  98. ; rrordered - same as rrmemory, except the queue member order from config file
  99. ; is preserved
  100. ; linear - rings interfaces in the order specified in this configuration file.
  101. ; If you use dynamic members, the members will be rung in the order in
  102. ; which they were added
  103. ; wrandom - rings random interface, but uses the member's penalty as a weight
  104. ; when calculating their metric. So a member with penalty 0 will have
  105. ; a metric somewhere between 0 and 1000, and a member with penalty 1 will
  106. ; have a metric between 0 and 2000, and a member with penalty 2 will have
  107. ; a metric between 0 and 3000. Please note, if using this strategy, the member
  108. ; penalty is not the same as when using other queue strategies. It is ONLY used
  109. ; as a weight for calculating metric.
  110. ;
  111. ;strategy = ringall
  112. ;
  113. ; Second settings for service level (default 0)
  114. ; Used for service level statistics (calls answered within service level time
  115. ; frame)
  116. ;servicelevel = 60
  117. ;
  118. ; A context may be specified, in which if the user types a SINGLE
  119. ; digit extension while they are in the queue, they will be taken out
  120. ; of the queue and sent to that extension in this context.
  121. ;
  122. ;context = qoutcon
  123. ;
  124. ; A limit can be set to disregard penalty settings when the queue has
  125. ; too few members. No penalty will be weighed in if there are only X
  126. ; or fewer queue members. (default 0)
  127. ;
  128. ;penaltymemberslimit = 5
  129. ;
  130. ;----------------------QUEUE TIMING OPTIONS------------------------------------
  131. ; A Queue has two different "timeout" values associated with it. One is the
  132. ; timeout parameter configured in queues.conf. This timeout specifies the
  133. ; amount of time to try ringing a member's phone before considering the
  134. ; member to be unavailable. The other timeout value is the second argument
  135. ; to the Queue() application. This timeout represents the absolute amount
  136. ; of time to allow a caller to stay in the queue before the caller is
  137. ; removed from the queue. In certain situations, these two timeout values
  138. ; may clash. For instance, if the timeout in queues.conf is set to 5 seconds,
  139. ; the retry value in queues.conf is set to 4, and the second argument to Queue()
  140. ; is 10, then the following may occur:
  141. ;
  142. ; A caller places a call to a queue.
  143. ; The queue selects a member and attempts to ring that member.
  144. ; The member's phone is rung for 5 seconds and he does not answer.
  145. ; The retry time of 4 seconds occurs.
  146. ; The queue selects a second member to call.
  147. ;
  148. ; How long does that second member's phone ring? Does it ring for 5 seconds
  149. ; since the timeout set in app_queue is 5 seconds? Does it ring for 1 second since
  150. ; the caller has been in the queue for 9 seconds and is supposed to be removed after
  151. ; being in the queue for 10 seconds? This is configurable with the timeoutpriority
  152. ; option. By setting the timeoutpriority to "conf" then you are saying that you would
  153. ; rather use the time specified in the configuration file even if it means having the
  154. ; caller stay in the queue longer than the time specified in the application argument.
  155. ; For the scenario described above, timeoutpriority=conf would result in the second
  156. ; member's phone ringing for 5 seconds. By specifying "app" as the value for
  157. ; timeoutpriority, you are saying that the timeout specified as the argument to the
  158. ; Queue application is more important. In the scenario above, timeoutpriority=app
  159. ; would result in the second member's phone ringing for 1 second.
  160. ;
  161. ; There are a few exceptions to the priority rules. For instance, if timeoutpriority=appp
  162. ; and the configuration file timeout is set to 0, but the application argument timeout is
  163. ; non-zero, then the timeoutpriority is ignored and the application argument is used as
  164. ; the timeout. Furthermore, if no application argument timeout is specified, then the
  165. ; timeoutpriority option is ignored and the configuration file timeout is always used
  166. ; when calling queue members.
  167. ;
  168. ; In timeoutpriority=conf mode however timeout specified in config file will take higher
  169. ; priority than timeout in application arguments, so if config file has timeout 0, each
  170. ; queue member will be called indefineately and application timeout will be checked only
  171. ; after this call attempt. This is useful for having queue members with custom timeouts
  172. ; specified within Dial application of Local channel, and allows handling NO ANSWER which
  173. ; would otherwise be interrupted by queue destroying child channel on timeout.
  174. ;
  175. ; The default value for timeoutpriority is "app" since this was how previous versions of
  176. ; Asterisk behaved.
  177. ;
  178. ;timeout = 15
  179. ;retry = 5
  180. ;timeoutpriority = app|conf
  181. ;
  182. ;-----------------------END QUEUE TIMING OPTIONS---------------------------------
  183. ; Weight of queue - when compared to other queues, higher weights get
  184. ; first shot at available channels when the same channel is included in
  185. ; more than one queue.
  186. ;
  187. ;weight=0
  188. ;
  189. ; After a successful call, how long to wait before sending a potentially
  190. ; free member another call (default is 0, or no delay)
  191. ;
  192. ;wrapuptime=15
  193. ;
  194. ; Autofill will follow queue strategy but push multiple calls through
  195. ; at same time until there are no more waiting callers or no more
  196. ; available members. The per-queue setting of autofill allows you
  197. ; to override the default setting on an individual queue level.
  198. ;
  199. ;autofill=yes
  200. ;
  201. ; Autopause will pause a queue member if they fail to answer a call
  202. ; no: Member will not be paused
  203. ; yes: Member will be paused only in the queue where the timeout took place
  204. ; all: Memeber will be paused in all queues he/she is a member
  205. ;autopause=yes
  206. ;
  207. ; Autopausedelay delay autopause for autopausedelay seconds from the
  208. ; last call if a member has not taken a call the delay has no effect.
  209. ;autopausedelay=60
  210. ;
  211. ; Autopausebusy controls whether or not a queue member is set as paused
  212. ; automatically upon the member device reporting busy. The autopausedelay
  213. ; option applies. Defaults to 'no'.
  214. ;autopausebusy=no
  215. ;
  216. ; Autopauseunavail controls whether or not a queue member is set as paused
  217. ; automatically upon the member device reporting congestion. The autopausedely
  218. ; option applies. Defaults to 'no'.
  219. ;autopauseunavail=no
  220. ;
  221. ; Maximum number of people waiting in the queue (0 for unlimited)
  222. ;
  223. ;maxlen = 0
  224. ;
  225. ; If set to yes, just prior to the caller being bridged with a queue member
  226. ; the following variables will be set
  227. ; MEMBERINTERFACE is the interface name (eg. Agent/1234)
  228. ; MEMBERNAME is the member name (eg. Joe Soap)
  229. ; MEMBERCALLS is the number of calls that interface has taken,
  230. ; MEMBERLASTCALL is the last time the member took a call.
  231. ; MEMBERPENALTY is the penalty of the member
  232. ; MEMBERDYNAMIC indicates if a member is dynamic or not
  233. ; MEMBERREALTIME indicates if a member is realtime or not
  234. ;
  235. ;setinterfacevar=no
  236. ;
  237. ; If set to yes, just prior to the caller being bridged with a queue member
  238. ; the following variables will be set:
  239. ; QEHOLDTIME callers hold time
  240. ; QEORIGINALPOS original position of the caller in the queue
  241. ;
  242. ;setqueueentryvar=no
  243. ;
  244. ; If set to yes, the following variables will be set
  245. ; just prior to the caller being bridged with a queue member
  246. ; and just prior to the caller leaving the queue
  247. ; QUEUENAME name of the queue
  248. ; QUEUEMAX maxmimum number of calls allowed
  249. ; QUEUESTRATEGY the strategy of the queue;
  250. ; QUEUECALLS number of calls currently in the queue
  251. ; QUEUEHOLDTIME current average hold time
  252. ; QUEUECOMPLETED number of completed calls for the queue
  253. ; QUEUEABANDONED number of abandoned calls
  254. ; QUEUESRVLEVEL queue service level
  255. ; QUEUESRVLEVELPERF current service level performance
  256. ;
  257. ;setqueuevar=no
  258. ; if set, run this macro when connected to the queue member
  259. ; you can override this macro by setting the macro option on
  260. ; the queue application
  261. ;
  262. ;membermacro=macro_name[,arg1[,...][,argN]]
  263. ; if set, run this gosub when connected to the queue member
  264. ; you can override this gosub by setting the gosub option on
  265. ; the queue application
  266. ;
  267. ;membergosub=gosub_context_name[,arg1[,...][,argN]]
  268. ; How often to announce queue position and/or estimated
  269. ; holdtime to caller (0=off)
  270. ; Note that this value is ignored if the caller's queue
  271. ; position has changed (see min-announce-frequency)
  272. ;
  273. ;announce-frequency = 90
  274. ;
  275. ; The absolute minimum time between the start of each
  276. ; queue position and/or estimated holdtime announcement
  277. ; This is useful for avoiding constant announcements
  278. ; when the caller's queue position is changing frequently
  279. ; (see announce-frequency)
  280. ;
  281. ;min-announce-frequency = 15
  282. ;
  283. ; How often to make any periodic announcement (see periodic-announce)
  284. ;
  285. ;periodic-announce-frequency=60
  286. ;
  287. ; Should the periodic announcements be played in a random order? Default is no.
  288. ;
  289. ;random-periodic-announce=no
  290. ;
  291. ; If set to yes, the periodic announcment frequency will be timed from the end
  292. ; of each announcment rather than from the start of each announcment. This
  293. ; defaults to off.
  294. ;
  295. ;relative-periodic-announce=yes
  296. ;
  297. ; Should we include estimated hold time in position announcements?
  298. ; Either yes, no, or only once.
  299. ; Hold time will be announced as the estimated time.
  300. ;
  301. ;announce-holdtime = yes|no|once
  302. ;
  303. ; Queue position announce?
  304. ; Valid values are "yes," "no," "limit," or "more." If set to "no," then the caller's position will
  305. ; never be announced. If "yes," then the caller's position in the queue will be announced
  306. ; to the caller. If set to "more," then if the number of callers is more than the number
  307. ; specified by the announce-position-limit option, then the caller will hear that there
  308. ; are more than that many callers waiting (i.e. if a caller number 6 is in a queue with the
  309. ; announce-position-limit set to 5, then that caller will hear that there are more than 5
  310. ; callers waiting). If set to "limit," then only callers within the limit specified by announce-position-limit
  311. ; will have their position announced.
  312. ;
  313. ;announce-position = yes
  314. ;
  315. ; If enabled, play announcements to the first user waiting in the Queue. This may mean
  316. ; that announcements are played when an agent attempts to connect to the waiting user,
  317. ; which may delay the time before the agent and the user can communicate. Disabled by
  318. ; default.
  319. ;
  320. ; announce-to-first-user = no
  321. ;
  322. ; If you have specified "limit" or "more" for the announce-position option, then the following
  323. ; value is what is used to determine what announcement to play to waiting callers. If you have
  324. ; set the announce-position option to anything else, then this will have no bearing on queue operation
  325. ;
  326. ;announce-position-limit = 5
  327. ;
  328. ; What's the rounding time for the seconds?
  329. ; If this is non-zero, then we announce the seconds as well as the minutes
  330. ; rounded to this value.
  331. ; Valid values are 0, 5, 10, 15, 20, and 30.
  332. ;
  333. ; announce-round-seconds = 10
  334. ;
  335. ; Use these sound files in making position/holdtime announcements. The
  336. ; defaults are as listed below -- change only if you need to.
  337. ;
  338. ; Keep in mind that you may also prevent a sound from being played if you
  339. ; explicitly set a sound to be an empty string. For example, if you want to
  340. ; prevent the queue from playing queue-thankyou, you may set the sound using
  341. ; the following line:
  342. ;
  343. ; queue-thankyou=
  344. ;
  345. ; ("You are now first in line.")
  346. ;queue-youarenext = queue-youarenext
  347. ; ("There are")
  348. ;queue-thereare = queue-thereare
  349. ; ("calls waiting.")
  350. ;queue-callswaiting = queue-callswaiting
  351. ; ("The current est. holdtime is")
  352. ;queue-holdtime = queue-holdtime
  353. ; ("minute.")
  354. ;queue-minute = queue-minute
  355. ; ("minutes.")
  356. ;queue-minutes = queue-minutes
  357. ; ("seconds.")
  358. ;queue-seconds = queue-seconds
  359. ; ("Thank you for your patience.")
  360. ;queue-thankyou = queue-thankyou
  361. ; ("Hold time")
  362. ;queue-reporthold = queue-reporthold
  363. ; ("All reps busy / wait for next")
  364. ;periodic-announce = queue-periodic-announce
  365. ;
  366. ; A set of periodic announcements can be defined by separating
  367. ; periodic announcements to reproduce by commas. For example:
  368. ;periodic-announce = queue-periodic-announce,your-call-is-important,please-wait
  369. ;
  370. ; The announcements will be played in the order in which they are defined. After
  371. ; playing the last announcement, the announcements begin again from the beginning.
  372. ;
  373. ; Calls may be recorded using Asterisk's monitor/MixMonitor resource
  374. ; This can be enabled from within the Queue application, starting recording
  375. ; when the call is actually picked up; thus, only successful calls are
  376. ; recorded, and you are not recording while people are listening to MOH.
  377. ; To enable monitoring, simply specify "monitor-format"; it will be disabled
  378. ; otherwise.
  379. ;
  380. ; You can specify the monitor filename with by calling
  381. ; Set(MONITOR_FILENAME=foo)
  382. ; Otherwise it will use MONITOR_FILENAME=${UNIQUEID}
  383. ;
  384. ; Pick any one valid extension for monitor format recording. If you leave
  385. ; monitor-format commented out, it will not record calls.
  386. ;
  387. ; monitor-format = gsm|wav|wav49
  388. ;
  389. ; Monitor Type
  390. ; By setting monitor-type = MixMonitor, when specifying monitor-format
  391. ; to enable recording of queue member conversations, app_queue will
  392. ; now use the new MixMonitor application instead of Monitor so
  393. ; the concept of "joining/mixing" the in/out files now goes away
  394. ; when this is enabled. If you do not specify or comment out this option,
  395. ; it will default to the old 'Monitor' behavior to keep backward
  396. ; compatibility.
  397. ;
  398. ; monitor-type = MixMonitor
  399. ;
  400. ; ----------------------- TYPE MIXMONITOR OPTIONS -----------------------------
  401. ;
  402. ;
  403. ; You can specify the options supplied to MixMonitor by calling (from the dialplan)
  404. ; Set(MONITOR_OPTIONS=av(<x>)V(<x>)W(<x>))
  405. ; The 'b' option for MixMonitor (only save audio to the file while bridged) is
  406. ; implied.
  407. ;
  408. ; You can specify a post recording command to be executed after the end of
  409. ; recording by calling (from the dialplan)
  410. ;
  411. ; Set(MONITOR_EXEC=mv /var/spool/asterisk/monitor/^{MONITOR_FILENAME} /tmp/^{MONITOR_FILENAME})
  412. ;
  413. ; or
  414. ;
  415. ; Set(MONITOR_EXEC=mv /var/spool/asterisk/monitor/^{MIXMONITOR_FILENAME} /tmp/^{MIXMONITOR_FILENAME})
  416. ;
  417. ; If you choose to use the latter, you will not be able to switch the monitor-type back to Monitor
  418. ; without changing this in the dialplan.
  419. ;
  420. ;
  421. ; The command specified within the contents of MONITOR_EXEC will be executed when
  422. ; the recording is over. Any strings matching ^{X} will be unescaped to ${X} and
  423. ; all variables will be evaluated just prior to recording being started.
  424. ;
  425. ; The contents of MONITOR_FILENAME will also be unescaped from ^{X} to ${X} and
  426. ; all variables will be evaluated just prior to recording being started.
  427. ;
  428. ; ---------------------- Queue Empty Options ----------------------------------
  429. ;
  430. ; Asterisk has provided the "joinempty" and "leavewhenempty" options for a while
  431. ; with tenuous definitions of what they actually mean. The "joinempty" option controls
  432. ; whether a caller may join a queue depending on several factors of member availability.
  433. ; Similarly, then leavewhenempty option controls whether a caller may remain in a queue
  434. ; he has already joined. Both options take a comma-separated list of factors which
  435. ; contribute towards whether a caller may join/remain in the queue. The list of
  436. ; factors which contribute to these option is as follows:
  437. ;
  438. ; paused: a member is not considered available if he is paused
  439. ; penalty: a member is not considered available if his penalty is less than QUEUE_MAX_PENALTY
  440. ; inuse: a member is not considered available if he is currently on a call
  441. ; ringing: a member is not considered available if his phone is currently ringing
  442. ; unavailable: This applies mainly to Agent channels. If the agent is a member of the queue
  443. ; but has not logged in, then do not consider the member to be available
  444. ; invalid: Do not consider a member to be available if he has an "invalid" device state.
  445. ; This generally is caused by an error condition in the member's channel driver.
  446. ; unknown: Do not consider a member to be available if we are unable to determine the member's
  447. ; current device state.
  448. ; wrapup: A member is not considered available if he is currently in his wrapuptime after
  449. ; taking a call.
  450. ;
  451. ; For the "joinempty" option, when a caller attempts to enter a queue, the members of that
  452. ; queue are examined. If all members are deemed to be unavailable due to any of the conditions
  453. ; listed for the "joinempty" option, then the caller will be unable to enter the queue. For the
  454. ; "leavewhenempty" option, the state of the members of the queue are checked periodically during
  455. ; the caller's stay in the queue. If all of the members are unavailable due to any of the above
  456. ; conditions, then the caller will be removed from the queue.
  457. ;
  458. ; Some examples:
  459. ;
  460. ;joinempty = paused,inuse,invalid
  461. ;
  462. ; A caller will not be able to enter a queue if at least one member cannot be found
  463. ; who is not paused, on the phone, or who has an invalid device state.
  464. ;
  465. ;leavewhenempty = inuse,ringing
  466. ;
  467. ; A caller will be removed from the queue if at least one member cannot be found
  468. ; who is not on the phone, or whose phone is not ringing.
  469. ;
  470. ; For the sake of backwards-compatibility, the joinempty and leavewhenempty
  471. ; options also accept the strings "yes" "no" "strict" and "loose". The following
  472. ; serves as a translation for these values:
  473. ;
  474. ; yes - (empty) for joinempty; penalty,paused,invalid for leavewhenempty
  475. ; no - penalty,paused,invalid for joinempty; (empty) for leavewhenempty
  476. ; strict - penalty,paused,invalid,unavailable
  477. ; loose - penalty,invalid
  478. ;
  479. ; If you wish to report the caller's hold time to the member before they are
  480. ; connected to the caller, set this to yes.
  481. ;
  482. ; reportholdtime = no
  483. ;
  484. ; If you want the queue to avoid sending calls to members whose devices are
  485. ; known to be 'in use' (via the channel driver supporting that device state)
  486. ; uncomment this option. This can be controlled on a per member basis by
  487. ; setting 'ringinuse' on that member. This can be done in the member definition,
  488. ; in the 'ringinuse' field on a realtime member, via the QUEUE_MEMBER dialplan
  489. ; function, or with CLI/AMI. By default, the per member value will be the same
  490. ; as the queue's ringinuse value if it isn't set on the member deliberately.
  491. ; (Note: only the SIP channel driver currently is able to report 'in use'.)
  492. ; ringinuse = no
  493. ;
  494. ; If you wish to have a delay before the member is connected to the caller (or
  495. ; before the member hears any announcement messages), set this to the number of
  496. ; seconds to delay.
  497. ;
  498. ; memberdelay = 0
  499. ;
  500. ; If timeoutrestart is set to yes, then the timeout for an agent to answer is
  501. ; reset if a BUSY or CONGESTION is received. This can be useful if agents
  502. ; are able to cancel a call with reject or similar.
  503. ;
  504. ; timeoutrestart = no
  505. ;
  506. ; If you wish to implement a rule defined in queuerules.conf (see
  507. ; configs/queuerules.conf.sample from the asterisk source directory for
  508. ; more information about penalty rules) by default, you may specify this
  509. ; by setting defaultrule to the rule's name
  510. ;
  511. ; defaultrule = myrule
  512. ;
  513. ; Each member of this call queue is listed on a separate line in
  514. ; the form technology/dialstring. "member" means a normal member of a
  515. ; queue. An optional penalty may be specified after a comma, such that
  516. ; entries with higher penalties are considered last. An optional member
  517. ; name may also be specified after a second comma, which is used in log
  518. ; messages as a "friendly name". Multiple interfaces may share a single
  519. ; member name. An optional state interface may be specified after a third
  520. ; comma. This interface will be the one for which app_queue receives device
  521. ; state notifications, even though the first interface specified is the one
  522. ; that is actually called.
  523. ;
  524. ; A hint can also be used in place of the state interface using the format
  525. ; hint:<extension>@<context>. If no context is specified then 'default' will
  526. ; be used.
  527. ;
  528. ; It is important to ensure that channel drivers used for members are loaded
  529. ; before app_queue.so itself or they may be marked invalid until reload. This
  530. ; can be accomplished by explicitly listing them in modules.conf before
  531. ; app_queue.so. Additionally, if you use Local channels as queue members, you
  532. ; must also preload pbx_config.so and chan_local.so (or pbx_ael.so, pbx_lua.so,
  533. ; or pbx_realtime.so, depending on how your dialplan is configured).
  534. ;
  535. ; syntax: member => interface,[,penalty][,membername][,state_interface][,ringinuse]
  536. ;
  537. ;member => DAHDI/1
  538. ;member => DAHDI/2,10
  539. ;member => DAHDI/3,10,Bob Johnson
  540. ;member => Local/1001@agents,0,May Flowers,Agent:1001
  541. ;member => Local/1002@agents,0,John Doe,Agent:1002
  542. ;member => Local/1000@default,0,John Smith,SIP/1000
  543. ;member => Local/2000@default,0,Lorem Ipsum,SIP/2000,no