[asterisk-bugs] [Asterisk 0017599]: odbc can't insert specyfic record
Asterisk Bug Tracker
noreply at bugs.digium.com
Fri Jul 9 05:27:51 CDT 2010
A NOTE has been added to this issue.
======================================================================
https://issues.asterisk.org/view.php?id=17599
======================================================================
Reported By: jamicque
Assigned To: tilghman
======================================================================
Project: Asterisk
Issue ID: 17599
Category: CDR/cdr_odbc
Reproducibility: always
Severity: minor
Priority: normal
Status: assigned
Asterisk Version: 1.6.2.7
JIRA:
Regression: No
Reviewboard Link:
SVN Branch (only for SVN checkouts, not tarball releases): N/A
SVN Revision (number only!):
Request Review:
======================================================================
Date Submitted: 2010-07-07 11:47 CDT
Last Modified: 2010-07-09 05:27 CDT
======================================================================
Summary: odbc can't insert specyfic record
Description:
Below I paste a cdr record, which cannot be inserted via odbc (via
cdr_pgsql works).
The mentioned column "sip_proxy_host" exists, I don't know why there is an
"v_" before it in log.
I can insert the query to the database manually.
INSERT INTO cdr
(clid,src,dst,dcontext,channel,dstchannel,lastapp,lastdata,duration,billsec,disposition,amaflags,accountcode,uniqueid,userfield,number_a,number_b,src_interface,dst_interface,is_outbound,is_inbound,sip_proxy_host)
VALUES ('"Unknown"
<Unknown>','Unknown','boniek420','CALLEX','SIP/boniek420-00000041','SIP/boniek420-00000042','Dial','SIP/0693618338 at boniek420,45,wW',12,2,'ANSWERED',3,'boniek420','1278503202.119','UID:1278503202.119;','Unknown','+48693618338','SIP/testowy','SIP/testowy','f','f','sip.freeconet.pl')
======================================================================
----------------------------------------------------------------------
(0124374) jamicque (reporter) - 2010-07-09 05:27
https://issues.asterisk.org/view.php?id=17599#c124374
----------------------------------------------------------------------
I've done some research, and the problem occurred in cdr_pgsql also.
After analysing postgres logs I found it was a mistake in pgsql trigger
made on the table.
Ticket can be closed.
Issue History
Date Modified Username Field Change
======================================================================
2010-07-09 05:27 jamicque Note Added: 0124374
======================================================================
More information about the asterisk-bugs
mailing list