[asterisk-bugs] [Asterisk 0016282]: Double CDR if unanswered call

[Asterisk Bug Tracker]

The following issue has been UPDATED. 
====================================================================== 
https://issues.asterisk.org/view.php?id=16282 
====================================================================== 
Reported By:                jamicque
Assigned To:                
====================================================================== 
Project:                    Asterisk
Issue ID:                   16282
Category:                   CDR/General
Reproducibility:            always
Severity:                   minor
Priority:                   normal
Status:                     closed
Asterisk Version:           1.6.0.18 
JIRA:                        
Regression:                 No 
Reviewboard Link:            
SVN Branch (only for SVN checkouts, not tarball releases): N/A 
SVN Revision (number only!):  
Request Review:              
Resolution:                 no change required
Fixed in Version:           
====================================================================== 
Date Submitted:             2009-11-19 04:10 CST
Last Modified:              2009-11-19 09:34 CST
====================================================================== 
Summary:                    Double CDR if unanswered call
Description: 
There is a bug in creating CDR's in unasnwered calls.
If the option in cdr.conf "unanswered" is set to "yes" and the call is
unanswered when the user is logged (registered) to asterisk there are 2
CDR's - normal one and one strange from s extension (?). In my dialplan
there is no S extensions except these to:
[ Context 'app_queue_gosub_virtual_context' created by 'app_queue' ]
  's' =>            1. NoOp()                                    
[app_queue]

[ Context 'app_dial_gosub_virtual_context' created by 'app_dial' ]
  's' =>            1. NoOp()                                    
[app_dial]

However if the user is not registered to Asterisk there is only one CDR
created (without s extension).

There is a log in attachment

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

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2009-11-19 09:34 lmadsen        Resolution               open => no change
required
======================================================================