[asterisk-bugs] [JIRA] (ASTERISK-27954) Queue Log "CONNECT" event incorrect "ringtime" value

[Kevin Harwell (JIRA)]

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

Kevin Harwell updated ASTERISK-27954:
-------------------------------------

    Status: Open  (was: Triage)

> Queue Log "CONNECT" event incorrect "ringtime" value
> ----------------------------------------------------
>
>                 Key: ASTERISK-27954
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-27954
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: Applications/app_queue
>    Affects Versions: 15.4.1, 13.22.0
>         Environment: Ubuntu 16.04 in docker container
>            Reporter: Dmitry Ramenev
>
> Queue has *30 s* config timeout and *300 s* app timeout. It's using "ringall" strategy. There are 2 agents assigned to queue, for example chris (penalty=1) and dmitry (penalty=2). 
> So, when queue having inbound call and when chris have been rejected this call after *17 s*, then the call will be received and answered by dmitry. For example he answering after *7 s*. We'll have in queue log: ENTERQUEUE => RINGNOANSWER(*17000*) => CONNECT(24, XXXX, *24*).
> It seems CONNECT event includes chris's ringtime / RINGNOANSWER time.
> But what if chris will be not available (paused)? Then dmitry first time rejects the call after *23 s* and after next call receiving - answering call. We'll have in queue log: ENTERQUEUE => RINGNOANSWER(*23000*) => CONNECT(34, XXXX, *4*).
> Why this time CONNECT event is not including dmitry's ringtime before reject? Should this event include all previous RINGNOANSWER time or it should include only last ring time?



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