Feature Reference
Call detail recording
1434
Administrator’s Guide for Avaya Communication Manager
November 2003
You can assign FEAC in the following ways:
•
All calls marked for FEAC on the Toll Analysis table
If you activate this CDR system parameter, all users must dial an account code when the digits
dialed match a digit string with FEAC=y. This includes calls made by ARS or TAC.
•
Toll calls made by users with a specific COR
If FEAC is assigned to a specific COR, any telephone user assigned that COR must dial an
account code before making calls that are administered forced entry of account codes.
•
All calls made over a trunk group with FEAC in COR (TAC calls)
Users cannot access a trunk group that is assigned a COR with FEAC until they dial an account
code. If a call is routed via ARS, the system does not check for FEAC in the trunk group’s COR.
Therefore, if you want your users to enter account codes for ARS calls, you must administer this
in the Toll Analysis table.
If an account code is required for a call and the user does not enter one, the system responds with
intercept tone.
The following types of calls never require an account code:
•
Attendant originated call
•
Busy verification of a trunk by an attendant or telephone user
•
DCS (unless required by the trunk group’s COR)
•
PCOL
•
Remote access without barrier codes
•
Trunk-to-trunk connections
Call Splitting
Call splitting keeps track of calls where more than two parties are involved. These can be calls that are
transferred, conferenced, or where an attendant becomes involved. If you have call splitting activated and
any of these situations arise, CDR produces a separate record for each new party on the call.
You can administer call splitting for both incoming and outgoing trunks, and both can have attendant
calls recorded separately.
Incoming trunk call splitting
If incoming trunk call splitting is enabled, CDR starts a new record whenever an incoming trunk call is
conferenced or transferred. Whenever a user drops from the call or the call is successfully transferred,
CDR produces a record relevant to this user’s participation. These call records show the amount of time
each party was on the call, the incoming trunk access code, the dialed number and the condition code, as
well as the other fields specified in the record format.
For incoming trunk calls that are conferenced, CDR creates a new record whenever a new party comes on
the call. The duration field in these records shows how long each party participated on the call.
Conference calls produce records with duration fields that overlap. The duration of a transferred call
begins when the transferring party presses the
TRANSFER
button for the second time, so there is no
overlap.