ATT DEFINITY Communications System Generic 3 Instructions Manual

							Call Detail Recording (CDR)
Issue  3   March 1996
3-357
Table 3-40. CDR Data Format — Int-Direct
ASCII Character 
Position Data Field Description
01 Date of Month - (tens)
02 Date of Month - (units)
03 Month - (tens)
04 Month - (units)
05 Year  - (tens)
06 Year - (units)
07 Space
08 Time Hour - (tens)
09 Time Hour - (units)
10 Time Minute - (tens)
11 Time Minute - (units)
12 Space
13 Duration Hour
14 Duration Minute - (tens)
15 Duration Minute - (units)
16 Duration Minute - (tenths)
17 Space
18 Condition Code
19 Space
20-22 Access Code dialed
1
23-25 Access Code used1
26 Space
27-44 Dialed Number used
1,2
45 Space
46-50 Calling Number
1
51 Space
52-66 Account Code
1
67 Space 
						

							Feature Descriptions
3-358Issue  3   March 1996 
1. Data is right justified and padded with blanks (spaces).
2. 27-29 are blank
3. Data is right justified and padded with zeros
68-72 PPM Count1
73 Space
74-75 Incoming Circuit ID
3
76 Space
77-78 Outgoing Circuit ID
3
79 Carriage Return
80 Line Feed
Table 3-41. CDR Data Format — Int-ISDN
ASCII Character 
Position Data Field Description
01 Time - Hours (tens)
02 Time - Hours (units)
03 Time - Minutes (tens)
04 Time - Minutes (units)
05 Space
06 Duration - Hours (units)
07 Duration - Minutes (tens)
08 Duration - Minutes (units)
09 Duration - Minutes (tenths)
10 Space
11 Condition Code
Continued on next page
Table 3-40. CDR Data Format — Int-Direct
ASCII Character 
Position Data Field Description 
						

							Call Detail Recording (CDR)
Issue  3   March 1996
3-359
12 Space
13-16 Access Code dialed
1
17 Space
18-21 Access Code used
1
22 Space
23-37 Dialed Number
1
38 Space
39-48 Calling Number
1
49 Space
50-64 Account Code
1
65 Space
66-72 Authorization Cod e
1
73 Space
74 Line Feed
75 Space
76 FRL
77 Space
78 Incoming Cir ID (hundreds)
79 Incoming Cir ID (tens)
80 Incoming Cir ID (units)
81 Space
82 Outgoing Cir ID (hundreds)
83 Outgoing Cir ID (tens)
84 Outgoing Cir ID (units)
85 Space
86 Feature Flag
87 Space
88 Attendant Console (1st digit)
1
Table 3-41. CDR Data Format — Int-ISDN
ASCII Character 
Position Data Field Description
Continued on next page 
						

							Feature Descriptions
3-360Issue  3   March 1996 
89 Attendant Console (2nd digit)
90 Space
91 Inc Trk A cc Code (1st d i git)
1
92 Inc Trk A cc Code (2nd digit)
93 Inc Trk A cc Code (3rd digit)
94 Inc Trk A cc Code (4th d igit)
95 Space
96 Node Number (1st digit)
1
97 Node Number (2nd digit)
98 Space
99 INS (1st digit)
1
100 INS (2nd digit)
101 INS (3rd digit)
102 Space
103 IXC (1st digit)
1
104 IXC (2nd digit)
105 IXC (3rd digit)
106 IXC (4th digit)
107 Space
108 BCC
109 Space
110   MA-UUI
111 Space
112 Resource Flag
113 Space
114 Reserve d (1st digit)
1
115 Reserve d (2nd digit)
116 Reserve d (3rd  di git)
Table 3-41. CDR Data Format — Int-ISDN
ASCII Character 
Position Data Field Description
Continued on next page 
						

							Call Detail Recording (CDR)
Issue  3   March 1996
3-361
Call Detail Record Fields
The following list describes the CDR data collected for each call and the number 
of digits in each field. All information is right adjusted in the respective field, 
unless otherwise indicated.
— The CDR out put for intraswitch CDR record s contain only the time, 
duration, condition code, dialed number, calling number, the character 
‘‘W’’ for a Wideband call, the bandwidth values 1 through 31 for Bandwidth 
calls (only for Enhanced Unformatted, Enhanced Expanded, and 
customized formats), and optionally who disconnected first information 
(refer to the “ FRL”  field description) fields. The length of the field can be 
customized. For customized or customized formats, Vector Directory 
Number (VDN) is available for intraswitch calls.
— The field name for Customized (Variable) Record Formats for G3rV1, 
G3V2, and later releases are indicated for each field description.
1. Data is right justified and padded with blanks (spaces).
117 Reserved (4th digit)
118 Reserved (5th digit)
119 Reserved (6th digit)
120 Reserved (7th digit)/PPM (1st digit)
121 Reserved (8th digit)/PPM (2nd digit)
122 Reserved (9th digit)/PPM (3rd digit)
123 Reserved (10th d igit)/PPM (4th d igit)
124 Reserved (11th d igit)/PPM (5th d igit)
125-131 Space
132 Carriage return
133 Line Feed
134-136 Null
Table 3-41. CDR Data Format — Int-ISDN
ASCII Character 
Position Data Field Description
Continued on next page 
						

							Feature Descriptions
3-362Issue  3   March 1996 
nAccess Code Dialed (up to three or four digits [24-word formats ])
NOTE:
The field name for Customized CDR Record s for G3rV1, G3V2, and 
later releases is ‘‘code-dial’’; the default length = 4.
This field is used only for outgoing calls. This field can be the ARS access 
code, AAR access code, or the access code of a specific trunk group. 
This field does not exist in the ISDN 18-word record  formats. In G3r, this 
field is also used to record the X.25 Feature Ac cess Code of an outgoing 
X.25 addressed call. The field is labeled ‘‘access code dialed’’ in the 
record layouts.
Intra-switch CDR will not output this field.
nAccess Code Used (up to three or four d igits [24-word formats] )
NOTE:
The field name for Customized CDR Record s for G3rV1, G3V2, and 
later releases is ‘‘code-used.’’
This field is used only for outgoing calls and when the trunk group used is 
different than the access c o de dialed. It is not used when TAC is dialed. 
For exam ple, most customers use FAC for ARS. This field contains the 
access code of the actual trunk group that the call was routed over. When 
the dialed and used access code are the same, this field will be blank 
(unless one of the ISDN record formats is used with ISDN, Enhanced, 
TELE SE ER ,  LS U , o r  Printer Only). In this case, the field always shows the 
access code of the used trunk group, even if it is the same as the dialed 
access code.
nAccount Code (up to 15 digits)
NOTE:
The field name for Customized CDR Record s for G3rV1, G3V2, and 
later releases is ‘‘acct-code.’’
This field is optional b ut c an c ontain a number to associate call information 
with projects or account numb ers. Ac count Codes must be prefixed with 
an access code which is either a fixed digit or a series of digits. The 
access code is administrable on the ‘Feature Access Code’ form. On 
outgoing calls, the account code access code must be dialed before the 
trunk access code, AAR access code, or ARS code.  Information in this 
field is right adjusted. These account codes allow the System Manager to 
associate calling information with projects or account numbers. The 
access code is not recorded because it is not part of the CDR account 
code.
Four d i git IXCs will use one d i git of the 15-digit account code on the 
Enhanced LSU format. 
						

							Call Detail Recording (CDR)
Issue  3   March 1996
3-363
Account code dialing can be optional or mandatory (forced).  Forced 
account code entry is set on a per-COR basis or per system.  If the trunk 
group used for a call requires an account code and one is not dialed, the 
call is denied. Forced account code entry can also be assigned for all toll 
calls. Service calls, directory assistance calls, and WATS calls are 
excluded.
If the ISDN LSU 18-word format is used, a maximum of 12 account code 
digits may be output to the record.  If the account code is longer than 12 
digits, the least significant digits are d rop ped. If the Enhanced LSU format 
is used, only 11 digits can be used for account code output.
Intra-switch CDR will not output this field.
nAttendant Console (two d i gits) (24-Word Record Only)
NOTE:
The field name for Customized CDR Record s for G3rV1, G3V2, and 
later releases is ‘‘attd-console.’’
This field contains the attendant console number of the attendant that 
handled the call in a record that is marked as being attendant handled.
Intra-switch CDR will not output this field.
nAuthorization Code (seven digits)
NOTE:
The field name for Customized CDR Record s for G3rV1, G3V2, and 
later releases is ‘‘auth-code.’’
This field contains the four- to seven-d igit authorization c o de used to make 
the call. For non-ISDN and ISDN LSU formats, the authorization c o de is 
fewer than six digits in length. It is five for Enhanced LSU. On the 
59-character record, the authorization code is never recorded.
Intra-switch CDR will not output this field.
nBearer Capability Class (BCC) (one digit) (24-Word  Re cord Only)
NOTE:
The field name for Customized CDR Record s for G3rV1, G3V2, and 
later releases is ‘‘bcc.’’
This field contains the BCC for ISDN calls, identifying the type of an ISDN 
call.  It will distinguish between voice and different types of data. The BCC 
is a single digit. Either of the following d i gits may appear in this field.
— 0 = Voice Grade Data and Voice
— 1 =  Mode 1 (56 kb ps synchronous data)
— 2 = Mode 2 (less than 19.2 kbps synchronous or asynchronous 
data) 
						

							Feature Descriptions
3-364Issue  3   March 1996 
— 3 = Mode 3 (64 k b ps data for LAPD protocol)
— 4 = Mode 0 (64 k b ps data clear)
— w = Wideband
Intra-switch CDR only outputs a value in this field for Wideband 
calls only and, in this case, the value is ‘‘w.’’
nBandwidth (two digits)(24-word record  and customized record for G3V2 
and later releases only)
NOTE:
The field name for Customized CDR Record s for G3rV1, G3v2, and 
later releases is “bandwidth.”
— Used to capture the bandwidth of the wideband calls to support 
H0, H11, H12, and N x 64 kbps data rates, where 2 < = N 
						

							Call Detail Recording (CDR)
Issue  3   March 1996
3-365
If the Calling Number is related to SID/ANI, this field contains SID/ANI 
information; otherwise, this field contains TAC information. If an outgoing 
call type, this field will contain the calling extension. This field  is specified 
on the CDR customized record.
nCarriage Return (one character)
NOTE:
The field name for Customized CDR Record s for G3rV1, G3V2, and 
later releases is ‘‘return.’’
The ASCII carriage return character followed by a line feed is used to 
terminate CDR records.
nCondition Code (one character)
These c o des, reflect special events relating to the call. Condition c o des 
for the 59-character CDR record are d ifferent from the codes in Table 3-43 
but can be mapped to these codes as shown in Table 3-42:
Table 3-43 shows the actual condition codes.
Table 3-42. Condition Code Mapping
CONDITION CODE MAPPING FOR 59-CHARACTER RECORD
59-Character Condition Code Code from Table 3-43
A1
D4
E6
G7
H8
I9
LC
NE 
						

							Feature Descriptions
3-366Issue  3   March 1996 
Table 3-43. Condition Codes
 Condition Codes Description
0 Identifies an intraswitch call (a call that originates and terminates 
on the switch).
1 Identifies an attendant-handled call or an attendant-assisted call 
(except conference calls).
4 Identifies an extremely long call (10 hours or more) or an 
extremely high message count TSC (9999 messages or more). 
On a call exc eeding 10 hours, a call record with this condition 
code and a duration entry of 9 hours, 59 minutes, and 1 to 9 
tenths of a minute is produced after the first period.  A similar call 
record  with this condition code is produced after each 
succeeding 10-hour period.  When the c all d oes terminate, a final 
call record with a different condition code identifying the call type 
is produced.
6 Identifies calls that are not record ed because of resource 
exhaustion. A record with this condition code is only generated 
for calls that are routed to the attendant or calls that require CDR 
to overwrite records. This record includes the time and duration 
of the outage. Note:  This condition code applies to G3r V1 and 
V2 only.
7 Identifies calls served by the AAR or ARS Selection feature.
8 Identifies calls which have been serve d on a delayed basis via 
the Ringback Queuing feature.
9 Identifies an incoming or tandem call.
A Identifies an outgoing call.
B Identifies an adjunct-p laced outgoing call.
C Identifies a conference call.  For trunk CDR, a separate call 
record  with this condition code is produced for each incoming or 
outgoing trunk serving the conference connection.  The only 
voice terminal recorded for a conference call is the conference 
call originator. For intraswitch CDR, if the originator is o ptioned 
for intra-switch, each time the originator dials a non-trunk party a 
separate call record is produced with this condition code. If the 
originator is not optioned for intraswitch CDR, a separate record  
with this condition code is produced for each intraswitch party 
d ialed.