Comms CDR
From Taridium
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.
CDR Fields
Field | Description |
---|---|
calldate | Start Date and Time of the call. |
clid | The caller ID for the call. |
src | The source extension for the call. |
dst | The destination of the call. |
dcontext | The destination context. Usually this would be 'inside', 'incoming' or 'outgoing'. |
channel | The channel of the call. |
dstchannel | The destination channel of the call. |
lastapp | The last Asterisk application that was called. |
lastdata | The last Asterisk application data that was passed. |
duration | The duration of the call including call set up. |
billsec | The billing duration of the call. Relevant duration for billing purposes. |
disposition | The call disposition: ANSWERED, NO ANSWER, CONGESTION, FAILED, BUSY. |
amaflags | The AMA flags (unused in comms)/ |
accountcode | The account code for the call placing channel. |
uniqueid | The unique ID for the call as generated by Asterisk. Will also include the switch ID. |
userfield | The user field for the receiving channel - See also account code. |
pilot | The comms Pilot/BTN as set by the application. |
commsapp | The last comms application with parameters. |
ID | The unique database ID for the call. |
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.