[asterisk-bugs] [Asterisk 0010668]: Incomplete CDR lock

[noreply at bugs.digium.com]

A NOTE has been added to this issue. 
====================================================================== 
http://bugs.digium.com/view.php?id=10668 
====================================================================== 
Reported By:                arkadia
Assigned To:                murf
====================================================================== 
Project:                    Asterisk
Issue ID:                   10668
Category:                   CDR/General
Reproducibility:            always
Severity:                   minor
Priority:                   normal
Status:                     assigned
Asterisk Version:           1.4.11  
SVN Branch (only for SVN checkouts, not tarball releases):  1.4  
SVN Revision (number only!):  
Disclaimer on File?:        N/A 
Request Review:              
====================================================================== 
Date Submitted:             09-07-2007 08:26 CDT
Last Modified:              06-02-2008 10:52 CDT
====================================================================== 
Summary:                    Incomplete CDR lock
Description: 
This is all about the meaning of AST_CDR_FLAG_LOCKED flag for CDR. 
I assume if CDR has this flag set then it wont be updated anymore by any
ast_cdr_ functions except cases when we force such update. ast_cdr_reset()
is example of function which allows to update locked CDRs if special flag
is given.

Based on this assumption I prepared the patch with such changes:

  ast_cdr_setvar() - not allowed to touch locked CDRs. I don't see any
cases when we need to change locked CDRs too. Not touching locked CDRs is
helpfull when ForkCDR being used and every new CDR may have different
custom variables.

  ast_cdr_answer() - don't change status of locked CDRs. That might be
helpfull when we have a chain of CDRs for one incoming call for which we
perform several tries to make outgoing call. Every outgoing attempt may
finish with its own completion code. And if the final attempt is 'answered'
then we have only one CDR with 'answered' status. All other will keep
connection error codes which is very helpful for error monitoring.

 ast_cdr_end() - don't change locked CDRs by the same reason as
ast_cdr_answer()

As there will be no changes in CDR after lock, app_forkcdr.c should be
updated to end original locked CDR.
Also it'll be great to make optional cdr reset in this application, but
thats a theme for another patch.
======================================================================
Relationships       ID      Summary
----------------------------------------------------------------------
related to          0012726 ForkCDR application fails to set duration
====================================================================== 

---------------------------------------------------------------------- 
 arkadia - 06-02-08 10:52  
---------------------------------------------------------------------- 
What I'm doing is explained in 0070379 note. I'm calling Dial several times
for different routes. I would like to collect dial status on every route.
So I need pairs: route+status. I don't want to collect it in one CDR.
So every Dial attempt is a call leg which overs with a CDR. ForkCDRext()
is used to create new CDR for every dial attempt. In my case all CDRs ends
at different time. 

I also understand the case when ForkCDR() maybe used and people needs CDRs
to be ended at the same time when the call is over. I'm saying we'll have
this behavior if we add a new flag AST_CDR_FLAG_FORKLOCK in ast_cdr_.. API.
Do you understand this idea? In ForkCDR() cdr will be marked with
AST_CDR_FLAG_FORKLOCK flag and it'll pass in section locked with
AST_CDR_FLAG_LOCKED.

E.g. ast_cdr_answer may look like this:

void ast_cdr_answer(struct ast_cdr *cdr)
{
        char *chan;
        while (cdr) {
             if (!ast_test_flag(cdr, AST_CDR_FLAG_LOCKED) ||       
ast_test_flag(cdr, AST_CDR_FLAG_FORKLOCK)) {
    ....do the job...
              }
              cdr = cdr->next;
        }
} 

Issue History 
Date Modified   Username       Field                    Change               
====================================================================== 
06-02-08 10:52  arkadia        Note Added: 0087655                          
======================================================================