[asterisk-bugs] [JIRA] (ASTERISK-25038) Queue log "EXITWITHTIMEOUT" does not always contain waiting time

[Rusty Newton (JIRA)]

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

Rusty Newton updated ASTERISK-25038:
------------------------------------

    Status: Open  (was: Triage)

> Queue log "EXITWITHTIMEOUT" does not always contain waiting time
> ----------------------------------------------------------------
>
>                 Key: ASTERISK-25038
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-25038
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: Applications/app_queue
>    Affects Versions: 11.17.1
>            Reporter: Etienne Lessard
>            Severity: Minor
>
> In app_queue, the EXITWITHTIMEOUT event is not always generated with the same parameters, i.e. sometimes the waiting time (3rd parameter) is missing.
> For example, in the queue_exec function, you have a first occurence of the EXITWITHTIMEOUT event, which looks like this:
> {noformat}
> 		if (qe.expire && (time(NULL) >= qe.expire)) {
> 			record_abandoned(&qe);
> 			reason = QUEUE_TIMEOUT;
> 			res = 0;
> 			ast_queue_log(args.queuename, ast_channel_uniqueid(chan),"NONE", "EXITWITHTIMEOUT", "%d|%d|%ld",
> 				qe.pos, qe.opos, (long) (time(NULL) - qe.start));
> 			break;
> 		}
> {noformat}
> and then a few lines lower, you have:
> {noformat}
> 		if (qe.expire && (time(NULL) >= qe.expire)) {
> 			record_abandoned(&qe);
> 			reason = QUEUE_TIMEOUT;
> 			res = 0;
> 			ast_queue_log(args.queuename, ast_channel_uniqueid(chan), "NONE", "EXITWITHTIMEOUT", "%d", qe.pos);
> 			break;
> 		}
> {noformat}
> i.e the first occurrence logs more information than the second, and there does not seem to be any particular reason for the second occurrence to log less information.



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