[asterisk-bugs] [Asterisk 0016611]: CDR and ForkCDR write wrong data on hangup in AGI execution
Asterisk Bug Tracker
noreply at bugs.digium.com
Fri Jan 15 13:16:58 CST 2010
The following issue requires your FEEDBACK.
======================================================================
https://issues.asterisk.org/view.php?id=16611
======================================================================
Reported By: t-o
Assigned To:
======================================================================
Project: Asterisk
Issue ID: 16611
Category: Applications/app_cdr
Reproducibility: always
Severity: minor
Priority: normal
Status: feedback
Asterisk Version: 1.4.28
JIRA:
Regression: No
Reviewboard Link:
SVN Branch (only for SVN checkouts, not tarball releases): N/A
SVN Revision (number only!):
Request Review:
======================================================================
Date Submitted: 2010-01-15 07:23 CST
Last Modified: 2010-01-15 13:16 CST
======================================================================
Summary: CDR and ForkCDR write wrong data on hangup in AGI
execution
Description:
If an AGI execution is stopped because the caller hung up, the written CDR
will have partially wrong data, i.e. wrong context ("default" instead of
the actual value), wrong caller id (leading "0" which was added by
chan_misdn is missing), wrong extension (originally dialled value instead
of version that was modified during dial plan execution).
Also CDRs written by ForkCDR during AGI execution will have the same wrong
data as listed above.
On the other hand, if the AGI hangs up the channel itself, the resulting
CDR will be correct.
======================================================================
----------------------------------------------------------------------
(0116737) lmadsen (administrator) - 2010-01-15 13:16
https://issues.asterisk.org/view.php?id=16611#c116737
----------------------------------------------------------------------
Can you provide some console output and an example of how to reproduce
this? It seems pretty straight forward, but would be useful for a developer
to have all the information to reproduce this easily once they get to it.
Thanks!
Issue History
Date Modified Username Field Change
======================================================================
2010-01-15 13:16 lmadsen Note Added: 0116737
2010-01-15 13:16 lmadsen Status new => feedback
======================================================================
More information about the asterisk-bugs
mailing list