[asterisk-users] No CDR after upgrade (1.6.x -> 10.2.1)

[Matthew Jordan]

----- Original Message -----
> From: "Mike Diehl" <mdiehl at dominion.diehlnet.com>
> To: asterisk-users at lists.digium.com
> Cc: "Matthew Jordan" <mjordan at digium.com>
> Sent: Thursday, August 9, 2012 12:08:01 PM
> Subject: Re: [asterisk-users] No CDR after upgrade (1.6.x -> 10.2.1)
> 
> On Thursday 09 August 2012 7:19:57 am Matthew Jordan wrote:
> 
> 
> Thank you for the detailed reply.
> However, my ODBC library has Unicode support:
> 
> =================================================
> configure:28090: checking whether ODBC has support for Unicode types
> configure:28104: gcc -o conftest -g -O2   conftest.c -lm  >&5
> configure:28104: $? = 0
> configure:28105: result: yes
> =================================================

Can you check your generated autoconfig.h?  It should have the following
in it:

#define HAVE_ODBC_WCHAR 1

If so, and if cdr_adaptive_odbc is re-compiled, it should enable support
for columns of type SQL_WCHAR, SQL_WVARCHAR, and SQL_WLONGVARCHAR.

> It almost sounds like I should turn off Unicode support in my
> Mysql....  I
> don't believe I'm storing anything that needs Unicode.

That would probably be easiest.

> Also, this database and configuration was working with Asterisk
> 1.6.2.  Was the
> ODBC/CDR system changed that much since then?
> 

The compile time checks for that particular column type are newer, yes.
The overall system was not changed much between 1.6.2 and 10, although
there have been some improvements.

--
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