Comms CDR
From Taridium
(Difference between revisions)
| Line 1: | Line 1: | ||
| - | The comms CDR database collects call detail records for all calls placed to, or from the switches. It can either reside on the same physical server as the configuration database, or in a separate server/cluster. Per default comms will not collect unanswered calls. Please refer to the switch configuration cdr.conf file [general] section and set unanswered = yes if you want to collect these calls. Please be aware that this can cause a substantial increase in collected records. | + | The comms CDR database collects call detail records for all calls placed to, or from the switches. It can either reside on the same physical server as the configuration database, or in a separate server/cluster. Per default comms will not collect unanswered calls. Please refer to the switch configuration cdr.conf file [general] section and set unanswered = yes if you want to collect these calls. Please be aware that this can cause a substantial increase in collected records. See also [[Comms_Administrator_Interface#System Maintenance|CDR Maintenance]]. |
== CDR Fields == | == CDR Fields == | ||
Revision as of 15:16, 21 July 2016
The comms CDR database collects call detail records for all calls placed to, or from the switches. It can either reside on the same physical server as the configuration database, or in a separate server/cluster. Per default comms will not collect unanswered calls. Please refer to the switch configuration cdr.conf file [general] section and set unanswered = yes if you want to collect these calls. Please be aware that this can cause a substantial increase in collected records. See also CDR Maintenance.
CDR Fields
| Viewer Name | Database Field Name | Description |
|---|---|---|
| Date and Time | calldate | Start Date and Time of the call. |
| Caller ID | clid | The caller ID for the call. |
| Source | src | The source extension for the call. |
| dst | Destination | The destination of the call. |
| Context | dcontext | The destination context. Usually this would be 'inside', 'incoming' or 'outgoing'. |
| Source Channel | channel | The channel of the call. |
| Destination Channel | dstchannel | The destination channel of the call. |
| Application | lastapp | The last Asterisk application that was called. |
| Application Data | lastdata | The last Asterisk application data that was passed. |
| Duration | duration | The duration of the call including call set up. |
| Billing Duration | billsec | The billing duration of the call. Relevant duration for billing purposes. |
| Call Disposition | disposition | The call disposition: ANSWERED, NO ANSWER, CONGESTION, FAILED, BUSY. |
| (not shown) | amaflags | The AMA flags (unused in comms) |
| Account Code | accountcode | The account code for the call placing channel. Format: [enterprise ID]-[extension], [retail ID] or just [enterprise ID]. |
| Call ID | uniqueid | The unique ID for the call as generated by Asterisk. Will also include the switch ID. |
| User Field | userfield | The user field for the receiving channel - See also account code. Format: [enterprise ID]-[extension], [retail ID] or just [enterprise ID]. |
| Pilot/BTN | pilot | The comms Pilot/BTN as set by the application. |
| Comms Application | commsapp | The last comms application with parameters. |
| (not shown) | ID | The unique database ID for the call. |
| Peer IP | ipaddr | The IP address of the peer if available. |
Please refer to the latest installed cdr-db.sql schema file in /usr/local/comms/install for details on data types and indices.
