----- Original Message ----- > From: "Support" <[email protected]> > To: "Asterisk Users Mailing List - Non-Commercial Discussion" > <[email protected]> > Sent: Thursday, August 9, 2012 1:54:21 AM > Subject: [asterisk-users] No CDR after upgrade (1.6.x -> 10.2.1) > > However, when I complete a call, I get this error message. (edited > down for space.) > > =================================================== > [Aug 8 19:58:44] WARNING[27764]: cdr_adaptive_odbc.c:686 odbc_log: > Column type -9 (field > 'diehlnet:cdr:disposition') is unsupported at this time. > [ 'diehlnet:cdr:dst_number') is unsupported at this time. > [Aug 8 19:58:44] WARNING[27764]: cdr_adaptive_odbc.c:686 odbc_log: > Column type -9 (field > 'diehlnet:cdr:src_codec') is unsupported at this time. > [Aug 8 19:58:44] WARNING[27764]: cdr_adaptive_odbc.c:686 odbc_log: > Column type -9 (field > 'diehlnet:cdr:dst_codec') is unsupported at this time. > [Aug 8 19:58:44] WARNING[27764]: cdr_adaptive_odbc.c:686 odbc_log: > Column type -9 (field 'diehlnet:cdr:trunk') is > unsupported at this time. > [Aug 8 19:58:44] WARNING[27764]: cdr_adaptive_odbc.c:686 odbc_log: > Column type -8 (field 'diehlnet:cdr:direction') > is unsupported at this time. > [Aug 8 19:58:44] > [INSERT INTO cdr > (duration,billsec,amaflags) VALUES (15,1,3)] > =================================================== > > This configuration worked before the upgrade, and I made sure to > compile in support for odbc cdr. > > Where else can I look?
A column value of -9 corresponds to column type SQL_WVARCHAR. By default, cdr_adaptive_odbc does not have support for Unicode columns. This had to be made optional, as ODBC libraries without Unicode support would interact poorly with portions of Asterisk when it assumed they had it. This should be detected automatically when Asterisk is configured. In your configure log, you should see something like the following: configure:28104: checking whether ODBC has support for Unicode types configure:28118: gcc -o conftest -g -O2 conftest.c -lm >&5 configure:28118: $? = 0 configure:28119: result: yes If the result here is no, then the ODBC library installed on the system Asterisk is running on was not detected to have support for Unicode types. You can either update your database schema to use the non-Unicode column types, or you could explore updating the ODBC library on your system. -- Matthew Jordan Digium, Inc. | Engineering Manager 445 Jan Davis Drive NW - Huntsville, AL 35806 - USA Check us out at: http://digium.com & http://asterisk.org -- _____________________________________________________________________ -- Bandwidth and Colocation Provided by http://www.api-digital.com -- New to Asterisk? Join us for a live introductory webinar every Thurs: http://www.asterisk.org/hello asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
