diff options
| author | Matthew Jordan <mjordan@digium.com> | 2014-08-11 00:07:22 +0000 |
|---|---|---|
| committer | Matthew Jordan <mjordan@digium.com> | 2014-08-11 00:07:22 +0000 |
| commit | 95871451f638203e8d76049221cbad0cbc930dbf (patch) | |
| tree | 15a679edda1b3a7f77b42ce675ebe4f91572769a /UPGRADE.txt | |
| parent | 8b411f710b9e972c9a22891d93d2f471197f22eb (diff) | |
app_queue: Add RealTime support for queue rules
This patch gives the optional ability to keep queue rules in RealTime. It is
important to note that with this patch:
(a) Queue rules in RealTime are only examined on module load/reload
(b) Queue rules are loaded both from the queuerules.conf file as well as the
RealTime backend
To inform app_queue to examine RealTime for queue rules, a new setting has been
added to queuerules.conf's general section "realtime_rules". RealTime queue
rules will only be used when this setting is set to "yes".
The schema for the database table supports a rule_name, time, min_penalty, and
max_penalty columns. min_penalty and max_penalty can be relative, if a '-' or
'+' literal is provided. Otherwise, the penalties are treated as constants.
For example:
rule_name, time, min_penalty, max_penalty
'default', '10', '20', '30'
'test2', '20', '30', '55'
'test2', '25', '-11', '+1111'
'test2', '400', '112', '333'
'test3', '0', '4564', '46546'
'test_rule', '40', '15', '50'
which would result in :
Rule: default
- After 10 seconds, adjust QUEUE_MAX_PENALTY to 30 and adjust
QUEUE_MIN_PENALTY to 20
Rule: test2
- After 20 seconds, adjust QUEUE_MAX_PENALTY to 55 and adjust
QUEUE_MIN_PENALTY to 30
- After 25 seconds, adjust QUEUE_MAX_PENALTY by 1111 and adjust
QUEUE_MIN_PENALTY by -11
- After 400 seconds, adjust QUEUE_MAX_PENALTY to 333 and adjust
QUEUE_MIN_PENALTY to 112
Rule: test3
- After 0 seconds, adjust QUEUE_MAX_PENALTY to 46546 and adjust
QUEUE_MIN_PENALTY to 4564
Rule: test_rule
- After 40 seconds, adjust QUEUE_MAX_PENALTY to 50 and adjust
QUEUE_MIN_PENALTY to 15
If you use RealTime, the queue rules will be always reloaded on a module
reload, even if the underlying file did not change. With the option disabled,
the rules will only be reloaded if the file was modified.
Review: https://reviewboard.asterisk.org/r/3607/
ASTERISK-23823 #close
Reported by: Michael K
patches:
app_queue.c_realtime_trunk.patch uploaded by Michael K (License 6621)
git-svn-id: https://origsvn.digium.com/svn/asterisk/branches/13@420624 65c4cc65-6c06-0410-ace0-fbb531ad65f3
Diffstat (limited to 'UPGRADE.txt')
| -rw-r--r-- | UPGRADE.txt | 8 |
1 files changed, 8 insertions, 0 deletions
diff --git a/UPGRADE.txt b/UPGRADE.txt index 368d33d2e..cfd9a8446 100644 --- a/UPGRADE.txt +++ b/UPGRADE.txt @@ -66,6 +66,9 @@ ConfBridge: new method to achieve this functionality is by using sound_begin to play a sound to the conference when waitmarked users are moved into the conference. +Queue: + - Queue rules provided in queuerules.conf can no longer be named "general". + SetMusicOnHold: - The SetMusicOnHold dialplan application was deprecated and has been removed. Users of the application should use the CHANNEL function's musicclass @@ -342,6 +345,11 @@ Realtime Configuration: - A new set of Alembic scripts has been added for CDR tables. This will create a 'cdr' table with the default schema that Asterisk expects. + - A new upgrade script has been added that adds a 'queue_rules' table for + app_queue. Users of app_queue can store queue rules in a database. It is + important to note that app_queue only looks for this table on module load or + module reload; for more information, see the CHANGES file. + Resources: res_odbc: |