[asterisk-bugs] [Asterisk 0016797]: Originating a call from within the dialplan using Originate() does not result in a CDR

[Asterisk Bug Tracker]

A NOTE has been added to this issue. 
====================================================================== 
https://issues.asterisk.org/view.php?id=16797 
====================================================================== 
Reported By:                VarnishedOtter
Assigned To:                mnicholson
====================================================================== 
Project:                    Asterisk
Issue ID:                   16797
Category:                   Applications/General
Reproducibility:            always
Severity:                   major
Priority:                   normal
Status:                     assigned
Target Version:             1.6.2.8
Asterisk Version:           SVN 
JIRA:                       SWP-893 
Regression:                 No 
Reviewboard Link:            
SVN Branch (only for SVN checkouts, not tarball releases): 1.6.2 
SVN Revision (number only!): 245908 
Request Review:              
====================================================================== 
Date Submitted:             2010-02-10 00:57 CST
Last Modified:              2010-04-22 16:49 CDT
====================================================================== 
Summary:                    Originating a call from within the dialplan using
Originate() does not result in a CDR
Description: 
Originating a call from within the dialplan using Originate() does not
result in a CDR.

Here is the line I am using:

exten =>
_61XXXXXXXXX,53,Originate(SIP/${TRUNK}/${PREFIX}${PHONE},exten,${DESTCONTEXT},${PHONE},1);

The call goes out fine, but the CDR's dont get inserted into the DB.

I have tried this with 1.6.2.1, 1.6.2.2 and 1.6.2.3-rc2 from the SVN with
the same results.
======================================================================
Relationships       ID      Summary
----------------------------------------------------------------------
related to          0016222 [patch] CDR always set disposition as N...
related to          0014167 [patch] CDR does not get produced with ...
====================================================================== 

---------------------------------------------------------------------- 
 (0120784) svnbot (reporter) - 2010-04-22 16:49
 https://issues.asterisk.org/view.php?id=16797#c120784 
---------------------------------------------------------------------- 
Repository: asterisk
Revision: 258670

U   branches/1.4/main/cdr.c
U   branches/1.4/main/channel.c
U   branches/1.4/res/res_features.c

------------------------------------------------------------------------
r258670 | mnicholson | 2010-04-22 16:49:07 -0500 (Thu, 22 Apr 2010) | 11
lines

Fix broken CDR behavior.

This change allows a CDR record previously marked with disposition
ANSWERED to be set as BUSY or NO ANSWER.

Additionally this change partially reverts r235635 and does not set the
AST_CDR_FLAG_ORIGINATED flag on CDRs generated from ast_call().  To
preserve proper CDR behavior, the AST_CDR_FLAG_DIALED flag is now cleared
from all brige CDRs in ast_bridge_call().

(closes issue https://issues.asterisk.org/view.php?id=16797)
Reported by: VarnishedOtter
Tested by: mnicholson


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

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

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2010-04-22 16:49 svnbot         Checkin                                      
2010-04-22 16:49 svnbot         Note Added: 0120784                          
======================================================================