[Asterisk-bugs] [Asterisk 0009279]: fields "start", "answer" and "end" are always empty.
noreply at bugs.diguim.com
noreply at bugs.diguim.com
Thu Jun 28 16:25:12 CDT 2007
email_notification_title_for_action_bug_reopened
======================================================================
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
======================================================================
Date Submitted: 03-14-2007 13:35 CDT
Last Modified: 06-28-2007 16:25 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.
======================================================================
----------------------------------------------------------------------
junky - 03-14-07 14:30
----------------------------------------------------------------------
Do you use any specific CDR stuff (like ForkCDR, etc) ?
----------------------------------------------------------------------
rottenroddy - 03-14-07 15:19
----------------------------------------------------------------------
I did some error checking with plpgsql and the fields are not sent as part
of the new record. ie. they are not in the SQL formatted by the client. Not
"empty" as I had first assumed.
Junky - no ForkCDR in dialplan just Set(CDR(accountcode)=123456),
Set(CDR(amaflags)="BILLING") and Set(CDR(userfield)=16048720002)
cdr_manager.conf; enable=yes
----------------------------------------------------------------------
junky - 03-14-07 15:21
----------------------------------------------------------------------
I will take a look at this, but if you could attach a quick dialplan
invoking this, that will be useful.
Also, do you use cdr batch mode?
----------------------------------------------------------------------
rottenroddy - 03-14-07 15:46
----------------------------------------------------------------------
CLI
CDR logging: enabled
CDR mode: simple
CDR registered backend: pgsql
for this run I had not loaded cdr_manager but it made no difference.
Thanks and have fun
----------------------------------------------------------------------
rottenroddy - 03-14-07 16:00
----------------------------------------------------------------------
Just a short update:
I had the field names wrong -"startdate", "answerdate" and "enddate" and
they are in the SQL insert but they are NULL as first reported.
----------------------------------------------------------------------
file - 06-27-07 17:31
----------------------------------------------------------------------
I'm closing this out, the schema for pgsql does not show those fields being
part of it.
----------------------------------------------------------------------
rottenroddy - 06-28-07 16:25
----------------------------------------------------------------------
Interesting rational; Are you saying that you are deciding not to support
the pgsql interface for the 1.4x product, or are you saying that the 1.4x
product does not have a standard interface across databases? Either way the
results diminish the Asterisk product. By not carrying these fields forward
you are cutting off all integration with realtime billing systems
utilizing pgsq. Oh, and by the by, why, if the schema does not contain the
fields, are they in the insert statement? I find your decision shortsighted
and inconsistent.
Issue History
Date Modified Username Field Change
======================================================================
03-14-07 13:35 rottenroddy New Issue
03-14-07 13:35 rottenroddy Issue Monitored: rottenroddy
03-14-07 13:35 rottenroddy Asterisk Version => 1.4.1
03-14-07 13:35 rottenroddy SVN Branch (only for SVN checkou => N/A
03-14-07 13:35 rottenroddy Disclaimer on File? => No
03-14-07 14:30 junky Note Added: 0060874
03-14-07 14:30 junky Status new => assigned
03-14-07 14:30 junky Assigned To => junky
03-14-07 15:19 rottenroddy Note Added: 0060876
03-14-07 15:21 junky Note Added: 0060877
03-14-07 15:42 rottenroddy File Added: modules.conf_cdrtest.txt
03-14-07 15:42 rottenroddy File Added: extensions.conf_cdrtest.txt
03-14-07 15:43 rottenroddy File Added: sip.conf_cdrtest.txt
03-14-07 15:46 rottenroddy Note Added: 0060879
03-14-07 16:00 rottenroddy Note Added: 0060880
06-14-07 08:39 Mithraen Issue Monitored: Mithraen
06-27-07 17:31 file Status assigned => resolved
06-27-07 17:31 file Resolution open => no change
required
06-27-07 17:31 file Note Added: 0065818
06-27-07 17:31 file Status resolved => closed
06-28-07 16:25 rottenroddy Status closed => feedback
06-28-07 16:25 rottenroddy Resolution no change required =>
reopened
06-28-07 16:25 rottenroddy Note Added: 0065871
======================================================================
More information about the Asterisk-bugs
mailing list