ATT DEFINITY Communications System Generic 3 Instructions Manual

Call Detail Recording (CDR)
Issue  3   March 1996
3-387
If the originator is not optioned for intraswitch CDR,  but one or more 
parties brought into the c onference are, one record with Condition Code C 
is generated for each dialed intraswitch party.  For example, Station A 
calls Station B, which is optioned for intraswitch CDR.  Station A 
conferences Station C.  Station A d rops from the c all.  Station B or C drops 
from the call. One CDR record is output with condition code C for the A to 
B...

Feature Descriptions
3-388Issue  3   March 1996 
nHot Line Service
The stored number used on an outgoing or intraswitch Hot Line call is 
recorded by CDR the same as if it was manually dialed.
nIntercept Treatment
If an outgoing or tandem call is route d to Intercept Treatment, the numb er 
dialed by the calling party is recorded as the dialed number, and 
Condition Code F is record ed.
nIntercom — Automatic
Intercom calls can generate intraswitch CDR record s.
nIntercom — Dial
Intercom calls can...

Call Detail Recording (CDR)
Issue  3   March 1996
3-389
LDNs cannot be administered for intraswitch CDR. However, a call from 
an intraswitch optioned extension to a LDN will produce an intraswitch 
CDR.
nNight Service — Night Station
The extension number assigned to the attendants is record ed as the 
dialed number. For G3vsV1/G3sV1 and  G3iv1, the attendant extension 
number is always 0. For G3i-Global, G3rV1, G3V2, and  later releases, the 
attendant extension numb er is administrable (the default is...

Feature Descriptions
3-390Issue  3   March 1996 
When an outgoing call is queued for a trunk and is unsuccessful (the 
queue times out or the calling party d oes not answer the callback) an CDR 
record is not g enerated for the call.
nSecurity Violations Notification (SVN)
SVN calls will generate intraswitch CDR if the terminating extension is 
monitored. The originating extension for SVN c alls cannot be administered 
for intraswitch monitoring.
nService Observing
No CDR records will be generated for...

Call Detail Recording (CDR)
Issue  3   March 1996
3-391
generated, one for each ‘leg’ of the call. For example, station 1 to outgoing 
number and station 2 to the same outgoing number. The call duration is 
appropriately assigned for each ‘leg’.
Intra-switch CDR records are generated for each call to or from an 
intraswitch optioned extension.  For example, Station A, which is 
intraswitch optioned, calls Station B.  Station A then transfers the call to 
Station C.  When either Station B or C drops, two...

Feature Descriptions
3-392Issue  3   March 1996 
nWATS and 800 Service
Calls made on a WATS or 800 Service trunk g roup will be recorded, if CDR 
is administered for the trunk group.
Administration
CDR is administered by the System Manager. The command  is change 
system-parameters CDR for G3V2 a n d later releases. The following items can 
be administered.
System Parameters
nType of CDR output format to be used. The type of output format must  be 
assigned for both the primary and secondary output...

Call Detail Recording (CDR)
Issue  3   March 1996
3-393
outgoing trunks that are unavailable d ue to trunk usage allocation for ISDN 
Call-By-Call Service Selection trunks and incoming calls rejected by the 
switch due to NSF mismatch.
nThe number of trailing d i gits in the “ CDR Dialed Number”  field to be 
blanked on output for an outgoing call originating from a station with CDR 
Privacy enabled.
nWhether intraswitch CDR records will b e generated for internal calls.
nWhether call splitting is...

Feature Descriptions
3-394Issue  3   March 1996 
IXC Codes
nIXC access numbers
nName of IXC (optional)
Data Modules and Modems
One or both of the CDR output devices can be connected to a PDM, Trunk Data 
Module, or a Modem. The following items must be administered:
nFor G3vs/s/i, a netcon channel must be assigned using a ‘Data Module’ 
form and entering data-channel or netcon channel for the type. This 
channel provides a path for CDR data from the Switch Processing Element 
to the time-division bus.
If...

Call Detail Recording (CDR)
Issue  3   March 1996
3-395
Security
Call d etail records should be monitored daily for unusual calling patterns, long 
calls, international calls, calls outside of normal business hours, and other 
indications of toll fraud.  Call accounting systems such as the AT&T Hacker 
Tracker provide automatic monitoring for fraudulent calling patterns. 

Feature Descriptions
3-396Issue  3   March 1996 
Call Forwarding All Calls
Feature Availability
This feature is available with all Generic 3 releases. Call Forwarding Override and 
the List Call Forwarding command are only available with G3V4 and later 
releases.
Description
Allows all calls to an extension numb er to be forwarded to a selected internal 
extension number, external (off-premises) number, the attendant  group, or a 
specific attendant.  This feature is activated or d eactivated by dial a c...