Summary:	ASTERISK-15374: No CDR record for non-bridged outgoing calls
Reporter:	Jim Gottlieb (tokyojimu)	Labels:
Date Opened:	2009-12-28 22:57:00.000-0600	Date Closed:	2011-07-27 13:26:12
Priority:	Major	Regression?	No
Status:	Closed/Complete	Components:	CDR/General
Versions:		Frequency of Occurrence
Related Issues:
Environment:		Attachments:
Description:	An outgoing call (made by dropping a file in /var/spool/asterisk/outgoing) in 1.4 does not generate a CDR record for the call it connects the dialed party to, unless it uses the Dial() command.  This worked fine in 1.2. In other words, if we call someone, and then Dial() is used to connect them, we get CDR.  But if we call someone and then just play them a recording or an IVR tree, then no CDR is generated for the call. According to http://www.asterisk.org/node/48358 the generation of CDR in 1.4 was moved from the Hangup routine to ast_bridge_call, so I suspect the problem is that these calls are never being handled in ast_bridge_call.  I've tried using ResetCDR() and ForkCDR() with various options but still, no CDR is generated. I'm marking as 'major' since this results in customers not being billed, which puts us out of business :-). ****** ADDITIONAL INFORMATION ****** The call file looks like: Channel: Local/8585551234@outtrunk-collect Callerid: 8585551234 MaxRetries: 5 RetryTime: 20 WaitTime: 45 Context: collect-approval Extension: 16191000001 Priority: 1 And for purposes of testing, I sent that number to:  exten => _XXX,1,Answer()  exten => _XXX,n,Wait(5)  exten => _XXX,n,Hangup() If I use a Dial(), then CDR gets generated, but this isn't always appropriate, and kludging it by using a Dial(Local/${EXTEN}@default) did not work either as the resulting channel structure was messed up.
Comments:	By: Jim Gottlieb (tokyojimu) 2009-12-28 22:59:46.000-0600 Those exten lines were actually:  exten => _XX.,1,Answer()  exten => _XX.,n,Wait(5)  exten => _XX.,n,Hangup() so they _did_ match the extension 6191000001 By: Leif Madsen (lmadsen) 2010-01-04 11:06:30.000-0600 I'm acknowledging this, but I have a feeling this is a duplicate of another issue, but I can't seem to find it. Perhaps it has been closed. Can you try with the latest 1.4 branch from SVN to verify if it hasn't already been resolved? svn co http://svn.asterisk.org/svn/asterisk/branches/1.4 Thanks! By: Jim Gottlieb (tokyojimu) 2010-01-13 17:22:09.000-0600 I just tried with SVN checked out today (SVN-branch-1.4-r239838M) and the problem still exists. See also ASTERISK-15296 , which seems to be the same problem in the 1.6 branch.  Perhaps the same fix could be applied to 1.4. By: Jim Gottlieb (tokyojimu) 2010-01-13 17:26:13.000-0600 Another related bug is ASTERISK-968 . By: Russell Bryant (russell) 2011-07-27 13:25:39.374-0500 Per the Asterisk maintenance timeline page at http://www.asterisk.org/asterisk-versions maintenance (bug) support for the 1.4 and 1.6.x branches has ended. For continued maintenance support please move to the 1.8 branch which is a long term support (LTS) branch. For more information about branch support, please see https://wiki.asterisk.org/wiki/display/AST/Asterisk+Versions If this is still an issue, please open a new issue so it can be re-triaged appropriately. Thanks!