[asterisk-bugs] [JIRA] (ASTERISK-19196) Queue and local channels - Agent hunting order incorrect

[Joshua Colp (JIRA)]

     [ https://issues.asterisk.org/jira/browse/ASTERISK-19196?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Joshua Colp updated ASTERISK-19196:
-----------------------------------

    Affects Version/s: 13.18.4

> Queue and local channels - Agent hunting order incorrect
> --------------------------------------------------------
>
>                 Key: ASTERISK-19196
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-19196
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: Applications/app_queue
>    Affects Versions: 1.8.8.1, 13.18.4
>         Environment: Redhat Enterprise 4
> Dell Server
>            Reporter: Tuan Le
>         Attachments: extensions.txt, myDebugLog_issue_19196_3, queues-MISSDemo.conf
>
>
> 2 Agents statically entered using local channel -- See configs
> Queues.conf:
> [Demo]
> strategy=rrmemory 
> timeout=8
> autofill=no
> member => Local/1003 at Demo/n
> member => Local/1004 at Demo/n
> Extension dialing context
> [Demo]
> exten => _1004,1,Set(Group(...)
> exten => _1004,n,Dial(SIP/GWLB_OUT/11234567890)
> Asterisk 1.8.8.1 
> Sample of issue:
> -- Executing [1004 at Demo:3] Dial("Local/1004 at Demo....)
> -- Nobody picked up in 8000 ms
> -- Executing [1004 at Demo:3] Dial("Local/1004 at Demo....)
> -- Nobody picked up in 8000 ms
> -- Executing [1003 at Demo:3] Dial("Local/1003 at Demo....)
> When it is dialing the same agent the second time, Agent 1003 status shows Not In Use so its not because the agent is busy on another call. This is all in a controlled testing so there were no other random events confusing things.
> The dial() statement executes a macro which basicallyl returns a Macro_Exit() or set MACRO_RESULT=BUSY if the call gets answered.
> This scenario happens sporadically in our controlled test environment.  For maybe 20 test calls, it works flawlessly.  But then, the above happens for a short burst of calls and then everything goes back to working as expected.



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