Avaya Aura Communication Manager

Feature Description and Implementation

August 29, 2019

Avaya Aura Communication Manager Feature Description and Implementation

Notices
© 2019 copy rights

You may, at your own risk, assemble a MyDocs collection solely for your own internal business purposes,
which constitutes a modification to the original published version of the publications. Avaya shall not be
responsible for any modifications, additions, or deletions to the original published version of publications. You
agree to defend, indemnify and hold harmless Avaya, Avaya's agents, servants and employees against all
claims, lawsuits, demands and judgments arising out of, or in connection with, your modifications, additions or
deletions to the publications.

A single topic or a collection of topics may come from multiple Avaya publications. All of the content in your
collection is subject to the legal notices and disclaimers in the publications from which you assembled the
collection. For information on licenses and license types, trademarks, and regulatory statements, see the
original publications from which you copied the topics in your collection.

Except where expressly stated by Avaya otherwise, no use should be made of materials provided by Avaya on
this site. All content on this site and the publications provided by Avaya including the selection, arrangement
and design of the content is owned by Avaya and/or its licensors and is protected by copyright and other
intellectual property laws including the sui generis rights relating to the protection of databases. Avaya owns all
right, title and interest to any modifications, additions or deletions to the content in the Avaya publications.

August 29, 2019 Avaya Aura Communication Manager Feature Description and Implementation
Avaya Aura Communication Manager Feature Description and Implementation

Call detail record field descriptions

The following information describes the CDR data that the system collects for each call, and the length of
each field. The information is right adjusted in the CDR record field, unless otherwise indicated. The
system displays the customized field name if the field names for the customized differ from the names of
standard records.

Access Code Dialed

Customized field name: code-dial
Length: 3 or 4 digit
This field contains the access code that the user dials to place an outgoing call. The access can be the
automatic route selection (ARS) access code, an Automatic Alternate Routing (AAR) access code, or the
access code of a specific trunk group. This field is also used to record the X.25 Feature Access Code of
an outgoing X.25-addressed call.

Access Code Used

Custom field name: code-used
Length: 3 or 4 digits
This field is used only for outgoing calls when the system uses a trunk group that differs from the access
code that the user dials. This field is not used when a user dials a TAC. For example, your system might
use an FAC for ARS. This field contains the access code of the trunk group that the system uses to route
the call. When the access code that the user dials, and the access code that the systems uses are the
same, this field is blank.
If you use ISDN or enhanced formats with TELESEER, LSU, or printer record types, this field contains the
access code of the trunk group, even if the user dials the same access code.
Length: 2 digits
If an attendant participates in a call, this field contains the number of the attendant console.

Account Code
Custom field name: acct-code
Length: 1 to 15 digits
This field is either blank, or contain a number to associate call information with projects or account
numbers. For some formats, a long account code overwrites spaces on the record that are assigned to
other fields.

Attendant Console
Custom field name: attd-console
Length: 2 digits

August 29, 2019 Avaya Aura Communication Manager Feature Description and Implementation 3
Avaya Aura Communication Manager Feature Description and Implementation

If a user uses an attendant to make a call, the attd-console field displays the console number of the
attendant. If multiple attendants are used, the console number of the last attendant is recorded. For
incoming and non operator-handled calls, this field remains blank.

Authorization Code
Custom field name: auth-code
Length: 4 to 13 digits
This field contains the authorization code that the user used to make the call. The system truncates an
authorization code to 7 digits for formats other than customized formats.
Note that the authorization code for the non-ISDN format and the ISDN local storage init (LSU) format has
fewer than 6 digits. The authorization code for the Enhanced LSU format has 5 digits. The system does
not record the authorization on the 59-character record.

Bandwidth
Length: 2 digits
This field contains the bandwidth of the wide band calls to support H0, H11, H12, and N x 64 kbps data
rates. For Enhanced Expanded, Enhanced Unformatted, and customized record formats, this value in this
field is the number of DSOs of 64-kbps channels that comprise a call.

Bearer Capability Class

Custom field name: bcc
Length: 1 digit
This field contains the bearer capability class (BCC) for ISDN calls. The BCC identifies various
capabilities that are available for a ISDN call. Any one of the following BCCs can appear in this field.
0 - Voice grade data and voice
1 - Mode 1, 56 kbps synchronous data
2 - Mode 2, less than 19.2 kbps synchronous or asynchronous data
3 - Mode 3, 64 kbps data for Link Access Procedure data (LAPD) protocol
4 - Mode 0, 64 kbps data clear
M - Multimedia
W - Wideband
Note:
The Bearer Capability Class field in the CDR records shows the capabilities that are available for a given
call. It is not a report of the capabilities that were used for the call. For intraswitch CDR records, the BCC
field system provides information for wideband calls only.

Calling Number
Custom field name: calling-num

August 29, 2019 Avaya Aura Communication Manager Feature Description and Implementation 4
Avaya Aura Communication Manager Feature Description and Implementation

Number of digits, standard: 1 to 10

Number of digits, custom: 1 to 15
For outgoing or intraswitch calls, this field contains the extension of the originating telephone user. For
incoming and tandem calls, this field contains the TAC in standard formats. The fifth digit is the first digit of
a 5-digit dialing plan.
For formats in which the Calling Number field has 7 digits, the field contains the TAC of the incoming call.
For Unformatted records or Expanded records, this field contains the number of the calling party. If the
number of the calling party is unavailable, this field is blank for both the Unformatted and the Expanded
record formats.
For an outgoing, or an originating, NCA-TSC CDR record, this field contains the local extension of the
noncall-associated/temporary-signaling connection (NCA-TSC) endpoint. This field is blank for
terminating, tandem, or unsuccessful NCA-TSC CDR records.

Call Type
Custom field name: calltype
Length: 1 digit
This field is only used in the customized format and is used to indicate whether the called party number
was handled by calltype digit analysis or not. If the call was handled by calltype digit analysis, the field is
set to a 1, otherwise it is set to a 0. This field was formerly called logdial.

Calling Number/Incoming TAC

Custom field name: clg-num/in-tac
You can use this field on a customized record to display the calling number, if the calling number is
available.
If the calling party number is unavailable, this field contains the incoming TAC.
For outgoing calls, this field contains the calling extension.

Calling Party Category

Custom field name: clg-pty-cat
Length: 2 digits
This field is used only on the customized format. This parameter is associated with R2MFC trunks.

Carriage Return
Custom field name: return
The ASCII carriage return character, followed by a line feed, indicates the end of a call record.

Condition Code
Length: 1 character

August 29, 2019 Avaya Aura Communication Manager Feature Description and Implementation 5
Avaya Aura Communication Manager Feature Description and Implementation

The condition code indicates the type of call that this record describes. For example, condition code C
identifies a conference call, and condition code 7 identifies an ARS call.
The table shows the condition codes for most record formats. The condition codes for the 59-character
format differ from the condition codes of the other record types. The codes that apply to 59-character
records appear in parentheses in the table.
Table 1. Condition codes

Condition codes Description

0 Identifies an intraswitch call, which is a call that originates and terminates on the switch

1 (A) Identifies an attendant-handled call or an attendant-assisted call, except conference calls

Identifies an extremely long call or a call with an extremely high message count TSC. An
extremely long call is a call that lasts for 10 or more hours. An extremely high message count
TSC is 9999 or more messages.
When a call exceeds10 hours, the system creates a call record with this condition code and a
4 (D) duration of 9 hours, 59 minutes, and 1-9 tenths of a minute.
The system creates a similar call record with this condition code after each succeeding 10-hour
period.
When the call terminates, the system creates a final call record with a different condition code
that identifies the type of call.

Identifies calls where no CDR records are generated because the CDR (SMDR) processes do
not have enough resources available to generate a record. For example, a CDR resource
6 (E)
shortage could be the CDR buffer space available. The CDR record that includes this condition
code also includes the time and the duration of the CDR resource outage.

7 (G) Identifies calls that use the AAR or ARS feature.

8 (H) Identifies calls that are served on a delayed basis by the Ringback Queuing feature.

Identifies:

• An incoming call
9 (I) • A tandem call
• An incoming NCA-TSC call
• A tandem NCA-TSC call

A Identifies an outgoing call.

B Identifies an adjunct-placed outgoing call.

August 29, 2019 Avaya Aura Communication Manager Feature Description and Implementation 6
Avaya Aura Communication Manager Feature Description and Implementation

Condition codes Description

Identifies a conference call.

For trunk CDR, the system creates a separate call record, with this condition code, for each
incoming or outgoing trunk that is used during the conference call.
If you disable ITCS and OTCS, the system records the extension of the originator of the
conference call. The system does not record any other extension.
C (L)
If you disable ITCS, and you administer the originator of the conference call to use Intraswitch
CDR, the system generates a call with this condition code whenever the originator of the
conference dials a nontrunk conference participant.
If ITCS is active, and you do not administer the originator of the conference call to use
Intraswitch CDR, the system generates a call with this condition code whenever the originator
of the conference dials an intraswitch conference participant.

Identifies a call that the system does not complete because the following facilities to complete
the call are unavailable:

• Outgoing calls
• The trunks are busy, and no queue exists.
• The trunks are busy, and the queue is full.
E (N) • Incoming calls
• The extension is busy.
• The extension is unassigned.

This condition code also identifies an ISDN Call By Call Service Selection call that is
unsuccessful because of an administered trunk usage allocation plan. Incoming trunk calls to a
busy telephone do not generate a CDR record.

Identifies a call that the system does not complete because of one of the following conditions:

• The originator of the calls has insufficient calling privileges.

F
• An NSF mismatch occurs for an ISDN call.
• An authorization mismatch occurs for a data call.

G Identifies a call that the system terminates to a ringing station.

H Notes that the system abandoned a ringing call.

I Identifies a call that the system terminates to a busy station.

Identifies an incoming trunk call that is a new connection that uses Additional Network Feature-
J Path Replacement (ANF-PR) or DCS with Rerouting. For more information on QSIG and ANF-
PR, see Administering Avaya Aura® Communication Manager, 03-300509.

Identifies an outgoing trunk call that is a new connection that uses ANF-PR or DCS with
K Rerouting. For more information on QSIG and ANF-PR, see Administering Avaya Aura®
Communication Manager, 03-300509.

August 29, 2019 Avaya Aura Communication Manager Feature Description and Implementation 7
Avaya Aura Communication Manager Feature Description and Implementation

Condition codes Description

Identifies an outgoing trunk calls that the system disconnects because the call exceeds the
M
allotted time.

Identifies CDR records for calls that meet the following conditions:

• The Condition Code ‘T’ for Redirected Calls? field on the CDR System Parameters screen is
T set to y.
• The incoming trunk group is direct inward dialing (DID).
• The system automatically redirects an incoming call off of the server.

O Identifies CDR records for all calls in which URI was used as dialed digits.

P Identifies CDR records for all calls in which SA8957 PIN code for Private Calls was used.

If the Trunk-group CDR Reports field is set to ring, CDR records the ring time to answer or abandon for
incoming calls that the trunk group originates. CDR also indicates if the incoming destination is busy. This
record is separate from the normal call duration record that is printed for an answered call. This
information is indicated by the condition code.
When a trunk group originates an incoming call with this option set that is terminated to an internal
destination, the call is tracked from the time that ringing feedback is given to the originator. If the call is
answered, a CDR record is printed with condition code G, and the duration reflects the time between the
start of ringing and when the call is answered. If the call is abandoned before being answered, the system
prints a record with condition code H, and the duration reflects the time between the start of ringing and
the time that the call was abandoned. If the destination is busy, a CDR record is printed with condition
code I and a duration of 0.

Condition code overrides

If two condition codes apply to the same call, one code overrides the other. The following matrix, the
table, defines the overrides.
To use this table, locate one of the condition codes that you want to compare in the row of condition
codes at the top of the table. Then locate the other condition code that you want to compare in the column
of condition code at the far left of the table. Then locate the intersection of these two condition codes. The
condition code at the intersection of the two condition codes, is the condition code that the system uses.
For example, assume that the system can assign condition 7 and condition code A to the same call. The
system uses condition code 7 for the call.
If the intersection of the two condition codes contains a dash, the two conditions never occur for the same
call.

August 29, 2019 Avaya Aura Communication Manager Feature Description and Implementation 8
Avaya Aura Communication Manager Feature Description and Implementation

Table 2. Condition code override matrix

Condition codes

0 1 4 6 7 8 9 A B C E F J K M T

0 - 0 4 6 0 - - - B C - - - - - -

1 0 - 4 6 1 - 9 1 B C E - J K - -

4 4 4 - 6 4 4 4 4 4 4 - - J K - -

6 6 6 6 - 6 6 6 6 6 6 6 6 6 6 - -

7 0 1 4 6 - 7 9 7 B C E F J K - -

8 - - 4 6 7 - - 8 B C E - - K - -

9 - 9 4 6 9 - - - - C E F - - - -

A - 1 4 6 7 8 - - B C E F - - - -

B B B 4 6 B B - B - B E F - K - -

C C C 4 6 C C C C B - - - J K M -

E - E - 6 E E E E E - - - E E - -

F - - - 6 F - F F F - - - F F - -

J - J J 6 J - - - - J E F - - - -

K - K K 6 K K - - - K E F - - - -

M - - - - - - - - - M - - - - - -

T - - - - - - - - - - - - - - - -

Contact Uniform Resource Identifier

Custom field name: contact-uri
Length: 20 digits
The Contact-URI field contains the Uniform Resource Identifier (URI) associated with the calling party on
a SIP call. This field is used only with the customized format. The Contact header contains the IP address
of the machine or telephone that the call originated from. This header remains the same throughout the
entire call.

August 29, 2019 Avaya Aura Communication Manager Feature Description and Implementation 9
Avaya Aura Communication Manager Feature Description and Implementation

Country From
Custom field name: country-from
Number of digits: 3
The country-from field is a country number, used with the Multinational Locations feature, for currency
conversion. The field length is 3, the same as the length of the Country code for CDR field on the
Location Parameters screen. The country-from field indicates the administered CDR country code of the
PBX interface of the calling party.

Country To
Custom field name: country-to
Number of digits: 3
The country-to field is a country number, used with the Multinational Locations feature, for currency
conversion. The field length is 3, the same as the length of the Country code for CDR field on the
Location Parameters screen. The country-to field indicates the administered CDR country code of the
PBX interface of the called party.
Note:
If the Multinational Locations feature is turned off in the license file, the key words country-from and
country-to are invalid.

Date
You can include the date in customized CDR records only. The format of the date is based on the value of
the CDR Date Format field on the CDR System Parameters screen.

Dialed Number
Custom field name: dialed-num
Length: 23 digits
For an outgoing call, this field contains the number that the system user dials. For an incoming call, this
field contains the extension of the system user that is called. If a Dialed Number Identification System
(DNIS) exists, the field contains the implied extension for an incoming call. If the originator of the call dials
more than eighteen digits, the system truncates the number or the extension to 18 digits. The system
truncates the least significant digits, starting at the right. For example, if the originator of the call dials the
number 111111111111111111852, the system truncates the digits 852.

• CDR PrivacyIf CDR Privacy is active for the calling number, and this CDR record is for an outgoing call,
the system modifies and records the number that the user dials according to the following procedure:
• The system truncates the numbers that the user dials to 18 digits
• The system replaces some of the digits with blanks to ensure the privacy of the call.
• NCA-TSC or tandem NCA-TSC outgoing callsFor outgoing NCA-TSC or tandem NCA-TSC calls, this
field contains the digits that the user dials, and that the system uses to establish a route to the server.
The field contains the local extension that is used as the NCA-TSC endpoint when the extension is for

August 29, 2019 Avaya Aura Communication Manager Feature Description and Implementation 10
Avaya Aura Communication Manager Feature Description and Implementation

a terminating NCA-TSC. For an unsuccessful NCA-TSC outgoing call, this field is blank. The field can
contain a pound sign (#) or the letter E for either ARS calls or TAC calls when:
• A user dials a pound sign (#) at the end of a string of digits
• An outgoing call exceeds the interdigit-timeout interval that is in the ARS Analysis table
• A user makes a TAC call, which then routes through Look Ahead Interflow (LAI). For example, a
successful LAI to <TAC> 1001, where 1001 is the remote VDN extension, yields 1001E or 1001# in the
Dialed Number field. The vector processing software uses the pound sign (#) or E to indicate the end of
the string of digits that the user dials.You administer the CDR System Parameter screen so the pound
sign (#) or the letter E need not be the last digit of the CDR record.

Duration
Custom field name: duration or sec-dur
Length: 4 digits
This field contains the duration of the call, which the system records in hours (0 to 9), minutes (00 to 59),
and tenths of minutes (0 to 9). The system rounds the duration of the call down in 6-second increments.
For example, the system records the duration of a 5-second call as a duration of zero. If this field contains
the value 9999, the call was in progress when a time change was made in the switch.
You can use the customized record format to report the duration of the call in hours, minutes, and
seconds.

end-date(4d)
Length: 8 digits
This field is associated with Special Application SA8201. Go to the Avaya Support website at http://
support.avaya.com for current documentation, product notices, and knowledge articles related to Special
Application features.

Feature Flag
Custom field name: feat-flag
Length: 1 digit
The feature flag indicates whether a call received network answer supervision, and whether the call was
interworked in the network. The duration of the call starts when the system receives the network answer.
You can administer the Feature flag field on the CDR System Parameters screen to reflect whether the
network reported an outgoing ISDN call as interworked.

• The number 0 in this field indicates either a voice call without network answer supervision or a call for
which NCA-TSC is not established.
• The number 1 in this field indicates a data call without network answer supervision.
• The number 2 in this field indicates a voice call with network answer supervision, but interworked.
• The number 3 in this field indicates a data call with network answer supervision, but interworked.
• The number 4 in this field indicates a voice call with network answer supervision.

August 29, 2019 Avaya Aura Communication Manager Feature Description and Implementation 11
Avaya Aura Communication Manager Feature Description and Implementation

• The number 5 in this field indicates a data call with network answer supervision. The time of the answer
and the duration of the call are accurate if the feature flag indicates that the call received network
answer supervision. The time of the answer and the duration of the call can be inaccurate, if the call
does not receive network answer supervision, or the call receives answer supervision but is
interworked with non-ISDN trunks. Calls are considered data calls if the calls use a conversion
resource, such as a modem, and the calls either originate or terminate on a data module.

Format Code
Length: 2 digits
This field contains two values:

• 00 indicates no PPM.
• 03 indicates a PPM count in the digits record.

FRL
Length: 1 digit
Facilities restriction levels (FRLs) are numbered 0 through 7, are associated with the AAR and the ARS
features, and define calling privileges. If the call is an:

• Outgoing call, and an authorization code is not used to make the call, this field contains the FRL of the
originating user FRL.
• Outgoing call, and an authorization code is used to make the call, this field contains the FRL that is
associated with the authorization code that the user dials.
• Incoming or a tandem call, this field contains the FRL that is assigned to the incoming trunk group.
• Incoming tandem tie trunk call, this field contains either the FRL that is assigned to the tandem tie trunk
or the TCM sent with the tandem tie trunk call. If an FRL was used to complete the call, the field
contains the FRL. If a TCM was used to complete the call, the field contains the TCM. With ISDN calls,
this field always contains the TCM, if the TCM was received.You can administer CDR so that this field
contains disconnect information instead of the FRL. If you administer CDR so this field contains
disconnect information for trunk CDR, the system records the information shown in the table.
Table 3. Disconnect information for trunk CDR

Data Meaning

0 The system cannot determine which participant on the call dropped the call first.

1 The switch participant dropped the call first.

2 CO participant dropped the call first.

3 Maintenance seized the trunk

For intraswitch CDR, the field contains the information that is shown in the table instead of the FRL.

August 29, 2019 Avaya Aura Communication Manager Feature Description and Implementation 12
Avaya Aura Communication Manager Feature Description and Implementation

Table 4. Intra-switch CDR call disconnect information

Data Meaning

0 The system cannot determine which participant on the call dropped the call first.

1 The calling participant dropped the call first.

2 The dialed participant dropped the call first.

From-URI
Length: 20 digits
The From-URI field contains the URI associated with the calling party on a SIP call. This field is used only
with the customized format. The From header contains the caller ID information. This header can contain
ID information that the calling party wants the header to contain. The ID information might or might not be
accurate and therefore is not considered to be a reliable source of information.
Note:
To have a more consistent and repeatable information in the CDR records, use the Contact-URI field
instead of the From-URI field.

Incoming Circuit Identification

Custom field name: in-crt-id
Length: 3 digits
This field contains the member number of a trunk within a trunk group that is used for an incoming call.
For outgoing calls, this field is blank. Tandem calls contain both incoming and outgoing circuit ID numbers.
The format of this field varies from record to record. For printer, TELESEER, and 59-character formats,
the numbers are inverted on the record. For example, the system displays the circuit ID 123 as 231 (tens,
units, hundreds). If you want to change the order to hundreds, tens, units format, for example, 123, use
the Modified Circuit ID Display field on the CDR System Parameters screen.

Incoming TAC
Custom field name: in-trk-code
Length: 4 digits
This field contains the access code of the incoming trunk group.

INS
Length: 3 digits
This field specifies the ISDN Network Service (INS) that is requested for a call. This field applies only to
ISDN calls. Each network specific facility has a corresponding INS value, shown in the table.
The system displays this field also as ISDN NSV (network service value).

August 29, 2019 Avaya Aura Communication Manager Feature Description and Implementation 13
Avaya Aura Communication Manager Feature Description and Implementation

Table 5. Network-specific facility to INS mapping

Network specific facility INS value

OUTWATS Band 0 33
OUTWATS Band 1-255 34-288

Network Operator 324

Pre subscribed Common Carrier Operator 325

Software Defined Network (SDN) 352

MEGACOM 800 353

MEGACOM 354

INWATS 355

Maximum Banded WATS 356

ACCUNET Digital Service 357

AT&T Long Distance Service 358

International 800 359

Multiquest 367

Internal Codec
Custom field name: internal-codec
Length: 2 digits
This field is associated with Special Application SA8702. Go to the Avaya Support website at http://
support.avaya.com for current documentation, product notices, and knowledge articles related to Special
Application features.

ISDN CC
The call charge that the ISDN advice of charge function supplies.

ISDN Call Charge/Periodic Pulse Metering

Custom field name: isdn-cc/ppm
Length: 11 digits
This field is used only on the customized format.

August 29, 2019 Avaya Aura Communication Manager Feature Description and Implementation 14
Avaya Aura Communication Manager Feature Description and Implementation

ISDN NSV
See INS.

IXC Code
The length for non-ISDN formats: 1 digit hexadecimal
Interexchange Carrier (IXC) codes,1-F hexadecimal, indicate the carrier used on the call. This information
is sent to the CDR output device in ASCII code as a hexadecimal representation, for example, ASCII F
equals 15 that is.
Users must dial an IXC access number to access a specific common carrier for a call. In the US, this
number is in the form 10XXX, 950 - 1XXX, or any 8 to 11 digit number. The IXC access numbers that are
applicable at a given location are associated with an IXC code on the Inter-Exchange Carrier Codes
screen.
When ARS is used, and a route pattern inserts one of the administered IXC codes, the report contains the
associated IXC code. If no IXC access number is used, or the carrier is selected at the central office (CO),
the report contains a zero.
Length for ISDN formats: 3 or 4 digits
With an ISDN record format, this 3-digit or 4-digit field identifies the actual IXC used on an ISDN call. This
information is determined from the route pattern administration. For AAR and ARS calls, the 3-digit IXC
value is administered in the route pattern for all ISDN calls. If a user dials an IXC code with a 10XXX
format as administered on the Inter-Exchange Carrier Codes screen, the CDR record contains only the
last 3 digits (4 digits or Enhanced). If a user dials a 7-digit IXC code, this field contains a zero.

Line Feed
Length: 1 character
The ASCII line feed character comes after a carriage return to terminate CDR records.

Location From
Custom field name: location-from
Number of digits: 3
The location-from field is a location number, used with the Multinational Locations feature, for record
sorting. The field length is 3, the same as the length of the location field on the cabinet, media gateway,
remote office, and ip-network region screens. The location-from field indicates the location code of the
PBX interface of the calling party.

Location To
Custom field name: location-to
Number of digits: 3
The location-to field is a location number, used with the Multinational Locations feature, for record sorting.
The field length is 3, the same as the length of the location field on the Cabinet, Media Gateway, Remote

August 29, 2019 Avaya Aura Communication Manager Feature Description and Implementation 15
Avaya Aura Communication Manager Feature Description and Implementation

Office, and IP Network Region screens. The location-to field indicates the location code of the PBX
interface of the called party.
Note:
If the Multinational Locations feature is turned off in the license file, the key words location-from and
location-to are invalid.

MA-UUI
Length: 1 digit
Message Associated User-to-User Signaling shows the number of ISDN messages that contain user data
that are sent on an outgoing call. This field contains a number from 0 to 9.

Node Number
Custom field name: node-num
Length: 2 digits
This field identifies the DCS node number of a switch within a DCS arrangement. This number is the local
ID, which is the same as the node number on the Dial Plan screen.

Null
Length: 1 character
The Null character, usually in triplets, is used to terminate and divide CDR Records, when a receiving
adjunct needs a record divider or terminator.

Outgoing Circuit Identification

Custom field name: out-crt-id
Length: 3 digits
For outgoing calls, this field contains the member number of the trunk within a trunk group that is used on
the call. This field is blank for incoming calls. Tandem calls include both incoming and outgoing circuit ID
numbers. For outgoing and tandem NCA-TSCs, this field contains the signaling group that is used to carry
the NCA-TSC.
The format of this field varies from record to record. For printer, TELESEER and 59-character formats,
and the ISDN and Enhanced forms of those records, the numbers are inverted on the record. For
example, the system displays the circuit ID 123 as 231 (tens, units, hundreds). If you want to change the
order to hundreds, tens, units format, for example, 123, use the Modified Circuit ID Display field on the
CDR System Parameters screen.

Packet Count
Custom field name: tsc_ct
Length: 4 digits
For ISDN TSCs, this field contains the number of ISDN-PRI USER INFO messages that are sent,
received, or, for tandem TSCs, passed through the switch.

August 29, 2019 Avaya Aura Communication Manager Feature Description and Implementation 16
Avaya Aura Communication Manager Feature Description and Implementation

PPM
Periodic Pulse Metering (PPM) contains the pulse counts that are transmitted over the trunk line from the
serving CO. The pulse counts are used to determine call charges.

Request Uniform Resource Identifier

Custom field name: request-uri
Length: 20 digits
The Request-URI field contains the URI associated with the called party on a SIP call. This field is used
only with the customized format. Request-URI contains the destination of the request.

Resource Flag
Custom field name: res-flag
Length: 1 digit
This field indicates whether a conversion resource was used, or if the call involved a Multimedia
Application Server Interface (MASI) terminal or MASI trunk, or if a video or wideband codec was used.

• 0 indicates no conversion device used, no video or wideband codec and no MASI devices
• 1 indicates wideband audio codec used
• 2 indicates conversion device used
• 4 indicates video codec used
• 5 indicates video codec and wideband audio codec used
• 8 indicates a MASI call
• indicates a MASI call with a conversion device used
Note:
Video or wideband takes precedence over MASI/conversion. If video or wideband is used, the field
does not indicate if MASI or a conversion device was used.

Sec-dur
For customized records only, you can uses this field to set the duration field to record seconds instead of
tenths of minutes.

seq-num
Length: 10 digits
This field is associated with Special Application SA8702. Go to the Avaya Support website at http://
support.avaya.com for current documentation, product notices, and knowledge articles related to Special
Application features.

August 29, 2019 Avaya Aura Communication Manager Feature Description and Implementation 17
Avaya Aura Communication Manager Feature Description and Implementation

Space
Length: 0 to 40 characters
The ASCII space character separates other CDR fields or fills unused record locations.

start-date
Length: 6 digits
This field is associated with Special Application SA8201. Go to the Avaya Support website at http://
support.avaya.com for current documentation, product notices, and knowledge articles related to Special
Application features.

start-date(4d)
Length: 8 digits
This field is associated with Special Application SA8201. Go to the Avaya Support website at http://
support.avaya.com for current documentation, product notices, and knowledge articles related to Special
Application features.

start-time
Length: 6 digits
This field is associated with Special Application SA8201. Go to the Avaya Support website at http://
support.avaya.com for current documentation, product notices, and knowledge articles related to Special
Application features.

Time
This fields contains the time that the call ended, or if Call Splitting is active, the time that a user dropped
from a multiparty call.

Timezone From
Custom field name: timezone-from
Number of digits: 5
The timezone-from field is a time zone offset number, used with the Multinational Locations feature, for
call time. The field length is 5, the same as the length of the timezone offset field on the Cabinet, Media
Gateway, Remote Office, and IP Network Region screens. The timezone-from field indicates the timezone
offset of the PBX interface of the calling party.

Timezone To
Custom field name: timezone-to
Number of digits: 5

August 29, 2019 Avaya Aura Communication Manager Feature Description and Implementation 18
Avaya Aura Communication Manager Feature Description and Implementation

The timezone-to field is a time zone offset number, used with the Multinational Locations feature, for call
time. The field length is 5, the same as the length of the location field on the Locations screen. The
timezone-to field indicates the timezone offset of the PBX interface of the called party.
Note:
If the Multinational Locations feature is turned off in the license file, the key words timezone-from and
timezone-to are invalid.

To-URI
Length: 20 digits
The To-URI field contains the URI associated with the called party on a SIP call. This field is used only
with the customized format. The To header contains the originating endpoint view of the dialed number
and remains the same during the duration of the call.

TSC-Count
Custom field name: tsc_ct
Length: 4 digits
This field is the customized name for Packet Count. See Packet Count for more information.

TSC Flag
Custom field name: tsc_flag
Length: 1 digit
This field describes call records that pertain to temporary signaling connections. When the value of this
field is not equal to zero, this field indicates the status of the TSC. The table shows the TSC flag
encoding.
Table 6. Encoding for the TSC flag

Code Description

0 Circuit-switched call without TSC requests

1-3 Reserved

Call Associated TSC requested and accepted in response to SETUP, no congestion

4 control (applicable to originating node). Call Associated TSC received and accepted
by SETUP, no congestion control (applicable to terminating node).

Call Associated TSC received and accepted by SETUP, congestion control

5
(applicable to terminating node).

Call Associated TSC requested, accepted after SETUP, no congestion control

6 (applicable to originating node). Call Associated TSC received and accepted after
SETUP, no congestion control (applicable to terminating node).

August 29, 2019 Avaya Aura Communication Manager Feature Description and Implementation 19
Avaya Aura Communication Manager Feature Description and Implementation

Code Description

Call Associated TSC received and accepted after SETUP, congestion control
7
(applicable to terminating node).

Call Associated TSC requested, rejected (rejection came from outside the local
8
switch).

Call Associated TSC requested, rejected (rejection came from the local switch, that
9
is, lack of resource).

Non-call-associated (NCA) TSC received, accepted, no congestion control

A (applicable to terminating node). NCA TSC received, accepted, no congestion control
(applicable to terminating node).

NCA TSC requested, accepted, congestion control (applicable to originating node).

B
NCA TSC received, accepted, congestion control (applicable to terminating node).

C NCA TSC requested, rejected (rejection came from outside the local switch).

Non Call Associated TSC requested, rejected (rejection came from the local switch,
D
that is, lack of resource).

E Reserved for future use.

F Reserved for future use.

trunk-codec
Length: 2 digits
This field is associated with Special Application SA8702. Go to the Avaya Support website at http://
support.avaya.com for current documentation, product notices, and knowledge articles related to Special
Application features.

ucid
Length: 20 digits
This field is associated with Special Application SA8702. Go to the Avaya Support website at http://
support.avaya.com for current documentation, product notices, and knowledge articles related to Special
Application features.

VDN
Custom field name: vdn
Length: 13 digits
This field is available on customized records only. The call record contains the VDN extension number. If
VDN Return Destination is active, this field contains the first VDN that the caller accessed.

August 29, 2019 Avaya Aura Communication Manager Feature Description and Implementation 20