asterisk users - Jan 2004 - cdr_odbc not logging integers eg duration

I've just noticed that since swapping from the direct mysql cdr driver to 
cdr_odbc, the call duration (and anything else that's an integer) isn't 
logged - anyone else seen this and know the reason.  The cdr_odbc driver 
gives no error messages and records any string based fields correctly.

  Iain

Check your tables.  I logged everything as integer.

set verbose 10 and make a call and watch it.. then do reload and watch the
output.  It will unload and reload and you can check to make sure your
accually connetcing to the database.

bkw

On Sat, 17 Jan 2004, Iain Stevenson wrote:
>
> I've just noticed that since swapping from the direct mysql cdr driver
to
> cdr_odbc, the call duration (and anything else that's an integer)
isn't
> logged - anyone else seen this and know the reason.  The cdr_odbc driver
> gives no error messages and records any string based fields correctly.
>
>   Iain
>
>
> _______________________________________________
> Asterisk-Users mailing list
> Asterisk-Users@lists.digium.com
> http://lists.digium.com/mailman/listinfo/asterisk-users
> To UNSUBSCRIBE or update options visit:
>    http://lists.digium.com/mailman/listinfo/asterisk-users
>

Hi Iain,
> -----Original Message-----
> I've just noticed that since swapping from the direct mysql 
> cdr driver to cdr_odbc, the call duration (and anything else 
> that's an integer) isn't logged - anyone else seen this and 
> know the reason.  The cdr_odbc driver gives no error messages 
> and records any string based fields correctly.
Hm, my bet would be to check if the database definition is correct, this has
been modified slightly in the recent past. It works just fine for me (after
I figured out I needed that userfield appended)...

Florian

Hi!
> > I've just noticed that since swapping from the direct mysql 
> > cdr driver to cdr_odbc, the call duration (and anything else 
> > that's an integer) isn't logged - anyone else seen this and 
> > know the reason.  The cdr_odbc driver gives no error messages 
> > and records any string based fields correctly.
> 
> Hm, my bet would be to check if the database definition is correct, this
has
> been modified slightly in the recent past. It works just fine for me (after
> I figured out I needed that userfield appended)...
This could also be an issue with unixODBC or mySQL or their interplay 
with cdr_odbc, so better make sure to check all sides and maybe use the 
occasion to upgrade mySQL.

Cheers, Philipp