Call detail record
(expanded content) |
(added proviso about storing CDRs in the local database.) |
||
| Line 13: | Line 13: | ||
== TelcoBridges and Call detail records == | == TelcoBridges and Call detail records == | ||
TelcoBridges products support the generation of call detail records. Starting with [[Version 2.3|version 2.3]] of the [[Toolpack]] software environment, they also support the ability to export call detail records to a [[RADIUS]] server for accounting purposes. | TelcoBridges products support the generation of call detail records. Starting with [[Version 2.3|version 2.3]] of the [[Toolpack]] software environment, they also support the ability to export call detail records to a [[RADIUS]] server for accounting purposes. | ||
| + | |||
| + | |||
| + | '''NOTE:''' Specifically regarding the [[TMG3200]] and [[TMG800]] media gateways that feature internal storage and an onboard linux host, while call detail records can be stored locally, it is likely that the capacity of the internal hard drive will be insufficient for larger record volumes in the internal database. Instead, it is recommended that call detail records not be stored in the internal database at all, but that they instead be made available for export to an external RADIUS server and deleted locally following successful export. | ||
[[category:Glossary]] | [[category:Glossary]] | ||
Revision as of 15:07, 21 August 2009
A call detail record, or CDR for short, is a data record containing call-related information such as:
- Source NAP
- Destination NAP
- Calling #
- Called #
- Start time
- End Time
Call detail records are the foundation of subscriber billing activities by telecom service providers.
TelcoBridges and Call detail records
TelcoBridges products support the generation of call detail records. Starting with version 2.3 of the Toolpack software environment, they also support the ability to export call detail records to a RADIUS server for accounting purposes.
NOTE: Specifically regarding the TMG3200 and TMG800 media gateways that feature internal storage and an onboard linux host, while call detail records can be stored locally, it is likely that the capacity of the internal hard drive will be insufficient for larger record volumes in the internal database. Instead, it is recommended that call detail records not be stored in the internal database at all, but that they instead be made available for export to an external RADIUS server and deleted locally following successful export.
