[asterisk-bugs] [Asterisk 0010751]: Duplicated and meaningless CDR Records

[noreply at bugs.digium.com]

A NOTE has been added to this issue. 
====================================================================== 
http://bugs.digium.com/view.php?id=10751 
====================================================================== 
Reported By:                easyec
Assigned To:                
====================================================================== 
Project:                    Asterisk
Issue ID:                   10751
Category:                   Applications/app_cdr
Reproducibility:            always
Severity:                   minor
Priority:                   normal
Status:                     new
Asterisk Version:           1.4.11  
SVN Branch (only for SVN checkouts, not tarball releases): N/A  
SVN Revision (number only!):  
Disclaimer on File?:        N/A 
Request Review:              
====================================================================== 
Date Submitted:             09-17-2007 21:29 CDT
Last Modified:              09-17-2007 22:04 CDT
====================================================================== 
Summary:                    Duplicated and meaningless CDR Records
Description: 
We found that there is a duplicated CDR for the failed / No Answer call. 
The called Number of the duplicated record is 's'. In the duplicated CDR
except the in coming channel, dial command and out going channel are
missing, all the other fields are identical to the other one. e.g.
"","34531619","s","from-pstn","34531619","Zap/94-1","","","","2007-09-14
09:47:42",,"2007-09-14 09:47:46",4,0,"NO
ANSWER","DOCUMENTATION","1189763262.7",""
"","34531619","8675583871124","from-pstn","34531619","Zap/5-1","Zap/94-1","Dial","Zap/r4/0508675583871124|10","2007-09-14
09:47:42",,"2007-09-14 09:47:46",4,0,"NO
ANSWER","DOCUMENTATION","1189763262.6",""

It is a bugs of asterisk 1.4.11?

Since we upgrade the asterisk from 1.2 to 1.4 we found this problem. 

I tried to reproduce the problem in a another machine. The OS is CentOS
5.0.
Kernel version is 2.6.18-8.1.8.el5. Asterisk Version is 1.4.11. Zaptel
version is 1.4.5.1. Libpri version is 1.4.1. I using the default configure
files from asterisk. However, the problem is still there.

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

---------------------------------------------------------------------- 
 samdell3 - 09-17-07 22:04  
---------------------------------------------------------------------- 
This is apparent in all 1.4.x versions, it caught me out too.

I understand it's 'just one of those things' due to a major CDR overhaul
that now support lots of new stuff in v1.4.

There is a simple workaround to completely fix the issue:

The two key rules are:
1) Make sure your dial() command is in a context or subroutine and NOT a
macro.
2) Within this subroutine or context, make the pattern match the number
you with to dial, and dont use 's' or anything else textual 
eg:  
[dial-context]
exten => _XXXXX.,1,Dial(SIP/${EXTEN},60)


If you need to execute the dial command from a macro, just do something
like:
Goto(dial-context,${EXTEN},priority) or GoSub equivalent if you need to
return back to your macro. 

Issue History 
Date Modified   Username       Field                    Change               
====================================================================== 
09-17-07 22:04  samdell3       Note Added: 0070713                          
======================================================================