[asterisk-bugs] [Asterisk 0011721]: When using ForkCDR Asterisk does not set the duration and billsec correcty
noreply at bugs.digium.com
noreply at bugs.digium.com
Wed Mar 19 07:04:53 CDT 2008
A NOTE has been added to this issue.
======================================================================
http://bugs.digium.com/view.php?id=11721
======================================================================
Reported By: voipgate
Assigned To: murf
======================================================================
Project: Asterisk
Issue ID: 11721
Category: Applications/app_forkcdr
Reproducibility: always
Severity: major
Priority: normal
Status: assigned
Asterisk Version: SVN
SVN Branch (only for SVN checkouts, not tarball releases): trunk
SVN Revision (number only!): 92122
Disclaimer on File?: N/A
Request Review:
======================================================================
Date Submitted: 01-09-2008 19:46 CST
Last Modified: 03-19-2008 07:04 CDT
======================================================================
Summary: When using ForkCDR Asterisk does not set the
duration and billsec correcty
Description:
When using ForkCDR and the call has not been answered, Asterisk creates 2
cdr's but one of them lacks the data for billsec and duration. The purpose
of a fork is to create 2 cdrs but with different variables (accountcode,
userfield) but the duration and bill seconds as well as the disposition
must be set.
======================================================================
----------------------------------------------------------------------
sh0t - 03-19-08 07:04
----------------------------------------------------------------------
I have the same problem with ForkCDR on 1.4.18 and 1.4.19-rc3
both values (billsec and duration) are zero after ForkCDR
It was working with 1.4.11
log from the cli:
[Mar 19 12:19:20] == Spawn extension (info800-2, s, 2) exited non-zero
on 'SIP/48525514155-b790c8a8'
[Mar 19 12:19:20] == End MixMonitor Recording SIP/48525514155-b790c8a8
[Mar 19 12:19:20] WARNING[3121]: cdr.c:993 post_cdr: CDR on channel
'SIP/48525514155-b790c8a8' lacks end
[Mar 19 12:19:20] NOTICE[3121]: cdr.c:437 ast_cdr_free: CDR on channel
'SIP/48525514155-b790c8a8' lacks end
Removing AST_CDR_FLAG_LOCKED as mentioned above makes my CDR record not to
fork (I have only one record per call)
Issue History
Date Modified Username Field Change
======================================================================
03-19-08 07:04 sh0t Note Added: 0084231
======================================================================
More information about the asterisk-bugs
mailing list