asterisk users - Jan 2004 - Odbc not logging

Hi,

Since a few days I'm experiencing this:

       > cdr_odbc: Connected to asterisk
       > cdr_odbc: Error in Query -1
       > cdr_odbc: Query FAILED Call not logged!
       > cdr_odbc: Connected to asterisk
       > cdr_odbc: Reconnecting to dsn asterisk
       > cdr_odbc: Trying Query again!
       > cdr_odbc: Error in Query -2
       > cdr_odbc: Query FAILED Call not logged!

It does this consitently, and I don't believe I modified any configuration
since I set it up. Can anyone enlighten me about what these error numbers
mean ?

Florian

Hi,
either turn  loguniqueid=off or add a field userfield to your sql table ( i
made it varchar 20 since i could not find any information ;) after the
loguniqueid field in the db.
michael 

-----Urspr?ngliche Nachricht-----
Von: asterisk-users-admin@lists.digium.com
[mailto:asterisk-users-admin@lists.digium.com] Im Auftrag von Florian
Overkamp
Gesendet: Freitag, 16. Januar 2004 09:49
An: asterisk-users@lists.digium.com
Betreff: [Asterisk-Users] Odbc not logging

Hi,

Since a few days I'm experiencing this:

       > cdr_odbc: Connected to asterisk
       > cdr_odbc: Error in Query -1
       > cdr_odbc: Query FAILED Call not logged!
       > cdr_odbc: Connected to asterisk
       > cdr_odbc: Reconnecting to dsn asterisk
       > cdr_odbc: Trying Query again!
       > cdr_odbc: Error in Query -2
       > cdr_odbc: Query FAILED Call not logged!

It does this consitently, and I don't believe I modified any configuration
since I set it up. Can anyone enlighten me about what these error numbers
mean ?

Florian


_______________________________________________
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!
> either turn  loguniqueid=off or add a field userfield to your sql table ( i
> made it varchar 20 since i could not find any information ;) after the
> loguniqueid field in the db.
That should be varchar 32 as far as I know.

I guess Florian's problem comes from upgrading which probably removed 
compile options to include the uniqueid field? At least I had this once 
for the cdr mysql support (don't use odbc yet).

Cheers, Philipp

Hi,
> -----Original Message-----
> either turn  loguniqueid=off or add a field userfield to your 
> sql table ( i made it varchar 20 since i could not find any 
> information ;) after the loguniqueid field in the db.
Yes!

mysql> alter table cdr add column userfield varchar(255) not null after
uniqueid;

Solved my issue.

Thanks

Florian