[asterisk-bugs] [Asterisk 0016611]: CDR and ForkCDR write wrong data on hangup in AGI execution

[Asterisk Bug Tracker]

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 18:01 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.

====================================================================== 

---------------------------------------------------------------------- 
 (0116769) t-o (reporter) - 2010-01-15 18:01
 https://issues.asterisk.org/view.php?id=16611#c116769 
---------------------------------------------------------------------- 
I have now prepared a second test set, comprising of
misdn-2.conf, extensions-2.conf, typescript-2.txt
This examples uses the same AGI as the first.

Here you can see that in the case of normal termination of the AGI the
correct context (zv-ext), the correct caller id (02315315266) and the
correctly cut version of the extension (2292) gets logged, while in test
case 2, when the AGI is terminated by the user hanging up while "GET DATA"
is running, wrong context (default), and wrong caller id (2315600125) and
unmodified extension (906292292) gets logged.

Please do also note that the AGI debug shows that the AGI environment has
the correct data in both cases. 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2010-01-15 18:01 t-o            Note Added: 0116769                          
======================================================================