[asterisk-bugs] [Asterisk 0014167]: CDR does not get produced with .call files

Asterisk Bug Tracker noreply at bugs.digium.com
Sat Jan 24 10:29:08 CST 2009


A NOTE has been added to this issue. 
====================================================================== 
http://bugs.digium.com/view.php?id=14167 
====================================================================== 
Reported By:                jpt
Assigned To:                murf
====================================================================== 
Project:                    Asterisk
Issue ID:                   14167
Category:                   CDR/General
Reproducibility:            always
Severity:                   minor
Priority:                   normal
Status:                     feedback
Asterisk Version:           1.4.22 
Regression:                 No 
SVN Branch (only for SVN checkouts, not tarball releases): N/A 
SVN Revision (number only!):  
Request Review:              
====================================================================== 
Date Submitted:             2009-01-02 16:41 CST
Last Modified:              2009-01-24 10:29 CST
====================================================================== 
Summary:                    CDR does not get produced with .call files
Description: 
CDR is not being produced as csv or via cdr_mysql with .call files.  It
works fine with 1.4.21.2 (zaptel 1.4.12.1 and asterisk-addons 1.4.7) but
does not with 1.4.22 or 1.4.23-rc3 (with dahdi 2.1.0.2 and asterisk-addons
1.4.7)
====================================================================== 

---------------------------------------------------------------------- 
 (0098667) cbbs70a (reporter) - 2009-01-24 10:29
 http://bugs.digium.com/view.php?id=14167#c98667 
---------------------------------------------------------------------- 
This problem was first reported on a customer setup. Prior to this, the
setup ran without hitch for 6 months or more. By looking into the CDR's,
they stopped being recorded the day I upgraded Asterisk. That's how I found
it. By downgrading Asterisk on the customer setup, the problem was
resolved. I have reproduced this error first on my own setup. By
downgrading my own setup, the error was resolved. I tested that the calls
were completing by inserting my own phone number into both setups. If
necessary, I can put together a test setup and give others access to it. I
only wish that it's an error on my part, something simple, something that
exists only in my version of bizarro world. It's a very plain vanilla
Asterisk setup except for the Thirdlane GUI interface. Tell me what you
need me to do.
Regards;
FSD 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2009-01-24 10:29 cbbs70a        Note Added: 0098667                          
======================================================================




More information about the asterisk-bugs mailing list