[asterisk-bugs] [Asterisk 0011070]: cdr_sqlite3_custom backend error when logging to db

noreply at bugs.digium.com noreply at bugs.digium.com
Tue Dec 4 13:44:03 CST 2007


The following issue has been ASSIGNED. 
====================================================================== 
http://bugs.digium.com/view.php?id=11070 
====================================================================== 
Reported By:                wvolz
Assigned To:                qwell
====================================================================== 
Project:                    Asterisk
Issue ID:                   11070
Category:                   CDR/cdr_sqlite3_custom
Reproducibility:            always
Severity:                   major
Priority:                   normal
Status:                     assigned
Asterisk Version:            SVN 
SVN Branch (only for SVN checkouts, not tarball releases):  trunk 
SVN Revision (number only!): 86839 
Disclaimer on File?:        N/A 
Request Review:              
====================================================================== 
Date Submitted:             10-23-2007 15:24 CDT
Last Modified:              12-04-2007 13:44 CST
====================================================================== 
Summary:                    cdr_sqlite3_custom backend error when logging to db
Description: 
Every time the cdr_sqlite3_custom log function is called I see errors in my
messages log that look like the following:

[Oct 23 14:35:55] ERROR[4552]: cdr_sqlite3_custom.c:180 sqlite3_log:
cdr_sqlite3_custom: unrecognized token: "081d81d8". sentence: INSERT INTO
cdr (calldate, clid, dcontext, channel, dstchannel, lastapp, lastdata,
duration, billsec, disposition, amaflags, accountcode, uniqueid, userfield,
test) VALUES (''''2007-10-23 14:35:53'''',''''"Cisco 7960-1"
<1001>'''',''''localports'''',''''SIP/cisco-7960-1-081d81d8'''','''''''',''''VoiceMailMain'''','''''''',''''2'''',''''2'''',''''ANSWERED'''',''''DOCUMENTATION'''','''''''',''''1193171753.0'''','''''''','''''''').

I've gone back and changed the schema thinking that was related, but even
with the default settings and created schema I see this error. The other
sqlite backends work correctly.
====================================================================== 

Issue History 
Date Modified   Username       Field                    Change               
====================================================================== 
12-04-07 13:44  seanbright     Status                   ready for testing =>
assigned
12-04-07 13:44  seanbright     Assigned To               => qwell           
======================================================================




More information about the asterisk-bugs mailing list