mirror of
https://github.com/signalwire/freeswitch.git
synced 2026-11-16 22:38:38 +00:00
merge mod_cdr changes to trunk
git-svn-id: http://svn.freeswitch.org/svn/freeswitch/trunk@2188 d0543943-73ff-0310-b7d9-9358b9ac24b2
This commit is contained in:
1 parent
4395e55493
commit
8246f730fc
6 files changed
+119
-105
No files matched your search
@@ -49,7 +49,7 @@ Configuration: Section name: <pddcdr>
|
||||
|
||||
Class: MysqlCDR, located in mysqlcdr.h and mysqlcdr.cpp
|
||||
Description: This class logs the call detail record to a MySQL 4.1.x or greater database using prepared
|
||||
statements. This class is a little more complex than the prior two in that the fixed channel variables are treated as additional columns on the main freeswitchcdr database table for improved normalization of the database. As such, you need to specify the format of each fixed channel variable as well. If you do not specify, it will default to a varchar column type, and will not execute if the table schema does not match. Therefore it is very important to make sure that any fixed channel variables you log exist as columns on the table. The supplemental channel variables are stored in a separate table using a key / value pair linking to the callid of the call.
|
||||
statements. This class is a little more complex than the prior two in that the fixed channel variables are treated as additional columns on the main freeswitchcdr database table for improved normalization of the database. As such, you need to specify the format of each fixed channel variable as well. If you do not specify, it will default to a varchar column type, and will not execute if the table schema does not match. Therefore it is very important to make sure that any fixed channel variables you log exist as columns on the table. The supplemental channel variables are stored in a separate table using a key / value pair linking to the callid of the call. Recommended to use at least one other logger in conjuction with this one just to be on the safe side, as failover handling of errors to write to the db are not yet implemented, and therefore there is a risk of data loss if the database connection is lost entirely (it will be limited to only those records created at the time of the loss of connection) or some other fatal error is encountered.
|
||||
Configuration: Section: <mysqlcdr>
|
||||
<param name="hostname" value=""/> value is the hostname or IP of the MySQL server (required)
|
||||
<param name="username" value=""/> value is the username to connect to the MySQL server with (required)
|
||||
|
||||
Reference in new issue
Block a user