[Home]

Summary:ASTERISK-10326: Duplicated and meaningless CDR Records
Reporter:Yves (easyec)Labels:
Date Opened:2007-09-17 21:29:38Date Closed:2007-11-02 16:40:24
Priority:MinorRegression?No
Status:Closed/CompleteComponents:Applications/app_cdr
Versions:Frequency of
Occurrence
Related
Issues:
Environment:Attachments:
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.


****** ADDITIONAL INFORMATION ******

Here is the cdr.conf configure
[general]

[csv]
usegmtime=no    ; log date/time in GMT.  Default is "no"
loguniqueid=yes  ; log uniqueid.  Default is "no
loguserfield=yes ; log user field.  Default is "no
Comments:By: Sam Deller (samdell3) 2007-09-17 22:04:15

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 supports 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 wish 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.


By: Yves (easyec) 2007-09-18 22:55:57

Thank You.

I did what you said.
I never use a macro or 's' or anything else textual.
But the problem is still there.
By: Andrey S Pankov (casper) 2007-09-20 05:02:28

Please try latest asterisk 1.4 branch from svn (see ASTERISK-1059659 for reference).
By: Jason Parker (jparker) 2007-11-02 16:40:12

Closing, due to lack of response.  Please reopen if this is still an issue after updating to revision 82262 or later.