Ticket #5069 (new Feature Requests)

Opened 2 years ago

Last modified 2 years ago

cdr_mysql is now tagged as unsupported - use cdr_adaptive_odbc instead

Reported by: mickecarlsson Assigned to: tonyclewis
Priority: minor Milestone: 2.11
Component: FreePBX Distro Version: 2.9-branch
Keywords: Cc:
Confirmation: Unreviewed Distro:
Backend Engine: All Distro Ver:
Backend Ver: SVN Revision (if applicable):

Description

From https://issues.asterisk.org/view.php?id=19117 

Index: addons/cdr_mysql.c
===================================================================
--- addons/cdr_mysql.c	(revision 313649)
+++ addons/cdr_mysql.c	(working copy)
@@ -680,7 +680,7 @@
 	return ret;
 }
 
-AST_MODULE_INFO(ASTERISK_GPL_KEY, AST_MODFLAG_DEFAULT, "MySQL CDR Backend",
+AST_MODULE_INFO(ASTERISK_GPL_KEY, AST_MODFLAG_DEFAULT, "MySQL CDR Backend (UNSUPPORTED) -- see cdr_adaptive_odbc",

Change History

04/13/11 18:46:19 changed by p_lindheimer

  • owner set to tonyclewis.
  • component changed from Reports to FreePBX Distro.
  • milestone changed from Cut Line to 2.10.

07/27/11 15:32:31 changed by p_lindheimer

We need an "inventory" of what this affects? As far as Asterisk connections for CDR, we can move that to ODBC I assume and that is a distro configuration issue (e.g. it could be done today). Does that also affect MySQL dialplan commands as I believe at least the callerid lookup module uses some?

09/29/11 01:11:32 changed by mickecarlsson

  • milestone changed from 2.10 to 2.11.

See my notes here: http://www.freepbx.org/trac/wiki/cdr-with-odbc

We need to auto generate the /etc/asterisk/res_odbc.conf or use an empty res_odbc.conf with includes as that file contains a section uith username and password: 

[odbccdr]
enabled => yes
dsn => MySQL-asteriskcdrdb
username => <username for MySQL, same as in AMPDBUSER>
password => <password for MySQL same as in AMPDBPASS>

All other info is in the link above.

/etc/asterisk/cdr_adaptive_odbc.conf also needs to be included, but it is static: 

[first]
connection=odbccdr
table=cdr
alias start => calldate

OR, we could redo the cdr database to include the three new fields, start, answer, and end instead of calldate

That change requires CDR Reports to be rewritten to include those fields.

Deferring to 2.11, but our distro should begin to install odbc to be prepped for future use.