[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-07 16:16 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).


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

---------------------------------------------------------------------- 
 (0093337) murf (administrator) - 2008-10-07 16:16
 http://bugs.digium.com/view.php?id=13637#c93337 
---------------------------------------------------------------------- 
Oh, atis, if only you knew what you were asking...!

I know why this is happening, I know roughly what to do, and I'm pondering
the fine points. This and app_dial should both have the same things done.

This is *the* simple case, and the CDR you want isn't printing, because on
no-answer, it's disposition is not updated. Updating the disposition and
letting it post is *not* the best/most complete option, tho, with
unanswered=yes set in your cdr.conf. A much more interesting case is if you
dial 2 or more phones. The CDR you do see, is the one attached to "peer"
(dialed) channel. Your userinfo is stored on the "chan"'s CDR, and that is
the one you'd rather probably see... but, in the case where multiple
channels are rung, and none answer, what is the 'destination channel"? 

So, maybe now is the time to "do it right", and output the unanswered
channel CDRs with the proper info attached, like src & dest channels, etc,
and userinfo, etc. 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2008-10-07 16:16 murf           Note Added: 0093337                          
======================================================================