[Home]

Summary:ASTERISK-05898: queue_log is not complete for some actions
Reporter:Dov Bigio (dovb)Labels:
Date Opened:2005-12-23 10:55:50.000-0600Date Closed:2011-06-07 14:02:41
Priority:MajorRegression?No
Status:Closed/CompleteComponents:Core/NewFeature
Versions:Frequency of
Occurrence
Related
Issues:
Environment:Attachments:
Description:- queue_log should display call time from CONNECT to TRANSFER, on the TRANSFER entry.
- What is the meaning of the last EXITWITHKEY? The user was not in a queue any more... Isn't EXITWITHKEY and indication that the user quit a queue by dialing a number?


1135338340|1135338308.919319|cobranca|NONE|ENTERQUEUE||339
1135338343|1135338308.919319|cobranca|Agent/5440|CONNECT|3
1135338381|1135338308.919319|cobranca|Agent/5440|TRANSFER|235|default
1135338381|1135338308.919319|cobranca|NONE|EXITWITHKEY||1
Comments:By: Tilghman Lesher (tilghman) 2005-12-23 11:08:46.000-0600

Why does it need to display call time?  That can be calculated with the log, if you need it.  EXITWITHKEY would probably be better titled "EXITWITHEXTENSION", but this would break backwards compatibility if we were to change it.  Given that there's no functional problem with the log, there's no overriding reason to change it.
By: Dov Bigio (dovb) 2005-12-23 11:26:01.000-0600

It certainly can be calculated... but having this field would make things much easier... If you check action COMPLETEAGENT or COMPLETCALLER, such as the example I am including here, the 8 seconds the user waited on the queue are not only logged on the CONNECT entry, but are repeated on the COMPLETEAGENT entry.

It would really be easier to handle if TRANSFERs behavior was the same.


1135334019|1135333987.909608|cobranca|NONE|ENTERQUEUE||339
1135334027|1135333987.909608|cobranca|Agent/5450|CONNECT|8
1135334055|1135333987.909608|cobranca|Agent/5450|COMPLETEAGENT|8|28
By: Dov Bigio (dovb) 2005-12-23 11:29:44.000-0600

About EXITWITHKEY or EXITWITHEXTENSION, I agree... but my understanding is that it could happen between an ENTERQUEUE and a CONNECT. How can it happen after a TRANSFER, COMPLETEAGENT or COMPLETECALLER, as in the example I had put originally? Am I missing something? At least that's what one would understand from documentation on the wiki...
By: Tilghman Lesher (tilghman) 2005-12-23 11:37:19.000-0600

It happens after a transfer, because they're exiting the queue with a new extension.  Not sure why it would happen after any of the other events, though.

In terms of "it'd be nice if...", that's a feature request.
By: Olle Johansson (oej) 2006-01-04 12:46:18.000-0600

Closing this issue due to lack of activity.
By: Dov Bigio (dovb) 2006-01-04 12:49:34.000-0600

Does that mean that the feature request was rejected?
By: Olle Johansson (oej) 2006-01-04 13:02:52.000-0600

dovb: Feature requests are usually closed if there's no patch. The issue tracker is not really meant for handling feature requests, but we do keep them open for a short discussion, then put them to rest in the archives for programmers to check.

Please don't expect any activity if you don't get positive feedback or pay someone to produce a patch. Take this discussion to the -dev list to get more feedback, that's a proper forum for this kind of discussions.

Thank you.

/Olle