[asterisk-bugs] [Asterisk 0011321]: CDR(billsec) return 0 in some scenarios
noreply at bugs.digium.com
noreply at bugs.digium.com
Thu Dec 6 23:14:36 CST 2007
A NOTE has been added to this issue.
======================================================================
http://bugs.digium.com/view.php?id=11321
======================================================================
Reported By: IgorG
Assigned To: murf
======================================================================
Project: Asterisk
Issue ID: 11321
Category: PBX/pbx_config
Reproducibility: always
Severity: minor
Priority: normal
Status: assigned
Asterisk Version: SVN
SVN Branch (only for SVN checkouts, not tarball releases): trunk
SVN Revision (number only!): 89442
Disclaimer on File?: N/A
Request Review:
======================================================================
Date Submitted: 11-20-2007 04:59 CST
Last Modified: 12-06-2007 23:14 CST
======================================================================
Summary: CDR(billsec) return 0 in some scenarios
Description:
I have developing small system for user scheduled audio notification. Here
must be feature to repeat notification if user do not hear all message.
I have create call by call-file, one leg is dialplan context with
application Dial, second is AGI application, that read message from
database and call many time Playback app.
If user reach end of the message and AGI stopped, then all is normal: I
have billsec in variable. If user hangup first, then I have CDR(billsec)
equal to 0. In both cases right values posted to cdr.
======================================================================
----------------------------------------------------------------------
IgorG - 12-06-07 23:14
----------------------------------------------------------------------
This can be closed.
Latest trunk now works.
Issue History
Date Modified Username Field Change
======================================================================
12-06-07 23:14 IgorG Note Added: 0075003
======================================================================
More information about the asterisk-bugs
mailing list