[Asterisk-bugs] [Asterisk 0009279]: fields "start", "answer" and "end" are always empty.

[noreply at bugs.digium.com]

A NOTE has been added to this issue. 
====================================================================== 
http://bugs.digium.com/view.php?id=9279 
====================================================================== 
Reported By:                rottenroddy
Assigned To:                junky
====================================================================== 
Project:                    Asterisk
Issue ID:                   9279
Category:                   CDR/cdr_pgsql
Reproducibility:            always
Severity:                   minor
Priority:                   normal
Status:                     feedback
Asterisk Version:           1.4.1 
SVN Branch (only for SVN checkouts, not tarball releases): N/A 
SVN Revision (number only!):  
Disclaimer on File?:        No 
Request Review:              
====================================================================== 
Date Submitted:             03-14-2007 13:35 CDT
Last Modified:              07-18-2007 15:53 CDT
====================================================================== 
Summary:                    fields "start", "answer" and "end" are always empty.
Description: 
CDR format and content are different between given interfaces and
documentation is inconsistent. Default CDR construction in cdr-csv is 18
fields and matches the documentation for the module(see below). For the
remaining non-configurable interfaces, mysql,mssql and pgsql, mssql is the
only documentation matching the standard format while the others do not.
mssql was not tested for functionality. cdr_pgsql.so should match the
output of the single standard cdr format for 1.4x. It does not. Fields
"start", "answer" and "end" are always empty.
====================================================================== 

---------------------------------------------------------------------- 
 Corydon76 - 07-18-07 15:53  
---------------------------------------------------------------------- 
We could also grab the code that cdr_adaptive_odbc uses in the pgsql odbc
driver and conditionally create those fields, if they exist in the table
schema.  This has the distinct advantage of it being completely backwards
compatible with the old schema, yet it will populate the new fields, if
they exist. 

Issue History 
Date Modified   Username       Field                    Change               
====================================================================== 
07-18-07 15:53  Corydon76      Note Added: 0067551                          
======================================================================