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

noreply at bugs.digium.com noreply at bugs.digium.com
Mon Oct 29 16:35:13 CDT 2007


A NOTE has been added to this issue. 
====================================================================== 
http://bugs.digium.com/view.php?id=11070 
====================================================================== 
Reported By:                wvolz
Assigned To:                
====================================================================== 
Project:                    Asterisk
Issue ID:                   11070
Category:                   CDR/cdr_sqlite3_custom
Reproducibility:            always
Severity:                   major
Priority:                   normal
Status:                     new
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:              10-29-2007 16:35 CDT
====================================================================== 
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.
====================================================================== 

---------------------------------------------------------------------- 
 qwell - 10-29-07 16:35  
---------------------------------------------------------------------- 
I still suspect that this has something to do with quotes.  Do you have
quotes in your values column?  There appear to be an extra set on every one
of them.

And yes, it probably should account for quotes. 

Issue History 
Date Modified   Username       Field                    Change               
====================================================================== 
10-29-07 16:35  qwell          Note Added: 0072699                          
======================================================================




More information about the asterisk-bugs mailing list