1.5 Administrator's Guide

  1. Home
  2. Docs
  3. 1.5 Administrator’s Guide
  4. Advanced Administration
  5. Telephone Management Systems (TMS)
  6. MAN 3000
  7. CDR format

CDR format

Records are streamed to MAN 3000 in the following format:

2 3 4 5 6 Column: 1 7 8 9
Type / Line Date Time Channel Source Type / Line Destination Bill Account Code

Table 49: Man3000 CDR format column headers

Field Content
Type / Line In the first column, a value of ‘I’ indicates that the record is for an incoming call. Any other value indicates the line number as defined in /etc/commagui/man3000.patterns for an outgoing call, or 9 in case the channel for the outgoing call was not pattern matched.
Type / Line In the second column, a value of ‘O’ indicates that the record is for an outbound call or 9 as the line number for an incoming call.

This process cannot correctly cater for all conditions, since the specific configuration details of any given system is variable. The outbound pattern match requires the following conditions in order to match a call as outbound:

•                      The call context must be “from-internal”

•                      The destination may not be a local extension

•                      The destination may not include “Local”

•                      It may not be a follow-me call or internal transfer.

If any of these conditions are not met, the call is flagged as internal.

Configuring a line number pattern match as described in section overrides the checks above and is the recommended way of ensuring that outbound calls are correctly classified.

Date The date of the start of call (including channel access / call setup / ringing) in the following format: ccyy/mm/dd
Time The time of the start of call (including channel access / call setup / ringing) in the following format: hh:mm:ss
Channel The channel from which the call originated in the inbound case or over which the call was placed in the outbound case. The values of this field will be pattern matched against the entries in /etc/commagui/man3000.patterns to determine the line number. If a match cannot be made, the line number is set to 9.
Source The originating number for the call. This can be the CID of the caller for an incoming call, or the CID (extension number) of the caller for an outgoing call.

Note: If the CID on the trunk used to place the outgoing call overrides the caller’s CID (e.g. extension number), the trunk’s override CID will be logged here.
Destination The destination number of the call in the outbound case, or the destination extension or service of the call in the inbound case.
Bill The billable duration of the call in seconds, excluding call setup (ring) time.
Account Code The account code assigned to the Com.X, FlexPath or extension (defaults to 0000).


Table 50: Man3000 CDR format field descriptions

Example CDR output:
9 I 2010/05/07 06:36:23 n/a  9905  *97  37  0000 
9 I 2010/05/07 06:56:11 n/a  9906  *98  13  0000
9 I 2010/05/07 06:56:38 n/a  9906  *98  3  0000 
9 I 2010/05/07 06:56:43 n/a  9906  *98  3  0000 
2 I 2010/05/07 06:59:15 SIP/9905­00000e9 9902  9905  18  0000 
9 I 2010/05/07 07:12:39 n/a  9930  *97  20  0000 
2 I 2010/05/07 07:20:46 SIP/9905­00000e9 9906  9905  5  0000 
2 I 2010/05/07 07:39:04 SIP/9901­00000e9 9921  9901  22  0000 
O 3 2010/05/07 07:39:52 mISDN/1­u3809  01154XXXXX   01266YYYYY   26  0000 
2 I 2010/05/07 07:40:23 SIP/9901­00000e9 9921  9901  12  0000 
3 I 2010/05/07 07:42:08 mISDN/1­u3813  01154XXXXX   02159ZZZZZ   37  0000 
3 I 2010/05/07 07:42:24 mISDN/2­u3818  01154XXXXX   01231AAAAA   25  0000