[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 16:29:34 CST 2010
A NOTE has been added to this issue.
======================================================================
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: SWP-731
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 16:29 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.
======================================================================
----------------------------------------------------------------------
(0116768) t-o (reporter) - 2010-01-15 16:29
https://issues.asterisk.org/view.php?id=16611#c116768
----------------------------------------------------------------------
Ok.
I tried to produce a set of config files as small as possible by removing
as many directives as possible.
Find the results attached:
typescript.txt contains console output
misdn.conf, extensions.conf and the AGI in agi2.agi
Notes:
- I was only able to produce this error in conjunction with calls arriving
via chan_misdn. But here the error occurs always.
- The test in typescript.txt comprises two calls. In
https://issues.asterisk.org/view.php?id=1 the AGI hangs up
and the Master.csv shows the (correct) context "von-ascotel". In
https://issues.asterisk.org/view.php?id=2 the
caller hangs up while the AGI is still playing the "tt-weasels", and in
this case the Master.csv shows the context "default". (See output of "tail"
at the end of "typescript.txt").
- If you activate the (now commented) "FORKCDR" in the AGI, this will also
produce the wrong context output.
- In my test scenario I currently do not have external phone lines
available, thus I cannot demonstrate the problem whith the missing "0" at
the beginning of the external phone numbers at the moment.
Issue History
Date Modified Username Field Change
======================================================================
2010-01-15 16:29 t-o Note Added: 0116768
======================================================================
More information about the asterisk-bugs
mailing list