[asterisk-bugs] [Asterisk 0013637]: Missing userfield for Queue call with NO ANSWER

[Asterisk Bug Tracker]

A NOTE has been added to this issue. 
====================================================================== 
http://bugs.digium.com/view.php?id=13637 
====================================================================== 
Reported By:                atis
Assigned To:                murf
====================================================================== 
Project:                    Asterisk
Issue ID:                   13637
Category:                   CDR/General
Reproducibility:            always
Severity:                   major
Priority:                   normal
Status:                     assigned
Asterisk Version:           1.6.0 
SVN Branch (only for SVN checkouts, not tarball releases): N/A 
SVN Revision (number only!):  
Disclaimer on File?:        N/A 
Request Review:              
====================================================================== 
Date Submitted:             2008-10-07 09:42 CDT
Last Modified:              2008-10-08 14:31 CDT
====================================================================== 
Summary:                    Missing userfield for Queue call with NO ANSWER
Description: 
Sample dialplan (attached) has two SIP devices: 

90023 -> Queue(22901) -> 90132

If 90023 hangs up, queue cancels call and resulting CDR is missing
userfield (set before entering queue).


====================================================================== 

---------------------------------------------------------------------- 
 (0093380) atis (reporter) - 2008-10-08 14:31
 http://bugs.digium.com/view.php?id=13637#c93380 
---------------------------------------------------------------------- 
Ok, that explains what i observed in tests (i'll attach them shortly).

However if i set unanswered=yes, i would defineately want all the CDRs. In
case of multiple phones - CDR for each one. 

As for Queue, i already have my dialplan built over concept that queue
generates one long CDR for all the time caller spends there, if it's
answered - it shows dstchannel of bridged peer (but thanks to my userfield
magic i don't need it :). And each call from queue generates separate CDR
for ringing time, by having it's start time i can exactly calculate
whatever durations necessary.
Of course having one CDR for time in queue and another for ring and
conversation would be way better, but that would be too huge change for
1.6

About unanswered CDR's - i'm already used to have some unnecessary
duplicates since that major change in 1.4. I just trash them, and use
whatever i have with userfield set. Now in 1.6 i see that there are even
more of them (or perhaps i just didn't analyzed them in 1.4 as i had all i
need).

But, if i have unanswered=yes, i still wonder - why there's no CDR with
queue call. While testing, i noticed that putting ResetCDR(w) after Queue
writes it, so it's somewhere.. but this would require quite some
refactoring of dialplan, putting ResetCDR's in hangup extensions or after
queue calls. I wouold have to check disposition, as i don't want to do
ResetCDR after answered call. Sounds like a big headache. 

Please see my next post with test scenarios and some comments. 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2008-10-08 14:31 atis           Note Added: 0093380                          
======================================================================