[asterisk-bugs] [JIRA] (ASTERISK-28619) data mismatching in "queue show" CLI
Asterisk Team (JIRA)
noreply at issues.asterisk.org
Mon Dec 2 12:01:31 CST 2019
[ https://issues.asterisk.org/jira/browse/ASTERISK-28619?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=248926#comment-248926 ]
Asterisk Team commented on ASTERISK-28619:
------------------------------------------
Suspended due to lack of activity. This issue will be automatically re-opened if the reporter posts a comment. If you are not the reporter and would like this re-opened please create a new issue instead. If the new issue is related to this one a link will be created during the triage process. Further information on issue tracker usage can be found in the Asterisk Issue Guidlines [1].
[1] https://wiki.asterisk.org/wiki/display/AST/Asterisk+Issue+Guidelines
> data mismatching in "queue show" CLI
> -------------------------------------
>
> Key: ASTERISK-28619
> URL: https://issues.asterisk.org/jira/browse/ASTERISK-28619
> Project: Asterisk
> Issue Type: Bug
> Security Level: None
> Components: Applications/app_queue
> Affects Versions: 13.22.0
> Environment: VMware, 2vCore, 4vRAM, FreePBX 14
> Reporter: Germán Hurtado González
> Assignee: Germán Hurtado González
> Severity: Minor
>
> I reset queue stats at 7 am every day. I am monitoring queue stats during the day with "queue show" and queue_log.
> Answered call data has a mismatch.
> This issue happens in distinct queues every day.
> #asterisk -rx "queue show 9105"
> 9105 has 0 calls (max unlimited) in 'rrmemory' strategy (6s holdtime, 165s talktime), W:0, C:11, A:0, SL:100.0% within 60s
> #grep 9105 /var/log/asterisk/queue_log |grep ENTERQUEUE
> 1573803651|1573803635.131704|9105|NONE|ENTERQUEUE||4444461352|1
> 1573805085|1573805077.131855|9105|NONE|ENTERQUEUE||4444412268|1
> 1573806099|1573806092.131952|9105|NONE|ENTERQUEUE||4444446940|1
> 1573806174|1573806150.131967|9105|NONE|ENTERQUEUE||444444810|1
> 1573806868|1573806862.132022|9105|NONE|ENTERQUEUE||444448629|1
> 1573807953|1573807943.132140|9105|NONE|ENTERQUEUE||444444852|1
> 1573808517|1573808509.132206|9105|NONE|ENTERQUEUE||99999810|1
> 1573816452|1573816443.133180|9105|NONE|ENTERQUEUE||99999631|1
> 1573816517|1573816493.133185|9105|NONE|ENTERQUEUE||66662422|1
> #grep 9105 /var/log/asterisk/queue_log |grep CONNECT
> 1573803654|1573803635.131704|9105|SIP/8524|CONNECT|3|1573803651.131707|2
> 1573805089|1573805077.131855|9105|SIP/8514|CONNECT|4|1573805085.131856|4
> 1573806108|1573806092.131952|9105|SIP/8514|CONNECT|9|1573806099.131955|8
> 1573806184|1573806150.131967|9105|SIP/8525|CONNECT|10|1573806174.131972|9
> 1573806881|1573806862.132022|9105|SIP/8529|CONNECT|12|1573806874.132024|12
> 1573807955|1573807943.132140|9105|SIP/8524|CONNECT|2|1573807953.132141|2
> 1573808524|1573808509.132206|9105|SIP/8529|CONNECT|7|1573808517.132207|6
> 1573816459|1573816443.133180|9105|SIP/8524|CONNECT|7|1573816452.133182|7
> 1573816527|1573816493.133185|9105|SIP/8517|CONNECT|10|1573816517.133195|9
--
This message was sent by Atlassian JIRA
(v6.2#6252)
More information about the asterisk-bugs
mailing list