[asterisk-bugs] [JIRA] (ASTERISK-27017) Linear queue retries as many agents as were skipped

Jared Hull (JIRA) noreply at issues.asterisk.org
Thu May 25 14:37:57 CDT 2017


Jared Hull created ASTERISK-27017:
-------------------------------------

             Summary: Linear queue retries as many agents as were skipped
                 Key: ASTERISK-27017
                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-27017
             Project: Asterisk
          Issue Type: Bug
      Security Level: None
          Components: Applications/app_queue
    Affects Versions: 13.15.0
            Reporter: Jared Hull


When using a linear queue, all agents are dialed in the order they are added to queues.conf. With the option 'n' added to the queue application, I would expect the queue to stop once it has reached the timeout of the last agent. It does this when all agents are (Not in use).

n - No retries on the timeout; will exit this application and go to the next step

Paused or unavailable agents (due to an unavailable contact status) will cause the queue to loop around to the first agent and ring as many agents as there were paused or unavailable before 'Exiting on time-out cycle'.

testbed*CLI> queue show
linearQ has 0 calls (max unlimited) in 'linear' strategy (0s holdtime, 0s talktime), W:0, C:0, A:0, SL:0.0% within 60s
   Members:
      PJSIP/109 (ringinuse enabled) (paused) (Not in use) has taken no calls yet
      PJSIP/100 (ringinuse enabled) (Unavailable) has taken no calls yet
      PJSIP/103 (ringinuse enabled) (Not in use) has taken no calls yet
      PJSIP/102 (ringinuse enabled) (Not in use) has taken no calls yet
   No Callers



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



More information about the asterisk-bugs mailing list