Datasets:
Squidnutz
/
extractedtest

Dataset card Data Studio Files
xet
 Community
1
text
stringlengths
0
152
The default value is app (which is the default behavior in previous versions of Aster‐
isk). Probably in most cases you’ll want to use conf (especially if you want your caller
experience to be as non-weird as possible).
MySQL> update `asterisk`.`queues` set timeoutpriority='conf'
where name in ('sales','support','support-priority');
The goal is to get callers to agents, yes?
230
|
Chapter 12: Automatic Call Distribution Queues
Controlling when to join and leave a queue
Asterisk provides two options that control when callers can join and are forced to
leave queues, both based on the statuses of the queue members. The first option, join
empty, is used to control whether callers can enter a queue in the first place. The sec‐
ond option, leavewhenempty, is used to control events that will cause callers already
in a queue to be removed from that queue (i.e., if all of the queue members become
unavailable). Both options allow for a comma-separated list of values to control this
behavior, as listed in Table 12-5.
Table 12-5. Options that can be set for joinempty or leavewhenempty
Value
paused
penalty
inuse
ringing
Description
Members are considered unavailable if they are paused.
Members are considered unavailable if their penalties are less than QUEUE_MAX_PENALTY.
Members are considered unavailable if their device status is InUse.
Members are considered unavailable if their device status is Ringing.
unavailable Applies primarily to agent channels; if the agent is not logged in but is a member of the queue, the
invalid
unknown
wrapup
channel is considered unavailable.
Members are considered unavailable if their device status is Invalid. This is typically an error condition.
Members are considered unavailable if device status is unknown.
Members are considered unavailable if they are currently in the wrapup time after the completion of a call.
For joinempty, prior to placing a caller into the queue, all the members are checked
for availability using the factors you list as criteria. If all members are deemed to be
unavailable, the caller will not be permitted to enter the queue, and dialplan execu‐
tion will continue at the next priority.6 For the leavewhenempty option, the members’
statuses are checked periodically against the listed conditions; if it is determined that
no members are available to take calls, the caller is removed from the queue, with
dialplan execution continuing at the next priority.
An example use of joinempty could be:
joinempty=unavailable,invalid,unknown
With this configuration, prior to a caller entering the queue the statuses of all queue
members will be checked, and the caller will not be permitted to enter the queue
unless at least one queue member is found to have a status that is not unavailable,
invalid, or unknown.
The leavewhenempty example could be something like:
6 If the priority n+1 (from where the Queue() application was called) is not defined, the call will be hung up. In
other words, don’t use this functionality unless your dialplan does something useful at the step immediately
following Queue().
Advanced Queues
|
231
leavewhenempty=unavailable,invalid,unknown
In this case, the queue members’ statuses will be checked periodically, and callers will
be removed from the queue if no queue members can be found who do not have a
status of unavailable, invalid, or unknown.
Previous versions of Asterisk used the values yes, no, strict, and loose as the avail‐
able values to be assigned. The mapping of those values is shown in Table 12-6.
Table 12-6. Mapping between old and new values for controlling when callers join and leave
queues
Value
yes
no