I’ve enabled CEL on a server and configured it to connect to our MySQL database via ODBC. All other data is working fine from the database, but CEL logging results in errors for every column in the CEL table.
Here’s an example of the output:
[Jun 15 08:40:23] WARNING[23435]: cel_odbc.c:701 odbc_log: Column type -9 (field 'pbx-connector:cel:peer') is unsupported at this time.
Table structure is as follows (taken from the mailing lists):
CREATE TABLEcel(idbigint(20) unsigned NOT NULL auto_increment,eventtypevarchar(255) collate utf8_unicode_ci NOT NULL,eventtimetimestamp NOT NULL default CURRENT_TIMESTAMP on update CURRENT_TIMESTAMP,userdeftypevarchar(255) collate utf8_unicode_ci NOT NULL,cid_namevarchar(255) collate utf8_unicode_ci NOT NULL,cid_numvarchar(255) collate utf8_unicode_ci NOT NULL,cid_anivarchar(255) collate utf8_unicode_ci NOT NULL,cid_rdnisvarchar(255) collate utf8_unicode_ci NOT NULL,cid_dnidvarchar(255) collate utf8_unicode_ci NOT NULL,extenvarchar(255) collate utf8_unicode_ci NOT NULL,contextvarchar(255) collate utf8_unicode_ci NOT NULL,channamevarchar(255) collate utf8_unicode_ci NOT NULL,appnamevarchar(255) collate utf8_unicode_ci NOT NULL,appdatavarchar(255) collate utf8_unicode_ci NOT NULL,amaflagsint(11) NOT NULL,accountcodevarchar(255) collate utf8_unicode_ci NOT NULL,peeraccountvarchar(255) collate utf8_unicode_ci NOT NULL,uniqueidvarchar(255) collate utf8_unicode_ci NOT NULL,linkedidvarchar(255) collate utf8_unicode_ci NOT NULL,userfieldvarchar(255) collate utf8_unicode_ci NOT NULL,peervarchar(255) collate utf8_unicode_ci NOT NULL, UNIQUE KEYid(id) ) ENGINE=InnoDB AUTO_INCREMENT=53 DEFAULT CHARSET=utf8 COLLATE=utf8_unicode_ci;
The only modification I did was increase the storage size on the columns, because our DBA thought that might be a quick fix.
Does anyone have any thoughts?
Thanks,
Sherwood McGowan