Call Detail Records Modules - Revision history

Dana at 12:55, 11 January 2014

2014-01-11T12:55:58Z

Dana at 12:10, 11 January 2014

2014-01-11T12:10:30Z

Dana at 12:01, 11 January 2014

2014-01-11T12:01:57Z

Dana at 10:57, 11 January 2014

2014-01-11T10:57:18Z

Dana at 10:56, 11 January 2014

2014-01-11T10:56:55Z

Dana at 10:55, 11 January 2014

2014-01-11T10:55:34Z

Dana at 10:54, 11 January 2014

2014-01-11T10:54:47Z

Dana at 10:53, 11 January 2014

2014-01-11T10:53:43Z

Dana at 10:52, 11 January 2014

2014-01-11T10:52:50Z

Dana at 09:13, 11 January 2014

2014-01-11T09:13:55Z

@@ Line 99: / Line 99: @@
 ===Examples of writing CDRs to file===
-====Writing CDRs to file====
+====Writing CDRs per channel to file====
 * Make sure the [[CDR Build Module|cdrbuild]], and [[CDR File Module|cdrfile]] modules are loaded.
@@ Line 117: / Line 117: @@
-====Writing CDRs to file using combined====
+====Writing CDRs per call to file====
 * Make sure the cdrcombine, [[CDR Build Module|cdrbuild]], and [[CDR File Module|cdrfile]] modules are loaded.

@@ Line 1: / Line 1: @@
-There are 3 modules for CDR in Yate:
+There are 4 modules for CDR in Yate:
 * [[CDR_Build_Module|Cdrbuild]]
 * [[Register]]
 * [[CDR File Module|Cdrfile]]

@@ Line 96: / Line 96: @@
 '''See also'''
 * [[CDRcombine Module]]
 * [[CDR_Build_Module|CDRbuild Module]]

@@ Line 8: / Line 8: @@
 In YATE, if you wish to collect information with which you can then either bill customers or verify the bills you received from other service providers, you will need to configure YATE to record [http://en.wikipedia.org/wiki/Call_detail_record CDRs]. CDRs can be collected and output to either '''files''' using [[CDR File Module|cdrfile]], or inserted into a '''database''' using [[register]].
-'''Cdrbuild''' module generates CDRs per channel not like '''cdrcombine''' module that generates CDR per call. The cdrcombine module enables the writing of a single CDR entry per call instead of multiple entries, one for each call leg (one for the incoming leg and one or more for outgoing leg(s)). There is no configuration file for cdrcombine module. In order to use it set 'combine' option to true in '''cdrfile.conf''' or set '''cdr_combined''' in register module '''[call.cdr]''' section.
+'''Cdrbuild''' module generates CDRs per channel not like '''cdrcombine''' module that generates CDR per call. The cdrcombine module enables the writing of a single CDR entry per call instead of multiple entries, one for each call leg (one for the incoming leg and one or more for outgoing leg(s)). There is no configuration file for cdrcombine module. In order to use it set '''combine''' option to true in '''cdrfile.conf''' or set '''cdr_combined''' in register module '''[call.cdr]''' section.
 If you wish to store CDRs to a file, you will need to use '''cdrfile.conf'''. If you wish to store CDRs in a database you will need to edit either '''mysqldb.conf''' or '''pgsqldb.conf''', for either MySQL or PostgreSQL respectively and then '''register.conf''' to specify the queries to use.

@@ Line 8: / Line 8: @@
 In YATE, if you wish to collect information with which you can then either bill customers or verify the bills you received from other service providers, you will need to configure YATE to record [http://en.wikipedia.org/wiki/Call_detail_record CDRs]. CDRs can be collected and output to either '''files''' using [[CDR File Module|cdrfile]], or inserted into a '''database''' using [[register]].
-Cdrbuild module generates CDRs per channel not like cdrcombine module that generates CDR per call. The cdrcombine module enables the writing of a single CDR entry per call instead of multiple entries, one for each call leg (one for the incoming leg and one or more for outgoing leg(s)). There is no configuration file for cdrcombine module. In order to use it set '''combine''' option to true in '''cdrfile.conf''' or set '''cdr_combined'' in register module '''[call.cdr]''' section.
+'''Cdrbuild''' module generates CDRs per channel not like '''cdrcombine''' module that generates CDR per call. The cdrcombine module enables the writing of a single CDR entry per call instead of multiple entries, one for each call leg (one for the incoming leg and one or more for outgoing leg(s)). There is no configuration file for cdrcombine module. In order to use it set 'combine' option to true in '''cdrfile.conf''' or set '''cdr_combined''' in register module '''[call.cdr]''' section.
 If you wish to store CDRs to a file, you will need to use '''cdrfile.conf'''. If you wish to store CDRs in a database you will need to edit either '''mysqldb.conf''' or '''pgsqldb.conf''', for either MySQL or PostgreSQL respectively and then '''register.conf''' to specify the queries to use.

@@ Line 2: / Line 2: @@
 There are 3 modules for CDR in Yate:
 * [[Register]]
 * [[CDR File Module|Cdrfile]]
-In YATE, if you wish to collect information with which you can then either bill customers for or verify the bills you receive from other service providers.
+In YATE, if you wish to collect information with which you can then either bill customers or verify the bills you received from other service providers, you will need to configure YATE to record [http://en.wikipedia.org/wiki/Call_detail_record CDRs]. CDRs can be collected and output to either '''files''' using [[CDR File Module|cdrfile]], or inserted into a '''database''' using [[register]].
-You will need to configure YATE to record [http://en.wikipedia.org/wiki/Call_detail_record CDRs].
+'''Cdrbuild''' module generates CDRs per channel not like '''cdrcombine''' module that generates CDR per call. The cdrcombine module enables the writing of a single CDR entry per call instead of multiple entries, one for each call leg (one for the incoming leg and one or more for outgoing leg(s)). There is no configuration file for cdrcombine module. In order to use set '''combine''' option to true in '''cdrfile.conf''' or set '''cdr_combined'' in register module '''[call.cdr]''' section.
-CDRs can be collected and output to either '''files''', or inserted into a '''database'''.
+If you wish to store CDRs to a file, you will need to use '''cdrfile.conf'''. If you wish to store CDRs in a database you will need to edit either '''mysqldb.conf''' or '''pgsqldb.conf''', for either MySQL or PostgreSQL respectively and then '''register.conf''' to specify the queries to use.
-To enable the collection of CDRs, edit the configuration file '''cdrbuild.conf'''.
+=== Examples of writing CDRs to databases ===
-Specify the resolution you want (usec is recommended) and if you wish to override any fields.
+==== CDRs to PostgreSQL====
-−
-Initially, you should not need to override any. Wait until the need arises.
-−
-If you wish to store CDRs to a file, you will need to use '''cdrfile.conf'''. If you wish to store CDRs in a database you will need to edit either '''mysqldb.conf''' or '''pgsqldb.conf''', for either MySQL or Postgres respectively and then '''register.conf''' to specify the queries to use.
-−
-=== CDRs to databases ===
-−
-==== CDRs to Postgres====
 Once you have configured your database access details in [[PostgreSQL|pgsqldb.conf]] you will need to create a table to hold the CDRs.
-The recommend table to use is:
+The recommend table to store the CDRs is:
   CREATE TABLE cdr (
@@ Line 50: / Line 42: @@
 * id you can use within the database to assign a canonical sitewide CDR id to a call. If you have a single Yate instance, it may be hard to imagine why you would want this. But anyone running multiple YATEs should have it.
 * ended will be used by the queries in '''register.conf''' to mark when a CDR is complete.
 * billed you can use in your billing system to mark when a particular set of records has been either billed, or exported for billing.
 * billed_on is used to indicate what date a record was exported. Let's say you need to re-send CDRs for a particular date range, this can help you. Arguably billed_on makes billed redundant as a not null value is the same as billed = true; in practise I've found that querying against billed is faster than billed_on.
@@ Line 60: / Line 49: @@
 ==== CDRs to MySQL ====
 First you need to configure [[MySQL|mysqldb.conf]]. Then you create a database (or use an existing one) with one table.