Avaya Aura Communication Manager Feature Description and Implementation

Interactions for Call Detail Recording

Last Updated : Oct 06, 2023 |

Prolog information

Metadata

Keywords:

This section provides information about how the Call Detail Recording (CDR) feature interacts with other features on the system. Use this information to ensure that you receive the maximum benefits of Call Detail Recording in any feature configuration.

Abbreviated Dialing

When a user uses either Abbreviated Dialing or a Facility Busy Indicator button to place a call, all the outpulsed digits appear on the record.

Answer Detection

CDR starts recording call duration at the time that the call classifier detects the answer.

Answer Detection provides more accurate call records where tone detection is possible, and Network Answer Supervision is not received.

Attendant Console

If an attendant-assisted call uses an outgoing trunk, the system records the primary extension of the user who requests the attendant service as the calling number in the CDR record. The system records the primary extension of the user, even if the attendant dialed an outside number.

Condition code 1 indicates an attendant assisted the call.

If the attendant allows through dialing, the system records the primary extension of the user who dialed the number as the calling party. Condition code 1 indicates that an attendant extended a trunk access code (TAC). Condition code 7 indicates that an attendant extended a Feature Access Code (FAC).

If Incoming or Outgoing Attendant Call Record is enabled, the system produces a separate record for the attendant portion of incoming or outgoing calls that the attendant transfers.

With attendant-assisted calls that require an account code, enter the account code before the TAC.

If the attendant redirects an incoming call to an extension, the attendant can dial an account code before the attendant dials the extension number.

There are no intraswitch-optioned attendant calls. However, the system generates intraswitch records for an intraswitch-optioned extension call to an the attendant or for a call from the attendant to an intraswitch-optioned extension. In the case of an attendant-assisted call that involves an intraswitch extension, the system records the extension of the user who called the attendant as the dialing number. The system records the extension to which the attendant extended the call as the dialed number. In this case, the record has condition code 0.

Avaya Aura® Messaging

The following example describes CDR for remote Avaya Aura® Messaging in a QSIG or Avaya Aura® (SIP) network. If station A on node 1 forwards calls to Avaya Aura® Messaging on node 2, each switch produces a call record. The record from node 1 contains A as the dialed number. The record from node 2 contains Avaya Aura® Messaging as the dialed number.

If the calling number is on a different switch within the QSIP or SIP network, or the call comes in over ISDN, the system records the:

The actual calling number in the Calling Number field
The TAC of the trunk that brings the call into the local switch in the Incoming Trunk Access Code field of 24-word records

If the system uses an outgoing trunk when a user forwards, transfers, or conferences an incoming call, the system generates two separate CDR records. The system generates a record for incoming usage, and a record for outgoing trunk usage. The system records Avaya Aura® Messaging as the calling number in the outgoing trunk usage record

If Incoming Trunk Call Splitting is enabled, and Transfer out of Voice Mail is used, CDR generates two records. The first record contains Avaya Aura® Messaging, the second record contains the transferred-to party.

Authorization Codes

The system records authorization codes in CDR records as follows:

The account codes do not exceed 5 digits in length for non-ISDN formats and ISDN LSU formats
The account codes do not exceed 4 digits in length for enhanced LSU formats

The system does not record authorization codes in the 59-character CDR International Processing and International Direct records.

Automatic Selection of Direct Inward Dialing (DID) Numbers

If the system records an incoming call, the system records the DID extension number, not the room extension number.

Automatic Alternate Routing (AAR) and Automatic Route Selection (ARS)

For ARS calls, the system records the:

Calls made through ARS
Calling extension number
Facilities restriction level (FRL) of the calling extension
Called number
TAC of the trunk group that is used for the ARS call
Time of call completion
Call duration
Interexchange carrier (IXC) code, if any

The system does not generate a CDR record if CDR is suppressed for the trunk group that ARS uses.

If CDR is not suppressed, the system generates condition code 7. The system records the following information:

The ARS access code in the Access Coded Dialed field.
The TAC for the trunk group that the call used in the Access Code Used field.

If an AAR call is placed to a busy trunk group, and CDR is suppressed for that trunk group, the user hears the reorder tone, and the CDR record shows an ineffective call attempt.

If an ARS call is an attendant-assisted call, the CDR record shows the call with condition code 7 instead of condition code of 1. Condition code 7 indicates an ARS call. Condition code 1 indicates an attendant-assisted call. The system generates these condition codes, because CDR is not notified until after the trunk is seized and, in this case, the trunk is not seized until the user dials the number.

With the Forced Entry of Account Codes (FEAC) capability, the system does not use the class of service (COR) of the trunk group to determine if the user must enter an account code, if the system uses ARS to access the trunk.

Automatic Callback

When the Automatic Callback feature is used for an intraswitch call, the system does not generate a CDR record for the first call attempt, nor for the ringback. However, if intraswitch is enabled for either the calling user or the called user, the system generates a CDR record of the call, if the called user answers and completes the call.

Automatic Circuit Assurance (ACA)

ACA calls generate intraswitch CDR records if CDR monitors the terminating extension. The originating extension for ACA calls cannot be administered for intraswitch monitoring.

Automatic Wakeup

The system does not generate CDR intraswitch records for wake-up calls.

Bridged Call Appearance

The system does not record CDR information about the user who bridges onto a call. Instead, the system records the number that a user dialed in the Dialed Number field of the CDR record. The system records the duration of the call when the last party drops off the call.

If the user originates a call over a bridged appearance, the call record contains the calling number of the bridged appearance extension, and not the extension number of the original, calling station.

Busy Verification of Terminals and Trunks

Attendants and users do not need to enter an account code to make a busy verification.

Call-by-Call Service Selection

When the system successfully makes a call on a Call-by-Call Service Selection trunk, the system translates the network-specific facility that the system uses for the call into an ISDN network service (INS) number. The system records the INS number in the INS field of the CDR record.

If the system is unsuccessful in making a call on a Call-by-Call Service Selection trunk because of an administered trunk usage allocation plan, the system records the INS number in the INS field of the CDR Record with condition code E.

CallVisor Adjunct-Switch Application Interface (ASAI)

Call classification competes with CallVisor ASAI switch-classified calls for ports on the call classifier media module. Answer Detection sends a report of a connect event to ASAI.

Call Coverage

If the system does not route a call to an off-network coverage point, the system records the extension number that the calling user dials as the dialed number when a user answers an incoming call or an intraswitch call at a covering extension.

If the system routes a call to an off-network coverage point, the system records the number at the off-network location as the dialed number. The system records the extension that has the off-network location in its coverage path as the calling number.

Call Forwarding All Calls

If the system does not forward a call to an off-network location, the system records the number that the user dials as the dialed number.

If the system forwards a call to an off-network location, the system records the number of the off-network location as the dialed number. The system records the extension from which the call was forwarded as the calling number.

The system generates one CDR record for a forwarded intraswitch call. The dialed number in the record is the extension that the calling user dialed.

The system generates two CDR records for a trunk call to a station that the system forwards to another trunk. The first record shows an incoming trunk call to the station. The second record shows an outgoing trunk call from the station.

With the FEAC capability, the system cannot forward to a destination at which a user must enter an account code.

Call Park

When a user parks an incoming call or an intraswitch call, the system records the extension of the user as the dialed number in the CDR record. The system records the entire time that the incoming trunk is busy as the duration of the incoming call. The system records the time that the call started until the call ends as the call duration for an intraswitch call.

Call Pickup

The system records the number that the user dials as the dialed number when a member of a pickup group answers an incoming call or an intraswitch call.

Call Prompting

Call classification competes with Call Prompting for ports on the call classifier media module.

Call Vectoring

You can administer CDR so the system records the vector directory number (VDN) extension instead of the extension of the Hunt Group or of the member. If you administer CDR so the system records the VDN extension, you override the Calls to Hunt Group - Record option of CDR for incoming call vectoring calls.

Outgoing vector calls generate ordinary outgoing CDR records. The system records the originating extension as the calling number.

The system records the duration of the call from the time that answer supervision is returned for incoming calls to a VDN.

If the vector returns answer supervision, and the call does not go to another extension, the system records the VDN extension as the called number in the CDR record. The vector can return answer supervision with an announcement, collect, disconnect, or wait with music command.
If the call terminates to a hunt group, the system records the VDN, the hunt group extension, or the agent extension as the called number in the CDR record.
If the call terminates to a trunk, CDR generates an:
- Incoming record with the incoming TAC as the dialed number.
- Outgoing record with the incoming TAC as the calling number and the digits that are dialed through the vector step as the dialed number.
If you administer member extension for CDR, the system records an incoming call to the station if the system successfully routes a call to the station with the route-to command.

The system does not generate ineffective call attempt records for unsuccessful Call Vectoring route-to commands.

If a vector interacts with an extension or a group that has Call Forwarding All Calls active, normal Call Forwarding and CDR interactions apply.

Some calls look like intraswitch calls. Such calls include, for example, a call for a station that is administered for intraswitch CDR to a VDN, which becomes an outgoing call on an outgoing trunk. The system does not generate instraswitch CDR records for calls that look like intraswitch calls, but that are not intraswitch calls. The system generates a record with condition code A, which indicates outgoing.

Call Waiting Termination

The system starts the call duration timer when a user answers an incoming call.

Centralized Attendant Services (CAS)

The system records the extension of the user who originates a call as the originator of a call, if a CAS attendant extends the call to the user, and CDR is unassigned to the RLT trunk group.

The system records the RLT trunk as the originator of a call, if a CAS attendant extends the call to the user and CDR is assigned to the release-link trunk (RLT) trunk group.

The system does not generate a CDR record, if a CAS attendant answers a call but does not extend the call to a user.

CO Trunks

The system records all incoming and outgoing calls on a central office (CO) trunk group, if CDR is assigned to the trunk group, and CDR is administered to record incoming calls.

Conference

The system records a conference call for CDR, if either of the following conditions is met:

The call uses at least one trunk that is eligible for CDR, and has two or more parties
The call has at least one party that is optioned for intraswitch CDR.

The system records condition code C for each conference call CDR record.

The system generates a separate conference call CDR record for each outgoing trunk and each incoming trunk that serves the conference call. If you enable either, the system also generates a separate record for each internal party on the call.

For the outgoing portion of a conference call that involve multiple extensions, the system records the extension of the user who requests the outside dial tone to include another participant, as the calling party.

The system records the entire time that an incoming trunk or an outgoing trunk is used for a conference call, as the duration of the call.

The system generates a separate CDR record for each trunk that is used in a trunk-to-trunk transfer. If incoming trunk call splitting (ITCS) is active, the incoming trunk record shows the duration of the entire call.

The system starts a new CDR record whenever the originator of a conference call dials a nontrunk participant, if the conference call is optioned for intraswitch CDR. For example, station 1 is optioned for intraswitch CDR and calls station 2. Station 1 includes station 3 in the conference call. Station 1 drops from the call. Station 2 or station 3 drops from the call. The system generates two CDR records with condition code C. The system generates one record from station 1 to station 2, and another record from station 1 to station 3.

The system generates one record with condition code C for each dialed intraswitch conference participant, if any of the conference participants are optioned for intraswitch CDR. The system generates a record with condition code C, even if the originator of the conference is not optioned for intraswitch CDR. For example, station calls station 2, which is optioned for intraswitch CDR. Station 1 includes station 3 into the conference call. Station 1 drops from the call. Station 2 or station 3 drops from the call. The system generates one CDR record with condition code C from station 1 to station 2.

The system generates intraswitch conference call CDR records when both the calling party and the called party call drop from the call. The system records the call duration from the time that the called party answers the call until both the calling party and the called party drop from the call.

If an attendant originates a conference, the system generates CDR records only for the dialed numbers that correspond to any intraswitch optioned extensions.

Distributed Communications System DCS

The system does not pass station information throughout the DCS network for CDR records.

Direct inward dial (DID) trunks

If you administer the system to record incoming CDR information, and if you administer CDR for the trunk group, the system records all incoming calls on the DID trunk group.

Emergency Access to the Attendant

The system does not generate intraswitch CDR records for Emergency Access calls.

Expert Agent Selection (EAS)

You can assign a logical extension to an agent who can then use the logical extension to log in to a telephone. You can administer CDR so that the system records the logical extension of the agent as the called number. The system records the logical extension as the called number instead of the extension of the hunt-group or the hunt group member.

Foreign Exchange (FX) Trunks

If you want the system to generate CDR records for calls to FX trunks, you must administer your system to generate those records. You must also administer each trunk group so the system generates a CDR record for the trunk group.

Hotline Service

The system generates a CDR record of the stored number that is used on an outgoing or intraswitch Hotline call as if someone manually dialed the number.

Hunt Groups

You can administer CDR so the system records either the extension of the hunt group or the extension of the individual hunt group member as the called number.

Intercept Treatment

If the system routes an outgoing call or a tandem call to intercept treatment, the system records the number that the user dialed as the dialed number. The system also records condition code F.

Inter-PBX Attendant Calls

The table shows the information that the system records if a user calls an Inter-PBX attendant, and the call uses a trunk group that has CDR assigned.

Inter-PBX CDR information
CDR data field	Value
Condition Code	A
Access Code Dialed	Blank
Access Code Used	The TAC of the trunk that the call used
Dialed Digits	The Inter-PBX attendant access code

ISDN

The system sends an indication to the CDR device when the system receives a true answer supervision.

The system creates a CDR record each time that the system networks an ISDN call. In this case, the answer supervision information that the system records might not be accurate. If you use unformatted or expanded record formats, the CDR record displays the station identification number (SID) or the automatic number identification (ANI), if the SID or ANI is sent.

Last Number Dialed

The system stores the CDR access code and the account code that the user dials as part of the Last Number Dialed. However, some digits might be lost, because of the limit on the number of digits that can be stored for the Last Number Dialed feature.

Manual Originating Line Service

If an attendant establishes an outgoing call for a user, and designates the call as a Manual Originating Line call, the system generates an attendant-assisted outgoing call CDR record. The system records the extension of the user who originated the call as the calling number, and applies condition code 1.

Multiple Listed Directory Numbers (LDNs)

If the system records incoming call information, the system records the extension number or the TAC to which the attendant completes the call, as the called number of LDN calls.

If the system records incoming call information, the system records the attendant extension as the dialed number, if the call terminates at the attendant console.

You cannot administer LDNs for intraswitch CDR. However, the system generates an intraswitch CDR record for a call from an intraswitch-optioned extension to an LDN.

Night Service

The system records the extension number that is assigned to the attendants as the dialed number for night service calls.

Off-Premises Station

The system generates a CDR record for a call to an off-premises station when the:

Call involves an outgoing or an incoming trunk call.
Off-premises station is optioned for intraswitch CDR.
Other terminal that is involved in the call is optioned for intraswitch CDR.

Personal Central Office Line (PCOL) trunks

If the system records incoming calls, the system records the primary extension of the user who answers the call as the called number for incoming PCOL call.

The system records an outgoing PCOL call as a call from the originating extension number through the trunk group that is associated with the PCOL.

The system records the dialed number in the Dialed Number field for an outgoing PCOL call. The system does not record the TAC in the Dialed Number field for an outgoing PCOL call.

Planned Interchange

When any planned interchange occurs, the system might record calls that end within 10 to 20 seconds after the interchange as calls that have an invalid duration. A call with an invalid duration is a call with a duration of 9:59:9, and a condition code other than 4. These call records are invalid. Deviations in the clocks between the two processors, and the short duration of the calls, cause the invalid duration.

Private Network Access

The system records Private Network Access calls, if CDR is assigned for incoming or outgoing tie trunks.

Remote Access

The system records remote access calls if Remote Access is provided on a per-trunk-group basis, and you administered CDR for those trunks. The trunk group access code in the call record is the only indication that the record is for a remote access call.

Ringback Queuing

The system records condition code 8 for an outgoing call that is in a trunk queue before the call is complete. The system does not record the time that the call is in the queue.

The system does not generate a CDR record if a call waits in a trunk queue, and the call is completed. The call is not completed successfully if the time that the call waits in the queue exceeds the wait limit for the queue, or if the calling party does not answer the callback.

Security Violation Notification (SVN)

The system generates a CDR record for a SVN call if the terminating extension is monitored. You cannot administer the originating extension for intraswitch monitoring.

Service Observing

The system does not generate CDR records for Service Observing calls.

Tandem Tie-Trunk Switching

The calling party on an incoming trunk can dial the CDR account code. The system records the TAC for the incoming trunk group in the Calling Number field in the CDR record. The system records the number that the user dials as the number dialed.

Temporary Bridged Appearance

A CDR record is unaffected if a second user, or subsequent user, bridges a call.

Temporary Signaling Connections (TSCs)

If you administer CDR to use ISDN layouts, the system records call-associated TSCs and TSC requests in the call record. If you administer CDR to record noncall-associated/temporary-signaling connection (NCA TSCs) and TSC requests, the system generates separate CDR records for each type of TCS. The system records the TCS data in the TSC Flag field and Packet Count field.

Tie-Trunk Access

Tie-trunk calls are recorded if CDR is administered to record the trunk group, and to record incoming calls.

Transfer

If a user originates a call on an outgoing trunk and then transfers the call to another extension, the system records the originating extension as the calling party.

If a user receives a call on an incoming trunk and then transfers the call to another extension, the system records the extension that originally received the call as the dialed number.

If a user receives an intraswitch call and then transfers the call to another extension, the system records the extension that originally received the call as the dialed number.

The system generates two CDR records if all the following conditions are met:

Call splitting is active.
A user receives or originates a trunk call.
The user transfers the call to another extension

The system generates intraswitch CDR records 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 station C drops, the system generates two CDR records with a condition code 0. The system generates a CDR record for a call from station A to station B, and a second record for the call from station A to station C.

The system generates intraswitch CDR transfer records when both the calling party and the called party drop from the call. The system records the call duration from the time that the called party answers the call until both the calling party and the called party drop the call.

The system generates an incoming trunk call CDR record if ITCS is enabled, and a user transfers the call to a local extension that is optioned for Intraswitch CDR. The system does not generate an intraswitch record.

When a user transfers a call to another extension, a users cannot dial an account code, unless the user has console permissions.

When a user transfers a call to a trunk, the user can dial an account code before the user dials the ARS or the TAC.

Trunk-to-Trunk Transfer

With CDR, the system processes a trunk-to-trunk transfer connection as a conference call. The system generates a separate CDR record for each trunk in the connection.

You can administer CDR so that the system records unanswered trunk calls. You can administer each trunk group so the system records unanswered calls if the calls remain unanswered for an interval that you specify.

If Incoming Trunk Call Splitting is active, the system generates a CDR record for a trunk-to-trunk transfer. The system generates a record of the incoming call, and a record of the outgoing call. The system records the duration of the outgoing call from the time that the user transfers the call until both parties drop the call. The system records the duration of the incoming call from the time that the user answers the call until both parties drop the call.

Uniform Dial Plan (UDP)

The table shows the information that the system records if a user uses a UDP extension to call another user, and the trunk group that the call uses has CDR assigned.

Uniform dial plan CDR information
CDR data field	Value
Condition Code	7
Access Code Dialed	Blank
Access Code Used	The TAC of the trunk that the call used
Dialed Digits	The UDP extension

VDN Return Destination

The system does not generate a CDR record for an incoming call until the originator drops from the call. The system creates a CDR record when all the following conditions are met:

A call goes to the return-destination VDN.
The originator has not dropped.
Vector processing, that is the return destination VDN, routes the call to an outgoing trunk.

The system does not create a CDR record if vector processing routes a call from the return-destination VDN to an internal call. The system records only the first VDN that the caller accesses, regardless of the number of other extensions that are involved in the call.

If the system routes an incoming VDN call to a station, the system includes the station in the CDR record. If the system routes an incoming VDN call to an outgoing trunk, the system includes the VDN in the CDR record.

Send Feedback

No results found