[asterisk-dev] Re: The Trouble with CDR's...!

[Rajkumar S]

For the case of queue:
A call to queue produces 2 entries, like this. (this is from 1.2.12)

""1006" <1006>","1006","1001","from-sip","Local/1001 at from-sip-ed64,2","SIP/1001-081ba610","Dial","SIP/1001||tL(60000:30000)","2006-12-21
12:43:47","2006-12-21 12:43:55","2006-12-21
12:43:55","8","0","ANSWERED","DOCUMENTATION","","1166685227.10","",""

""1006" <1006>","1006","900","from-sip","SIP/1006-081afd60","Agent/1001","Queue","Auth-Enq|t","2006-12-21
12:43:46","2006-12-21 12:43:55","2006-12-21
12:44:00","14","5","ANSWERED","DOCUMENTATION","","1166685226.8","agent-1001-1166685227-11.wav",""

and queue_log has these 2 entries:

1166685226|1166685226.8|Auth-Enq|NONE|ENTERQUEUE||1006
1166685235|1166685226.8|Auth-Enq|Agent/1001|CONNECT|9
1166685239|1166685226.8|Auth-Enq|Agent/1001|COMPLETEAGENT|9|4

Now, the unique_id of queue_log and second entry of the cdr are same
and they can be matched. But there is no way to connect the final
entry in the cdr and rest of the cdr entries for the same call.
(except putting it in an database and finding all calls between the
start and end time of the final entry, from the same extension.) If
the unique_id was same for all the log entries in cdr and queue_log it
is easy to correlate them.

my 2 paisa,
raj