Call Detail Recording - Avaya Communication Manager Administrator's Manual

Call detail recording

Call Detail Recording (CDR) tracks call information on a per-trunk-group or station-to-station basis. For
every trunk group (including auxiliary trunks) that you administer for CDR reports, the system keeps
track of incoming, outgoing and tandem calls. You can also receive reports on temporary signaling
connections (TSCs) that involve trunks, and calls made using loudspeaker paging or code calling access.
Detailed description
You can also ask the system to report on ineffective call attempts. This may greatly increase the number
of calls recorded, but may also help you to increase security, since the system records call attempts that
are blocked because of insufficient calling privileges. This can also let you know if your users are not
able to make calls because all trunks are busy.
CDR tracks the audio service link calls that the switch uses for IP softphones set up as telecommuter. An
IP softphone may use one audio service link to make many short calls, but this appears as one long call on
the CDR reports.
Some call accounting systems do not support all of the information offered by CDR. See your Avaya
representative for details.
Account Code Dialing
Account Code Dialing allows certain calls to be associated with a particular project or account number.
To do this, users enter account codes when they place certain types of outgoing calls. These account
codes then appear on the call record, which you can use for accounting or billing purposes. Account code
dialing can be optional or mandatory (forced).
To associate an account code with a particular call, a user first dials the CDR account code access code
that you have established, then dials the desired account code. Next, the user dials the desired trunk
access code, or ARS access code, followed by the phone number.
The call record contains the account code, Trunk Access Code (TAC) or Automatic Route Selection
(ARS) access code, and the phone number. It does not contain the account code feature access code
(FAC).
Forced Entry of Account Codes
You can force your users to enter account codes on a system-wide, per-trunk or per-user basis, or on the
basis of the digit string the user dials. If you have this feature in place, the system rejects any call that
requires an account code where one is not supplied. To maximize system security, Avaya recommends
that you use Forced Entry of Account Codes (FEAC).
!
SECURITY ALERT:
Avaya Communication Manager does not verify account codes. As long as the user enters
a digit string of the appropriate length, the system allows the call. You must use
Authorization Codes if you want the system to determine if the user is authorized to make
the call.
Administrator's Guide for Avaya Communication Manager
November 2003
Feature Reference
Call detail recording
1433