6 thoughts on - Error Writing CDR

• Can you post the output of “describe ;”? At least the first error message is probably related to a not so optimal primary key definition.

  jg

• Thanx for the reply.

  request follows…

  mysql> describe cdr ;
  +————-+————–+——+—–+———————+——-+
  | Field | Type | Null | Key | Default | Extra |
  +————-+————–+——+—–+———————+——-+
  | calldate | datetime | NO | PRI | 0000-00-00 00:00:00 | |
  | dst | varchar(80) | NO | PRI | NULL | |
  | accountcode | varchar(20) | NO | PRI | NULL | |
  | clid | varchar(80) | NO | | NULL | |
  | src | varchar(80) | NO | MUL | NULL | |
  | dcontext | varchar(80) | NO | | NULL | |
  | channel | varchar(80) | NO | | NULL | |
  | dstchannel | varchar(80) | NO | | NULL | |
  | lastapp | varchar(80) | NO | | NULL | |
  | duration | int(11) | NO | | 0 | |
  | billsec | int(11) | NO | | 0 | |
  | disposition | varchar(45) | NO | MUL | NULL | |
  | amaflags | int(11) | NO | | 0 | |
  | userfield | varchar(255) | NO | | NULL | |
  | lastdata | varchar(80) | NO | | NULL | |
  | uniqueid | varchar(32) | YES | MUL | NULL | |
  +————-+————–+——+—–+———————+——-+
  16 rows in set (0.00 sec)

  FYI this has been running smooth for years.

  This “problem” started a few days ago.

  Ethy

• Further informations.

  For all those registers in error I have two entries in the database.

  (Based on the uniqueid of these entries I inferred that these errors started last April 7th)

  echo ‘select calldate,dst,disposition,uniqueid from cdr where uniqueid like “%1429994989%”;’ | mysql -u xxx -pxxx xxx

  calldate dst disposition uniqueid
  0000-00-00 00:00:00 1140573129 ANSWERED 1429994989.1186
  2015-04-25 17:49:49 1140573129 ANSWERED 1429994989.1186

  Ethy

• Hi Ethy,

  why date and time are empty?

  At least date is used as a unique key and a unique key has to be unique. In other words, the same key can not exist twice like in your case.

  Check why there is no date and time anymore …

  Regards Guenther

  —–BEGIN PGP SIGNATURE—

• Or define your table with and independent primary key that gets added automatically:

  mysql> describe cdr;
  +——————+————–+——+—–+———————+—————-+
  | Field | Type | Null | Key | Default | Extra |
  +——————+————–+——+—–+———————+—————-+
  *| id | int(11) | NO | PRI | NULL | auto_increment |*
  | clid | varchar(80) | NO | | | |
  | src | varchar(80) | NO | MUL | | |
  | dst | varchar(80) | NO | | | |
  …
  | lastapp | varchar(80) | NO | | | |
  | lastdata | varchar(80) | NO | | | |
  | duration | int(11) | NO | | 0 | |
  | billsec | int(11) | NO | | 0 | |
  | disposition | varchar(45) | NO | | | |
  | start | datetime | NO | MUL | 0000-00-00 00:00:00 | |
  | answer | datetime | NO | | 0000-00-00 00:00:00 | |
  | end | datetime | NO | | 0000-00-00 00:00:00 | |
  | uniqueid | varchar(45) | NO | | | |
  …

  Just in case you get bogus records with offending primary keys due to some other problem, you would still have valid data base entries and you would be able to look at the pattern.

  jg

• Hi guys

  I maybe have encountered a bug or I am doing something very stupid.

  That is what happened: I disabled a connection I am playing around on res_odbc.conf and the problem stopped. Just did this, nothing else.

  By the beginning of this month I was trying to do a CDR extension to accommodate calls statistics. I did not touched the CDR as you can see by the “describe” above.

  I just follow some “stepping stones” at http://www.asteriskdocs.org/en/3rd_Edition/asterisk-book-html-chunk/installing_configuring_odbc.html and http://…/3rd_Edition/asterisk-book-html-chunk/database_storing-cdr.html to activate ODBC and then I created a “h” extension at the extensions.conf file to harvest some stats. No attributions at all (like Set(CDR(foo)