[asterisk-bugs] [JIRA] (ASTERISK-23823) [patch] Option to keep queuerules in realtime

[Michael K. (JIRA)]

    [ https://issues.asterisk.org/jira/browse/ASTERISK-23823?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=220961#comment-220961 ] 

Michael K. commented on ASTERISK-23823:
---------------------------------------

Still waiting for more reviews and approval on reviewboard:(

> [patch] Option to keep queuerules in realtime
> ---------------------------------------------
>
>                 Key: ASTERISK-23823
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-23823
>             Project: Asterisk
>          Issue Type: New Feature
>      Security Level: None
>          Components: Applications/app_queue
>    Affects Versions: SVN, 1.8.27.0
>            Reporter: Michael K.
>            Assignee: Matt Jordan
>            Severity: Minor
>         Attachments: app_queue.c_realtime_trunk.patch, app_queue.patch, queue_rules.sql
>
>
> This patch the ability (optional) to keep queuerules in realtime (rules would be loaded from file too)
> To test add to queuerules.conf :
> [general]
> realtime_rules = yes
> and add the realtime setting to extconfig.conf, for example in my case it's mysql and it looks like(will attach the .sql with create for table):
> queue_rules => mysql,asterisk,queue_rules
> in table as you can see you need to specify rule name and as in regular rules you can use relative setings for min and max (with "-" and "+", e.g. "+100")
> If you use realtime, the rules will be always reloaded (no cache option here), in other words it would delete all rules and re-add them from realtime and file. It's important to understand that with realtime on it would reload rules from file doesn't matter if file was or was not change.
> While with the option off it would act exactly like it was before patch (file would not be reloaded if it was not changed)



--
This message was sent by Atlassian JIRA
(v6.2#6252)