[asterisk-bugs] [JIRA] (ASTERISK-22864) Queue agent order when changing to linear strategy not correct on reload

Scott Griepentrog (JIRA) noreply at issues.asterisk.org
Mon Nov 18 15:54:03 CST 2013


Scott Griepentrog created ASTERISK-22864:
--------------------------------------------

             Summary: Queue agent order when changing to linear strategy not correct on reload
                 Key: ASTERISK-22864
                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-22864
             Project: Asterisk
          Issue Type: Bug
      Security Level: None
          Components: Applications/app_queue
    Affects Versions: 1.8.24.0
            Reporter: Scott Griepentrog


Linear strategy requires that the in-memory list of agents matches the list provided in queue.conf.  However, starting Asterisk with random strategy, and then switching queue.conf to linear and reloading asterisk does not produce the correct order from queue show until Asterisk is restarted (core restart gracefully).

Sequence to reproduce:

1) Configure queue with 3 agents and random strategy:

{noformat}
[100]
announce-frequency=0
announce-holdtime=no
announce-position=no
autofill=yes
autopause=no
autopausedelay=0
eventmemberstatus=yes
eventwhencalled=yes
joinempty=yes
leavewhenempty=no
maxlen=0
memberdelay=0
penaltymemberslimit=0
periodic-announce-frequency=0
queue-callswaiting=silence/1
queue-thereare=silence/1
queue-youarenext=silence/1
reportholdtime=no
retry=5
ringinuse=yes
servicelevel=60
setinterfacevar=yes
strategy=random
timeout=15
timeoutpriority=app
timeoutrestart=no
weight=0
wrapuptime=0
member=Local/201 at from-queue/n,0,Test One,hint:201 at ext-local
member=Local/202 at from-queue/n,0,Test Two,hint:202 at ext-local
member=Local/203 at from-queue/n,0,Test Three,hint:203 at ext-local
{noformat}

2) Result of CLI "queue show 100" is:

{noformat}
100 has 0 calls (max unlimited) in 'random' strategy (0s holdtime, 0s talktime), W:0, C:0, A:0, SL:0.0% within 60s
   Members:
      Test Three (Local/203 at from-queue/n) (Invalid) has taken no calls yet
      Test Two (Local/202 at from-queue/n) (Invalid) has taken no calls yet
      Test One (Local/201 at from-queue/n) (Invalid) has taken no calls yet
{noformat}

3) reconfigure strategy to linear and issue CLI "core reload":

{noformat}
strategy=linear
{noformat}

4) Result of CLI "queue show 100" is:

{noformat}
100 has 0 calls (max unlimited) in 'linear' strategy (0s holdtime, 0s talktime), W:0, C:0, A:0, SL:0.0% within 60s
   Members:
      Test Three (Local/203 at from-queue/n) (Invalid) has taken no calls yet
      Test Two (Local/202 at from-queue/n) (Invalid) has taken no calls yet
      Test One (Local/201 at from-queue/n) (Invalid) has taken no calls yet
{noformat}

Note that the agent order is still reversed from queue.conf

5) Issue CLI "core restart gracefully" and result of CLI "queue show 100" is:

{noformat}
100 has 0 calls (max unlimited) in 'linear' strategy (0s holdtime, 0s talktime), W:0, C:0, A:0, SL:0.0% within 60s
   Members:
      Test One (Local/201 at from-queue/n) (Invalid) has taken no calls yet
      Test Two (Local/202 at from-queue/n) (Invalid) has taken no calls yet
      Test Three (Local/203 at from-queue/n) (Invalid) has taken no calls yet
{noformat}

Note that the agent order is now matching queue.conf

This has been tested with the same results on 1.8 and 11.


--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.asterisk.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira



More information about the asterisk-bugs mailing list