[asterisk-bugs] [JIRA] (ASTERISK-29357) Inconsistent info in QueueMemberStatus

[Asterisk Team (JIRA)]

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

Asterisk Team commented on ASTERISK-29357:
------------------------------------------

Thanks for creating a report! The issue has entered the triage process. That means the issue will wait in this status until a Bug Marshal has an opportunity to review the issue. Once the issue has been reviewed you will receive comments regarding the next steps towards resolution. Please note that log messages and other files should not be sent to the Sangoma Asterisk Team unless explicitly asked for. All files should be placed on this issue in a sanitized fashion as needed.

A good first step is for you to review the [Asterisk Issue Guidelines|https://wiki.asterisk.org/wiki/display/AST/Asterisk+Issue+Guidelines] if you haven't already. The guidelines detail what is expected from an Asterisk issue report.

Then, if you are submitting a patch, please review the [Patch Contribution Process|https://wiki.asterisk.org/wiki/display/AST/Patch+Contribution+Process].

Please note that once your issue enters an open state it has been accepted. As Asterisk is an open source project there is no guarantee or timeframe on when your issue will be looked into. If you need expedient resolution you will need to find and pay a suitable developer. Asking for an update on your issue will not yield any progress on it and will not result in a response. All updates are posted to the issue when they occur.

Please note that by submitting data, code, or documentation to Sangoma through JIRA, you accept the Terms of Use present at [https://www.asterisk.org/terms-of-use/|https://www.asterisk.org/terms-of-use/].

> Inconsistent info in QueueMemberStatus
> --------------------------------------
>
>                 Key: ASTERISK-29357
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-29357
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: Applications/app_queue
>    Affects Versions: 16.16.2, 17.9.3, 18.2.2
>            Reporter: Roman Pertsev
>         Attachments: 1st-ami-output-action-incall.txt, 1st-ami-output-after-call.txt, 1st-ami-output-dial-and-answer.txt, 1st-cli-output.PNG, 2nd-ami-output-action-after-call.txt, 2nd-cli-output-after-call.PNG, extensions.conf, queues.conf
>
>
> First problem:
> Header "InCall" in Event: QueueMemberStatus permanent show 0 when agent in call(1st-ami-output-dial-and-answer.txt). Asterisk cli output(1st-cli-output.PNG) and manually Action: QueueStatus (1st-ami-output-action-incall.txt) at this moment show correct info.
> Also this problem confirms in ASTERISK-29195
> Second problem:
> After call in queue 600, cli output(2nd-cli-output-after-call.PNG) and Action: QueueStatus (2nd-ami-output-action-after-call.txt) show us that agent 1000 in queue 600 has 1 call, and agent 1000 in queue 601 has 1 call, but agent 1000 has call only in queue 600!
> Documentation https://wiki.asterisk.org/wiki/display/AST/Asterisk+16+ManagerEvent_QueueMemberStatus says that header "CallsTaken" - The number of calls this queue member has serviced. This queue member - right, like "InCall" or "Paused" header, is not it?!



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