Hi all,
I just completed an upgrade from 1.6.2 to 10.2.1 and I've run into a few
issues.
The issue I'm trying to fix rght now is that after the upgrade, I no longer
get any
CDR's. I'm trying to log to a Mysql database via odbc.
When I do an odbc show all, it shows that it's connected. Likewise, when I
do a
cdr show status, it shows the adaptive ODBC backend registered:
cdr show status
Call Detail Record (CDR) settings
----------------------------------
Logging: Enabled
Mode: Simple
Log unanswered calls: No
* Registered Backends
-------------------
Adaptive ODBC
cdr-custom
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?
--
Take care and have fun,
Mike Diehl.
--
Mike Diehl.
Matthew Jordan
2012-Aug-09 13:19 UTC
[asterisk-users] No CDR after upgrade (1.6.x -> 10.2.1)
----- Original Message -----> From: "Support" <mdiehl at diehlnet.com> > To: "Asterisk Users Mailing List - Non-Commercial Discussion" <asterisk-users at lists.digium.com> > 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
Matthew Jordan
2012-Aug-09 17:33 UTC
[asterisk-users] No CDR after upgrade (1.6.x -> 10.2.1)
----- 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