[asterisk-bugs] [JIRA] (ASTERISK-30410) Queues doesn't load members according to the configuration files

[Joshua C. Colp (JIRA)]

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

Joshua C. Colp edited comment on ASTERISK-30410 at 1/28/23 4:19 PM:
--------------------------------------------------------------------

Was the strategy changed and then Asterisk reloaded? Or was this fresh after an Asterisk start? (Using the given configuration for me the order is as given)


was (Author: jcolp):
Was the strategy changed and then Asterisk reloaded? Or was this from scratch? (Using the given configuration for me the order is as given)

> Queues doesn't load members according to the configuration files
> ----------------------------------------------------------------
>
>                 Key: ASTERISK-30410
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-30410
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: Applications/app_queue
>    Affects Versions: 18.16.0
>         Environment: OS: Debian 11
> Host: VirtualBox
> Architecture: x86_64
> CPU(s): 2
> Thread(s) per core: 1
> CPU Model: Intel(R) Core(TM) i7-10700 CPU @ 2.90GHz
>            Reporter: Jose Miguel Rivera
>            Assignee: Jose Miguel Rivera
>            Severity: Major
>
> Adding a queue with static members in a particular order using the linear strategy is ignored by Asterisk.
> Consider the configuration file below.
> {code:title=queues.conf|borderStyle=solid}
>  [Q520]
> setqueueentryvar=yes
> setqueuevar=yes
> timeoutpriority=app
> strategy=linear
> musicclass=default
> autofill=yes
> maxlen=0
> announce=
> wrapuptime=0
> announce-round-seconds=0
> announce-to-first-user=no
> announce-position=no
> relative-periodic-announce=no
> announce-holdtime=no
> autopause=no
> ringinuse=no
> timeoutrestart=no
> joinempty=yes
> timeout=15
> leavewhenempty=no
> retry=5
> member=>Local/302 at queue-call-to-agents/n,0,302,hint:302 at extension-hints,no
> member=>Local/100 at queue-call-to-agents/n,0,100,hint:100 at extension-hints,no
> queue-thankyou=
> {code}
> The Asterisk CLI shows the following result:
> {code:title=asterisk.cli|borderStyle=solid}
> ast-srv*CLI> queue show Q520
> Q520 has 0 calls (max unlimited) in 'linear' strategy (0s holdtime, 0s talktime), W:0, C:0, A:0, SL:0.0%, SL2:0.0% within 0s
>    Members: 
>       100 (Local/100 at queue-call-to-agents/n from hint:100 at extension-hints) (ringinuse disabled) (Not in use) has taken no calls yet (login was 92 secs ago)
>       302 (Local/302 at queue-call-to-agents/n from hint:302 at extension-hints) (ringinuse disabled) (Not in use) has taken no calls yet (login was 92 secs ago)
>    No Callers
> {code}
> As you can see, the order doesn't match the configuration file. But the main problem is that instead of dialing the first member defined in the configuration files, it dials the first member that appears in the Asterisk CLI.
> {code:title=asterisk.cli|borderStyle=solid}
> Executing [520 at cos-all-post:16] Queue("PJSIP/101-00000000", "Q520,,,,,,,,,") in new stack
>     -- Started music on hold, class 'default', on channel 'PJSIP/101-00000000'
>     -- Called Local/100 at queue-call-to-agents/n
> {code}



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