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

Asterisk Bug Tracker noreply at bugs.digium.com
Thu May 21 11:19:31 CDT 2009


A NOTE has been added to this issue. 
====================================================================== 
https://issues.asterisk.org/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:                     closed
Asterisk Version:           1.4.23 
Regression:                 No 
SVN Branch (only for SVN checkouts, not tarball releases): N/A 
SVN Revision (number only!):  
Request Review:              
Resolution:                 fixed
Fixed in Version:           
====================================================================== 
Date Submitted:             2009-03-25 05:37 CDT
Last Modified:              2009-05-21 11:19 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.

======================================================================
Relationships       ID      Summary
----------------------------------------------------------------------
related to          0013797 [patch] forkcdr() doesn't fork when cal...
====================================================================== 

---------------------------------------------------------------------- 
 (0105233) svnbot (reporter) - 2009-05-21 11:19
 https://issues.asterisk.org/view.php?id=14744#c105233 
---------------------------------------------------------------------- 
Repository: asterisk
Revision: 195894

_U  branches/1.6.0/
U   branches/1.6.0/include/asterisk/cdr.h
U   branches/1.6.0/main/cdr.c

------------------------------------------------------------------------
r195894 | mnicholson | 2009-05-21 11:19:29 -0500 (Thu, 21 May 2009) | 27
lines

Merged revisions 195882 via svnmerge from 
https://origsvn.digium.com/svn/asterisk/trunk

................
  r195882 | mnicholson | 2009-05-21 10:33:55 -0500 (Thu, 21 May 2009) | 20
lines
  
  Merged revisions 195881 via svnmerge from 
  https://origsvn.digium.com/svn/asterisk/branches/1.4
  
  ........
    r195881 | mnicholson | 2009-05-21 10:25:50 -0500 (Thu, 21 May 2009) |
13 lines
    
    This commit prevents cdr records with AST_CDR_FLAG_ANSLOCKED and
AST_CDR_FLAG_LOCKED from being updated in certain cases.
    
    This is accomplished by adding two functions to update the answer time
and disposition of calls that checks for the proper lock flags.  These
functions are used in the ast_bridge_call() function so that ForkCDR(A)
calls are respected.
    
    This patch also modifies the way ast_bridge_call() chooses the cdr
record to base the bridged_cdr on.  Previously the first unlocked cdr
record would be chosen, now instead the first cdr record is chosen and
forked cdr records are moved to the bridge_cdr.  This allows the original
cdr record and any forked cdr records to be properly updated with answer
and end times.
    
    (closes issue https://issues.asterisk.org/view.php?id=13797)
    Reported by: sh0t
    Tested by: sh0t
    
    (closes issue https://issues.asterisk.org/view.php?id=14744)
    Reported by: deepesh
  ........
................

------------------------------------------------------------------------

http://svn.digium.com/view/asterisk?view=rev&revision=195894 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2009-05-21 11:19 svnbot         Checkin                                      
2009-05-21 11:19 svnbot         Note Added: 0105233                          
======================================================================




More information about the asterisk-bugs mailing list