[asterisk-bugs] [JIRA] (ASTERISK-18416) [patch] Realtime queue agents unavailable via AMI before a call event.

[Asterisk Team (JIRA)]

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

Asterisk Team updated ASTERISK-18416:
-------------------------------------

    Target Release Version/s: 18.11.0

> [patch] Realtime queue agents unavailable via AMI before a call event.
> ----------------------------------------------------------------------
>
>                 Key: ASTERISK-18416
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-18416
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: Core/ManagerInterface
>    Affects Versions: 1.8.5.0, 13.18.4
>         Environment: RHEL 6.1 64 Bit, Queues stored realtime in MySQL via ODBC.
>            Reporter: kwk
>            Severity: Major
>              Labels: patch
>      Target Release: 16.25.0, 18.11.0
>
>         Attachments: app_queue_qstatus.patch
>
>
> Hi,
> I have an asterisk with realtime queues.
> When I fire an AMI "queuestatus" event for my realtime queue 1650, the AMI returns no info for the queue:
> {panel:title=Query AMI for Queue 1650|borderStyle=dashed| borderColor=#ccc| titleBGColor=#F7D6C1| bgColor=#FFFFCE}{color:blue}{noformat}action: queuestatus
> queues: 1650
> Response: Success
> Message: Queue status will follow
>  
> Event: QueueStatusComplete{noformat}{color}{panel}
> When I do {color:blue}{{queue show 1650}}{color} on the CLI and fire the same AMI event from before afterwards, I get the correct queue status.
> {panel:title=Query CLI for Queue 1650|borderStyle=dashed| borderColor=#ccc| titleBGColor=#F7D6C1| bgColor=#FFFFCE}{color:blue}{noformat}
> myhost*CLI> queue show 1650
> 1650 has 0 calls (max 1) in 'rrmemory' strategy (0s holdtime, 0s talktime), W:0, C:0, A:0, SL:0.0% within 0s
>    Members: 
>       SIP/1660 (realtime) (Not in use) has taken no calls yet
>       SIP/1660 (realtime) (Not in use) has taken no calls yet
>    No Callers
> {noformat}{color}{panel}
> {panel:title=Query AMI for Queue 1650 again|borderStyle=dashed| borderColor=#ccc| titleBGColor=#F7D6C1| bgColor=#FFFFCE}{color:blue}{noformat}
> action: queuestatus
> queues: 1650
> Response: Success
> Message: Queue status will follow
> Event: QueueParams
> Queue: 1650
> Max: 1
> Strategy: rrmemory
> Calls: 0
> Holdtime: 0
> TalkTime: 0
> Completed: 0
> Abandoned: 0
> ServiceLevel: 0
> ServicelevelPerf: 0.0
> Weight: 0
> Event: QueueMember
> Queue: 1650
> Name: SIP/1660
> Location: SIP/1660
> Membership: static
> Penalty: 0
> CallsTaken: 0
> LastCall: 0
> Status: 1
> Paused: 0
> Event: QueueMember
> Queue: 1650
> Name: SIP/1660
> Location: SIP/1660
> Membership: static
> Penalty: 0
> CallsTaken: 0
> LastCall: 0
> Status: 1
> Paused: 0
> Event: QueueStatusComplete
> {noformat}{color}{panel}
> I've discussed this issue on IRC with irroot and we found out that only a *call*-event in between two AMI requests will show the logged in agents. If an agent logs in a queue between two AMI requests, the AMI request {color:blue}{{action: queuestatus \n queues: 1650}}{color} still won't return the agents.
> I hope, there's a way to avoid a CLI query before the AMI produces useable answers to queue status requests. IMO it shouldn't be that the AMI reacts differently if the queues are stored in a realtime DB or statically.



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