A common interface for exporting cdr and agent state data to other formats. Once a backend successfully saved the data, the gen_cdr_dumper would mark the data as exported for the specific node in mnesia. Once all nodes had flagged data as exported, it would be removed from mnesia.

Warning This module has been supplanted by OACD Hop, and thus has not been maintained. It is unlikely to work, and documented here primarily for historical reasons.

gen_cdr_dumper has 4 existing modes of operation, each with their own configuration options: Null, ODBC, CSV, and DETS.

This backend simply flagged the data as exported, basically disabling data exporting on the node. This is the default dumper.

Given a dsn to commit to, gen_cdr_dumper will attempt to store cdr and agent state data in a database. The SQL to create the expected tables can be found in misc/agent_states.sql and billing_records.sql.

Enabling trace enables debug output to the console.

Writes each cdr's and agent state records to a comma seperated values file.

Writes the exact structure mensia uses to a pair of DETS files. DETS is to mnesia what sqlite is to MySQL (or similar database server).

Each of the above options can be better implemented using a consumer for OACD Hop.

back to Configuring Modules