[Home]

Summary:ASTERISK-26154: There is no Custom fields on second CDR
Reporter:cagdas kopuz (cagdas)Labels:
Date Opened:2016-06-27 02:26:16Date Closed:2020-01-14 11:14:04.000-0600
Priority:MinorRegression?
Status:Closed/CompleteComponents:CDR/cdr_adaptive_odbc
Versions:11.21.0 Frequency of
Occurrence
Related
Issues:
Environment:Attachments:
Description:I have two cdr tables at two different servers, and I use cdr_adaptive_odbc
Asterisk doesn't write Custom fields to second CDR table.

Custom fields = durum,tenant,direction,recording,aranan
{noformat}
(exten => s,n,Set(CDR(recording)=${FILENAME}))
{noformat}

{noformat}
cdr_adaptive_odbc.conf:
[cdr]
connection=veritabani
table=sanalsantralcdr

[cdr2]
connection=sniffer
table=asterisk_cdr
{noformat}
-----------------------------
Same call record's query log for each server:

cdr server query log:
{noformat}
INSERT INTO [*******].[dbo].[sanalsantralcdr]
([start],[answer],[clid],[src],[dst],[aranan],[dcontext],[channel],[dstchannel],[lastapp],[lastdata],[duration],[billsec],[disposition],[amaflags],[accountcode],[uniqueid],[linkedid],[linked_updated],[userfield],[durum],[tenant],[direction],[sequence],[recording])
VALUES
('2016-06-27 09:53:35.000','2016-06-27 09:53:39.000','"******" <****>','*****','s','****-queue-****','****-queue-*****','SIP/*****-00002923','Local/102@from-internal-*****-00001a04;1','Queue','*****-queue-****,itT,,,,','312','308','ANSWERED','3','NULL','1467010415.23715','1467010415.23715','NULL','******','***','in','26638','****-2016-06-27-09-53-39-*****-1467010415.23715.wav')
{noformat}

cdr2 server query log:
{noformat}
INSERT INTO asterisk_cdr (clid,src,dst,dcontext,channel,dstchannel,lastapp,lastdata,duration,billsec,disposition,amaflags,userfield,uniqueid,linkedid,sequence)
VALUES
('"******" <*******>','******','s','*******2200-queue-********','SIP/******-00002923','Local/102@from-internal-****-00001a04;1','Queue','*****-queue-*****,itT,,,,',312,308,'ANSWERED',3,'*****','1467010415.23715','1467010415.23715','26638')
{noformat}
Comments:By: Asterisk Team (asteriskteam) 2016-06-27 02:26:19.202-0500

Thanks for creating a report! The issue has entered the triage process. That means the issue will wait in this status until a Bug Marshal has an opportunity to review the issue. Once the issue has been reviewed you will receive comments regarding the next steps towards resolution.

A good first step is for you to review the [Asterisk Issue Guidelines|https://wiki.asterisk.org/wiki/display/AST/Asterisk+Issue+Guidelines] if you haven't already. The guidelines detail what is expected from an Asterisk issue report.

Then, if you are submitting a patch, please review the [Patch Contribution Process|https://wiki.asterisk.org/wiki/display/AST/Patch+Contribution+Process].
By: Joshua C. Colp (jcolp) 2016-06-27 12:42:35.379-0500

Please provide the schema (on BOTH servers), database in use, and the console output.
By: Asterisk Team (asteriskteam) 2016-07-12 12:00:01.203-0500

Suspended due to lack of activity. This issue will be automatically re-opened if the reporter posts a comment. If you are not the reporter and would like this re-opened please create a new issue instead. If the new issue is related to this one a link will be created during the triage process. Further information on issue tracker usage can be found in the Asterisk Issue Guidlines [1].

[1] https://wiki.asterisk.org/wiki/display/AST/Asterisk+Issue+Guidelines