[asterisk-bugs] [Asterisk 0014744]: ForkCDR creates 3 CDR's

[Asterisk Bug Tracker]

A NOTE has been added to this issue. 
====================================================================== 
http://bugs.digium.com/view.php?id=14744 
====================================================================== 
Reported By:                deepesh
Assigned To:                mnicholson
====================================================================== 
Project:                    Asterisk
Issue ID:                   14744
Category:                   Applications/app_forkcdr
Reproducibility:            always
Severity:                   minor
Priority:                   normal
Status:                     assigned
Asterisk Version:           1.4.23 
Regression:                 No 
SVN Branch (only for SVN checkouts, not tarball releases): N/A 
SVN Revision (number only!):  
Request Review:              
====================================================================== 
Date Submitted:             2009-03-25 05:37 CDT
Last Modified:              2009-03-29 07:26 CDT
====================================================================== 
Summary:                    ForkCDR creates 3 CDR's
Description: 
Hello,

After upgrading to asterisk 1.4.23.2 from asterisk 1.4.19.1, I am facing
problems with ForkCDR. While using ForkCDR I am getting three cdr's instead
of two. My dialplan is as follows.

[dialexten]
exten => 763,1,SetCDRUserField(764)
exten => 763,n,ForkCDR()
exten => 763,n,SetCDRUserField(763)
exten => 763,n,Dial(SIP/763)
exten => 763,n,Hangup

After exten 763 is answered it creates three cdrs.
The first cdr has userfield 763 and ANSWERED
Second cdr has userfield 764 and ANSWERED
Third cdr has userfield 763 and NO ANSWER

In the earlier version (1.4.19.1) only the first two cdrs used to be
created.

Thanks in advance.

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

---------------------------------------------------------------------- 
 (0102354) deepesh (reporter) - 2009-03-29 07:26
 http://bugs.digium.com/view.php?id=14744#c102354 
---------------------------------------------------------------------- 
I too use it for a similar application.
1. Incoming call comes to a context.
2. The call is answered (billsecs should start now).
3. ForkCDR
4. Dial another extension (billsecs should start when this extension
answers)

Thus I should be having 2 cdrs with different bill secs. But what I get is
2 cdrs with different bill secs. Billsecs for both cdrs start when the
extension answers. If the extension takes a few seconds to answer then I
lose that seconds in the first cdr (incoming call). 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2009-03-29 07:26 deepesh        Note Added: 0102354                          
======================================================================