Historical Reporting and Data Dictionary
Historical Reporting and Data Dictionary
Information is subject to change without notice. Nortel reserves the right to make changes in design
or components as progress in engineering and manufacturing may warrant.
The process of transmitting data and call messaging between the Nortel Meridian 1 PBX and
Contact Center Manager Server is proprietary to Nortel. Any other use of the data and the
transmission process is a violation of the user license unless specifically authorized in writing by
Nortel prior to such use. Violations of the license by alternative usage of any portion of this process
or the related hardware constitutes grounds for an immediate termination of the license and Nortel
reserves the right to seek all allowable remedies for such breach.
This page and the following page are considered the title page, and contain Nortel and third-party
trademarks.
*Nortel, the Nortel logo, the Globemark, CallPilot, DMS, DMS-10, DMS-100, DMS-200, DMS-250,
DMS-300, DMS-500, DMS-MTX, DMS-STP, DPN, DPX, Dualmode, Helmsman, ICN, IVR, MAP,
Nortel Meridian 1 PBX, Meridian Mail, Meridian SL, Norstar, Optera, Optivity, Passport, Periphonics,
SL, SL-1, Succession, Supernode, and Symposium are trademarks of Nortel.
3COM, US ROBOTICS, and SPORTSTER are trademarks of 3Com Corporation.
ACCELERAID, IBM, and MYLEX are trademarks of International Business Machines Corporation.
ACROBAT, ACROBAT READER, ADOBE, ADOBE ACROBAT, FRAME, FRAMEMAKER, and
POSTSCRIPT are trademarks of Adobe Systems Incorporated.
ACTIVE DIRECTORY, INTERNET EXPLORER, MICROSOFT, MICROSOFT ACCESS, MS-DOS,
POWERPOINT, WINDOWS, WINDOWS NT, WINDOWS 2000, WINDOWS Server 2003 and
WINDOWS XP are trademarks of Microsoft Corporation.
ANSI is a trademark of the American National Standards Institute, Inc.
CELERON, INTEL INSIDE XEON, INTEL XEON, ITANIUM, PENTIUM, PENTIUM II XEON, and
XEON are trademarks of Intel Corporation.
CITRIX is a trademark of Citrix Systems, Inc.
COMPAQ and PROLIANT are trademarks of Compaq Information Technologies Group, L.P.
CRYSTAL REPORTS is a trademark of Crystal Decisions, Inc.
DELL, OPTIPLEX, POWEREDGE, and POWERVAULT are trademarks of Dell Computer
Corporation.
HEWLETT PACKARD, HP, and SURESTORE are trademarks of Hewlett-Packard Company.
ORBIX is a trademark of Iona Technologies PLC.
MCAFEE and NETSHIELD are trademarks of Networks Associates Technology, Inc.
NOVELL is a trademark of Novell, Inc.
PCANYWHERE and THE NORTON ANTIVIRUS are both trademarks of Symantec Corporation.
RACORE is a trademark of Racore Computer Products, Inc.
REPLICATION AGENT, REPLICATION SERVER, and SYBASE are trademarks of Sybase, Inc.
SEAGATE is a trademark of Seagate Technology, LLC.
STRATUS is a trademark of Stratus Computer Systems, S.à.r.l.
TANDBERG is a trademark of Tandberg Data ASA.
VISIBROKER is a trademark of Visigenic Software, Inc.
WINZIP is a trademark of Nico Mak Computing, Inc.
February 2008 Contents
Contents
1 Getting Started 17
New in this release . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
About this guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
About Contact Center database. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
How to use this guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
Skills you need . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
Related Documents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
How to get help. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
2 Advanced Reporting 35
Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
Section A: Expert reports 37
Introduction. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
ODBC access to Contact Center Standby Server . . . . . . . . . . . . . . . . . . . . . . 40
Defining a connection to the Contact Center Manager Server . . . . . . . . . . . 41
Running the Database View Definitions report . . . . . . . . . . . . . . . . . . . . . . . 49
Defining a connection to the Contact Center Multimedia server . . . . . . . . . . 52
Creating a new Contact Center Manager report in Crystal Reports . . . . . . . . 56
Using database aliases in Crystal Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . 66
Setting the page orientation for a report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68
Creating a new Contact Center Manager report in another application . . . . . 69
Importing a report created in Crystal Reports . . . . . . . . . . . . . . . . . . . . . . . . 84
Adding customized formulas in Crystal Reports . . . . . . . . . . . . . . . . . . . . . . 94
Creating a custom report to export data to Record format . . . . . . . . . . . . . . . 96
Section B: Filters 99
Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100
Creating filters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102
PhoneNumbers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 692
Phrases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 695
Preferences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 697
Questions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 699
RegularHours . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 702
Restores. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 704
RestoredAudits . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 707
RoutePoints. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 709
Rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 710
RuleAdmins . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 713
RuleKeywordGroups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 715
Servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 717
Services. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 719
Sessions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 721
Sites. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 722
SiteComponents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 725
SiteParameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 726
Skillsets. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 728
SkillsetOnHoldURLs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 732
Updates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 733
Users . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 735
UserResets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 738
WebCommsMessages. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 739
WebCommsSessions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 741
Additional tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 743
Section B: Database views 745
Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 746
CampaignAgentScriptResult . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 747
CampaignCallByCallDetails. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 748
CampaignSummary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 751
ContactsByContacts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 753
ContactsOutstanding. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 755
ContactsOutstandingDetail . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 756
ContactsOutstandingSumm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 758
ScriptSummary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 759
Glossary 1429
Index 1469
Getting Started
In this chapter
New in this release 18
Overview 21
About this guide 22
About Contact Center database 23
How to use this guide 28
Skills you need 29
Related Documents 31
How to get help 33
The following sections detail what is new in the Nortel Contact Center Manager
Historical Reporting and Data Dictionary (297-2183-914) for release 8.11.
“Features” on page 18
“Other changes” on page 19
Features
See the following sections for information about feature changes:
“Contact Center Manager database views” on page 18
“Crystal Reports” on page 19
Crystal Reports
Contact Center Manager Release 6.0 provides support for Crystal Reports, by
Business Objects. Business Objects advises that Crystal Reports is backwards-
compatible. This means that the current version of Crystal Reports can open and
run reports originally created in earlier versions of Crystal Reports (versions 4.5
and later).
Other changes
See the following sections for information about changes that are not feature-
related.
“Updated database views” on page 19
For more information about these views and their field descriptions, see
“Contact Center Manager Data dictionary” on page 145.
Overview
Nortel designed the Contact Center Manager to provide a contact center solution
for varied and changing business environments. It provides an open database
that is accessible from the client application and from other report writers and
applications that support Open Database Connectivity (ODBC) and Structured
Query Language (SQL).
This guide explains how to create and use customized reports. It also provides
information you need to export data to other applications.
Types of reports
Contact Center Manager offers a set of standard reports to analyze statistics such
as skillset activity, agent performance, and demographics of a specific customer.
You can create user-defined reports using the standard reports as a template.
Use the Report Creation Wizard to create reports and edit them. You can also
create user-created (or expert) reports using Crystal Reports or any other
standard report writer that conforms to the industry standards of ODBC and
SQL.
This guide is for Contact Center Manager administrators and supervisors who
create, manage, and use reports.
Access rights
This guide assumes that you have the required privileges and access rights to
perform the procedures in this guide. For more information, see the Contact
Center Manager Administrator’s Guide.
Optional features
Some of the features described in this guide are optional. Fields and commands
for features that you did not purchase are not available.
Switch references
Contact Center Manager provides interworking support for the following switch
types:
Meridian 1 PBX
DMS
Meridian SL-100
Communication Server 1000
Communication Server 2x00
MCS 5100
The Contact Center database is an open database; you can access the data in this
database with any SQL- or ODBC-compliant application. You can use the data
in many ways, including the following:
Import the data into a spreadsheet for manipulation.
Import the data into your corporate database.
Import the data into a workforce management system for analysis.
Develop customized reports using Crystal Reports or another reporting
application.
The software required to access this data is installed on the Contact Center
Manager Administration server. With this software, a browser on a client PC can
access the data through the applications available on the Contact Center
Manager server.
To directly access this data from any other PC, first install and configure ODBC
and Sybase.
ATTENTION
Nortel recommends that you do NOT use a third-party
reporting application to develop customized reports on
computers running Contact Center Manager Administration.
ODBC
The Contact Center Manager database is ODBC-compatible; therefore, install
ODBC version 3.5 or later on the PC from which you access it, and define a
Data Set Name (DSN) for the database. If ODBC is not installed and configured
on your PC, follow these steps:
1 Install ODBC.
ODBC is part of the Data Access Components (DAC) and is distributed with
Microsoft Windows.
2 Configure a DSN using the ODBC Administrator.
Nortel does not support ODBC software that is not installed with Contact
Center Manager.
Sybase
The Sybase Server manages the database on Contact Center Manager Server. To
connect to the Sybase Server, use the Sybase Open Client version 12.5.
When you generate a report, the definition is updated to point to the server to
which you are currently connected.
Nortel does not support Sybase software that is not provided with Contact
Center Manager.
Database views
The actual structure of the database is invisible, and you cannot access the
database tables directly. (Direct access to the tables might compromise the
integrity of the database and jeopardizes server performance.) You access data
through database views, or logical representations of the database. Database
views are used to organize the information in the database for your use. This
guide provides a definition of all the database views available.
When creating data-warehouse applications, you use these database views. The
database views contain all the information for customized reporting and queries,
and are created on top of database tables. The database tables have indexes;
therefore, SQL queries running on the database views can use the table indexes.
The sysadmin logon account provides read-only access to a specific set of tables,
but not to all of the columns of those tables. For security and performance
reasons, no logon account provides read-only access to all of the database tables.
Third-party applications can access the database views using the Sysadmin
account. You can also use other accounts with reporting privileges on Contact
Center Manager to access data from the database views.
Types of data
The database contains four types of data:
Summarized historical statistics
Event statistics
Configuration data
Access and partition management data
Therefore, there are four types of database views: summarized historical statistic
views, event statistic views, configuration views, and access and partition
management views.
Event statistics
Event statistics are statistics collected on a per-event basis rather than
accumulated over a period of time. Contact Center Manager records the
following types of event statistics:
Agent logon and logoff statistics
Call-by-call statistics
IVR port logon and logoff statistics
IVR port logon and logoff statistics do not apply in SIP-enabled contact centers.
Configuration data
Configuration data describes the configuration of your server.
The Microsoft Access database file contains four tables that are used by the
reports.
Storage duration
When you configure historical statistics collection, you can choose how long to
store different types of statistics. The duration you choose determines the
amount of disk space required for the database. For more information, see the
Contact Center Manager Administrator’s Guide.
This guide includes a detailed table of contents and an index to help you find
specific information or procedures related to creating and using customized
reports. It also provides information you need to export data to other
applications. The “Where to start in this guide” section focuses only on the most
common tasks. If the task you want to perform is not listed, use the table of
contents or index to find the information you need.
This section describes the skills and knowledge you need to use this guide
effectively.
After you create a new report, you import it into Contact Center Manager. For
more information about importing reports, see “Importing a report created in
Crystal Reports” on page 84.
Related Documents
The following guides are available on the Contact Center portfolio DVD or on
the Nortel Web site (www.nortel.com).
This section explains how to get help for Nortel products and services. However,
before contacting Nortel for support, consult “Frequently asked questions” on
page 109 of this guide.
www.nortel.com/support
This site provides quick access to software, documentation, bulletins, and tools
to address issues with Nortel products. From this site, you can:
download software and related tools
download technical documents, release notes, and product bulletins
sign up for automatic notification of new software and documentation
search the Technical Support Web site and Nortel Knowledge Base for
answers to technical issues
open and manage technical support cases
Outside North America, go to the following Web site to obtain the phone
number for your region:
www.nortel.com/callus
www.nortel.com/erc
Advanced Reporting
In this chapter
Overview 36
Section A: Expert reports 37
Section B: Filters 99
Overview
This chapter describes procedures for working with expert reports, creating new
reports (with Crystal Reports or with another report writer), importing reports,
and customizing report formulas.
This chapter also describes how to create filters. With the filters feature, you can
select the sites and resources included in a network consolidated report. This
feature is applicable only to networking.
In this section
Introduction 38
ODBC access to Contact Center Standby Server 40
Defining a connection to the Contact Center Manager Server 41
Running the Database View Definitions report 49
Defining a connection to the Contact Center Multimedia server 52
Creating a new Contact Center Manager report in Crystal Reports 56
Using database aliases in Crystal Reports 66
Setting the page orientation for a report 68
Creating a new Contact Center Manager report in another application 69
Importing a report created in Crystal Reports 84
Adding customized formulas in Crystal Reports 94
Creating a custom report to export data to Record format 96
Introduction
You can import and schedule reports created in Crystal Reports only into
Contact Center Manager Administration. You cannot import reports created
with other applications, such as Call Center Management Information Systems
(CCMIS).
You can create user-defined reports using the standard reports available in the
Contact Center Manager Administration, or any other user-defined report, as a
template. When you create a user-defined report, you specify:
general report information—including report name
selection criteria—the entities included in the report
report schedule—when the report is generated
data range—the data collection period for the report
output options—the printer or file to which the report is output
Managing reports
You can change report properties, change the site name, print a list of reports, or
delete a user-defined or user-created report.
Using reports
You can preview a report, generate a report immediately, activate the report
schedule (so that it generates at the next scheduled time), or deactivate the
schedule.
For any system with the Contact Center Standby Server option (introduced in
Symposium Call Center Server Release 5.0), the standby Contact Center
Manager Server generates historical statistics accessible through ODBC.
Due to the design of the Contact Center Standby Server feature, the standby
Contact Center Manager server cannot run services (to ensure that no database
updates are applied to the standby Contact Center Manager Server, which makes
it out of sync with the primary Contact Center Manager server).
The database access for Contact Center Standby Server is through read-only
ODBC interface.
To access the Contact Center Manager database from a report writer application,
perform the following:
install ODBC and Sybase Open Client
configure a Sybase Server entry
configure an ODBC DSN
3 Click OK.
Result: The dsedit window appears.
5 In the Server Name box, type a name (for example, 47.10.25.3), and then
click OK.
Result: The dsedit window appears.
7 Click Add.
Result: The Input Network Address For Protocol window appears.
8 In the Network Address box, type <Nortel server subnet IP address of the
Contact Center Manager Server>,5000.
9 Click OK.
Result: The Nortel server subnet IP address appears in the Network
Address Attribute window.
10 Click OK.
Result: The dsedit window appears.
12 Click Ping.
Result: A message appears indicating that an open connection to the
server succeeded.
13 Click OK.
14 Click Done.
15 Choose File > Exit.
The details shown in the ODBC Sybase ASE Setup window depends on
the version of the driver installed.
7 In the Data Source Name box, type the name for the data source (for
example, CCMS_47.10.25.3_DSN).
8 In the Description box, type any additional information about the data
source. This is optional.
9 In the Network Address box, type the <CLAN IP address of the Contact
Center Manager>,5000. (for example, 47.10.25.3, 5000).
10 In the Database Name box, type blue.
12 In the Login ID box, type your logon ID for Contact Center Manager
Server. The Login ID corresponds to a user account that is created using
the Contact Center Manager Server Utility. (It is not a Windows 2000 ID
defined on the Contact Center Manager Server.)
13 In the Password box, type your password for Contact Center Manager
Server.
14 Click OK.
Result: The system message “Connection established” appears.
15 Click OK.
Result: The ODBC Sybase ASE Setup window appears.
16 Click OK.
Before creating a customized report, run the Database View Definitions report to
display all the database views available. This report lists all of the field names
available for use in your report. For more information about the report, see
“Database View Definitions” on page 954.
The Database View Definition report does not include views from the Contact
Center Multimedia database.
2 Select the Contact Center Manager Server from which you want to run the
report.
Result: The server expands to reveal a series of folders.
6 Click the Printer icon if you require a printout, or the Export icon if you
want to save the report.
10 Click OK.
1 From the Start menu, choose All Programs > Crystal 10.
Result: The Crystal Reports Welcome dialog box appears. The Crystal
Reports Welcome screen does not appear if you clear the option to Show
welcome dialog at startup.
3 If the Crystal Reports Welcome dialog does not appear, select File > New.
Result: The Crystal Reports Gallery dialog appears.
5 Expand the Create New Connection folder, and then select ODBC (RDO).
RDO stands for Remote Data Object.
6 Click Next.
Result: The Data Source Selection window appears.
8 In the User ID box, type the user ID. The user ID corresponds to a user
account that is created using the Contact Center Manager Server Utility. (It
is not a Windows 2000 ID defined on the Contact Center Manager Server.)
9 In the Password box, type the password for Contact Center Manager
Server. If you do not know your user ID or password, contact your system
administrator.
10 From the Database list, select blue.
11 Click Finish.
Result: The Data window appears.
12 Expand Current Connection > CCMS_47.10.25.3_DSN > blue > dbo >
Views.
Result: Available views to include in the report appear.
13 Select each view to include in the report, and click the right arrow button
(>). Ensure you use views, not tables, when you create the report.
14 Click Next.
Result: The Fields window appears.
15 From the Available Fields list, select fields to display on the report and
click the right arrow button.
16 Click Next.
Result: The Grouping window appears.
17 From the Available Fields list, select the fields you want to group data by,
and click the right arrow button (>).
18 Click Next.
Result: The Template window appears.
With Crystal Reports wizard you can set additional report elements by
presenting specific windows. Make changes if required on each of these
screens and click Next to continue. When you reach the last screen of the
wizard, the Next button is disabled and the Finish button is enabled.
20 Click Finish.
Result: The Crystal Reports window appears.
Example
For example, you can create a user-defined daily report. If you want an interval
report with identical fields, you can copy the daily report and change the
database alias to point to an interval view.
2 In the Selected Tables box, select the database view for which you want to
create an alias name.
3 Press F2
Result: The database view name becomes an editing box.
4 Enter the new alias.
5 Clear the database view to save the new name.
Example: Click on dAgentPerformanceStat under Selected Tables. In the
edit box, enter iAgentPerformanceStat. Clear the database view. The view
is now renamed iAgentPerformanceStat.
The following procedure outlines the steps to complete when selecting the page
orientation for the report.
Restriction
Reports created with this method cannot be imported into the server in Contact
Center Manager.
Applications
If the application supports importing data using ODBC, it is possible to use the
application for report creation. The examples provided in this section cover
Microsoft Access 2002 and Microsoft Excel 2002 only. The steps required may
not be the same for different versions of these applications. Refer to the
application documentation for details about how to import data.
6 In the Logon to Sybase ASE window, enter the Login ID and Password (if
required).
7 Click OK.
Result: The Query Wizard – Choose Columns window appears.
8 Select the columns to include in the report. If you want to filter the data by a
specific column, you must include that column in the query.
9 Click Next.
Result: The Query Wizard – Filter Data window appears.
10 (Optional) Select the columns and choose how to filter the data.
11 Click Next.
Result: The Query Wizard – Sort Order window appears.
15 Click Finish.
Result: The Import Data window appears.
16 Select where to import the data returned from the query. The data can be
imported into a new worksheet or imported into the current worksheet.
When importing data into the current worksheet you can select the starting
row and column for the data.
17 Click OK to import the data.
Result: The Microsoft Excel worksheet appears with the imported data.
4 In the Import window, select ODBC Database from the Files of type drop-
down list.
Result: The Select Data Source window appears.
5 In the Select Data Source window, click on the Machine Data Source tab.
6 Select the ODBC Data Source defined for the server.
7 Click OK.
Result: The Logon to Sybase ASE window appears.
9 Click OK.
Result: The Import Objects window appears.
10 From the Import Objects window, select the tables to import into the
Microsoft Access database.
11 Click OK.
The time required to import the data depends on the amount of data stored
in the selected tables.
Result: The Microsoft Access application window appears with the
imported tables.
12 After the tables are imported, you can now use the features available in
Microsoft Access to format the imported data and to create reports.
Example: For this example, create a new report using the Report Wizard.
13 Select Insert > Report.
Result: The New Report window appears.
17 Select the fields to include on the report from the list of available fields.
18 Click Next.
Result: The Report Wizard – Grouping window appears.
19 (Optional) Select the fields to group the report by from the list of fields. If
groups are not added to the report, proceed to step 20.
a. Click Grouping Options to set the options for the selected groups.
Result: The Report Wizard – Grouping Options window appears.
b. Select the grouping intervals for each of the selected group-level fields.
c. Click OK.
Result: The Report Wizard – Grouping window appears with new
options defined.
20 Click Next.
Result: The Report Wizard – Sort Order window appears.
21 (Optional) Select the fields used to sort the data on the report.
22 (Optional) Select the direction for sorting using the Ascending/
Descending button.
24 Click Next.
Result: The Report Wizard – Layout window appears.
25 (Optional) Select the layout and page orientation for the report.
26 Click Next.
Result: The Report Wizard – Style window appears.
28 Click Next.
Result: The Report Wizard – Finish window appears.
31 Click Finish.
Result: The Report Preview window appears.
32 Use the Design View feature of Microsoft Access to edit the report created
by the Report Wizard.
CAUTION
do move the file, the server cannot find the report, and you must
import it again.
Nortel does not support importing report templates that include references to
other data sources (for example, references to Microsoft Access databases are
not supported). Reports might include data from more than one database view;
however, link these views in the manner documented in this guide (for more
information, see “Linking views” on page 171). The use of unlinked views in
subreports is not supported.
ATTENTION
There is a major architectural change from Crystal Report 8.5
to Crystal Report 9.0 and later versions. From Crystal Report
version 9.0 onwards, Crystal Reports are Unicode compliant.
This is the cause for the delay or failure in the reports being
imported and generated on Contact Center Manager
Administration.
If your custom or user-created report templates created Crystal
Reports 8.5 experience this problem, you must resave the
report templates into Crystal Reports 9.0 or Crystal Reports 10
before importing them to Contact Center Manager
Administration. For a detailed procedure, see “Saving a report
template in Crystal Reports 10” on page 86.
If you use Crystal Report 9.0 software, the procedure is the
same except that the report templates are saved in the Crystal
9.0 version, which is supported by Contact Center Manager
Administration for importing the custom or user-created
reports.
Restrictions
The following restrictions apply:
Reports created in other applications cannot be imported.
Report templates that include references to other data sources (other than
the Contact Center Manager database) cannot be imported.
Limitations
The following limitations apply:
There are limitations in the way in which the reports application handles
user-created reports that contain subreports and use the Timestamp field.
For more information, see “Limitations with subreports” on page 91.
There are limitations with parameter fields in subreports. Define the
parameter fields in the main report for user-created parameterized reports
with subreports. If the report template with subreports does not have
parameter fields defined in the main report, the report cannot be imported
as parameter report to the Contact Center Manager Administration server.
ATTENTION
Do not install Crystal Reports10 software on the Contact
Center Manager Administration server.
2 Copy all your custom report templates created in Crystal 8.5 or earlier
versions in a directory.
Example: Copy reports into directory OldVersionTemplates on the PC
where you installed Crystal Reports 10 software.
3 Create a new directory named Crystal10Templates.
4 Start Crystal Reports 10.
5 Select File > Open.
6 Select the OldVersionTemplates directory.
Result: The OldVersionTemplates directory opens.
7 Select the appropriate report file and click Open.
Result: The report file opens in Crystal Reports.
8 Select File > Save As to save the report template into a Crystal 10 version
template.
9 Navigate to the Crystal10Templates directory.
10 Select Save to save the report template in the Crystal10Templates
directory.
Result: Report is saved in Crystal Reports 10 format.
11 After you save all the required templates, copy the Crystal report templates
to the PC you use for Contact Center Manager Administration browser to
import these report templates.
For a detailed procedure, see “Importing a user-created Crystal Report” on
page 87.
ATTENTION
You cannot import Crystal reports using Report Creation
Wizrd. You must use the Historical Reporting Template
Importing Wizard as indicated in this procedure.
2 Select the Contact Center Manager Server from which you want to run the
report (for example, the Galway server).
Result: The server expands to reveal a choice between public, private, and
any group folders created.
This section describes the process of linking subreport Timestamp fields and
outlines the limitations imposed.
Parameter report
If the report template with subreport has parameter fields defined only in the
subreport, the report cannot be imported as a parameter report. For user-created
report templates with parameter fields, the parameter fields must be defined in
the primary report. Also, the parameter fields defined in the primary fields
prompt for data entry or selection when running the parameter report.
Timestamp field
When you import a report, configure the Timestamp field. With the Timestamp
field you can enter the date and time in the report application used to filter the
data provided on the report. (For configuration reports, a Timestamp field is not
required, because the data is not time-specific).
When reports generate, the Timestamp filter is applied to the main (container)
report and not passed into any subreports. To filter the data on the subreports by
the same Timestamp field as the container report, link the Timestamp field on
each subreport to the Timestamp field in the container report.
Limitations
Because the subreports appear in the details section of the container report, the
subreports generate for each Timestamp field (rather than running for the whole
time interval passed into the main report). This limits the capabilities of the
subreports as each subreport generates reports based on a single database record.
5 In the field link section at the bottom of the window, ensure that the Select
data in subreport based on field checkbox is selected, and that the field
displayed is the correct Timestamp field for the subreport.
Result: The completed window resembles the following example:
Special formulas defined for use with Contact Center Manager include:
@site_id_name the name of the site; to change the site name, see the
Contact Center Manager Supervisor's Guide
For more information about formulas, see the Formula Editor topic in the
Crystal Reports online Help. (This topic is available from the Help Index.
Search for formula editor.)
To improve the readability of the reports and reduce the number of pages
generated, the following options are applied to some of the fields in the report
templates:
suppress
conditionally suppress
hide
conditionally hide
These options are not supported by the Record output format. As a result, when
you output reports to Record format, some data is not exported. To export this
data to Record format, create a new custom report and disable these options.
Static data (row and column headings) cannot be exported to Record format.
3 Copy the template file that you want to change to the folder containing your
custom reports. To do so, follow these steps:
a. Open Windows Explorer.
b. Browse to the path specified in the report footer, and then select the
template file.
c. Choose Edit > Copy.
d. Select the folder containing your custom reports.
e. Choose Edit > Paste to copy the template to this folder.
4 Rename the template file. Choose a name that identifies the purpose of the
new report.
5 Use Crystal Reports to open the new template file.
6 Choose Report > Expert.
Result: The Section Expert dialog box appears.
Section B: Filters
In this section
Overview 100
Creating filters 102
Overview
With the filters feature you select the sites and site resources to include in a
network consolidated report, for example, the Network Consolidated Skillset
Performance Report. Filters are applicable only to networking. After you create
a filter, you can include the filters whenever you generate a report (for more
information about using filters in reports, see the Contact Center Manager
Supervisor's Guide). You can create multiple filters, selecting different sets of
sites and resources for reporting.
Before you can use filters, you must Configure the Network Control Center. For
more information, refer to the Contact Center Manager Network Control Center
Administrator’s Guide.
Creating filters
Log in to the Contact Center Manager Administration using your login account,
and go to the Historical Reporting application to create and use the filters for
Network Consolidated reports.
Creating filters
1 Log into Contact Center Manager Administration.
2 Select Historical Reporting on the Launchpad.
3 Select Filters > Manage Filters.
In the Filters application, you can add new filters and delete any existing
filters that you created. All the existing filters appear in the left tree view.
When you select a filter, the list of nodal Contact Center Manager Servers
and the Network Control Center server appear under the filter. Servers are
disabled if you do not have access rights to them.
When you select an active server on the right, the following resource tabs
appear: Skillset, Application, DNIS, and Route. Click one of the resource
tabs on the horizontal bar to choose the elements to add to the filter. You
can select all elements per element type by selecting the Select All
checkbox. To clear all selected elements, clear the Select All checkbox.
5 Enter the name of filter in the text box in the format New Filter Name.
6 Click Submit.
Result: The new filter appears on the left.
7 Select one of the servers listed on the left. If you do not choose a filter, you
must select a site.
2 To delete many filters at the same time, click on the root node Filters.
Result: All available filters display.
3 Select the filters you want to delete.
4 Click Delete.
Using filters
1 Open the Historical Reporting application. If you are in the Filters
application, select Report > View Report to return to Reports.
2 Select the Network Control Center server.
3 Select the network consolidated report, for example, the Network
Consolidated Skillset Performance Report.
4 Click Selection Criteria.
5 Click Available.
6 Check the network site (or sites) on you want to run the report against.
7 Click Update Selection Criteria to confirm selection of network sites.
8 Click Filters link.
Result: List of filters that you created for the NCC reports appears.
In this chapter
Overview 110
General questions 111
Questions about intervals 114
Questions about agent statistics 116
Questions about activity and Not Ready statistics 123
Questions about skillset and application statistics 125
Questions about DNIS statistics 134
Questions about call-by-call statistics 135
Questions about ACD calls 136
Questions about DN calls 137
Questions about custom reports 139
Questions about Multimedia reporting 141
Questions about Contact Center Outbound campaign reporting 142
Questions about Pull-mode contacts 143
Overview
This chapter contains frequently asked questions about Contact Center Manager
statistics pegging and custom reports. The information in this section can also
help you troubleshoot any problems with your reports.
General questions
However, using identical names makes reports and real-time displays difficult to
interpret. Therefore, Nortel recommends that you use the suffix _sk for skillset
names, to help identify them.
Is there a difference between regular hold time versus hold time spent
while the agent is in conference mode?
When an agent presses the conference key, the agent is placed OnHold until the
conference is complete. HoldTime pegs exactly like regular hold time. The
pegging component does not differentiate between them.
How are Daylight Savings Time and other significant time changes
handled?
Daylight Savings Time (DST) and other significant time changes are handled
differently for summarized historical statistics and event statistics.
Event statistics
Event statistics are handled in much the same way as summarized historical
statistics. The only difference is that a DST event or a significant time change
event is written to each statistic object (for example, Call, Agent and IVR Port)
in each event-based statistic group (for example, CallByCall, Agent Login/
Logout and IVR Port Login/Logout).
When a DST occurs and the time is pushed forward to the next day, the daily
maintenance routines are carried out for the day in which the DST occurred. The
maintenance routines are carried out after the pre-DST statistics are wrapped up
as described for summarized historical statistics.
What time period does the interval from 7:00 to 7:15 represent?
When you generate a report for the interval from 7:00 to 7:15, the data included
in the report includes events occurring between 7:00 and 7:14:59. Events that
occur in the next second after 7:14:59 peg in the 7:15 to 7:30 interval.
What happens when an agent logs on and off during this interval?
The Agent Login report shows agent logon and logoff if you select both days.
If you select today, a message warns that “there is no login for this agent for
today,” and asks you to expand the reporting time frame.
I want to run a report from 11:00 p.m. to 1:00 a.m. Can I run a single
report that spans the midnight time frame?
To use this option with time spanning over midnight, you must submit two
reports: one report for 11:00 p.m. to 12:00 midnight and a second report for
12:00 midnight to 1:00 a.m.
You can run a report that includes all intervals between the start and end time,
even if the time spans over midnight. However, you cannot run the same report
with restricted selections (shift worker’s performance) by selecting the option
Only include intervals between 23:00:00 and 01:00:00 for each day.
For example, you select all intervals from 11:00 p.m. to 1:00 a.m. from 27/08/
2005 to 29/08/2005
If you set the same report interval and click the option Only include intervals
between 23:00:00 and 01:00:00 for each day, you receive the error message:
“The From Time must not be greater than the Until Time”.
9:00:20 The agent places the DN call on hold and answers a Contact
Center Manager call.
9:01:20 The agent releases the Contact Center Manager call and resumes
the DN call.
At the end of this period, the agent timers possess the following values.
LoggedInTime 90 seconds
WaitingTime 10 seconds
DNInCallsTalk Time (Communication Server 2x00/ 80 seconds
DMS) or DNIntInCallsTalkTime (Communication
Server 1000/Meridian 1 PBX)
TalkTime 60 seconds
The total activity time for the agent, as calculated in the following example,
exceeds the agent logon time of 90 seconds.
Total Activity Time <= ACD Talk Time + Break Time + Busy on Miscellaneous
Time + Consultation Time + NACD Talk Time + Not Ready Time + Reserved
Time + Ring Time + Talk Time + Waiting Time + Busy on DN Time
To calculate agent busy time, use the following formula (fields are from the
AgentBySkillset view): TotalStaffedTime – WaitTime
How is WaitTime pegged if the agent puts a DN call on hold and uses
alternate call answer to accept another contact?
In AgentBySkillsetStat, AgentByApplicationStat, Application, and Skillset
views, WaitTime pegs against the previous answered skillset and application for
that agent, if any. WaitTime also pegs as WaitingTime in AgentPerformanceStat
views regardless of whether the agent previously answered a skillset or
application contact.
Call Scenario
10:02 Agent gets queued a At this stage, no wait time pegs because there
skillset sales call and answers is no previous skillset to associate with it. The
answered skillset and application for
subsequent idle/wait time is noted.
10:04 Agent releases call and Idle/wait timestamp noted.
goes idle
10:06 Agent gets queued a Idle/wait time from 10:04 to 10:06, 2 minutes,
skillset support call and pegs to the previous skillset, which is skillset
answers sales. The new answered skillset and
application is noted to use in subsequent idle/
wait time calculation.
10:20 Agent gets queued a Idle/wait time from 10:15 to 10:20, 5 minutes,
skillset support call and pegs to the previous skillset, which is skillset
answers support. The new answered skillset and
application is noted to use in subsequent idle/
wait time calculation.
10:24 Agent makes DN outcall Idle/wait time from 10:23 to 10:24, 1 minutes,
pegs to the previous skillset, which is skillset
support. There is no skillset to note as previous
skillset/application remain the same.
10:32 Agent makes DN outcall Idle/wait time from 10:30 to 10:32, 2 minutes,
pegs to the previous skillset, which is skillset
support. There is no skillset to note as previous
skillset/application remain the same.
10:34 Agent presses ACD This makes the agent available for skillset
agent key calls. Agent is idle so idle/wait timestamp
noted.
10:36 Agent gets queued a Idle/wait time from 10:34 to 10:36, 2 minutes,
skillset sales call and answers pegs to the previous skillset, which is skillset
support. The new answered skillset and
application is noted to use in subsequent idle/
wait time calculation.
10:42 Agent restores DN call Agent goes busy when call is restored,
therefore Idle/wait time from 10:39 to 10:42, 3
minutes, pegs to the previous skillset, which is
skillset sales. There is no skillset to note as
previous skillset/application remain the same.
These actions reset the wait timestamp. This means the wait time is calculated
on these actions and pegs against the previous skillset/application:
CallAnswered
CallPresentedToAgent
AgentBusy
AgentNotReady
ACDCallAnswered
NACDCallAnswered
DNOutCallInitiated (handling for DNInCallAnswered is not required as the
Agent Busy event always precedes it and thus pegs the wait time).
The Agent Idle message (when the agent goes into idle state) is used to set the
idle/wait timestamp.
minus
Agent Idle event timestamp
Call scenario
A call can peg more than once if it is returned to the queue and then presented to
another agent.
With the call force option, why does RingTime peg for calls?
When you configure the Call Force option, you can set a Call Force Timer. This
timer indicates wait time after an agent becomes available before presenting the
agent with a call. During this time, the caller hears ringing, but the agent is
unaware of the waiting call. This time pegs as RingTime.
ATTENTION
If agents press Not Ready during this period, the call is sent to
the back of the queue and loses its priority.
Nortel recommends that you set the Call Force Timer to 0, and use the Break
Timer to provide agents with a break between calls.
When an agent is in the Not Ready state, the agent can account for time spent in
this state using Not Ready reason codes. The codes entered by the agent identify
the reason why the agent is in the Not Ready state.
Not Ready reason codes are activated by pressing the Not Ready key. However,
unlike activity codes, an agent must be in the Not Ready state before attempting
to enter a Not Ready reason code.
To prevent coffee break (Not Ready) time from accumulating in the Agent By
Skillset/Agent by Application Reports, after completing the call, the agent:
1. Presses the Not Ready key.
2. Presses Not Ready again.
3. Presses Not Ready and enter the Not Ready reason code.
This procedure stops the accumulation of post-call processing time, and the true
Not Ready time pegs against the agent activity (coffee break). The Not Reason
code at step 3 is optional. If it is not entered, post-call processing time still stops.
How does Contact Center Manager peg calls that use IVR transfers?
If you use Meridian Mail, CallPilot, Nortel Media Processing Server, or another
IVR system that uses a two-stage transfer (IVR Transfer) rather than a hook-
flash transfer, the CallsOffered statistic pegs each time the IVR system transfers
a call.
In this case, although CallsOffered is 1000, the number of calls from outside
callers is actually 600.
If a call receives the GIVE IVR treatment and the messaging system gives a
choice to leave a message or hold, and the caller chooses to leave a message and
hang up, the following statistics are recorded:
ApplicationStat views: CallsOffered, CallsAbandoned, CallsGivenIVR,
IVRCallsAbandoned, and IVRTerminated statistics are incremented.
IVRStat views: CallsAnswered, CallsOffered, and IVRAbandoned
statistics are incremented. IVRCompleted is not affected. IVRCompleted is
incremented only if call control returns to the application script after IVR
treatment, for example, upon return from a GIVE IVR with recorded
announcement command.
IVRPortStat views: CallsAnswered is incremented.
Why do calls that receive the Route Call treatment peg as Routed
even though they return to the script for further processing?
When a call receives the Route Call treatment, it is considered terminated by
Contact Center Manager (responsibility for the call is handed over to the
destination system). If the call returns to Contact Center Manager Server, it is
treated as a new call, even though it maintains its call ID.
In the skillset statistics, the time delay until calls are abandoned or answered is
calculated from the time the call is queued to the skillset. It does not include the
time required for the caller to navigate menus and listen to recorded
announcements, or time spent processing the script in the primary or secondary
applications, if any.
In previous versions, these delays are calculated from the time the call entered
the master script. Therefore, for a given application service level threshold,
CallsAnsweredAfterThreshold and CallsAbandonedAfterThreshold application
statistics have smaller values in this version than in previous versions, thus
leading to inflated application service levels.
For example, if you build the report against the iApplicationStat table, this
report must contain the following custom formula:
NumberVar TotalCallsapp:=0;
NumberVar CallsDelayedapp:=0;
TotalCallsapp:=Sum({iApplicationStat.CallsAnswered},
{iApplicationStat.ApplicationID}) +
Sum({iApplicationStat.CallsAbandoned},
{iApplicationStat.ApplicationID});
CallsDelayedapp:=Sum({iApplicationStat.CallsAnsweredAftThr
eshold}, {iApplicationStat.ApplicationID}) +
Sum({iApplicationStat.CallsAbandonedAftThreshold},
{iApplicationStat.ApplicationID});
//Service level percent
If you change the name of an application, data from before the name change
continues to be associated with the old name. However, this name no longer
appears on reports. Therefore, data from before the time of the name change
does not appear on reports.
WAIT 6
IF CDN = test_cdn THEN
EXECUTE SCRIPT Sales_App
END IF
and the primary script (Sales_App) can include the following commands:
WAIT 3
QUEUE TO SKILLSET Sales_Sk
WAIT 2
REMOVE FROM SKILLSET Sales_Sk
If a call arrives on the test CDN and agents are available in Sales_Sk, the
application statistics show an average delay of at least 3 seconds (depending on
the timing queue), and the skillset statistics show a delay of 0 to 2 seconds. Time
spent in the Master script is not included in the application statistics.
If the contact queues to multiple skillsets through separate script commands (or
through separate scripts), the answering skillset is the one in which the contact
first queued. Thus the CallsAnsweredDelay delay statistic measurement always
includes the longest queuing time a contact is queued to multiple skillsets.
How does Contact Center Manager peg calls offered in the Skillset
Statistics if a call is returned to queue?
If a call is returned to queue due to timeout or the agent returns the call to queue,
the calls offered for the skillset does not increment again.
How do I track call volume and work time for DNIS numbers?
This information is available in the DNISStat view, and in the DNIS Statistics
report.
For more information about Call by Call Events, see “Call events” on page 594.
However, the server can provide the following statistics for ACD calls presented
to a phoneset that is acquired by the server:
the number of ACD calls answered
the number of ACD calls conferenced and transferred
the amount of time spent on ACD calls
You can also map each ACD-DN to a skillset. If you map each ACD-DN to a
skillset, NACD calls peg against this skillset. All calls to that ACD-DN that are
answered on a phoneset acquired by the server peg against the skillset. (If you
do not map an ACD-DN, calls to that ACD-DN peg against the Default_ACD
skillset.)
Example 1
Agent goes into Not Ready PCP pegs against the Sales
Skillset
Example 2
Example 3
With Crystal Reports, can I create a report that accumulates totals for
a month?
As long as the data is still stored in the database, you can generate a report that
accumulates the total up to the current date.
For example, you want to generate a weekly report, and have the total
accumulate for that month only. To do so, set the data range start time to the
beginning of the month, and the end time to the time when you generate the
report. The total value for the week 3 report consists of the cumulative total for
that month up to week 3, and so on.
Can I create a report that contains statistics from more than one
view?
Data from multiple views are linked into one report by using the specified
linkage keys in each view. See section “Linking views” on page 171.
Why does my custom report print in a layout different from what I set
when I created the report?
When you create a report, the default page orientation matches the default page
orientation for the printer. If you accept the default page orientation for the
report, and then later change the printer orientation, there is a possibility that the
report will use the printer orientation. For example, the default orientation for
the report and the printer is portrait. If you later change the printer orientation
(on your desktop) to landscape, it is possible that when you print your report, the
report orientation will be landscape. To avoid this scenario, Nortel recommends
when you create the report, that you select a page orientation for the report that
is different from that of the printer. The following table lists possible scenarios.
To change the printer default orientation, you must make the change in the
printing preferences of the printer, not in Crystal Reports.
For more information, see “Setting the page orientation for a report” on page 68.
The contact is pegged against the Agent Queue To dummy skillset for this
contact type.
In this chapter
Overview 146
Access rights by view 156
Section A: Summarized historical statistics 165
Section B: Event statistics 345
Section C: Configuration views 373
Section D: Access and Partition Management views 499
Overview
The Contact Center Manager database is an open database. You can access the
data in this database with any SQL- or ODBC-compliant application. You can
use the data in many ways, including the following:
Import it into a spreadsheet for manipulation.
Import it into your corporate database.
Develop customized reports using Report Creation Wizard, Crystal
Reports, or another reporting application.
Types of data
This chapter describes the following types of data:
Summarized historical statistics—statistics accumulated over a period of
time (15-minute interval, daily, weekly, or monthly).
Event statistics—statistics that report each occurrence of an event.
Configuration data—information about the configuration of your server.
Resource usage
When you generate reports or export data from the database, you use system
resources, including server CPU and LAN bandwidth. To calculate resource
requirements for a specific application, use the Capacity Assessment Tool
(CapTool) application.
Default applications
There are five default applications that ship with Contact Center Manager:
Master_Script, Network_Script, ACD-DN, NACD-DN, and System. In some
views, activity code statistics peg against these default applications.
Application Description
Database views
The following new database views are available.
type int
ACD_QueueStatus
CDNStat type varchar, length 255 old type varchar, old length 10;
URI new type varchar, new length 30
CDN
DNISStat type varchar, length 255 old type smallint, new type int
URI MaxAbandonedDelay
MaxAnsweredDelay
type tinyint, length 1
Type
type varchar, length 30
NetworkCDN
type int
ACD_QueueStatus
The following tables lists the access rights needed to run reports, depending on
what view you are accessing.
Historical reports
The following table lists the access rights needed to run historical reports.
Run these reports run from the Network Control Center server.
You must configure users with these permissions on the Network Control Center
server and all Contact Center Manager Servers associated with the Network
Control Center server.
User permissions for the these views work on Contact Center Manager Server
6.0 only. If the Network Control Center server has a Symposium Call Center
Server 5.0 server configured, the users do not possess adequate permissions to
retrieve data from these views.
Event reports
The following table lists the access rights needed to run event reports.
Configuration reports
The following table lists the access rights needed to run configuration reports.
Skillset View
In this section
Overview of summarized historical statistics 166
Types of views 168
Linking views 171
Types of contacts 176
ActivityCodeStat views 188
AgentByApplicationStat views 197
AgentBySkillsetStat views 208
AgentPerformanceStat views 220
ApplicationStat views 249
CDNStat views 275
DNISStat views 280
IVRPortStat views 288
IVRStat views 293
LicenseStat views 298
NetworkInCallStat views 300
NetworkOutStat views 308
RANMusicRouteStat views 316
RouteStat views 319
SCCSDBSpace views 323
SkillsetStat views 325
TrunkStat views 340
These statistics are used in standard and user-defined reports. You can include
these statistics in your Report Creation Wizard-created and user-created reports.
You can enable or disable data collection for one of these groups at any time
while the system runs.
The number and type of statistics you choose to collect affects the amount of
disk space required for the database.
Storage duration
When you configure the Historical Statistics Collection, you can choose how
long to store different types of statistics. The duration you choose determines the
amount of disk space required for the database.
For more information about configuring the Historical Statistics Collection, see
the Contact Center Manager Administrator's Guide.
Types of views
Interval views
The server accumulates interval statistics for 15 minutes. The statistics
accumulate in the server RAM until the end of the 15-minute interval. The
server then creates a new record in the database for each entity (or combination
of entities). The new record contains the summarized statistics for that entity for
that interval. (The statistics collected depend on the type of entity.) The
Timestamp field of the new record is in the format YYYY/MM/DD
HH:MM:00:00, where MM is 00, 15, 30, or 45.
For example, to record agent by skillset statistics, the server creates a record for
each skillset for which an agent answered calls during the interval just ended.
ATTENTION
Interval statistics are not available until after the interval ends.
If you shut down the server without properly shutting down
the Contact Center Manager services, data for the current
interval is lost.
Daily views
Immediately after the end of the business day (after 12:00 midnight), the server
sums all of the interval records for the day, and creates corresponding daily
records. The Timestamp field of the daily records is in the format YYYY/MM/
DD 00:00:00:00.
Current day statistics are not available until the beginning of the next day (after
12:00 midnight).
Weekly views
After the end of the first day of the week (after 12:00 midnight), the server
creates weekly records that contain each of the daily totals. After the end of each
subsequent day in the week, the server adds the day total to the fields in the
weekly records. The Timestamp field of the weekly records is in the format
YYYY/MM/DD 00:00:00:00, where DD is the first day of the week.
Weekly statistics are not available until the beginning of the next week. You can
configure the first day of the week in the Historical Statistics Configuration.
Monthly views
Immediately after the end of the first day of the month (after 12:00 midnight),
the server creates monthly records that contain each of the daily totals. After the
end of each subsequent day in the month, the server adds the day total to the
fields in the monthly record. The Timestamp field of the monthly records is in
the format YYYY/MM/DD 00:00:00:00, where DD is 01.
Monthly statistics are not available until after 12:00 midnight of the first day in
the next month.
daily immediately after the end of the day (after 12:00 midnight)
weekly immediately after the end of the week (after 12:00 midnight
on the first day of the next business week)
monthly immediately after the end of the month (after 12:00 midnight
on the first day of the next month)
Linking views
To generate customized reports that combine statistics from two or more views,
use linkages between database views. Linkages are also known as relations or
joins. You can combine only the views that share a linkage key.
If several views use the same linkage key, you can create a report combining all
of those views.
If the SQL queries perform calculations such as Max, Min, Sum, or Avg, use the
Group By statement to ensure that the joined view does not contain duplicated
data. When using the Group By statement, specify linkage keys only as the
fields on which to group.
If you combine views that do not share a linkage key, or if you group by a field
that is not a linkage key, the resulting statistics are meaningless and misleading.
When comparing linkage key values in the SQL where clause, use left outer join
syntax. This ensures that rows in the left side view, which do not have
corresponding linkage key values in the right side view, are not left out of the
resulting joined view.
Example
The administrator of the BestAir contact center wants to create a report
containing the following statistics for each agent:
CallsAnswered
ShortCallsAnswered
PostCallProcessingTime
AgentPerformanceStat view
AgentByApplicationStat view
From the AgentPerformanceStat view, you can see that the number of
CallsAnswered for UserID 6709 is 8. The AgentByApplicationStat view tells
you that six of these calls are answered for Application ID 10000, and two calls
are answered for ApplicationID 10001.
Proper join
To obtain correct grand totals, use the following SQL query:
(select a.Timestamp, a.UserID, max(a.CallsAnswered),
max(a.ShortCallsAnswered), sum(isnull(b.CallsAnswered,0)),
sum(isnull(b.PostCallProcessingTime,0))
from iAgentPerformanceStat a,
iAgentByApplicationStat b
where a.Timestamp *= b.Timestamp
and a.UserID *= b.UserID
group by a.Timestamp, a.UserID
)
A left outer join of the views is used to ensure that all rows in the
iAgentPerformanceStat view are included in the result, even if no row in
iAgentByApplicationStat corresponds to the linkage key values. The isnull
function is used to provide a default value of 0 in this case. Without the isnull
function, the sum function could return NULL values, causing the query to fail.
The following table shows the resulting statistics for the interval beginning
13:00 on 31/10/2005.
PostCall
User Calls ShortCalls Calls Processing
Timestamp ID Answered Answered Answered Time
This query uses the Timestamp and UserID fields as linkage keys for the two
views. It creates a record for each unique combination of Timestamp, UserID,
and ApplicationID in iAgentByApplicationStat. For each record in
iAgentByApplicationStat, it finds the record with a matching UserID and
Timestamp in iAgentPerformanceStat. The new record contains the Timestamp
and UserID, the CallsAnswered and ShortCallsAnswered fields from
iAgentPerformanceStat, and the CallsAnswered and PostCallProcessingTime
fields from iAgentByApplicationStat.
The following table shows the resulting statistics for the interval beginning at
13:00 on 31/10/2005.
PostCall
User Application Calls ShortCalls Calls Processing
Timestamp ID ID Answered Answered Answered Time
Each entry contains two CallsAnswered fields. One field contains the calls
answered by the agent; the other field contains the calls answered by the agent
for the application. Grand totals of the two CallsAnswered fields produce the
following results:
8 + 8 + 5 = 21
6 + 2 + 5 = 13
The second total is correct (13). The first total counts CallsAnswered twice for
agent 6709, because it multiplies the agent's total CallsAnswered by the number
of applications for which the agent answered calls. The result is correct only if
each agent answered calls for only one application.
Types of contacts
The contact types described in this section are referred to in the descriptions of
database views. Contacts are categorized by media—voice contact types and
multimedia (non-voice) contact types.
When the Network Skills Based Routing (NSBR) option is available, some
contact types are also categorized by their network scope—local contacts and
NSBR contacts.
Unless otherwise specified, NSBR contacts include both incoming and outgoing
contacts.
In this document, when the terms calls and contacts are used together, calls
refers exclusively to voice calls and contacts refers to multimedia contacts.
Contacts used alone refers to all contact types (voice and multimedia), and calls
used alone usually refers to voice calls only.
In this document the term outbound is used to refer to Contact Center Outbound
contacts. Do not confuse outbound with the term outgoing, which refers to the
contact routing direction and can apply to voice and multimedia contact types,
including outbound.
Voice contacts
Voice contacts include:
Contact Center Manager calls
ACD calls
NACD calls
DN calls
SIP voice calls
Contact Center Manager calls are also described as local or Network Skills
Based Routing (NSBR) calls.
Local Contact Center Manager calls are calls that arrive at a CDN configured as
a local CDN. NSBR Contact Center Manager calls are calls that arrive at a CDN
configured as a network CDN (that is, incoming NSBR Contact Center Manager
calls), or calls offered to a remote site by the local server (that is, outgoing
NSBR Contact Center Manager calls).
Unless otherwise specified, Contact Center Manager calls include both local
Contact Center Manager calls and NSBR Contact Center Manager calls.
Tracking
Contact Center Manager calls are tracked from the time a call notification
message arrives from the switch until one of the following occurs:
the call is abandoned
the call is routed to the default DN
the call is given Force Disconnect command
the call is given Busy treatment
the call is given Overflow treatment
the call is given Queue to NACD treatment, and then abandoned
the call is given Queue to NACD treatment, and then answered and
released
the call is given Queue to Network Skillset treatment, and then abandoned
the call is given Queue to Network Skillset treatment, and then answered
and released
the call is given Queue to Network Skillset treatment, and then reaches a
non-ISDN trunk
the call is given Queue to Network Skillset treatment, and then treated by
the Network script at the remote site
the call is released
the call is transferred or conferenced out by an agent or resource
ACD calls
ACD calls are calls to an Automatic Call Distribution Directory Number (ACD-
DN) that are presented to a phoneset acquired by Contact Center Manager. ACD
calls are not applicable in SIP-enabled contact centers.
Tracking
For ACD calls, the server does not record information about call activity on the
switch. ACD calls are tracked from the time they are answered at a phoneset
acquired by Contact Center Manager. Therefore, the server does not record the
following statistics for ACD calls:
calls offered
calls waiting
calls abandoned (and abandon delay)
calls returned to queue
NACD calls
NACD calls are ACD calls that arrived from the network through a Network
ACD DN (ACD DN with a defined Day/Night network routing table) and are
presented to an agent phoneset acquired by Contact Center Manager. NACD
calls are not applicable in SIP-enabled contact centers.
Delay and abandon statistics are not available for NACD calls.
Tracking
For NACD calls, the server does not record information about call activity on
the switch. NACD calls are tracked from the time they are answered at a
phoneset acquired by Contact Center Manager. Therefore, the server does not
record the following statistics for NACD calls:
calls offered
calls waiting
calls abandoned (and abandon delay)
calls returned to queue
DN calls
DN calls are presented to or originate from the DN key of a phoneset that is
acquired by Contact Center Manager. The server pegs DN calls primarily in the
AgentPerformanceStat view. AgentByApplicationStat, AgentBySkillsetStat,
ApplicationStat, and SkillsetStat views do not include DN calls, except for
DNOutIntTalkTime and DNOutExtTalkTime. ActivityCodeStat views do not
include DN calls.
Tracking
DN calls are tracked from the time they are answered. The server does not track
activity for incoming DN calls automatically redirected by the switch, including:
hunting
call forward-busy
call forward-all calls
call forward-no answer
For the Communication Server 2x00/DMS switch, only one DN key can be
configured and monitored by Contact Center Manager. Activity on other DN
keys is not reported.
For SIP-enabled contact centers, only one DN key (SIP Line Address) can be
configured and monitored by Contact Center Manager. Activity on other DN
keys is not reported.
SIP voice calls are considered local calls. NSBR is not supported for SIP voice
calls.
Tracking
SIP voice calls are tracked from the time a SIP INVITE message arrives from
the call server until one of the following occurs:
the call is abandoned
the call is routed to the default RAN
the call is given Force Disconnect command
the call is given Busy treatment
the call is given Overflow treatment
the call is released
the call is transferred or conferenced out by an agent or resource
Multimedia contacts
Multimedia contacts include:
Contact Center Multimedia contacts
Contact Center Outbound contacts
SIP video contacts
Web_Communication
Contact Center Multimedia contacts are considered local contacts. NSBR is not
supported for Contact Center Multimedia contacts.
Tracking
Contact Center Multimedia contacts are tracked from the time a contact is
accepted into Contact Center Manager by the Contact Center Multimedia server
until one of the following occurs:
the contact is routed to the default Route Point
the contact is given Force Disconnect command
the contact is closed
the contact is transferred out by an agent or resource
Contact Center Outbound contacts are considered local contacts. NSBR is not
supported for Contact Center Outbound contacts.
Tracking
Contact Center Outbound contacts are tracked from the time a contact is injected
into Contact Center Manager by the Contact Center Outbound server until one
of the following occurs:
the contact is routed to the default Route Point
the contact is given Force Disconnect command
the contact is cancelled by the Outbound Campaign Management Tool
the contact is closed
the contact is transferred out by an agent or resource
SIP video contacts are considered local contacts. NSBR is not supported for SIP
video contacts.
Tracking
SIP video contacts are tracked from the time that a SIP INVITE message arrives
from the video contacts until one of the following occurs:
the contact is abandoned
The default skillset naming prefixes and the contact types associated with them
are listed in the following table.
EM_ EMail
OB_ Outbound
WC_ Web_Communication
VI_ Video
Contact Center Manager enforces that scripts only queue contacts of the correct
type to appropriate skillsets. For reporting purposes, the contact type display
name pegs in the skillset statistics views along with every skillset statistic.
Skillset statistics are selected and grouped by contact type in custom reports and
Report Creation Wizard to provide per-contact type summaries.
ATTENTION
In the case of applications, use of the naming convention is
useful only for the purpose of selecting and grouping statistics
by contact type. Contact Center Manager does not enforce that
an application only handles contacts of the type indicated by
its naming prefix. It is possible that inappropriately named
applications handle contacts of the wrong type. In this case,
application statistics selected or grouped by contact type are
incorrect.
ActivityCodeStat views
Activity code statistics identify the type of contacts handled by the agent, as well
as provide detailed information about how Not Ready time is spent. This
statistic provides information that can be used to monitor agents’ work and time
distribution within a work day. The linkage of activity code, agent, and
application provides another means to measure agents’ performance.
Activity code statistics include statistics for Not Ready reason codes. Agents
enter these codes when they go into Not Ready state.
For more information about Not Ready reason codes, see “Questions about
activity and Not Ready statistics” on page 123.
On the Communication Server 2x00/DMS switch, agents cannot use the Line of
Business (LOB) key while they are conferenced with another agent.
For the interval in which an agent goes into Not Ready state, if this is the first
Not Ready reason code entered for the agent, the Not Ready reason time starts
when the agent goes into Not Ready state. For subsequent Not Ready reason
codes entered during that interval, and for subsequent intervals, Not Ready
reason time starts when the agent enters the Not Ready reason code.
Not Ready reason time ends when:
the agent enters a new Not Ready reason code
the agent goes into Ready state
the agent logs off
Requirements
Fulfill the following requirements:
Define activity codes and Not Ready reason codes on the server in Contact
Center Manager. If you do not do this, activity codes statistics are collected,
but ActivityCodeName is blank.
Configure the server to collect activity code and Not Ready reason code
statistics (see the Contact Center Manager Administrator’s Guide).
Statistics are collected for all activity codes and Not Ready reason codes;
you cannot configure the system to collect statistics for selected codes.
Database views
Activity code statistics use the following views:
iActivityCodeStat
dActivityCodeStat
wActivityCodeStat
mActivityCodeStat
Field descriptions
The field descriptions for this view are described in this section.
ActivityCode
Description: A unique identifier for an activity code.
Type: varchar
Length: 32
ActivityCodeName
Description: The name of the activity code.
Type: varchar
Length: 30
ActivityTime
Description: The total time spent on this activity by this agent.
Triggers: Activity time begins when an agent:
answers a call or accepts a multimedia contact
presses the Activity key and enters a code
Activity time ends when the agent enters another activity code, when the call
ends, or when the multimedia contact is closed.
ActivityShortName
Description: Displays the short name for the Not Ready reason code, which is
displayed in Contact Center Manager Administration.
Type: varchar
Length: 30
AgentGivenName
Description: The given or first name of the agent.
Type: varchar
Length: 64
AgentLogin
Description: The numeric ID the agent uses to log in to the phoneset or agent
desktop.
Type: varchar
Length: 16
AgentSurName
Description: The family or surname of the agent.
Type: varchar
Length: 64
Application
Description: The name of the application is the same name as the primary
script.
Pegging: The following table shows how activity code statistics peg against
applications.
Statistics for Not Ready reason codes peg against the System_Application.
For more information about default applications mentioned in this table, see
“Default applications” on page 148.
Type: varchar
Length: 30
ApplicationID
Description: A unique number assigned by the server to identify the application
when the application is defined. This field is used for linking tables in data
queries.
Type: int
Length: 4
Occurrences
Description: The number of times the agent entered this activity code. An agent
can enter multiple activity codes (up to three for a Communication Server 2x00/
DMS switch) during a single call.
Contact Center Manager Server pegs a Not Ready reason code occurrence when
an agent:
goes into Not Ready state
presses the Activity key on the phoneset and enters a Not Ready reason
code or uses the agent desktop to enter a Not Ready reason code while in
Not Ready state
Pegging: See “Activity code pegging” on page 189 and “Not Ready reason
code pegging” on page 189.
Type: int
Length: 4
Site
Description: The configured name of this Contact Center Manager site.
Type: varchar
Length: 30
SiteID
Description: A unique number assigned by the system to identify this Contact
Center Manager site. The assigned SiteID remains unique over time even if a
configured site is deleted and another one is added with the same name. The
SiteID can be used in custom reports to identify statistics applicable to this site.
Time
Description: The time (in 24-hour HH:MM format) when the data is pegged by
the system.
Type: char
Length: 5
Timestamp
Description: The date and time when the data is pegged by the system. For
more information about the format of the Timestamp in interval, daily, weekly,
or monthly views, see “Overview of summarized historical statistics” on page
166. This field is used for linking tables in data queries.
Type: smalldatetime
Length: 4
UserID
Description: A unique number assigned by the server to identify the agent when
the agent is added. This field is used for linking tables in data queries.
Type: binary
Length: 16
The following table shows the statistics groups you can link activity codes to, as
well as the data fields used as linkage keys.
Specify all these fields as your linkage key, in the specified order.
AgentByApplicationStat views
For each application included in the report, the report lists summarized agent
performance information for each agent that handled a contact from that
application. You can use these statistics to monitor an agent’s contribution to an
application.
Statistics peg against a given combination of agent and application only for
those intervals in which a contact is answered by the specific agent and
processed by the specific application. Except for DNOutExtTalkTime and
DNOutIntTalkTime, these statistics do not include DN calls.
Definition: Application
An application is a logical entity that represents a script for reporting purposes.
The Master script and each script it references (that is, each primary script) is
represented by an application with a name that is the same as the script name.
Application pegging
The following table shows how contacts peg.
Requirements
Configure the server to collect agent by application code statistics (see the
Contact Center Manager Administrator’s Guide). Statistics are collected for all
agents; you cannot configure the system to collect statistics for selected agents.
Database views
Agent by application statistics use the following views:
iAgentByApplicationStat
dAgentByApplicationStat
wAgentByAppliationStat
mAgentByApplicationStat
Field descriptions
The field descriptions for this view are described in this section.
AgentGivenName
Description: The first or given name of the agent.
Type: varchar
Length: 64
If an agent record is deleted because the data is already collected, the agent name
is blank.
AgentLogin
Description: The numeric ID the agent uses to log in to the phoneset or agent
desktop.
Type: varchar
Length: 16
AgentSurName
Description: The last or surname of the agent.
Type: varchar
Length: 64
If an agent record is deleted because the data is already collected, the agent name
is blank.
Application
Description: The name of the application handling the contact when the agent
answered or accepted it.
Pegging: See “Application pegging” on page 197.
Type: varchar
Length: 30
ApplicationID
Description: A unique number assigned by the server to identify the application
when the application is defined. This field is used for linking tables in data
queries.
CallsAnswered
Description: The number of contacts, excluding DN calls, answered or
accepted by an agent for this application.
Pegging: Voice calls peg upon answer, and multimedia contacts peg upon
acceptance.
Type: int
Length: 4
CallsConferenced
Description: The number of local Contact Center Manager calls, incoming
NSBR calls, ACD calls, and NACD calls in this application that an agent
conferenced.
Triggers:
Type: int
Length: 4
CallsOffered
Description: The number of local Contact Center Manager calls, SIP voice
calls, local multimedia contacts, and incoming NSBR contacts handled by this
application and presented to this agent. This statistic includes contacts returned
to queue and contacts abandoned during presentation.
CallsReturnedToQ
Description: The number of local Contact Center Manager calls, SIP voice
contacts, local multimedia contacts, and incoming NSBR contacts handled by
this application that the agent returned to the skillset queue for reasons other
than timeout.
Pegging: A voice call is returned to the queue if the agent enters another state
(for example, if the agent presses the Not Ready or DN key) while the call is
presented. This statistic pegs when the agent state changes. A multimedia
contact returns to the queue if the agent rejects it using the Reject button.
Type: int
Length: 4
CallsReturnedToQDueToTimeout
Description: The number of local Contact Center Manager calls, SIP voice
calls, multimedia contacts, and incoming NSBR contacts handled by this
application that returned to the skillset queue automatically while in alerting
state, after a wait greater than or equal to the answering timeout for this agent as
defined in the call presentation class to which the agent belongs.
Type: int
Length: 4
CallsTransferred
Description: The number of Contact Center Manager calls, SIP voice calls,
ACD calls, NACD calls and SIP video contacts transferred by this agent for this
application.
Pegging: This statistic is pegged when the transfer is completed—when the
transfer key is invoked for the second time.
Type: int
Length: 4
ConsultTime
Description: The total time an agent spends in consultation while handling
contacts for this application. Consultation time occurs during a consult transfer
if the caller disconnects and the answering agent remains on the line.
Triggers: Consult time starts when the customer releases the call and ends when
the consult call is released.
Type: int
Length: 4
ContactType
Description: The type of contact determined by the name of this application.
This applies to SIP-enabled contact centers or if Contact Center Multimedia or
Contact Center Outbound is installed and this application name begins with one
of the configured prefixes as described in “Associating contact types with
applications and skillsets” on page 186. If the skillset does not have a prefix, the
contact pegs as voice.
DNOutExtTalkTime
Description: Communication Server 1000/Meridian 1 PBX switch only. The
total time spent in outgoing external DN calls, including hold time (see “Internal
versus External DN calls” on page 181 for a definition of external DN calls).
This statistic does not include the time spent on the DN outcall part of a Contact
Center Outbound contact.
Where multiple DN keys are configured on agent phonesets, talk time can
exceed 15 minutes (900 seconds) per interval. Talk time exceeding 15 minutes
per interval occurs when an agent makes one DN call, places that call on hold,
and then makes another DN call.
Triggers: Talk time begins when the call is answered and ends when the caller
disconnects or the agent releases the call.
Pegging: DNOutExtTalkTime pegs against the last application for which the
agent handled a contact during this logon.
Type: int
Length: 4
DNOutIntTalkTime
Description: Communication Server 1000/Meridian 1 PBX only. The total time
spent on outgoing internal DN calls, including hold time (see “Internal versus
External DN calls” on page 181 for a definition of external DN calls). This
statistic does not include the time spent on the DN outcall part of a Contact
Center Outbound contact.
Where multiple DN keys are configured on agent phonesets, talk time can
exceed 15 minutes (900 seconds) per interval. This occurs when an agent makes
one DN call, places that call on hold, and then makes another DN call.
Triggers: Talk time begins when the call is answered and ends when the caller
disconnects or the agent releases the call.
Pegging: DNOutIntTalkTime pegs against the last application for which the
agent handled a contact during this logon.
Type: int
Length: 4
HoldTime
Description: The total time an agent spends on hold during Contact Center
Manager calls for this application.
Triggers: Hold time begins when the agent places a Contact Center Manager
call in the Hold state. Hold time ends when the call resumes or the call
terminates.
Pegging: Hold time pegs at the end of the interval (for calls that are active at the
end of the interval), and when the call terminates.
Type: int
Length: 4
PostCallProcessingTime
Description: This data is the total time an agent spends performing post-contact
processing. Normally, an agent uses this time to complete any work related to
the contact just completed, such as filling in forms or filing papers.
Triggers: Post-call processing time begins when an agent presses Not Ready
after releasing any contact, except DN calls, and ends when the agent presses
Not Ready again, places or receives a DN call, or logs out.
Post Call Processing Time is calculated for the first Not Ready period after a
contact is closed. If the agent enters another state after the call (for example, by
answering or receiving a DN call or logging out of the skillset), and then enters
Not Ready state, the Not Ready time does not peg against
PostCallProcessingTime. Also, if the agent interrupts the Not Ready period to
enter another state, and then returns to Not Ready state, the second Not Ready
period does not peg against PostCallProcessingTime.
Pegging: This statistic pegs against the last application for which the agent
handled a contact.
Type: int
Length: 4
RingTime
Description: The total time an agent spends in the Ringing state before
answering a Contact Center Manager call or SIP voice call in this application.
Also the total time spent in the Alerting/Presenting state before accepting a
multimedia contact in this application.
Site
Description: The configured name of this Contact Center Manager site.
Type: varchar
Length: 30
SiteID
Description: A unique number assigned by the system to identify this Contact
Center Manager site. The assigned SiteID remains unique over time even if a
configured site is deleted and another one is added with the same name. The
SiteID can be used in custom reports to identify statistics applicable to this site.
TalkTime
Description: The total time this agent spends handling contacts, excluding DN
calls, after the contact is answered or accepted in this application. This statistic
includes hold time.
Triggers:
For voice calls, talk time begins when the agent answers the call.
For the Communication Server 1000/Meridian 1 PBX switch, talk time
ends when the caller disconnects or the agent releases or transfers the call.
For the Communication Server 2x00 switch, talk time ends when the agent
releases or transfers the call.
For multimedia contacts, talk time begins when the agent accepts the
contact and ends when the agent closes or transfers the contact.
For Contact Center Outbound contacts, talk time begins when the agent
accepts the contact, includes the time the agent is on the DN call, and ends
when the agent releases the DN call and closes the contact.
Type: int
Length: 4
Time
Description: The time (in 24-hour HH:MM format) when the data is pegged by
the system.
Type: char
Length: 5
Timestamp
Description: The date and time when the data is pegged by the system. For
more information about the format of the Timestamp in interval, daily, weekly,
or monthly views, see “Overview of summarized historical statistics” on page
166. This field is used for linking tables in data queries.
Type: smalldatetime
Length: 4
UserID
Description: A unique number assigned by the server to identify the agent when
the agent is added. This field is used for linking tables in data queries.
Type: binary
Length: 16
WaitTime
Description: The total time this agent spends waiting for a contact after
releasing a voice call or closing a multimedia contact handled by this
application.
Triggers: Wait time begins when the agent enters the idle state. For example, if:
the agent releases a voice call or multimedia contact, and the agent's call
presentation class is not configured for Break time or Variable Wrap.
the agent's Break or Variable Wrap timer elapses after a contact is released
or closed.
the agent presses the Not Ready key a second time after entering Not Ready
state.
WaitTime ends when the agent leaves the Idle state. If the agent handles another
contact from the same application as the most recently handled contact,
WaitTime resumes against that application when the agent returns to the Idle
state. If the agent handles a contact from a different application than the most
recently handled contact, WaitTime begins against the new application when the
agent returns to the Idle state.
For more information, see “How is WaitTime pegged if the agent puts a DN call
on hold and uses alternate call answer to accept another contact?” on page 117.
Pegging: WaitTime pegs against the last application for which the agent
handled a contact during this login. If the agent has not yet handled a contact
associated with an application, WaitTime is not pegged.
Type: int
Length: 4
The following table shows the statistics groups that agent by application
statistics can link to, as well as the data fields used as linkage keys.
Specify all these fields as your linkage key, in the specified order.
AgentBySkillsetStat views
Only contacts queued to a skillset are included in these statistics. (If a skillset is
mapped to an ACD DN, calls to that ACD DN are included.) Except for
DNOutExtTalkTime and DNOutIntTalkTime, these statistics do not include DN
calls.
Requirements
Configure the server to collect agent by skillset statistics (see the Contact Center
Manager Administrator’s Guide). Statistics are collected for all agents; you
cannot configure the system to collect statistics for selected agents.
Database views
Agent by skillset statistics use the following views:
iAgentBySkillsetStat
dAgentBySkillsetStat
wAgentBySkillsetStat
mAgentBySkillsetStat
Pegging
All statistics peg against a specific skillset. The following table shows how
contacts peg.
Pegging thresholds
Define a skillset threshold class value for the length (talk time) of a short call,
and then assign the threshold class to the skillset. The value for short call length,
then, can vary from one skillset to another. For more information about
threshold classes, refer to the Contact Center Manager Administrator’s Guide.
Field descriptions
The field descriptions for this view are described in this section.
AgentLogin
Description: The numeric ID the agent uses to log in to the phoneset or agent
desktop.
Type: varchar
Length: 16
AgentGivenName
Description: The first or given name of the agent.
If an agent record is deleted because the data is already collected, the agent name
is blank.
Type: varchar
Length: 64
AgentSurName
Description: The last name or surname of the agent.
If an agent record is deleted because the data is already collected, the agent name
is blank.
Type: varchar
Length: 64
CallsAnswered
Description: The number of contacts, excluding DN calls, answered or
accepted by an agent for this skillset.
Pegging: Voice calls peg upon answer and multimedia contacts peg upon
acceptance.
Type: int
Length: 4
CallsConferenced
Description: The number of contacts, excluding DN calls, in this skillset that an
agent conferenced.
Type: int
Length: 4
CallsOffered
Description: The number of local Contact Center Manager calls, SIP voice
calls, local multimedia contacts and incoming NSBR contacts handled by this
skillset and presented to this agent. This statistic includes contacts returned to
queue and contacts abandoned during presentation.
CallsReturnedToQ
Description: The number of local Contact Center Manager calls, SIP voice
calls, local multimedia contacts, and incoming NSBR contacts handled by this
skillset that the agent returned to the skillset queue for reasons other than
timeout.
Pegging: A voice call is returned to the queue if the agent enters another state
(for example, if the agent presses the Not Ready or DN key) while the call is
presented. This statistic pegs when the agent state changes. A multimedia
contact is returned to the queue if the agent rejects it using the Reject button.
Type: int
Length: 4
CallsReturnedToQDueToTimeout
Description: The number of local Contact Center Manager calls, SIP voice
calls, local multimedia contacts, and incoming NSBR contacts handled by this
skillset that returned to the skillset queue automatically, after a wait greater than
or equal to the answering timeout for this agent, as defined in the call
presentation class to which the agent belongs.
Type: int
Length: 4
CallsTransferred
Description: The number of Contact Center Manager calls, SIP voice calls,
ACD calls, NACD calls and SIP video contacts transferred by this agent for this
skillset.
This statistic does not include transferred Contact Center Multimedia or Contact
Center Outbound contacts.
Pegging: The call pegs when the transfer is complete—when the agent presses
the transfer key for the second time.
Type: int
Length: 4
ConsultTime
Description: The total time an agent spends in consultation while handling
contacts for this skillset. Consultation time occurs during a consult transfer if the
caller disconnects and the answering agent remains on the line.
Triggers: Consult time starts when the customer releases the call. Consult time
ends when the consult call is released.
Type: int
Length: 4
ContactType
Description: The type of contact determined by the name of this skillset. This
applies to SIP-enabled contact centers, MCS 5100 contact centers, if Contact
Center Multimedia, or if Contact Center Outbound is installed and this skillset
name begins with one of the configured prefixes as described in “Associating
contact types with applications and skillsets” on page 186.
DNOutExtTalkTime
Description: Communication Server 1000/Meridian 1 PBX switch only. The
total time spent on outgoing external DN calls, including hold time (see
“Internal versus External DN calls” on page 181 for a definition of external DN
calls). DN calls made as part of a Contact Center Outbound contact are not
included.
Where multiple DN keys are configured on agent phonesets, talk time can
exceed 15 minutes (900 seconds) per interval. This occurs when an agent makes
one DN call, places that call on hold, and then makes another DN call.
Pegging: DNOutExtTalkTime pegs against the last skillset for which the agent
answered a call.
Type: int
Length: 4
DNOutIntTalkTime
Description: Communication Server 1000/Meridian 1 PBX switch only. The
total time spent on outgoing internal DN calls, including hold time (see “Internal
versus External DN calls” on page 181 for a definition of external DN calls). DN
calls made as part of a Contact Center Outbound contact are not included.
Where multiple DN keys are configured on agent phonesets, talk time can
exceed 15 minutes (900 seconds) per interval. Talk time can exceed 15 minutes
when an agent makes one DN call, places that call on hold, and then makes
another DN call.
Triggers: Talk time begins when the call is answered and ends when the caller
disconnects or the agent releases the call.
Pegging: DNOutIntTalkTime pegs against the last skillset for which the agent
answered a call.
Type: int
Length: 4
HoldTime
Description: The amount of time this agent put local and incoming network
CDN calls on hold while answering. This hold time stops when the agent
restores the call. This also includes agent walkaway time.
Triggers: Hold time begins when the agent places a Contact Center Manager
call in the Hold state. Hold time ends when the call resumes or terminates.
Type: int
Length: 4
PostCallProcessingTime
Description: The total time an agent spends performing post-contact
processing. Normally, an agent uses this time to complete any work related to
the contact just released, such as filling in forms or filing papers.
Triggers: Post-call processing time begins when an agent presses the Not Ready
key after completing any contact, except DN calls, and ends when the agent
presses the Not Ready key again, places or receives a DN call, or logs out.
Pegging: If the agent is assigned to multiple skillsets, this statistic pegs against
the last skillset for which the agent handled a contact.
Post Call Processing Time is calculated for the first Not Ready period after a
contact is closed. If the agent enters another state after the contact (for example,
by answering or receiving a DN call or logging off of the skillset), and then
enters Not Ready state, the Not Ready time does not peg against
PostCallProcessingTime. Also, if the agent interrupts the Not Ready period to
enter another state, and then returns to Not Ready state, the second Not Ready
period does not peg against PostCallProcessingTime.
Type: int
Length: 4
RingTime
Description: The total time an agent spends in the Ringing state before
answering a Contact Center Manager call or SIP voice call from this skillset, and
in the Alerting/Presenting state before accepting a multimedia contact from this
skillset.
ShortCallsAnswered
Description: The total number of local Contact Center Manager calls, ACD
calls, NACD calls, SIP voice calls, local multimedia contacts, and incoming
NSBR calls accepted that have a talk time less than the short call threshold
assigned to the threshold class for the skillset.
Type: int
Length: 4
Site
Description: The configured name of this Contact Center Manager site.
Type: varchar
Length: 30
SiteID
Description: A unique number assigned by the system to identify this Contact
Center Manager site. The assigned SiteID remains unique over time even if a
configured site is deleted and another one is added with the same name. The
SiteID can be used in custom reports to identify statistics applicable to this site.
Skillset
Description: The name of the skillset.
Pegging: See “Pegging” on page 209.
Type: varchar
Length: 30
SkillsetID
Description: A unique number assigned by the server to identify a skillset when
the skillset is added.
Type: int
Length: 4
TalkTime
Description: The total time this agent spends handling contacts, excluding DN
calls, after the contact is answered or accepted in this skillset. This statistic
includes hold time.
Triggers:
For voice calls, talk time begins when the agent answers the call.
For the Communication Server 1000/Meridian 1 PBX switch, talk time
ends when the caller disconnects or the agent releases or transfers the call.
For the Communication Server 2x00 switch, talk time ends when the agent
releases or transfers the call.
For multimedia contacts, talk time begins when the agent accepts the
contact and ends when the agent closes or transfers the contact.
For Contact Center Outbound contacts, talk time begins when the agent
accepts the contact, includes the time the agent is on the DN call, and ends
when the agent releases the DN call and closes the contact.
Talk time is pegged at the end of the interval (for contacts that are active at the
end of an interval) and when the contact terminates.
Type: int
Length: 4
Time
Description: The time (in 24-hour HH:MM format) when the data is pegged by
the system.
Type: char
Length: 5
Timestamp
Description: The date and time when the data is pegged by the system. For
more information about the format of the Timestamp in interval, daily, weekly,
or monthly views, see “Overview of summarized historical statistics” on page
166. This field is used for linking tables in data queries.
Type: smalldatetime
Length: 4
TotalStaffedTime
Description: The total time an agent is logged on and assigned to this skillset.
Triggers: Staffed time begins when an agent:
logs in (if the agent is assigned to a skillset)
is assigned to the skillset with a priority of 1 or more
Length: 4
UserID
Description: A unique number assigned by the server to identify an agent when
the agent is added.
Type: binary
Length: 16
WaitTime
Description: The total time this agent spends waiting for a contact after
releasing a voice call or closing a multimedia contact from this skillset.
Triggers: Wait time begins when the agent enters the idle state. For example, if:
the agent releases a contact and the agent's call presentation class is not
configured for Break time or Variable Wrap.
the agent's Break or Variable Wrap timer elapses after a contact is released
or closed.
the agent presses the Not Ready key a second time after entering Not Ready
state.
WaitTime ends when the agent leaves the Idle state. If the agent handles another
contact that is queuing in the same skillset as the most recently handled contact,
WaitTime resumes against that skillset when the agent returns to the Idle state. If
the agent handles a contact that is queuing in a different skillset than the most
recently handled contact, WaitTime begins against the new skillset when the
agent returns to the Idle state.
For more information, see “How is WaitTime pegged if the agent puts a DN call
on hold and uses alternate call answer to accept another contact?” on page 117.
Pegging: WaitTime pegs against the last skillset for which the agent handled a
contact during this login. If the agent has not yet handled a contact that is
queuing in a skillset, WaitTime is not pegged.
Type: int
Length: 4
The following table shows the statistics groups that agent by skillset statistics
can link to, as well as the data fields used as linkage keys:
Specify all these fields as your linkage key, in the specified order.
AgentPerformanceStat views
Statistics peg only for those agents who are logged on.
Requirements
Configure the server to collect agent performance statistics (see the Contact
Center Manager Administrator’s Guide). Statistics are collected for all agents;
you cannot configure the system to collect statistics for selected agents.
Database views
Agent performance statistic use the following views:
iAgentPerformanceStat
dAgentPerformanceStat
wAgentPerformanceStat
mAgentPerformanceStat
Agent performance statistics are collected only for the combination of agent and
primary supervisor.
The Communication Server 1000/Meridian 1 PBX switch does not support blind
conferences.
DN statistics
Field descriptions
The field descriptions for this view are described in this section.
ACDCallsAnswered
Description: The number of ACD calls answered by the agent. On the
Communication Server 1000/Meridian 1 PBX switch, this statistic includes
parked ACD calls that return to an agent. On the Communication Server 2x00/
DMS switch, this statistic includes NACD calls answered. ACD calls are not
available in SIP-enabled contact centers.
Triggers: For answered calls, this statistic pegs when the call is answered. For
parked calls, this statistic pegs when the Call Park feature is used.
Type: smallint
Length: 2
ACDCallsConfToCDN
Description: The number of ACD calls that are conferenced from a phoneset
Contact Center Manager acquires to a CDN the server acquires. On the
Communication Server 1000/Meridian 1 PBX switch, this statistic includes calls
conferenced to agents on a remote node. On the Communication Server 2x00/
DMS switch, this statistic includes NACD calls conferenced. ACD calls are not
available in SIP-enabled contact centers.
Triggers: The call pegs when the conference is completed (that is, when the
conference key is pressed for the second time).
Type: smallint
Length: 2
ACDCallsConfToDN
Description: The number of ACD calls that are conferenced from a phoneset
acquired by Contact Center Manager to a personal or secondary DN key on a
phoneset acquired by the server. On the Communication Server 2x00/DMS
switch, this statistic includes conferenced NACD calls. ACD calls are not
available in SIP-enabled contact centers.
Triggers: The call pegs when the conference is completed (that is, when the
conference key is pressed for the second time).
Type: smallint
Length: 2
ACDCallsConfToIncalls
Description: The number of ACD calls that are conferenced from a phoneset
acquired by Contact Center Manager to an ACD-DN and presented to a
phoneset acquired by the server, or (for the Communication Server 2x00/DMS
switch) conferenced directly to an Incalls key on such a phoneset. On the
Communication Server 2x00/DMS switch, this statistic includes conferenced
NACD calls. ACD calls are not available in SIP-enabled contact centers.
Triggers: The call pegs when the conference is completed (that is, when the
conference key is pressed for the second time).
Type: smallint
Length: 2
ACDCallsConfToOther
Description: The number of ACD calls that are conferenced from a phoneset
acquired by Contact Center Manager to a resource external to the Contact Center
Manager system. On the Communication Server 2x00/DMS switch, this statistic
includes blind conferences and NACD calls conferenced. ACD calls are not
available in SIP-enabled contact centers.
Triggers: The call pegs when the conference is completed (that is, when the
conference key is pressed for the second time).
Type: smallint
Length: 2
ACDCallsTalkTime
Description: The total time spent on ACD calls, including hold time. On the
Communication Server 2x00/DMS switch, this field includes talk time for
NACD calls. ACD calls are not available in SIP-enabled contact centers.
Triggers: Talk time begins when the call is answered. For the Communication
Server 1000/Meridian 1 PBX switch, talk time ends when the caller disconnects
or the agent releases the call. For the Communication Server 2x00/DMS switch,
talk time ends when the agent releases the call.
Type: int
Length: 4
ACDCallsTransferredToCDN
Description: The number of ACD calls that are transferred from a phoneset
acquired by Contact Center Manager to a CDN acquired by the server. On the
Communication Server 1000/Meridian 1 PBX switch, this statistic includes calls
transferred to agents at a remote node. On the Communication Server 2x00/
DMS switch, this statistic includes NACD calls transferred to a CDN. ACD calls
are not available in SIP-enabled contact centers.
Triggers: The call pegs when the transfer is completed (that is, when the
transfer key is pressed for the second time).
Type: smallint
Length: 2
ACDCallsTransferredToDN
Description: The number of ACD calls that are transferred from a phoneset
acquired by Contact Center Manager to a personal or secondary DN key on a
phoneset acquired by the server. On the Communication Server 2x00/DMS
switch, this statistic includes transferred NACD calls. ACD calls are not
available in SIP-enabled contact centers.
Triggers: The call pegs when the transfer is completed (that is, when the
transfer key is pressed for the second time).
Type: smallint
Length: 2
ACDCallsTransferredToIncalls
Description: The number of ACD calls that are transferred from a phoneset
acquired by Contact Center Manager to an ACD-DN and presented to a
phoneset acquired by the server, or (for the Communication Server 2x00/DMS
switch) transferred directly to an Incalls key on such a phoneset. On the
Communication Server 2x00/DMS switch, this statistic includes NACD calls
transferred. ACD calls are not available in SIP-enabled contact centers.
Triggers: The call pegs when the transfer is completed (that is, when the
transfer key is pressed for the second time).
Type: smallint
Length: 2
ACDCallsTransferredToOther
Description: The number of ACD calls that are transferred from a phoneset
acquired by Contact Center Manager to a resource external to the Contact Center
Manager system. On the Communication Server 2x00/DMS switch, this statistic
includes blind transfers and NACD calls transferred. ACD calls are not available
in SIP-enabled contact centers.
Triggers: The call pegs when the transfer is completed (that is, when the
transfer key is pressed for the second time).
Type: smallint
Length: 2
AgentGivenName
Description: The first or given name of the agent.
Type: varchar
Length: 64
If an agent record is deleted because the data is already collected, the agent name
is blank.
AgentLogin
Description: The numeric ID the agent uses to log in to the phoneset or agent
desktop.
Type: varchar
AgentSurName
Description: The last or surname of the agent.
Type: varchar
Length: 64
If an agent record is deleted because the data is already collected, the agent name
is blank.
BreakTime
Description: Communication Server 1000/Meridian 1 PBX switch only. The
total time an agent is in the Break state for all skillsets. You can configure an
agent’s call presentation class to place the agent in Break state after each call.
Triggers: BreakTime begins when a contact, excluding ACD and NACD calls,
is released or closed, and ends when the break timer elapses.
Type: int
Length: 4
BusyMiscTime
Description: Communication Server 1000/Meridian 1 PBX switch only. The
total time the Incalls key of an agent is busy because of events not related to DN
calls (for example, programming the Call Forward key or ACD/NACD call
ringing).
Triggers: The following table shows when busy time begins and ends.
the agent presses the Forward key to the agent presses the Forward key again
program call forward to activate call forward
the agent presses the DN key the agent finishes dialing the number
an ACD /NACD call is presented to the agent answers the ACD/NACD call
the agent’s phoneset
Type: int
Length: 4
BusyOnDNTime
Description: Communication Server 1000/Meridian 1 PBX switch only. The
total time the Incalls key of an agent is busy because the agent pressed the
personal DN key or is busy on a DN call. This statistic does not include DN calls
originated as part of a Contact Center Outbound contact.
Triggers: Busy time begins when the agent presses the DN key and ends when
the DN call is released.
Type: int
Length: 4
CallsAnswered
Description: The number of local Contact Center Manager calls, SIP voice
calls, local multimedia contacts, and incoming NSBR contacts answered. This
statistic includes NACD calls routed to a local CDN.
CallsOffered
Description: The number of local Contact Center Manager calls, SIP voice
calls, local multimedia contacts, and incoming NSBR contacts handled by this
application and presented to this agent. This statistic includes contacts returned
to queue and contacts abandoned during presentation.
CallsReturnedToQ
Description: The number of Contact Center Manager contacts and incoming
NSBR contacts handled by this application that the agent returned to the skillset
queue for reasons other than timeout.
Pegging: A voice call is returned to queue if the agent enters another state (for
example, if the agent presses the Not Ready or DN key) while the call is
presented. This statistic pegs when the agent state changes.
A multimedia contact is returned to queue if the agent rejects it using the Reject
button.
Type: smallint
Length: 2
CallsReturnedToQDueToTimeout
Description: The number of local Contact Center Manager calls, SIP voice
calls, local multimedia contacts, and incoming NSBR contacts handled by this
application and returned to the skillset queue automatically after a wait greater
than or equal to the answering timeout for this agent, as defined in the call
presentation class to which the agent belongs.
Type: smallint
Length: 2
CDNCallsConfToCDN
Description: The number of contacts, excluding ACD, NACD, and DN calls,
that are conferenced to a CDN acquired by Contact Center Manager. On the
Communication Server 1000/Meridian 1 PBX switch, this statistic includes calls
conferenced to a CDN at a remote site.
Triggers: This statistic pegs when the conference is completed (that is, when the
conference key is pressed for the second time).
Type: smallint
Length: 2
CDNCallsConfToDN
Description: The number of contacts, excluding ACD, NACD, and DN calls,
that are conferenced to an agent’s personal or secondary DN on a phoneset
acquired by Contact Center Manager.
Triggers: This statistic pegs when the conference is completed (that is, when the
conference key is pressed for the second time).
Type: smallint
Length: 2
CDNCallsConfToIncalls
Description: The number of contacts, excluding ACD, NACD, and DN calls,
that are conferenced to an ACD-DN and presented to a phoneset acquired by
Contact Center Manager or (for the Communication Server 2x00/DMS switch)
conferenced directly to an Incalls key on such a phoneset.
Triggers: This statistic pegs when the conference is completed (that is, when the
conference key is pressed for the second time).
Type: smallint
Length: 2
CDNCallsConfToOther
Description: The number of contacts, excluding ACD, NACD, and DN calls,
that are conferenced to a resource external to the Contact Center Manager
system. On the Communication Server 2x00/DMS switch, this statistic includes
blind transfers.
On the SIP switch, no distinction is made on the nature of the target for
conference. All calls are tagged as either CDNCallsConfToOther or
DNCallsConfToOther.
Triggers: This statistic pegs when the conference is completed (that is, when the
conference key is pressed for the second time).
Type: smallint
Length: 2
CDNCallsTransferredToCDN
Description: The number of contacts, excluding ACD, NACD, and DN calls,
that are transferred to a CDN acquired by Contact Center Manager. On the
Communication Server 1000/Meridian 1 PBX switch, this statistic includes calls
transferred to a CDN at a remote site.
Triggers: This statistic pegs when the transfer is completed (that is, when the
transfer key is pressed for the second time).
Type: smallint
Length: 2
CDNCallsTransferredToDN
Description: The number of contacts, excluding ACD, NACD, and DN calls,
that are transferred to a personal or secondary DN on a phoneset acquired by
Contact Center Manager.
Triggers: This statistic pegs when the transfer is completed (that is, when the
transfer key is pressed for the second time).
Type: smallint
Length: 2
CDNCallsTransferredToIncalls
Description: The number of contacts, excluding ACD, NACD, and DN calls,
that are transferred to an ACD-DN and presented to a phoneset acquired by
Contact Center Manager, or (for the Communication Server 2x00/DMS switch)
transferred directly to an Incalls key on such a phoneset.
Triggers: This statistic pegs when the transfer is completed (that is, when the
transfer key is pressed for the second time).
Type: smallint
Length: 2
CDNCallsTransferredToOther
Description: The number of contacts, excluding ACD, NACD, and DN calls,
that are transferred to a resource external to the Contact Center Manager system.
On the Communication Server 2x00/DMS switch, this statistic includes blind
transfers.
On the SIP switch, no distinction is made on the nature of the target for
conference. All calls are tagged as either CDNCallsConfToOther or
DNCallsConfToOther.
Triggers: This statistic pegs when the transfer is completed (that is, when the
transfer key is pressed for the second time).
Type: smallint
Length: 2
ConsultationTime
Description: Communication Server 1000/Meridian 1 PBX switch only. The
total time an agent spends in consultation with another agent during a call
transfer or conference after the caller drops off the call.
Triggers: Consultation time begins when the caller disconnects and ends when
the call is released.
Type: int
Length: 4
DNCallsConfToACDDN
Description: The number of DN calls that are conferenced from a phoneset
acquired by Contact Center Manager to an ACD-DN and presented to a
phoneset acquired by Contact Center Manager. This statistic does not include
DN calls originated as part of a Contact Center Outbound contact.
Pegging: This statistic pegs upon answer.
Type: smallint
Length: 2
DNCallsConfToCDN
Description: The number of DN calls that are conferenced from a phoneset
acquired by Contact Center Manager to a CDN acquired by the server. On the
Communication Server 1000/Meridian 1 PBX switch, this statistic includes calls
conferenced to agents at a remote node. This statistic does not include DN calls
originated as part of a Contact Center Outbound contact.
Triggers: This statistic pegs when the conference is completed (that is, when the
conference key is pressed for the second time).
Type: smallint
Length: 2
DNCallsConfToDN
Description: The number of DN calls that are conferenced from a phoneset
acquired by the Contact Center Manager to a personal or secondary DN on a
phoneset acquired by the Contact Center Manager. This statistic does not
include DN calls originated as part of a Contact Center Outbound contact.
Triggers: This statistic pegs when the conference is completed (that is, when the
conference key is pressed for the second time).
Type: smallint
Length: 2
DNCallsConfToOther
Description: The number of DN calls that are conferenced from a phoneset
acquired by the Contact Center Manager to a resource external to the Contact
Center Manager system. On the Communication Server 2x00/DMS switch, this
statistic includes blind conferences. This statistic does not include DN calls
originated as part of a Contact Center Outbound contact.
On the SIP switch, no distinction is made on the nature of the target for
conference. All calls are tagged as either CDNCallsConfToOther or
DNCallsConfToOther.
Triggers: This statistic pegs when the conference is completed (that is, when the
conference key is pressed for the second time).
Type: smallint
Length: 2
DNCallsTransferredToACDDN
Description: The number of DN calls that are transferred from a phoneset
acquired by the Contact Center Manager to an ACD-DN and presented to a
phoneset acquired by the Contact Center Manager. This statistic does not
include DN calls originated as part of a Contact Center Outbound contact.
Length: 2
DNCallsTransferredToCDN
Description: The number of DN calls that are transferred from a phoneset
acquired by the Contact Center Manager to a CDN acquired by the server. On
the Communication Server 1000/Meridian 1 PBX switch, this statistic includes
calls transferred to agents at a remote node. This statistic does not include DN
calls originated as part of a Contact Center Outbound contact.
Triggers: This statistic pegs when the transfer is completed (that is, when the
transfer key is pressed for the second time).
Type: smallint
Length: 2
DNCallsTransferredToDN
Description: The number of DN calls that are transferred from a phoneset
acquired by the Contact Center Manager to a personal or secondary DN on a
phoneset acquired by the Contact Center Manager. This statistic does not
include DN calls originated as part of a Contact Center Outbound contact.
Triggers: This statistic pegs when the transfer is completed (that is, when the
transfer key is pressed for the second time).
Type: smallint
Length: 2
DNCallsTransferredToOther
Description: The number of DN calls that are transferred from a phoneset
acquired by the Contact Center Manager to a resource external to the Contact
Center Manager system. On the Communication Server 2x00/DMS switch, this
statistic includes blind transfers. This statistic does not include DN calls
originated as part of a Contact Center Outbound contact.
On the SIP switch, no distinction is made on the nature of the target for
conference. All calls are tagged as either CDNCallsConfToOther or
DNCallsConfToOther.
Triggers: This statistic pegs when the transfer is completed (that is, when the
transfer key is pressed for the second time).
Type: smallint
Length: 2
DNInCalls
Description: Communication Server 2x00/DMS switch and MCS 5100 only.
The number of calls to an agent’s DN key.
Pegging: This statistic pegs upon answer.
Type: int
Length: 4
DNInCallsTalkTime
Description: Communication Server 2x00/DMS switch and MCS 5100 only.
The total time spent on incoming DN calls, including hold time.
Triggers: Talk time begins when the call is answered and ends when the agent
releases the call.
Type: int
Length: 4
DNInExtCalls
Description: Communication Server 1000/Meridian 1 PBX switch only. The
total number of incoming internal DN calls (for a definition of external DN
calls, see “Internal versus External DN calls” on page 181). This statistic
includes parked external calls that are returned to the agent.
Pegging: This statistic pegs upon answer.
All DN calls are pegged as internal DN calls for a SIP-enabled contact center.
Therefore, the value of this element is zero.
Type: smallint
Length: 2
DNInExtCallsHoldTime
Description: The total time that incoming external DN calls spend on hold (for
a definition of external DN calls, see “Internal versus External DN calls” on
page 181).
Triggers: The following table shows when DNInExtCallsHold time begins and
ends.
the agent presses the Hold key the agent retrieves the call
the agent presses the Transfer or the agent finishes entering the destination
Conference key number
Type: int
Length: 4
DNInExtCallsTalkTime
Description: Communication Server 1000/Meridian 1 PBX switch only. The
total time spent on incoming external DN calls, including hold time.
Where multiple DN keys are configured on agent phonesets, talk time can
exceed 15 minutes (900 seconds) per interval (see “Internal versus External DN
calls” on page 181 for a definition of external DN calls). This happens when an
agent answers one DN call, places that call on hold, and then answers another
DN call.
Pegging: All DN calls are pegged as internal DN calls for a SIP-enabled contact
center. Therefore, the value of this element is zero.
Triggers: Talk time begins when the call is answered and ends when the caller
disconnects or the agent releases the call.
Type: int
Length: 4
DNInIntCalls
Description: Communication Server 1000/Meridian 1 PBX switch only. The
total number of incoming internal DN calls (see “Internal versus External DN
calls” on page 181 for a definition of internal DN calls). This statistic includes
parked internal calls returned to the agent.
Pegging: This statistic pegs upon answer.
All DN calls are pegged as internal DN calls for a SIP-enabled contact center.
Type: smallint
Length: 2
DNInIntCallsHoldTime
Description: The total time that incoming internal DN calls spend on hold (see
“Internal versus External DN calls” on page 181 for a definition of internal DN
calls).
On MCS 5100 systems, this includes hold time for all DNInCalls.
Triggers: The following table shows when DNInIntCallsHold time begins and
ends.
the agent presses the Hold key the agent retrieves the call.
the agent presses the Transfer or the agent finishes entering the
Conference key destination number.
Type: int
Length: 4
DNInIntCallsTalkTime
Description: Communication Server 1000/Meridian 1 PBX switch only. The
total time spent on incoming internal DN calls, including hold time.
Where multiple DN keys are configured on agent phonesets, talk time can
exceed 15 minutes (900 seconds) per interval (see “Internal versus External DN
calls” on page 181 for a definition of internal DN calls). This happens when an
agent answers one DN call, places that call on hold, and then answers another
DN call.
Pegging: All DN calls are pegged as internal DN calls for a SIP-enabled contact
center.
Triggers: Talk time begins when the call is answered and ends when the caller
disconnects or the agent releases the call.
Type: int
Length: 4
DNOutCalls
Description: Communication Server 2x00/DMS switch and SIP-enabled
systems only. The total number of DN calls originated by the agent from the
agent's DN key. This statistic does not include DN calls originated as part of a
Contact Center Outbound contact.
Pegging: This statistic pegs when the DN call is answered.
Type: int
Length: 4
DNOutCallsTalkTime
Description: Communication Server 2x00/DMS switch and SIP-enabled
systems only. The total time spent on outgoing DN calls, including hold time.
This statistic does not include DN calls originated as part of a Contact Center
Outbound contact.
Triggers: Talk time begins when the call is answered and ends when the agent
releases the call.
Type: int
Length: 4
DNOutExtCalls
Description: Communication Server 1000/Meridian 1 PBX switch only. The
total number of outgoing external DN calls. This statistic includes external
parked calls retrieved by an agent (see “Internal versus External DN calls” on
page 181 for a definition of external DN calls). This statistic does not include
DN calls originated as part of a Contact Center Outbound contact.
Pegging: This statistic pegs when the call is answered.
All DN calls are pegged as internal DN calls for a SIP-enabled contact center.
Therefore, the value of this element is zero.
Type: smallint
Length: 2
DNOutExtCallsHoldTime
Description: Communication Server 1000/Meridian 1 PBX switch only. The
total time that outgoing external DN calls spent on hold (see “Internal versus
External DN calls” on page 181 for a definition of external DN calls). This
statistic does not include DN calls originated as part of a Contact Center
Outbound contact.
Pegging: The following table shows when DNOutExtCallsHold time begins
and ends.
the agent presses the Hold key the agent retrieves the call
the agent presses the Transfer or the agent finishes entering the
Conference key destination number
All DN calls are pegged as internal DN calls for a SIP-enabled contact center.
Therefore, the value of this element is zero.
Type: int
Length: 4
DNOutExtCallsTalkTime
Description: Communication Server 1000/Meridian 1 PBX switch only. The
total time spent on outgoing external DN calls, including hold time. This statistic
does not include DN calls originated as part of a Contact Center Outbound
contact.
Where multiple DN keys are configured on agent phonesets, talk time can
exceed 15 minutes (900 seconds) per interval. This happens when an agent
answers one DN call, places that call on hold, and then answers another DN call
(see “Internal versus External DN calls” on page 181 for a definition of external
DN calls).
Pegging: All DN calls are pegged as internal DN calls for a SIP-enabled contact
center. Therefore, the value of this element is zero.
Triggers: Talk time begins when the agent presses the DN key and ends when
the caller disconnects or the agent releases the call.
Type: int
Length: 4
DNOutIntCalls
Description: Communication Server 1000/Meridian 1 PBX switch only. The
total number of outgoing internal DN calls. This statistic includes internal
parked calls retrieved by an agent (see “Internal versus External DN calls” on
page 181 for a definition of internal DN calls). This statistic does not include
DN calls originated as part of a Contact Center Outbound contact.
Pegging: This statistic pegs when the caller is connected.
All DN calls are pegged as internal DN calls for a SIP-enabled contact center.
Type: smallint
Length: 2
DNOutIntCallsHoldTime
Description: Communication Server 1000/Meridian 1 PBX switch only. The
total time that outgoing internal DN calls spent on hold (see “Internal versus
External DN calls” on page 181 for a definition of external DN calls). This
statistic does not include DN calls originated as part of a Contact Center
Outbound contact.
For SIP-enabled systems, this includes hold time for all DN outcalls (excluding
DN calls originated as part of a Contact Center Outbound contact).
Pegging: The following table shows when DNOutInCallsHold time begins and
ends.
the agent presses the Hold key the agent retrieves the call
the agent presses the Transfer or the agent finishes entering the
Conference key destination number
All DN calls are pegged as internal DN calls for a SIP-enabled contact center.
Type: int
Length: 4
DNOutIntCallsTalkTime
Description: Communication Server 1000/Meridian 1 PBX switch only. The
total time spent on outgoing internal DN calls, including hold time (see “Internal
versus External DN calls” on page 181 for a definition of internal DN calls).
This statistic does not include DN calls originated as part of a Contact Center
Outbound contact.
Where multiple DN keys are configured on agent phonesets, talk time can
exceed 15 minutes (900 seconds) per interval. Talk time exceeding 15 minutes
happens when an agent answers one DN call, places that call on hold, and then
answers another DN call.
Pegging: All DN calls are pegged as internal DN calls for a SIP-enabled contact
center.
Triggers: Talk time begins when the call is answered and ends when the caller
disconnects or the agent releases the call.
Type: int
Length: 4
HoldTime
Description: The amount of time this agent put local and incoming contacts on
hold, excluding DN calls, ACD calls, and NACD calls. This hold time stops
when the agent restores the call or contact. HoldTime also includes agent
walkaway time.
Triggers: The following table shows when hold time begins and ends.
the agent presses the Hold key the agent retrieves the call (for example,
by pressing the Incalls key).
the agent presses the Transfer or the agent finishes entering the
Conference key destination number.
Type: int
Length: 4
LoggedInTime
Description: The total time an agent is in the Login state.
Triggers: Logon time begins after the agent enters a logon ID and (if required) a
logon password, and the server determines that the agent is valid. Logon time
ends when the agent logs off.
Type: int
Length: 4
NACDCallsAnswered
Description: Communication Server 1000/Meridian 1 PBX switch only. The
number of NACD calls answered by an agent. NACD calls are not available in
SIP-enabled contact centers.
Pegging: This statistic pegs upon answer.
For the Communication Server 2x00/DMS switch, NACD calls peg as ACD
calls.
Type: smallint
Length: 2
NACDCallsTalkTime
Description: Communication Server 1000/Meridian 1 PBX switch only. The
total time spent on NACD calls by an agent, including hold time. NACD calls
are not available in SIP-enabled contact centers.
For the Communication Server 2x00/DMS switch, NACD calls peg as ACD
calls.
Triggers: Talk time begins when the call is answered and ends when the caller
disconnects or the agent releases the call.
Type: int
Length: 4
NetworkCallsAnswered
Description: NSBR option only. The number of incoming NSBR contacts
answered by an agent.
Pegging: For voice calls, this statistic pegs when the agent answers an incoming
NSBR call. For multimedia contacts, this statistic pegs when the agent accepts
an incoming NSBR contact.
The SIP-enabled contact center does not support Networking. This value is zero
at all times.
Type: smallint
Length: 2
NetworkCallsTalkTime
Description: NSBR option only. The total time that the agent spent handling
incoming NSBR contacts, including hold time.
Pegging: The SIP-enabled contact center does not support Networking. This
value is zero at all times.
Triggers: For voice calls, talk time begins when the agent answers the call and
ends when the caller disconnects or the agent releases the call. For multimedia
contacts, talk time begins when the agent accepts the contact, and ends when the
agent closes the contact.
Type: int
Length: 4
NotReadyTime
Description: The total time an agent spends in the Not Ready state. Not Ready
time includes post-call processing time and Not Ready time with reason codes.
Triggers: Not Ready time begins when the agent presses the Not Ready key and
ends when the agent presses the Not Ready key again.
Type: int
Length: 4
NumberTimesNotReady
Description: The total number of times an agent enters the not ready state.
Pegging: This is pegged when the agent enters the not ready state.
Type: smallint
Length: 2
ReservedForCall
Description: NSBR and NACD options only. The number of times the agent is
reserved to answer an NSBR or NACD call.
Pegging: The SIP-enabled contact center does not support Networking. This
value is zero at all times.
Type: smallint
Length: 2
ReservedTime
Description: NSBR and NACD options only. The total time the agent is in
Reserved state.
Triggers: Reserved time begins when the switch reserves the agent for an
NSBR or NACD call, and ends when the call is presented or the agent
reservation is canceled.
Type: int
Length: 4
RingTime
Description: The total time an agent spends in the Ringing state before
answering a Contact Center Manager call or SIP voice call, and in the Alerting
or Presenting state before accepting a multimedia contact.
ShortCallsAnswered
Description: The total number of contacts answered or accepted that have a talk
time less than the short call threshold assigned to the threshold class for the
skillset in which the contact is answered or accepted. This statistic does not
apply to DN calls.
Type: smallint
Length: 2
Site
Description: The configured name of this Contact Center Manager site.
Type: varchar
Length: 30
SiteID
Description: A unique number assigned by the system to identify this Contact
Center Manager site. The assigned SiteID remains unique over time even if a
configured site is deleted and another one is added with the same name. The
SiteID can be used in custom reports to identify statistics applicable to this site.
SupervisorGivenName
Description: The first or given name of the agent’s reporting supervisor, as
defined by the supervisor.
Type: varchar
Length: 64
SupervisorLogin
Description: The numeric ID the supervisor uses to log in to the phoneset or
desktop.
Type: varchar
Length: 16
SupervisorSurName
Description: The last or surname of the agent’s supervisor, as defined by the
supervisor.
Type: varchar
Length: 64
SupervisorUserID
Description: A unique number assigned by the server to identify the agent’s
reporting supervisor when the agent is added.
Type: binary
Length: 16
TalkTime
Description: The total time spent by the agent handling all contacts except DN
calls, ACD calls, and NACD calls, including hold time.
Triggers:
For voice calls, talk time begins when the agent answers the call.
For the Communication Server 1000/Meridian 1 PBX switch, talk time
ends when the caller disconnects or the agent releases or transfers the call.
For the Communication Server 2x00 switch, talk time ends when the agent
releases or transfers the call.
For multimedia contacts, talk time begins when the agent accepts the
contact and ends when the agent closes or transfers the contact.
For Contact Center Outbound contacts, talk time begins when the agent
accepts the contact, includes the time the agent is on the DN call, and ends
when the agent releases the DN call and closes the contact.
Pegging: Talk time pegs at the end of the interval (for calls and contacts that are
active at the end of an interval) and when the call is released or contact is closed.
Type: int
Length: 4
Time
Description: The time (in 24-hour HH:MM format) when the data is pegged by
the system.
Type: char
Length: 5
Timestamp
Description: The date and time when the data is pegged by the system. For
more information about the format of the Timestamp in interval, daily, weekly,
or monthly views, see “Overview of summarized historical statistics” on page
166. This field is used for linking tables in data queries.
Type: smalldatetime
Length: 4
UserID
Description: A unique number assigned by the server to identify the agent when
the agent is added. This field is used for linking tables in data queries.
Type: binary
Length: 16
VariableWrapTime
Description: Communication Server 2x00/DMS switch only. The total time an
agent is in the Variable Wrap state for all skillsets. You can configure the
Variable Wrap feature on the switch for an ACD group or agent. If you do, the
agent is put into Variable Wrap state for a predefined time after each call. To
allow Contact Center Manager to report Variable Wrap time, enable the
Variable Wrap feature for the call presentation class to which the agent belongs.
Triggers: Variable Wrap time begins when a call is released and ends when the
timer elapses.
Type: int
Length: 4
WaitingTime
Description: The total time this agent spends waiting for contacts. On the
Communication Server 2x00/DMS switch, WaitingTime includes time when the
agent is active on a secondary DN and when the agent is reserved on the switch.
Triggers: Waiting time begins when the agent goes into Idle state, for example,
if:
the agent logs on and presses the Not Ready key
the agent releases a call, and the agent’s call presentation class is not
configured for Break time or Variable Wrap
the agent’s break or variable wrap timer elapses after a call is released
the agent presses the Not Ready key a second time after entering Not Ready
state
WaitingTime ends when the agent leaves the Idle state. WaitingTime continues
to accumulate after return to the Idle state.
For more information, see “How is WaitTime pegged if the agent puts a DN call
on hold and uses alternate call answer to accept another contact?” on page 117.
Type: int
Length: 4
WalkawayTime
Description: The total time an agent is in the Walkaway state.
Triggers:
Walkaway time ends when the agent takes the phoneset off hook or plugs in the
headset.
The following table shows the statistics groups to which agent performance
statistics can be linked, as well as the data fields used as linkage keys.
Specify all these fields as your linkage key, in the specified order.
ApplicationStat views
Statistics peg against a given application only for those intervals in which a
contact arrives for that application. Except for DNOutExtCallsTalkTime and
DNOutIntCallsTalkTime, these statistics do not include DN calls.
Definition: Application
An application is a logical entity that represents a script for reporting purposes.
The Master script and each script it references (that is, each primary script) has
an application with a name that is the same as the script name.
Requirements
Configure the server to collect application statistics (see the Contact Center
Manager Administrator's Guide). Statistics are collected for all applications;
you cannot configure the system to collect statistics for selected applications.
Database views
Application statistics use the following views:
iApplicationStat
dApplicationStat
wApplicationStat
mApplicationStat
Pegging
Local contacts
When a local contact enters Contact Center Manager, it is handled by the Master
script. Most contacts are handed off by the Master script to a primary script. The
primary script might hand off the contact to a secondary script.
In some cases, a script queues a contact to a network skillset. (In these cases, the
call is referred to as an outgoing NSBR contact.) Pegging for outgoing NSBR
contacts is the same as for local contacts.
Contacts that receive Route Call treatment in a script are pegged against an
application only until the time they are routed.
Contacts handled by Master script—If the contact does not leave the Master
script, all time delays and events (such as treatments) peg against the
Master_Script application.
For contacts processed by a primary application, all delays begin when the
contact interflows to the primary application and peg against the primary
application only.
Contact Center Manager does not have access to abandoned events and delay
statistics for ACD and NACD calls; therefore, these statistics are not applicable
to ACD_DN and NACD_DN applications.
ACD and NACD calls are not applicable to the SIP-enabled contact center.
Pegging thresholds
You can define application threshold classes with different values for the service
level threshold and short call length. Thus, the value for service level and short
call length can vary from one application to another. For more information about
threshold classes, refer to the Contact Center Manager Administrator's Guide.
SIP enabled contact center does not differentiate between ISDN and non-ISDN
trunks. All calls are pegged on non-ISDN calls.
Field descriptions
The field descriptions for this view are described in this section.
The delay time includes any time that the caller spends going through menus and
listening to announcements in this application.
Pegging: For local contacts and outgoing NSBR contacts, delays begin when
the Master_Script hands off the contact to a primary application. For incoming
NSBR contacts, delays begin when the contact is logically queued to this site.
Delays end when the caller disconnects.
Type: int
Length: 4
For voice calls, the delay time includes any time that the caller spends going
through menus and listening to announcements in this application.
Pegging: For local contacts and outgoing NSBR contacts, delays begin when
the Master_Script hands off the contact to a primary application. For incoming
NSBR contacts, delays begin when the contact is logically queued to this site.
Delays end when the call is answered or contact is accepted.
Type: int
Length: 4
Application
Description: The name of the application.
Type: varchar
Length: 30
ApplicationID
Description: A unique number assigned by the server to identify an application
when the application is defined. This field is used for linking tables in data
queries.
Type: int
Length: 4
CallsAbandoned
Description: The number of contacts—excluding DN calls, ACD and NACD
calls—that entered the application and are released before the calls are
answered. This statistic includes calls abandoned during treatment such as IVR
or Broadcast Announcement.
Pegging: This statistic pegs when a caller disconnects while still in queue or
receiving treatment.
This statistic includes calls that receive the Give IVR treatment and are
presented with a messaging system voice menu, if the menu options are
programmed with EM (to go to a mailbox).
Type: int
Length: 4
CallsAbandonedAftThreshold
Description: The number of contacts—excluding DN calls, ACD and NACD
calls—abandoned for this application after a wait greater than or equal to the
service level threshold for the threshold class to which the application belongs.
Triggers: For local contacts and outgoing NSBR contacts, delays begin when
the Master_Script hands off the contact to a primary application. For incoming
NSBR contacts, delays begin when the contact is logically queued to this site.
Delays end when the caller disconnects.
Type: int
Length: 4
CallsAbandonedDelay
Description: The wait time experienced by all contacts—excluding DN calls,
ACD and NACD calls— that are abandoned by callers.
The delay time includes any time that the caller spends reviewing menus and
listening to announcements in this application. DNIS delay times include up
front menu time. Application delay times do not.
Triggers: For local contacts and outgoing NSBR contacts, delays begin when
the Master_Script hands off the contact to a primary application. For incoming
NSBR contacts, delays begin when the contact is logically queued to this site.
Delays end when the caller disconnects.
iApplicationStat int 4
dApplicationStat int 4
wApplicationStat numeric 6
mApplicationStat numeric 6
CallsAnswered
Description: The number of contacts, excluding DN calls, answered or
accepted for this application.
Pegging: Voice calls peg upon answer. Multimedia contacts peg upon
acceptance. ACD calls peg against the ACD_DN_Application, and NACD calls
against the NACD_DN_Application.
Type: int
Length: 4
CallsAnsweredAftThreshold
Description: The number of contacts—excluding DN calls, ACD and NACD
calls—answered or accepted after a wait greater than or equal to the service
level threshold for the threshold class to which the application belongs.
Triggers: For local and outgoing NSBR contacts, delays begin when the
Master_Script hands off the contact to a primary application. For incoming
NSBR voice contacts, delays begin when the contact is logically queued to this
site. Delays end when the contact is answered or the contact is accepted.
Type: int
Length: 4
CallsAnsweredDelay
Description: The wait time experienced by all contacts—excluding DN calls,
ACD and NACD calls—answered or accepted for this application.
The delay time includes any time that the caller spends going through menus and
listening to announcements in this application.
This statistic includes Contact Center Multimedia Web Communication and text
chat contacts presented to the agent even if the customer abandons the contact.
Triggers: For local and outgoing NSBR contacts, delays begin when the
Master_Script hands off the contact to a primary application. For incoming
NSBR contacts, delays begin when the contact is logically queued to this site.
Delays end when the contact is answered or the contact is accepted.
iApplicationStat int 4
dApplicationStat int 4
wApplicationStat numeric 6
mApplicationStat numeric 6
CallsAnsweredDelayAtSkillset
Description: The total wait time experienced in the skillset queue by all
contacts answered or accepted for this application.
Triggers: Delays begin when the contact is queued against the first skillset and
end when the contact is answered.
iApplicationStat int 4
dApplicationStat int 4
wApplicationStat numeric 6
mApplicationStat numeric 6
CallsConferencedIn
Description: The number of local Contact Center Manager calls, SIP calls, and
incoming NSBR calls conferenced to this application.
Type: int
Length: 4
CallsConferencedOut
Description: The number of local Contact Center Manager calls, SIP calls,
incoming NSBR calls, ACD calls, and NACD calls conferenced out of this
application.
Type: int
Length: 4
CallsGivenBroadcast
Description: Communication Server 1000/Meridian 1 PBX switch only. The
number of local Contact Center Manager calls, SIP calls, and incoming NSBR
calls given broadcast treatment for this application.
Restriction: The count is not increased if the same call receives this treatment
more than once.
Type: int
Length: 4
CallsGivenDefault
Description: The number of local Contact Center Manager contacts, SIP calls,
multimedia contacts, and incoming NSBR contacts given default treatment as
the result of an error condition.
This statistic does not include calls given default treatment by the switch.
Contact Center Manager is unaware of these calls.
Pegging: Contacts are given default treatment under the following conditions:
The script fails or end of script is reached before controlling treatment is
given to the contact.
A QUIT command or end of script is reached and the contact is not queued
or routed.
The script contains illegal first statements.
An error condition has occurred from which the script executor cannot
recover.
Contact Center Manager Server is down.
All agents log out of the skillsets to which a call is queued, or all skillsets
are put out of service and a QUIT command or end of script is reached.
All skillsets to which the script queues a new call are out of service.
Type: int
Length: 4
CallsGivenForceBusy
Description: The number of local Contact Center Manager calls and SIP calls
given Force Busy treatment for this application.
Pegging: This statistic pegs when the Give Busy script command is executed.
Type: int
Length: 4
CallsGivenForceDisconnect
Description: The number of local Contact Center Manager calls SIP calls, and
multimedia contacts and incoming NSBR calls given Force Disconnect
treatment for this application.
This statistic also includes any Contact Center Outbound contacts that are
removed from the system when an outbound campaign ends.
Pegging: This statistic pegs when the Disconnect script command is executed.
Type: int
Length: 4
CallsGivenForceOverflow
Description: The number of local Contact Center Manager calls and SIP calls
given Force Overflow treatment for this application.
Pegging: This statistic pegs when the Give Overflow script command is
executed.
Type: int
Length: 4
CallsGivenHostLookup
Description: The number of local contacts and incoming NSBR contacts for
which data is obtained from a remote host through Host Data Exchange (HDX)
for this application.
Pegging: This statistic pegs when the Send Request script command is
executed.
Restriction: The count is not increased if the same contact receives this
treatment more than once.
Type: int
Length: 4
CallsGivenIVR
Description: The number of local Contact Center Manager calls and incoming
NSBR calls given IVR treatment for this application.
Pegging: This statistic pegs when the Give IVR script command is executed.
Restriction: The count is not increased if the same call receives this treatment
more than once.
Type: int
Length: 4
CallsGivenMusic
Description: The number of local Contact Center Manager calls, SIP voice
calls, and incoming NSBR calls given music treatment through a music route for
this application.
Pegging: This statistic pegs when the Give Music script command is executed.
Restriction: The count is not increased if the same call receives this treatment
more than once.
Type: int
Length: 4
CallsGivenNACD
Description: Communication Server 1000/Meridian 1 PBX switch only. The
number of local Contact Center Manager calls given Network ACD (NACD)
treatment. This treatment sends calls to a switch that does not use the Contact
Center Manager NSBR feature.
CallsGivenRAN
Description: The number of local Contact Center Manager calls, SIP calls, and
incoming NSBR calls given recorded announcement (RAN) treatment for this
application.
Pegging: This statistic pegs when the Give RAN script command is executed.
Restriction: The count is not increased if the same call receives this treatment
more than once.
Type: int
Length: 4
CallsGivenRouteTo
Description: The number of Contact Center Manager calls, SIP calls, and
incoming NSBR contacts given Route Call treatment for this application.
Pegging: This statistic pegs when the Route Call script command is executed.
Type: int
Length: 4
CallsNACDOut
Description: Communication Server 1000/Meridian 1 PBX switch only. The
number of local Contact Center Manager calls networked out through an NACD
queue and answered at remote switches. NACD is used to send calls to a switch
that does not use the Contact Center Manager NSBR feature.
CallsOffered
Description: The number of local contacts, incoming NSBR contacts, ACD
calls, and NACD calls offered to this application.
Pegging: Local Contact Center Manager contacts peg against the Master_Script
application upon arrival, and against a primary application when the
Master_Script application hands over control. ACD and NACD calls peg when
the call is answered. After answer, ACD calls peg against the
ACD_DN_Application and NACD calls against the NACD_DN_Application.
This statistic includes calls that receive the Give IVR treatment and are
presented with a messaging system voice menu, if the menu options are
programmed with either CL (to go to a mailbox through a DN) or Call
Answering (to go to a mailbox).
Type: int
Length: 4
CallsTransferredIn
Description: Communication Server 1000/Meridian 1 PBX switch only. The
number of local and incoming NSBR contacts transferred to this application.
This statistic does not include Contact Center Multimedia contacts transferred to
an agent or skillset.
Pegging: This statistic pegs as soon as the transfer is initiated, regardless of
whether the transfer is completed.
Type: int
Length: 4
CallsTransferredOut
Description: The number of local contacts, incoming NSBR contacts, ACD
calls, and NACD calls transferred out of this application.
This statistic does not include Contact Center Multimedia contacts that are
transferred out of this application.
Pegging: This statistic pegs when the transfer is completed.
If the agent aborts the transfer before it is complete, this statistic does not peg.
Type: int
Length: 4
ContactType
Description: The type of contact determined by the name of this application.
This applies to SIP-enabled contact centers, MCS 5100 contact centers, if
Contact Center Multimedia, or if Contact Center Outbound is installed and this
application name begins with one of the configured prefixes as described in
“Associating contact types with applications and skillsets” on page 186.
DNOutExtCallsTalkTime
Description: Communication Server 1000/Meridian 1 PBX switch only. The
total time spent by agents on outgoing external DN calls (see “Internal versus
External DN calls” on page 181 for a definition of external DN calls), including
hold time, for this application. This statistic does not include the time spent on
the DN outcall part of a Contact Center Outbound contact.
Triggers: DNOutExtCallsTalkTime begins when the call is answered and the
agent's previous contact was handled by this application. Talk time ends when
the caller disconnects or the agent releases the call.
Type: int
Length: 4
DNOutIntCallsTalkTime
Description: Communication Server 1000/Meridian 1 PBX switch only. The
total time spent by agents on outgoing internal DN calls (see “Internal versus
External DN calls” on page 181 for a definition of internal DN calls), including
hold time, for this application. This statistic does not include the time spent on
the DN outcall part of a Contact Center Outbound contact.
Triggers: DNOutIntCallsTalkTime begins when the call is answered and the
agent's previous contact was handled by this application. Talk time ends when
the caller disconnects or the agent releases the call.
Type: int
Length: 4
IVRAbandoned
Description: The number of local Contact Center Manager calls and incoming
NSBR calls abandoned during IVR treatment.
Type: int
Length: 4
IVRTerminated
Description: The number of local Contact Center Manager calls and incoming
NSBR calls that received and completed the IVR treatment in this application.
This statistic includes calls transferred by IVR.
Type: int
Length: 4
IVRTransferred
Description: The number of local Contact Center Manager calls and incoming
NSBR calls transferred from an IVR session for this application.
MaxCallsAbandonedDelay
Description: The wait time experienced by the contact—excluding DN calls,
ACD and NACD calls—that waited the longest before the caller abandoned it.
Triggers: For local contacts and outgoing NSBR calls, delays begin when the
Master_Script hands off the contact to a primary application. For incoming
NSBR contacts, delays begin when the contact is logically queued to this site.
Delays end when the caller disconnects.
Type: int
Length: 4
MaxCallsAnsDelay
Description: The wait time experienced by the local contact, incoming NSBR
contact, or outgoing NSBR contact—excluding DN calls, ACD and NACD
calls—that waited the longest before the contact is answered or accepted.
Triggers: For local contacts and outgoing NSBR contacts, delays begin when
the Master_Script hands off the contact to a primary application. For incoming
NSBR contact, delays begin when the contact is logically queued to this site.
Delays end when the contact is answered or accepted.
Type: int
Length: 4
MaxCallsAnsDelayAtSkillset
Description: The wait time experienced by the contact that waited the longest in
the skillset queue before the contact is answered or accepted.
Triggers: Delays begin when the contact is queued against the first skillset and
end when the contact is answered or accepted for this application.
Type: int
Length: 4
MaxNetOutCallsAbandonedDelay
Description: NSBR option only. The wait time experienced by the outgoing
NSBR contact routed by this application that waited the longest before the
contact is abandoned at the destination site.
MaxNetOutCallsAnsweredDelay
Description: NSBR option only. The wait time experienced by the outgoing
NSBR contact routed by this application that waited the longest before the
contact is answered or terminated at the destination site.
Triggers: Delays begin when the Master_Script hands off the contact to a
primary application at the source site and end when the contact is answered or
accepted by an agent, answered by IVR, or terminated at the destination site.
Type: int
Length: 4
NetOutCalls
Description: NSBR option only. The number of outgoing NSBR contacts
successfully routed by this application to another site. This statistic includes
contacts answered (or accepted) or abandoned at the destination site, as well as
calls terminating on non-ISDN trunks and calls blocked by an all trunks busy
condition.
NetOutCallsAbandoned
Description: NSBR option only. The number of outgoing NSBR contacts sent
by this application and abandoned at the destination sites.
NetOutCallsAbandonedDelay
Description: NSBR option only. The total time delay experienced by outgoing
NSBR contacts sent by this application and abandoned at the destination sites.
The delay time includes any time that the caller spends going through menus and
listening to announcements in this application.
iApplicationStat int 4
dApplicationStat int 4
wApplicationStat numeric 6
mApplicationStat numeric 6
NetOutCallsAnswered
Description: NSBR option only. The number of outgoing NSBR contacts
routed by this application and answered or accepted at the destination site.
This includes contacts that arrive at the destination site, but the reserved agent
logs off or becomes unavailable, and the contact receives one of the following
treatments:
Disconnect
Route
Give Recorded announcement (RAN)
Give IVR
Give Music
NetOutCallsAnsweredDelay
Description: NSBR option only. The total wait time experienced by all
outgoing NSBR contacts routed by this application and answered or accepted at
the destination site.
The delay time includes any time that the caller spends going through menus and
listening to announcements in this application.
iApplicationStat int 4
dApplicationStat int 4
wApplicationStat numeric 6
mApplicationStat numeric 6
NetOutCallsReachNonISDN
Description: NSBR option only. The number of outgoing NSBR calls sent by
this application that reached a non-ISDN trunk on the way to its destination.
PostCallProcessingTime
Description: This data is the total time agents spent performing post-contact
processing after handling a local or incoming NSBR contact in this application.
Normally, agents use this time to complete any work related to the contact just
completed, such as filling in forms or filing papers.
Triggers: Post-call processing time begins when an agent presses Not Ready
after releasing any contact, except DN calls, and ends when the agent presses
Not Ready again, places or receives a DN call, or logs out.
Post Call Processing Time is calculated for the first Not Ready period after a
contact is closed. If the agent enters another state after the call (for example, by
answering or receiving a DN call or logging out of the skillset), and then enters
Not Ready state, the Not Ready time does not peg against
PostCallProcessingTime. Also, if the agent interrupts the Not Ready period to
enter another state, and then returns to Not Ready state, the second Not Ready
period does not peg against PostCallProcessingTime.
Pegging: This statistic pegs against the last application for which the agent
handled a contact.
Type: int
Length: 4
Site
Description: The configured name of this Contact Center Manager site.
Type: varchar
Length: 30
SiteID
Description: A unique number assigned by the system to identify this Contact
Center Manager site. The assigned SiteID remains unique over time even if a
configured site is deleted and another one is added with the same name. The
SiteID can be used in custom reports to identify statistics applicable to this site.
TalkTime
Description: The total time that agents spent handling local and incoming
NSBR contacts (excluding DN calls) in this interval, that were handled by this
application. This statistic includes hold time.
Triggers: The follow items trigger this statistic:
For voice calls, talk time begins when the agent answers the call.
For the Communication Server 1000/Meridian 1 PBX switch, talk time
ends when the caller disconnects or the agent releases or transfers the call.
For the Communication Server 2x00 switch, talk time ends when the agent
releases or transfers the call.
For multimedia contacts, talk time begins when the agent accepts the
contact and ends when the agent closes or transfers the contact.
For Contact Center Outbound contacts, talk time begins when the agent
accepts the contact, includes the time the agent is on the DN call, and ends
when the agent releases the DN call and closes the contact.
Type: int
Length: 4
Time
Description: The time (in 24-hour HH:MM format) when the data is pegged by
the system.
Type: char
Length: 5
TimeBeforeDefault
Description: The total time spent in the system by local Contact Center
Manager calls, SIP voice calls, multimedia contacts, and incoming NSBR
contacts that received default treatment for this application.
Pegging: For local contacts, pegging begins when the Master_Script is initiated.
For incoming NSBR contacts, pegging begins when the contact is queued to the
site. Pegging ends when treatment is given.
Type: int
Length: 4
TimeBeforeForceBusy
Description: The total time spent in the system by local Contact Center
Manager calls, SIP calls, and incoming NSBR calls that received Force Busy
treatment for this application.
Pegging: For local calls, pegging begins when the Master_Script is initiated.
For incoming NSBR calls, pegging begins when the contact is queued to the site.
Pegging ends when Give Busy treatment is given.
Type: int
Length: 4
TimeBeforeForceDisconnect
Description: The total time spent in the system by local Contact Center
Manager calls, SIP calls, multimedia contacts, and incoming NSBR calls that
received Force Disconnect treatment for this application.
Pegging: For local contacts, pegging begins when the Master_Script is initiated.
For incoming NSBR calls, pegging begins when the contact is queued to the site.
Pegging ends when Give Disconnect treatment is given.
Type: int
Length: 4
TimeBeforeForceOverflow
Description: The total time spent in the system by local Contact Center
Manager calls, SIP calls, and incoming NSBR calls that received Force
Overflow treatment for this application.
Pegging: For local Contact Center Manager calls, pegging begins when the
Master_Script is initiated. For incoming NSBR calls, pegging begins when the
contact is queued to the site. Pegging ends when Give Overflow treatment is
given.
Type: int
Length: 4
TimeBeforeInterflow
Description: The total amount of time that local contacts and outgoing NSBR
contacts spent in the Master_Script application before the contact is passed to a
primary application. For the Master_Script application, this is the total time
spent in the Master_Script by all contacts. For primary applications, this is the
total time spent in the Master_Script application by all contacts answered for the
primary application.
Pegging: Pegging begins when the Master_Script is initiated, and ends when
the contact is handed off to a primary application.
Type: int
Length: 4
TimeBeforeIVRTransferred
Description: The total time spent in the system by local Contact Center
Manager calls and incoming NSBR calls transferred to an IVR session for this
application.
TimeBeforeNACDOut
Description: The total time spent in the system by local Contact Center
Manager calls networked out through the NACD queue and answered at remote
nodes. NACD calls are sent to other switches without using the Contact Center
Manager NSBR feature.
TimeBeforeNetOut
Description: NSBR option only. The total time spent in the system by outgoing
NSBR contacts networked out by this application.
Pegging: Pegging begins when the contact arrives at the site and ends when the
contact is routed to the destination.
Type: int
Length: 4
TimeBeforeReachNonISDN
Description: NSBR option only. The total time spent in the system by outgoing
NSBR Contact Center Manager calls before they reached a non-ISDN trunk.
Pegging: Pegging begins when the call arrives at the site and ends when the call
is routed to a non-ISDN trunk.
Type: int
Length: 4
TimeBeforeRouteTo
Description: The total time spent in the system by local Contact Center
Manager calls, SIP voice calls, SIP video calls, and incoming NSBR calls that
received Route Call treatment.
Pegging: For local Contact Center Manager calls, pegging begins when the
Master_Script is initiated. For incoming NSBR calls, pegging begins when the
contact is queued to the site. Pegging ends when Route Call treatment is given.
Type: int
Length: 4
Timestamp
Description: The date and time when the data pegged. For more information
about the format of the Timestamp in interval, daily, weekly, or monthly views,
see “Overview of summarized historical statistics” on page 166. This field is
used for linking tables in data queries.
Type: smalldatetime
Length: 4
WaitTime
Description: The total time agents spend waiting for a contact after releasing a
voice call or closing a multimedia contact handled by this application.
Triggers: WaitTime begins when the agent goes into Idle state, for example, if:
an agent releases a voice call or closes a multimedia contact, and the
agent’s call presentation class is not configured for Break time or Variable
Wrap
an agent’s Break or Variable Wrap timer elapses after a contact is released
or closed
an agent presses the Not Ready key a second time after entering Not Ready
state
WaitTime ends when the agent leaves the Idle state. If the agent handles another
contact from the same application as the most recently handled contact,
WaitTime resumes against that application when the agent returns to the Idle
state. If the agent handles a contact from a different application than the most
recently handled contact, WaitTime begins against the new application when the
agent returns to the Idle state.
For more information, see “How is WaitTime pegged if the agent puts a DN call
on hold and uses alternate call answer to accept another contact?” on page 117.
Pegging: WaitTime pegs against the last application for which the agent
handled a contact during this login. If the agent has not yet handled a contact
associated with an application, WaitTime is not pegged.
Type: int
Length: 4
The following table shows the statistics groups to which application statistics
can be linked, as well as the data fields used as linkage keys.
Specify all these fields as your linkage key, in the specified order.
CDNStat views
Statistics peg only for those intervals in which there are contacts coming into the
contact center through a CDN or Route Point. Incoming ACD, NACD, and DN
calls are not routed through CDNs or Route Points and are not included in these
statistics.
Definition: CDN
A Control Directory Number (CDN) is a number configured in the switch as the
entry point for voice contacts into Contact Center Manager. You can configure
multiple CDNs in the switch and associate them with the Master script of
Contact Center Manager.
Requirements
Fulfill the following requirements:
Define CDNs and Route Points on Contact Center Manager.
Configure the server to collect CDN statistics (see the Contact Center
Manager Administrator’s Guide). Statistics are collected for all CDNs and
Route Points; you cannot configure the system to collect statistics for only
selected CDNs or Route Points.
Database views
Control Directory Number (CDN) statistics use the following views:
iCDNStat
dCDNStat
wCDNStat
mCDNStat
Field descriptions
The field descriptions for this view are described in this section.
CallsAbandoned
Description: The number of local contacts and incoming NSBR calls
abandoned from this CDN or Route Point. This includes local contacts
networked out through the NSBR feature and abandoned or terminated at the
destination site.
This statistic includes contacts that receive the Give IVR treatment and are
presented with a messaging system voice menu, if the menu options are
programmed with CA (to go to a mailbox).
Type: int
Length: 4
CallsAnswered
Description: The number of local contacts and incoming NSBR contacts
answered by this CDN or Route Point. This includes local contacts that are
networked out through the NSBR feature and answered or accepted by an agent
or IVR at the destination site.
Pegging: Voice calls peg upon answer and multimedia contacts peg upon
acceptance.
A contact pegs as answered if, when it arrives at the destination site, the reserved
agent logs out or becomes unavailable and it receives one of the following
treatments:
Disconnect
Route
Give Recorded announcement (RAN)
Give IVR
Give Music
Type: int
Length: 4
CallsOffered
Description: The number of local contacts and incoming NSBR contacts
offered to this CDN or Route Point.
This statistics include voice calls that receive the Give IVR treatment and are
presented with a messaging system voice menu, if the menu options are
programmed with either CL (to go to a mailbox through a DN) or CA (to go to a
mailbox).
Type: int
Length: 4
CallsTerminated
Description: The number of local contacts and incoming NSBR contacts for
this CDN or Route Point, which are terminated under one of the following
conditions:
This statistic includes voice calls that receive the Give IVR treatment and are
presented with a messaging system voice menu, if the menu options are
programmed with CL (to go to a mailbox through a DN).
Type: int
Length: 4
CallsWithDigitsCollected
Description: Communication Server 2x00/DMS switch only. The number of
voice calls that received IVR treatment and arrived at this CDN accompanied by
data collected during the IVR session.
Type: int
Length: 4
CDN
Description: A unique number to identify this CDN or Route Point, which the
server assigns when the CDN or Route Point is added.
Type: varchar
Length: 30
CDNName
Description: The name of this CDN as configured when it is added.
Type: varchar
Length: 30
Site
Description: The configured name of this Contact Center Manager site.
Type: varchar
Length: 30
SiteID
Description: A unique number assigned by the system to identify this Contact
Center Manager site. The assigned SiteID remains unique over time even if a
configured site is deleted and another one is added with the same name. The
SiteID can be used in custom reports to identify statistics applicable to this site.
Time
Description: The time (in 24-hour HH:MM format) when the data is pegged by
the system.
Type: char
Length: 5
Timestamp
Description: The date and time when the data is pegged by the system. For
more information about the format of the Timestamp in interval, daily, weekly,
or monthly views, see “Overview of summarized historical statistics” on page
166.
Type: smalldatetime
Length: 4
URI
Description: The name of this Route Point as configured when it is added.
Type: varchar
Length: 255
DNISStat views
Definition: DNIS
DNIS is an optional service to identify the dialed number for calls entering the
contact center. Typically, DNIS numbers are used for 1-800 numbers. For
example, a company might give customers different 1-800 numbers for sales and
customer service calls.
Requirements
Fulfill the following requirements:
Define DNISs on Contact Center Manager.
Configure the server to collect DNIS statistics (see the Contact Center
Manager Administrator’s Guide). Statistics are collected for all DNISs;
you cannot configure the system to collect statistics for selected DNISs.
Database views
Dialed Number Identification Service (DNIS) statistics use the following views:
iDNISStat
dDNISStat
wDNISStat
mDNISStat
Field descriptions
The field descriptions for this view are described in this section.
CallsAbandoned
Description: The number of local Contact Center Manager calls and incoming
NSBR calls abandoned for a DNIS number.
Type: int
Length: 4
CallsAbandonedAftThreshold
Description: The number of local Contact Center Manager calls and incoming
NSBR calls abandoned that experienced a delay greater than or equal to the
service level threshold for the DNIS number.
Triggers: For local Contact Center Manager calls, delays begin when the
Master_Script is initiated. For incoming NSBR calls, delays begin when the call
is logically queued to this site.
Type: int
Length: 4
CallsAbandonedDelay
Description: The total wait time experienced by all local Contact Center
Manager calls and incoming NSBR calls abandoned for a DNIS number.
Triggers: For local Contact Center Manager calls, delays begin when the
Master_Script is initiated. For incoming NSBR calls, delays begin when the call
is logically queued to this site.
The delay time includes any time that the caller spends navigating menus and
listening to announcements before it is queued to a skillset.
Type: int
Length: 4
CallsAnswered
Description: The number of local Contact Center Manager calls and incoming
NSBR calls answered for a DNIS number.
Pegging: Calls peg upon answer.
Type: int
Length: 4
CallsAnsweredAftThreshold
Description: The number of local Contact Center Manager calls and incoming
NSBR calls answered that experienced a delay greater than or equal to the
service level threshold for the DNIS number.
Triggers: For local Contact Center Manager calls, delays begin when the
Master_Script is initiated. For incoming NSBR calls, delays begin when the call
is logically queued to this site.
Type: int
Length: 4
CallsAnsweredDelay
Description: The wait time experienced by all local Contact Center Manager
calls and incoming NSBR calls answered for a DNIS number.
Triggers: For local Contact Center Manager calls, delays begin when the
Master_Script is initiated. For incoming NSBR calls, delays begin when the call
is logically queued to this site.
The delay time includes any time that the caller spends navigating menus and
listening to announcements before it is queued to a skillset.
Type: int
Length: 4
CallsGivenDefault
Description: The number of local Contact Center Manager calls and incoming
NSBR calls given default treatment for a DNIS number.
Type: int
Length: 4
CallsGivenForceBusy
Description: The number of local Contact Center Manager calls and incoming
NSBR calls given Force Busy treatment for a DNIS number.
Pegging: This statistic pegs when the Give Busy script command is executed.
Type: int
Length: 4
CallsGivenForceDisconnect
Description: The number of local Contact Center Manager calls and incoming
NSBR calls given Force Disconnect treatment for a DNIS number.
Pegging: This statistic pegs when the Disconnect script command is executed.
Type: int
Length: 4
CallsGivenForceOverflow
Description: The number of local Contact Center Manager calls and incoming
NSBR calls given Force Overflow treatment for a DNIS number.
Pegging: This statistic pegs when the Give Overflow script command is
executed.
Type: int
Length: 4
CallsGivenRouteTo
Description: The number of local Contact Center Manager calls and incoming
NSBR calls given Route Call treatment for a DNIS number.
Pegging: This statistic pegs when the Route Call script command is executed.
Type: int
Length: 4
CallsNACDOut
Description: Communication Server 1000/Meridian 1 PBX switch only. The
number of local Contact Center Manager calls networked out through an NACD
queue and answered at remote sites.
CallsNetworkedOut
Description: NSBR option only. The number of local Contact Center Manager
calls routed to a remote site and answered or abandoned.
CallsOffered
Description: The number of local Contact Center Manager calls and incoming
NSBR calls offered to this server with this DNIS number.
Pegging: Calls peg upon arrival.
Type: int
Length: 4
CallsReachNonISDN
Description: NSBR option only. The number of local Contact Center Manager
calls that reached a non-ISDN trunk while it is routed to a remote site.
Pegging: Calls networked out using the MCDN networking are pegged against
this field if the call reaches a non-ISDN trunk.
Restriction: If a call encounters a non-ISDN trunk while it is networked to
another Contact Center Manager site, the call information that normally travels
with the call does not reach the destination site. This means the destination site
cannot tell that the call came from the Contact Center Manager network. At the
destination site, the networked call is treated as a new call. At the source site, the
NSBR call is pegged as terminated.
Type: int
Length: 4
DNIS
Description: A unique number used to identify a DNIS, which the server
assigns when the DNIS is defined.
Type: varchar
Length: 16
DNISName
Description: The name of a DNIS.
Type: varchar
Length: 30
DNIS_Prefix
Description: Stores the prefix of a DNIS number. You can sort, filter, and
report on individual DNIS 800 numbers.
Type: varchar
Length: 16
IVRTransferred
Description: The number of local Contact Center Manager calls and incoming
NSBR calls transferred from an IVR session for a DNIS number.
NetworkCDN
Description: For future use. Not valid in this release.
Type: varchar
Length: 30
MaxAbandonedDelay
Description: The wait time experienced by the local Contact Center Manager
calls or incoming NSBR call that waited the longest before it is abandoned.
Triggers: For local Contact Center Manager calls, delays begin when the
Master_Script is initiated. For incoming NSBR calls, delays begin when the call
is logically queued to this site.
Type: int
Length: 4
MaxAnsweredDelay
Description: The wait time experienced by the local Contact Center Manager
calls or incoming NSBR call that waited the longest before it is answered.
Triggers: For local Contact Center Manager calls, delays begin when the
Master_Script is initiated. For incoming NSBR calls, delays begin when the call
is logically queued to this site.
Type: int
Length: 4
Site
Description: The configured name of this Contact Center Manager site.
Type: varchar
Length: 30
SiteID
Description: A unique number assigned by the system to identify this Contact
Center Manager site. The assigned SiteID remains unique over time even if a
configured site is deleted and another one is added with the same name. The
SiteID can be used in custom reports to identify statistics applicable to this site.
TalkTime
Description: The total time spent by all agents on local Contact Center Manager
calls and incoming NSBR calls for a DNIS number, including hold time.
Triggers:
Communication Server 1000/Meridian 1 PBX switch: The call pegs
when the caller disconnects or the agent releases the call.
Communication Server 2x00/DMS switch: The time pegs when the agent
releases the call.
Pegging: Talk time pegs at the end of the interval (for calls that are active at the
end of an interval), and when the call terminates.
Type: int
Length: 4
Time
Description: The time (in 24-hour HH:MM format) when the data is pegged by
the system.
Type: char
Length: 5
Timestamp
Description: The date and time when the data is pegged by the system. For
more information about the format of the Timestamp in interval, daily, weekly,
or monthly views, see “Overview of summarized historical statistics” on page
166.
Type: smalldatetime
Length: 4
Type
Description: Distinguishes between local and landing-pad DNIS.
Type: tinyint
Length: 1
URI
Description: For future use. Not valid in this release.
Type: varchar
Length: 255
IVRPortStat views
Requirements
Fulfill the following requirements:
Define voice ports on Contact Center Manager.
Configure the server to collect IVR port statistics (see the Contact Center
Manager Administrator’s Guide). Statistics are collected for all IVR ports;
you cannot configure the system to collect statistics for selected ports.
Restrictions
IVR statistics may not be available if a third-party IVR application is used
instead of a messaging system application.
Database views
IVR port statistics use the following views:
iIVRPortStat
dIVRPortStat
wIVRPortStat
mIVRPortStat
Field descriptions
The field descriptions for this view are described in this section.
CallsAnswered
Description: The number of calls answered by this IVR port.
Pegging: Calls peg upon answer.
Type: int
Length: 4
CallsConferenced
Description: The number of calls conferenced out from this IVR port.
Type: int
Length: 4
CallsTransferred
Description: The number of calls transferred out from this IVR port.
Type: int
Length: 4
IVRPortID
Description: A unique number assigned by the server to identify an IVR port
when the voice port is defined.
Type: varchar
Length: 30
IVRPortName
Description: The name of the IVR port.
Type: varchar
Length: 30
IVRQueueID
Description: A unique number assigned by the server to identify an IVR queue
when the IVR ACD-DN is defined. This field is used for linking tables in data
queries.
Type: varchar
Length: 7
IVRQueueName
Description: The name of the IVR queue.
Type: varchar
Length: 30
LoggedInTime
Description: The total time the IVR port is logged on.
Type: int
Length: 4
NotReadyTime
Description: The total time spent by the IVR port in the Not Ready state.
Type: int
Length: 4
Site
Description: The configured name of this Contact Center Manager site.
Type: varchar
Length: 30
SiteID
Description: A unique number assigned by the system to identify this Contact
Center Manager site. The assigned SiteID remains unique over time even if a
configured site is deleted and another one is added with the same name. The
SiteID can be used in custom reports to identify statistics applicable to this site.
Length: 4
TalkTime
Description: The total time the IVR port is in use.
Type: int
Length: 4
Time
Description: The time (in 24-hour HH:MM format) when the data is pegged by
the system.
Type: char
Length: 5
Timestamp
Description: The date and time when the data is pegged by the system. For
more information about the format of the Timestamp in interval, daily, weekly,
or monthly views, see “Overview of summarized historical statistics” on page
166. This field is used for linking tables in data queries.
Type: smalldatetime
Length: 4
WaitingTime
Description: The total time the IVR port is idle.
Type: int
Length: 4
The table on page 292 shows the views which application statistics link to, as
well as the data fields used as a linkage key.
Specify both of these fields as your linkage key, in the specified order.
If you generate a custom report THEN the linkage key data fields
using are
IVRStat Timestamp
IVRQueueID
IVRStat views
Interactive Voice Response (IVR) statistics monitor the usage of the port
resources of an ACCESS IVR queue.
You can use these statistics to determine whether enough resources exist to
handle the number of calls utilizing Open/Close Voice Session, Give Controlled
Broadcast, and Give IVR commands.
Requirements
Fulfill the following requirements:
Define IVR ACD-DNs on Contact Center Manager.
Configure the server to collect IVR queue statistics (see the Contact Center
Manager Administrator’s Guide). Statistics are collected for all IVR
queues; you cannot configure the system to collect statistics for selected
IVR queues.
Restrictions
IVR statistics may not be available if you use a third-party IVR application
instead of Meridian Mail or CallPilot.
Database views
IVR statistics use the following views:
iIVRStat
dIVRStat
wIVRStat
mIVRStat
Field descriptions
The field descriptions for this view are described in this section.
CallsAnswered
Description: The number of calls answered by this IVR queue.
Pegging: Calls peg upon answer.
Type: int
Length: 4
CallsAnsweredAftThreshold
Description: The number of calls answered that experienced a delay greater
than or equal to the service level threshold for the threshold class to which the
IVR ACD-DN belongs.
Type: int
Length: 4
CallsAnsweredDelay
Description: The total wait time experienced by all the calls answered.
Triggers: The delay begins when a call enters the IVR queue.
Type: int
Length: 4
CallsConferenced
Description: The number of calls conferenced out during an IVR session.
Type: int
Length: 4
CallsNotTreated
Description: The number of calls abandoned or pulled back while waiting in
this IVR queue.
Type: int
Length: 4
CallsNotTreatedAftThreshold
Description: The number of calls abandoned or pulled back that experienced a
delay greater than or equal to the service level threshold for the threshold class
to which the IVR ACD-DN belongs.
Triggers: The delay begins when a call is queued against the IVR queue and
ends when the call is abandoned or pulled back.
Type: int
Length: 4
CallsNotTreatedDelay
Description: The total wait time experienced by all the calls abandoned or
pulled back from an IVR queue.
Triggers: The delay begins when a call is queued against the IVR queue and
ends when the call is abandoned or pulled back.
Type: int
Length: 4
CallsOffered
Description: The number of calls offered to this IVR queue.
Type: int
Length: 4
CallsTransferred
Description: The number of calls transferred out during an IVR session.
Type: int
Length: 4
IVRAbandoned
Description: The number of calls abandoned during an IVR session.
Type: smallint
Length: 2
IVRCompleted
Description: The number of calls for which the IVR session completed
successfully.
Pegging: This statistic pegs when the IVR port disconnects.
Type: smallint
Length: 2
IVRInterrupted
Description: The number of calls interrupted by a script command during an
IVR session.
Type: smallint
Length: 2
IVRQueueID
Description: A unique number assigned by the server to identify an IVR queue
when the IVR ACD-DN is defined. This field is used for linking tables in data
queries.
Type: varchar
Length: 7
IVRQueueName
Description: The name of the IVR queue.
Type: varchar
Length: 30
Site
Description: The configured name of this Contact Center Manager site.
Type: varchar
Length: 30
SiteID
Description: A unique number assigned by the system to identify this Contact
Center Manager site. The assigned SiteID remains unique over time even if a
configured site is deleted and another one is added with the same name. The
SiteID can be used in custom reports to identify statistics applicable to this site.
Time
Description: The time (in 24-hour HH:MM format) when the data is pegged by
the system.
Type: char
Length: 5
Timestamp
Description: The date and time when the data is pegged by the system. For
more information about the format of the Timestamp in interval, daily, weekly,
or monthly views, see “Overview of summarized historical statistics” on page
166. This field is used for linking tables in data queries.
Type: smalldatetime
Length: 4
The following table shows the views which application statistics can link to, as
well as the data fields used as a linkage key.
Specify both of these fields as your linkage key, in the specified order.
IF you generate a custom report THEN the linkage key data fields
using are
IVRPortStat Timestamp
IVRQueueID
LicenseStat views
You can use License Manager statistics to view the distribution of licenses
between each of the Contact Center Manager applications—Contact Center
Manager Server, Contact Center Manager Administration, Communication
Control Toolkit, and Contact Center Multimedia—in the network. Statistics are
collected on the server running the License Manager Server.
The record statistics for the maximum license issued to each server in the
interval.
Requirements
License Manager statistics are collected by default.
Restrictions
Servers are identified by the IP address and not the server name.
Database views
License Manager statistics use the following views:
iLicenseStat
dLicenseStat
wLicenseStat
mLicenseStat
Field descriptions
The field descriptions for this view are described in this section.
ClientAddress
Description: The IP address of the client machine where the licenses are issued.
Type: varchar
Length: 30
Feature
Description: The Contact Center Manager feature issued to the client.
Type: varchar
Length: 70
MaxNumberLicenses
Description: The maximum number of licenses held by the client machine in
that interval. For example, the maximum number of licenses held each day.
Type: int
Length: 4
Timestamp
Description: The date and time when the data is pegged by the system. For
more information about the format of the Timestamp in interval, daily, weekly,
or monthly views, see “Overview of summarized historical statistics” on page
166. This field is used for linking tables in data queries.
Type: datetime
Length: 8
NetworkInCallStat views
NSBR option only. Network call statistics provide information that can be used
to monitor contact distribution and handling in a network environment. They
record statistics for all incoming NSBR contacts received at a site.
Network statistics only report on contacts that are controlled by the server (that
is, Contact Center Manager contacts and multimedia contacts). They do not
report on DN, ACD, or NACD calls.
Requirements
Configure the server to collect network call statistics (see the Contact Center
Manager Administrator’s Guide). Statistics are collected for all applications;
you cannot configure the system to collect statistics for selected applications.
Restrictions
Network call statistics generated on the server are collected on the destination
site only. To report on network contact handling at all sites, generate a network-
wide report from the Network Control Center.
Database views
Network call statistics use the following views:
iNetworkInCallStat
dNetworkInCallStat
wNetworkInCallStat
mNetworkInCallStat
Field descriptions
The field descriptions for this view are described in this section.
CallsAbandoned
Description: The number of incoming NSBR contacts abandoned at the local
site.
Type: int
Length: 4
CallsAbandonedAftThreshold
Description: The number of incoming NSBR contacts abandoned at the local
site after a wait that exceeds the service level threshold for the application.
Type: int
Length: 4
CallsAbandonedDelay
Description: The total wait time experienced by all incoming NSBR contacts
abandoned at the local site.
Triggers: Delays begin when the Master_Script is initiated at the source site and
end when the contact is abandoned at the local site.
The delay time includes any time that the caller spends going through menus and
listening to announcements before it is queued to a skillset.
iNetworkInCallStat int 4
dNetworkInCallStat int 4
wNetworkInCallStat numeric 6
mNetworkInCallStat numeric 6
CallsAbandonedDelayAtDest
Description: The total wait time experienced at the local site by all incoming
NSBR contacts abandoned at the local site.
Triggers: Delays begin when the Master_Script is initiated and end when the
contact is abandoned at the local site.
iNetworkInCallStat int 4
dNetworkInCallStat int 4
wNetworkInCallStat numeric 6
mNetworkInCallStat numeric 6
CallsAnswered
Description: The number of incoming NSBR contacts answered or accepted at
the local site.
Type: int
Length: 4
CallsAnsweredAftThreshold
Description: The number of incoming NSBR contacts answered or accepted at
the local site after a wait greater than or equal to the service level threshold for
the application. The delay begins when a contact enters the local site. The
service level threshold is set during system configuration of the local site.
Type: int
Length: 4
CallsAnsweredDelay
Description: The total wait time experienced by all incoming NSBR contacts
answered or accepted at the local site.
Triggers: Delays begin when the Master_Script is initiated at the source site and
end when the contact is answered or accepted at the local site.
The delay time includes any time that the caller spends going through menus and
listening to announcements in this application.
iNetworkInCallStat int 4
dNetworkInCallStat int 4
wNetworkInCallStat numeric 6
mNetworkInCallStat numeric 6
CallsAnsweredDelayAtDest
Description: The total wait time experienced at the local site by all incoming
NSBR contacts answered or accepted at the local site.
Triggers: Delays begin when the contact is queued to the local site and end
when the contact is answered or accepted at the local site.
iNetworkInCallStat int 4
dNetworkInCallStat int 4
wNetworkInCallStat numeric 6
mNetworkInCallStat numeric 6
CallsOffered
Description: The number of incoming NSBR contacts offered to the local site.
Type: int
Length: 4
DstApplication
Description: The name of the destination application. This name is always
Network_Script.
Type: varchar
Length: 30
DstApplicationID
Description: A unique number assigned by the server to identify the
Network_Script application.
Type: int
Length: 4
DstSite
Description: The name of the local Contact Center Manager site, as defined on
the Network Control Center.
Type: varchar
Length: 30
DstSiteID
Description: A unique number assigned by the server to identify the local
Contact Center Manager site when the site is defined on the Network Control
Center.
Type: int
Length: 4
MaxCallAbandonedDelay
Description: The wait time experienced by the incoming NSBR contact that
waited the longest before it is abandoned at the local site.
Triggers: Delays begin when the Master_Script is initiated at the source site and
end when the contact is abandoned at the local site.
Type: int
Length: 4
MaxCallAbandonedDelayAtDest
Description: The wait time experienced by the contact that waited the longest at
the local site before it is abandoned.
Triggers: Delays begin when a contact is logically queued to the local site and
end when the contact is abandoned.
Type: int
Length: 4
MaxCallAnsweredDelay
Description: The total wait time experienced by all calls answered or contacts
accepted at the local site.
Triggers: Delays begin when the Master_Script is initiated at the source site and
end when the call is answered or contact is accepted at the local site.
Type: int
Length: 4
MaxCallAnsweredDelayAtDest
Description: The wait time experienced by the contact that waited the longest at
the local site before it is answered or accepted.
Triggers: Delays begin when a contact is logically queued to the local site and
end when the contact is answered or accepted.
Type: int
Length: 4
SrcApplication
Description: The name of the source application.
Type: varchar
Length: 30
SrcApplicationID
Description: A unique number assigned by the server to identify the source
application when the application is defined.
Type: int
Length: 4
SrcSite
Description: The name of the source Contact Center Manager site, as assigned
when the site is defined on the Network Control Center.
Type: varchar
Length: 30
SrcSiteID
Description: The unique identifier for the source Contact Center Manager site
where a call originated.
Type: int
Length: 4
Time
Description: The time (in 24-hour HH:MM format) when the data is pegged by
the system.
Type: char
Length: 5
Timestamp
Description: The date and time when the data is pegged by the system, in local
(destination) site time. For more information about the format of the Timestamp
in interval, daily, weekly, or monthly views, see “Overview of summarized
historical statistics” on page 166. This field is used for linking tables in data
queries.
Type: smalldatetime
Length: 4
The table on page 307 shows the statistics groups which network call statistics
can link to, as well as the data fields used as linkage keys.
Specify all these fields as your linkage key, in the specified order.
NetworkOutStat views
Requirements
Configure the server to collect network outcall statistics (see the Contact Center
Manager Administrator’s Guide).
Restrictions
At each Contact Center Manager site, the historical network outgoing contact
statistics are only collected against the local site. These statistics contain
network outgoing contact traffic and handling information for contacts for
which the local site is the source.
Database views
Network outgoing contact statistics use the following views:
iNetworkOutStat
dNetworkOutStat
wNetworkOutStat
mNetworkOutStat
Field descriptions
The field descriptions for this view are described in this section.
CallsAbandoned
Description: The number of contacts abandoned at the destination site.
Type: int
Length: 4
CallsAbandonedDelayAtDest
Description: The total wait time experienced at the destination site by all
contacts from the local site abandoned at the destination site.
This statistic does not include Contact Center Multimedia Web Communication
or text chat contacts that are abandoned.
Triggers: Delays begin when the contact is queued to the destination site and
end when the contact is abandoned.
iNetworkOutStat int 4
dNetworkOutStat int 4
wNetworkOutStat numeric 6
mNetworkOutStat numeric 6
CallsAnswered
Description: The number of contacts answered or accepted by an agent,
answered by IVR, or terminated at the destination site.
Pegging: A contact pegs as answered if, when it arrives at the destination site,
the reserved agent logs off or becomes unavailable and it receives one of the
following treatments:
Disconnect
Route
Give Recorded announcement (RAN)
Give IVR
Give Music
Type: int
Length: 4
CallsAnsweredDelayAtDestination
Description: The total wait time experienced at the destination site by all
contacts from the local site answered or accepted by an agent, answered by IVR,
or terminated at the destination site.
Triggers: Delays begin when the contact is queued to the destination site and
end when the contact is answered or accepted.
iNetworkOutStat int 4
dNetworkOutStat int 4
wNetworkOutStat numeric 6
mNetworkOutStat numeric 6
CallsOffered
Description: The number of contacts offered to the destination site.
Type: int
Length: 4
DstApplication
Description: The name of the destination application (this is always
Network_Script).
Type: varchar
Length: 30
DstApplicationID
Description: A unique number assigned by the server to identify the destination
application.
Type: int
Length: 4
DstSite
Description: The name of the destination Contact Center Manager site, as
defined when the site is configured on the Network Control Center.
Type: varchar
Length: 30
DstSiteID
Description: A unique number assigned by the server to identify a destination
site when the site is configured on the Network Control Center.
Type: int
Length: 4
MaxCallsAbandonedDelay
Description: The wait time experienced by the contact originating at the local
site that waited the longest before it is abandoned at the destination site.
Triggers: Delays begin when the Master_Script is initiated at the local site and
end when the contact is abandoned.
Type: int
Length: 4
MaxCallsAbandonedDelayAtDest
Description: The wait time experienced by the contact originating at the local
site that waited the longest at the destination site before it is abandoned.
Triggers: Delays begin when the contact is queued to the destination site and
end when the contact is abandoned.
Type: int
Length: 4
MaxCallsAnsweredDelay
Description: The wait time experienced by the contact originating at the local
site that waited the longest before it is answered or accepted by an agent,
answered by IVR, or terminated at the destination site.
Triggers: Delays begin when the Master_Script is initiated at the local site and
end when the contact is answered or accepted.
Type: int
Length: 4
MaxCallsAnsweredDelayAtDest
Description: The wait time experienced by the contact originating at the local
site that waited the longest at the destination site before it is answered or
accepted by an agent, answered by IVR, or terminated.
Triggers: Delays begin when the contact is logically queued to the destination
site and end when the contact is answered or accepted.
Type: int
Length: 4
SrcApplication
Description: The name of the source application.
Type: varchar
Length: 30
SrcApplicationID
Description: A unique number assigned by the server to identify the source
application when the application is defined.
Type: int
Length: 4
SrcSite
Description: The name of the local site, as defined when the site is defined on
the Network Control Center.
Type: varchar
Length: 30
SrcSiteID
Description: A unique number assigned by the server to identify a source
Contact Center Manager site where a call originated when the site is defined on
the Network Control Center.
Type: int
Length: 4
Time
Description: The time (in 24-hour HH:MM format) when the data is pegged by
the system.
Type: char
Length: 5
Timestamp
Description: The date and time when the data is pegged by the system, in local
(source) site time. For more information about the format of the Timestamp in
interval, daily, weekly, or monthly views, see “Overview of summarized
historical statistics” on page 166. This field is used for linking tables in data
queries.
Type: smalldatetime
Length: 5
TotalCallsAbandonedDelay
Description: The total wait time experienced by all contacts from the local site
abandoned at the destination site.
Triggers: Delays begin when the Master_Script is initiated at the local site and
end when the contact is abandoned.
iNetworkOutStat int 4
dNetworkOutStat int 4
wNetworkOutStat numeric 6
mNetworkOutStat numeric 6
TotalCallsAnsweredDelay
Description: The total wait time experienced by all contacts from the local site
answered or accepted by an agent, answered by IVR, or terminated at the
destination site.
Triggers: Delays begin when the Master_Script is initiated at the local site and
end when the contact is answered.
iNetworkOutStat int 4
dNetworkOutStat int 4
wNetworkOutStat numeric 6
mNetworkOutStat numeric 6
The following table shows the statistics groups which network call statistics can
link to, as well as the data fields used as linkage keys.
Specify all these fields as your linkage key, in the specified order.
RANMusicRouteStat views
RAN and music route statistics are not applicable to multimedia contacts.
Requirements
Fulfill the following requirements:
Define RAN and music routes codes on Contact Center Manager.
Configure the server to collect music and route statistics (see the Contact
Center Manager Administrator’s Guide). Statistics are collected for all
music and RAN routes; you cannot configure the system to collect statistics
for selected routes.
Database views
RAN and music route statistics use the following views:
iRANMusicRouteStat
dRANMusicRouteStat
wRANMusicRouteStat
mRANMusicRouteStat
Field descriptions
The field descriptions for this view are described in this section.
RouteAccess
Description: The number of times a music or RAN route is accessed. Each time
the route is accessed by a single call, this statistic is incremented.
Type: int
Length: 4
RouteAccessTime
Description: The total time a music or RAN route is in use.
Type: int
Length: 4
RouteID
Description: A unique number assigned by the server to identify a music or
RAN route when the route is defined.
Type: int
Length: 4
RouteName
Description: The name of the music or RAN route.
Type: varchar
Length: 30
Site
Description: The configured name of this Contact Center Manager site.
Type: varchar
Length: 30
SiteID
Description: A unique number assigned by the system to identify this Contact
Center Manager site. The assigned SiteID remains unique over time even if a
configured site is deleted and another one is added with the same name. The
SiteID can be used in custom reports to identify statistics applicable to this site.
Time
Description: The time (in 24-hour HH:MM format) when the data is pegged by
the system.
Type: char
Length: 5
Timestamp
Description: The date and time when the data is pegged by the system. For
more information about the format of the Timestamp in interval, daily, weekly,
or monthly views, see “Overview of summarized historical statistics” on page
166.
Type: smalldatetime
Length: 4
RouteStat views
Requirements
Fulfill the following requirements:
Define routes on Contact Center Manager.
Configure the server to collect route statistics (see the Contact Center
Manager Administrator’s Guide). Statistics are collected for all routes; you
cannot configure the system to collect statistics for selected routes.
Pegging
CallsBlockedByAllTrunksBusy statistics apply to multiple routes and peg
against the Default_Route, 999.
Database views
Route statistics use the following views:
iRouteStat
dRouteStat
wRouteStat
mRouteStat
Field descriptions
The field descriptions for this view are described in this section.
AllTrunksBusy
Description: The number of times all trunks in this route are busy.
Type: int
Length: 4
AllTrunksBusyTime
Description: The total time all trunks in this route are busy.
Type: int
Length: 4
CallsBlockedByAllTrunksBusy
Description: NSBR option only. The number of calls offered to the network
through this route are blocked because all trunks are busy.
Pegging: This field pegs only against the Default_Route, 999.
Type: int
Length: 4
CallsReachNonISDN
Description: NSBR option only. The number of calls that reached a non-ISDN
trunk while it is routed to a remote site through this route.
Restriction: If a call encounters a non-ISDN trunk while it is networked to
another Contact Center Manager site, the call information that normally travels
with the call does not reach the destination site. This means the destination site
cannot tell that the call came from the Contact Center Manager network. At the
destination site, the networked call is treated as a new call. At the source site, the
NSBR call is treated as terminated.
Type: int
Length: 4
RouteID
Description: A unique number assigned by the server to identify a route when
the route is defined. This field is used for linking tables in data queries.
Type: int
Length: 4
RouteName
Description: The name of the route.
Type: varchar
Length: 30
Site
Description: The configured name of this Contact Center Manager site.
Type: varchar
Length: 30
SiteID
Description: A unique number assigned by the system to identify this Contact
Center Manager site. The assigned SiteID remains unique over time even if a
configured site is deleted and another one is added with the same name. The
SiteID can be used in custom reports to identify statistics applicable to this site.
Time
Description: The time (in 24-hour HH:MM format) when the data is pegged by
the system.
Type: char
Length: 5
Timestamp
Description: The date and time when the data is pegged by the system. For
more information about the format of the Timestamp in interval, daily, weekly,
or monthly views, see “Overview of summarized historical statistics” on page
166. This field is used for linking tables in data queries.
Type: smalldatetime
Length: 4
The table on page 322 shows the views which route statistics can link to, as well
as the data fields used as a linkage key.
Specify both of these fields as your linkage key, in the specified order.
IF you generate a custom report THEN the linkage key data fields
using are
TrunkStat Timestamp
RouteID
SCCSDBSpace views
SCCSDBSpace views display information about the size of the Contact Center
Manager database, including:
space allocated for the database
space used by the database
space available
With a report writer application, you can create a custom report using this view.
Field descriptions
The field descriptions for this view are described in this section.
DBName
Description: The name of the database. Contact Center Manager uses three
databases:
Master—Contains Sybase control information.
Blue—Contains all server configuration information and interval, daily,
weekly, and monthly statistics.
Call-by-call (CBC)—Contains call-by-call data, if you configure your
server to collect it.
Type: varchar
Length: 30
DBSize
Description: The database size in MB.
Type: float
Length: 8
FreeSpace
Description: The amount of free space in the database in MB.
Type: float
Length: 8
UsedSpace
Description: The current data volume in the database in MB.
Type: float
Length: 8
SkillsetStat views
Statistics peg for a given skillset only for those intervals in which the skillset is
staffed.
Only contacts queued to a skillset are included in these statistics (if a skillset is
mapped to an ACD DN or NACD DN, calls to that DN are included). Except for
DNOutExtCallsTalkTime and DNOutIntCallsTalkTime, these statistics do not
include DN calls.
Requirements
Configure the server to collect skillset statistics (see the Contact Center
Manager Administrator’s Guide). Statistics are collected for all skillsets; you
cannot configure the system to collect statistics for selected skillsets.
Pegging
All statistics peg against a specific skillset and application combination and
either the local or originating site.
Local contacts
Local Contact Center Manager contacts peg against the Master_Script or
primary application (depending on the location of the call in the system) and
against the answering skillset, or the Agent Queue To skillset (if the contact is
queued to a specific agent for the contact's contact type).
Closed contacts that are pulled for additional processing by the agent are pegged
against the Agent Queue To skillset for the contact’s contact type. New and New
Reply contacts that are pulled while already within Contact Center Manager are
pegged against the skillset they are queuing in, if any, up to the time they are
pulled, and then against the Agent Queue To skillset for the contact type. Local
contacts peg against the local site.
ACD calls
ACD calls peg against the ACD_DN_Application and either the skillset to
which this ACD-DN is mapped (if defined) or the Default_ACD skillset. ACD
calls peg against the local site.
NACD calls
NACD calls peg against the NACD_DN_Application and either the skillset to
which this Network ACD-DN is mapped (if defined) or the Default_NACD
skillset. NACD calls peg against the local site.
Pegging thresholds
You can define skillset threshold classes with different values for the service
level threshold and the length (talk time, handling time) of a short call or
contact. Thus, the value for service level and short call length can vary from one
skillset to another. For more information about threshold classes, refer to the
Contact Center Manager Administrator’s Guide.
For ACD calls, the server does not record information about call activity on the
switch. ACD calls are tracked from the time they are answered at a phoneset
acquired by Contact Center Manager.
Database views
Skillset statistics use the following views:
iSkillsetStat
dSkillsetStat
wSkillsetStat
mSkillsetStat
Field descriptions
The field descriptions for this view are described in this section.
ActiveTime
Description: The amount of time a skillset is in service. A skillset is in service
when it is not in Out of Service mode and at least one agent is logged on.
AllAgentBusyTime
Description: The total time that all agents assigned to this skillset are busy with
contacts or no agents are logged on.
Pegging: This field pegs only against the System_Application.
Type: int
Length: 4
Application
Description: The name of the application that queued the contact to this skillset.
Type: varchar
Length: 30
ApplicationID
Description: A unique number assigned by the server to identify an application
when the application is defined. This field is used for linking tables in data
queries.
Type: int
Length: 4
CallsAnswered
Description: The number of local contacts (excluding DN calls), incoming
NSBR calls, ACD calls, and NACD calls answered or accepted by agents in this
skillset.
CallsAnsweredAfterThreshold
Description: The number of local contacts (excluding DN, ACD and NACD
calls) and incoming NSBR contacts answered or accepted after a wait greater
than or equal to the service level threshold for the threshold class to which the
skillset belongs.
CallsAnsweredDelay
Description: The wait time experienced by all local contacts—excluding DN,
ACD, and NACD calls—and incoming NSBR contacts answered or accepted for
this skillset.
CallsOffered
Description: The number of contacts—excluding DN, ACD, and NACD
calls—offered to this skillset, regardless of whether the contacts are answered or
accepted for this skillset. This statistic is not incremented if the same contact is
offered to this skillset again.
Triggers: Contacts peg against the Master_Script application upon arrival, and
against a primary application when the Master_Script application hands over
control.
ContactType
Description: The type of contact determined by the name of this skillset. This
applies to SIP-enabled contact centers, MCS 5100 contact centers, if Contact
Center Multimedia, or if Contact Center Outbound is installed and this skillset
name begins with one of the configured prefixes as described in “Associating
contact types with applications and skillsets” on page 186.
DNOutExtCallsTalkTime
Description: Communication Server 1000/Meridian 1 PBX switch only. The
total time spent by agents on outgoing external DN calls (see “Internal versus
External DN calls” on page 181 for a definition of external DN calls), including
hold time, for this skillset. This statistic does not include the time spent on the
DN outcall part of a Contact Center Outbound contact.
Triggers: DNOutExtCallsTalkTime begins when the call is answered and the
agent's previous contact was queuing in this skillset. Talk time ends when the
caller disconnects or the agent releases the call. For a three-way conference call,
talk time ends only when the agent releases the call.
Type: int
Length: 4
DNOutIntCallsTalkTime
Description: Communication Server 1000/Meridian 1 PBX switch only. The
total time spent by agents on outgoing internal DN calls (see “Internal versus
External DN calls” on page 181 for a definition of internal DN calls), including
hold time, for this skillset. This statistic does not include the time spent on the
DN outcall part of a Contact Center Outbound contact.
Triggers: DNOutIntCallsTalkTime begins when the call is answered and the
agent's previous contact was queuing for this skillset. Talk time ends when the
caller disconnects or the agent releases the call. For a three-way conference call,
talk time ends only when the agent releases the call.
Type: int
Length: 4
MaxAnsweredDelay
Description: The wait time experienced by the local contact—excluding DN,
ACD, and NACD calls—or incoming NSBR contact that waited the longest
before it is answered or accepted.
MaxSkillsetAbandonedDelay
Description: The wait time experienced by the local contact—excluding DN,
ACD, and NACD calls—or incoming NSBR contact queued to this skillset that
waited the longest before it is abandoned.
NetCallsAnswered
Description: NSBR option only. The number of incoming NSBR contacts
answered or accepted for this skillset.
Type: int
Length: 4
PostCallProcessingTime
Description: This data is the total time agents spent performing post-contact
processing. Normally, agents use this time to complete any work related to the
contact just completed, such as filling in forms or filing papers.
Triggers: Post-call processing time begins when an agent presses Not Ready
after releasing any contact, except DN calls, and ends when the agent presses
Not Ready again, places or receives a DN call, or logs out.
Post Call Processing Time is calculated for the first Not Ready period after a
contact is closed. If the agent enters another state after the call (for example, by
answering or receiving a DN call or logging out of the skillset), and then enters
Not Ready state, the Not Ready time does not peg against
PostCallProcessingTime. Also, if the agent interrupts the Not Ready period to
enter another state, and then returns to Not Ready state, the second Not Ready
period does not peg against PostCallProcessingTime.
Pegging: This statistic pegs against the last skillset for which the agent handled
a contact.
Type: int
Length: 4
Site
Description: The configured name of the Contact Center Manager site that the
fields are applicable to. For incoming NSBR contacts, this is the originating site.
SiteID
Description: A unique number assigned by the system to identify the Contact
Center Manager site that the fields are applicable to. The assigned SiteID
remains unique over time even if a configured site is deleted and another one is
added with the same name. The SiteID can be used in custom reports to identify
statistics applicable to a particular site.
For incoming NSBR contacts, this is SiteID of the originating site. For the local
site, the SiteID is set to 0.
Skillset
Description: The name of the skillset.
Type: varchar
Length: 30
SkillsetAbandoned
Description: The number of contacts abandoned while queuing in this skillset.
This statistic does not include contacts abandoned while being presented to an
agent.
Type: int
Length: 4
SkillsetAbandonedDelay
Description: The total wait time experienced by contacts abandoned while
queuing in this skillset.
Triggers: The delay begins when the contact is queued to this skillset and ends
when the contact is abandoned.
Type: int
Length: 4
SkillsetAbandonedAftThreshold
Description: The number of contacts abandoned while queuing in this skillset
after a wait greater than or equal to the service level threshold for the threshold
class to which the skillset belongs.
Type: int
Length: 4
SkillsetID
Description: A unique number assigned by the server to identify this skillset
when the skillset is added. For network skillsets, this is the ID as it appears on
the local site.
Type: int
Length: 4
TalkTime
Description: The total time that agents spent handling contacts (excluding DN
calls) in this interval, that were queuing in this skillset. This statistic includes
hold time.
Triggers: The follow items trigger this statistic:
For voice calls, talk time begins when the agent answers the call.
For the Communication Server 1000/Meridian 1 PBX switch, talk time
ends when the caller disconnects or the agent releases or transfers the call.
For the Communication Server 2x00 switch, talk time ends when the agent
releases or transfers the call.
For multimedia contacts, talk time begins when the agent accepts the
contact and ends when the agent closes or transfers the contact.
For Contact Center Outbound contacts, talk time begins when the agent
accepts the contact, includes the time the agent is on the DN call, and ends
when the agent releases the DN call and closes the contact.
Type: int
Length: 4
Time
Description: The time (in 24-hour HH:MM format) when the data is pegged by
the system.
Type: int
Length: 5
Timestamp
Description: The date and time when the data is pegged by the system. For
more information about the format of the Timestamp in interval, daily, weekly,
or monthly views, see “Overview of summarized historical statistics” on page
166. This field is used for linking tables in data queries.
Type: smalldatetime
Length: 4
TotalStaffedTime
Description: The amount of logon time for all agents belonging to this skillset.
Pegging: This field pegs only against the System_Application.
Triggers: The logon time begins when an agent logs on to the skillset or is
reassigned (while logged on) to the skillset and ends when the agent logs off or
is reassigned out of the skillset.
Type: int
Length: 4
VirtualCallsAbandoned
Description: The number of contacts abandoned while queuing in this skillset,
provided that:
if the contact is queued to multiple skillsets simultaneously, this skillset is
the first listed skillset in the script.
for NSBR contacts, the contact originated from this site.
Type: int
Length: 4
VirtualCallsOffered
Description: The number of contacts offered in this skillset that are:
answered or accepted by an agent in this skillset and on this site.
or
WaitTime
Description: The total time agents spend waiting for a contact after releasing a
voice call or closing a multimedia contact handled that was queuing in this
skillset.
Triggers: WaitTime begins when the agent goes into Idle state, for example, if:
an agent releases a voice call or closes a multimedia contact, and the
agent’s call presentation class is not configured for Break time or Variable
Wrap
an agent’s Break or Variable Wrap timer elapses after a contact is released
or closed
an agent presses the Not Ready key a second time after entering Not Ready
state
WaitTime ends when the agent leaves the Idle state. If the agent handles another
contact from the same skillset as the most recently handled contact, WaitTime
resumes against that skillset when the agent returns to the Idle state. If the agent
handles a contact from a different skillset than the most recently handled
contact, WaitTime begins against the new skillset when the agent returns to the
Idle state.
For more information, see “How is WaitTime pegged if the agent puts a DN call
on hold and uses alternate call answer to accept another contact?” on page 117.
Pegging: WaitTime pegs against the last skillset for which the agent handled a
contact during this login. If the agent has not yet handled a contact that was
queuing in a skillset, WaitTime is not pegged.
Type: int
Length: 4
The following table shows the statistics groups which skillset statistics can link
to, as well as the data fields used as linkage keys.
Specify both of these fields as your linkage key, in the specified order.
TrunkStat views
Requirements
Fulfill the following requirements:
Define the routes to which the trunks belong on Contact Center Manager.
Configure the server to collect trunk statistics (see the Contact Center
Manager Administrator’s Guide). Statistics are collected for all trunks; you
cannot configure the system to collect statistics for selected trunks.
Database views
Trunk statistics use the following views:
iTrunkStat
dTrunkStat
wTrunkStat
mTrunkStat
Field descriptions
The field descriptions for this view are described in this section.
CallsAbandoned
Description: The number of Contact Center Manager calls abandoned while
waiting on this trunk.
Type: int
Length: 4
CallsAbandonedDelay
Description: The total wait time experienced by Contact Center Manager calls
that are abandoned.
Triggers: For local Contact Center Manager calls and outgoing NSBR calls,
delays begin when the Master_Script is initiated. For incoming NSBR calls,
delays begin when the call is logically queued to this site.
Type: int
Length: 4
CallsAnswered
Description: The number of Contact Center Manager calls answered.
Triggers: Calls peg upon answer.
Type: int
Length: 4
CallsAnsweredDelay
Description: The total wait time experienced by all Contact Center Manager
calls that came in through a trunk.
Triggers: For local Contact Center Manager calls and outgoing NSBR calls,
delays begin when the Master_Script is initiated. For incoming NSBR calls,
delays begin when the call is logically queued to this site.
Type: int
Length: 4
CallsOffered
Description: The number of Contact Center Manager calls offered to this trunk.
Triggers: Calls peg upon arrival.
Type: int
Length: 4
OccupancyTime
Description: The total time the trunk is occupied with Contact Center Manager
calls.
Triggers: Occupancy times begin when the Master_Script is initiated at the
source site and end when the call ends.
Type: int
Length: 4
Route
Description: The name of the route.
Type: varchar
Length: 30
RouteID
Description: A unique number assigned by the server to identify the route to
which the trunk belongs when the route is defined. This field is used for linking
tables in data queries.
Type: int
Length: 4
Site
Description: The configured name of this Contact Center Manager site.
Type: varchar
Length: 30
SiteID
Description: A unique number assigned by the system to identify this Contact
Center Manager site. The assigned SiteID remains unique over time even if a
configured site is deleted and another one is added with the same name. The
SiteID can be used in custom reports to identify statistics applicable to this site.
The actual local SiteID value is written in this field. SIP uses the configuration
default SiteID.
Type: int
Length: 4
Time
Description: The time (in 24-hour HH:MM format) when the data is pegged by
the system.
Type: char
Length: 5
Timestamp
Description: The date and time when the system pegs the data. For more
information about the format of the Timestamp in interval, daily, weekly, or
monthly views, see “Overview of summarized historical statistics” on page 166.
This field is used for linking tables in data queries.
Type: smalldatetime
Length: 4
TrunkID
Description: A unique number assigned by the server to identify the trunk
within the route.
Type: int
Length: 4
The following table shows the views which application statistics can link to, as
well as the data fields used as a linkage key.
Specify both of these fields as your linkage key, in the specified order.
IF you generate a custom report THEN the linkage key data fields
using are
RouteStat Timestamp
RouteID
In this section
Overview of event statistics 346
eAgentLoginStat view 347
eCallByCallStat views 351
eIVRPortLoginStat view 370
Event statistics are collected on a per-event basis rather than accumulated over a
period of time.
You can enable or disable the data collection option at any time while the system
is running.
eAgentLoginStat view
Agent logon and logoff statistics provide detailed information about the
distribution of an agent’s time during work hours. Agent logon and logoff
statistics show the amount of time spent on events such as Login, Logout,
Walkaway, and Return from walkaway. Ready and Not Ready events also peg
here.
Statistics peg only for those agents who are logged on.
Requirements
Configure the server to collect agent logon statistics (see the Contact Center
Manager Administrator’s Guide). Statistics are collected for all agents; you
cannot configure the system to collect statistics for selected agents.
Database view
Agent logon and logoff statistics use the eAgentLoginStat view.
Field descriptions
The field descriptions for this view are described in this section.
AgentGivenName
Description: The first or given name of the agent.
Type: varchar
Length: 64
AgentLogin
Description: The numeric ID the agent uses to log in to the phoneset or agent
desktop.
Type: varchar
Length: 16
AgentSurName
Description: The last or surname of the agent.
Type: varchar
Length: 64
Duration
Description: For events of type logoff, the time between first logon (or, if the
first event of the day is not logon, 12:00 midnight) and the last logoff of the day
(or if the last event of the day is not logoff, 12:00 midnight).
For events of type walkaway, the amount of time the agent is in the Walkaway
state.
Event Type
FirstEventTimeStamp
Description: The timestamp of the first event for this agent.
Type: datetime
Length: 8
PositionID
Description: A unique identifier for the agent’s position ID, as received from
the switch.
Type: int
Length: 4
SequenceNumber
Description: The sequence identifier of this event.
Type: int
Length: 4
Site
Description: The configured name of this Contact Center Manager site.
Type: varchar
Length: 30
SiteID
Description: A unique number assigned by the system to identify this Contact
Center Manager site. The assigned SiteID remains unique over time even if a
configured site is deleted and another one is added with the same name. The
SiteID can be used in custom reports to identify statistics applicable to this site.
Time
Description: The time (in 24-hour HH:MM format) when the data is pegged by
the system.
Type: char
Length: 5
Timestamp
Description: The date and time when the data is pegged by the system.
Type: datetime
Length: 4
UserID
Description: A unique number assigned by the server to identify the agent when
the agent is added.
Type: binary
Length: 16
eCallByCallStat views
Requirements
Configure the server to collect call-by-call statistics, and select the applications
on which to collect statistics (see the Contact Center Manager Administrator’s
Guide).
Restrictions
The amount of data generated for call-by-call statistics is very large; therefore,
the time required to generate a report using call-by-call statistics is much greater
than the time required to generate a report using summarized statistics.
Database view
Call-by-call statistics use the eCallByCallStatYYYYMMDD view.
Field descriptions
The field descriptions for this view are described in this section.
AssociatedData
Description: Associated data is information associated with a specific event,
such as:
the other extension, trunk ID (on the Communication Server 1000/Meridian
1 PBX switch), or outside phone number associated with a call that is
conferenced with another party, transferred to another party, or put on hold
while another call is placed
CallEvent
Description: A unique identifier for the type of event.
Type: int
Length: 4
CallEventName
Description: The type of event. For a complete list of events that can be
collected, refer to “Call Events” on page 355.
Type: varchar
Length: 80
CallID
Description: A unique number assigned by the Contact Center Manager Server
to identify the contact to which this call event applies. The assigned Call ID is
derived from the call identifier provided by the attached switch or contact
provider.
Call IDs are unique only for the life of the contact, and may be reused later for
new contacts.
When the Call ID range is exhausted, new contacts are assigned previously used
Call IDs. On systems with very high traffic, different contacts may be assigned
the same Call ID within a single reporting interval.
Call ID values are not necessarily sequential. Do not assume any patterns in the
assignment of Call IDs.
This version of Sybase does not support unsigned integers. Therefore, Call IDs
can appear negative in the database views.
Type: int
Length: 4
Destination
Description: The location where a contact is directed during an event. The
destination can be identified by, for example, a dialed number, trunk ID, agent
ID, skillset name, application name, IVR queue ID or name, or site ID.
Type: varchar
Length: 40
EventData
Description: The information related to or generated by this event. The data can
be a PIN entered by the caller in response to the collect digits command; an
ANI, CLID, site ID, or activity code; or reasons for the event.
Type: varchar
Length: 40
FirstEventTimeStamp
Description: The timestamp of the first event for this call
Type: datetime
Length: 8
NodeID
Description: (Communication Server 2x00/DMS switch only) A unique
identifier for the switch.
Type: varchar
Length: 40
SequenceNumber
Description: The sequence identifier of this event.
Type: Int
Length: 4
Site
Description: The configured name of this Contact Center Manager site.
Type: varchar
Length: 30
SiteID
Description: A unique number assigned by the system to identify this Contact
Center Manager site. The assigned SiteID remains unique over time even if a
configured site is deleted and another one is added with the same name. The
SiteID can be used in custom reports to identify statistics applicable to this site.
Source
Description: The location of this contact before this event occurred. The source
can be identified by a dialed number, trunk ID, agent ID, skillset name,
application name, IVR queue ID or name, or site ID, for example.
Type: varchar
Length: 40
TelsetLoginID
Description: The numeric ID the agent uses to log in to the phoneset or agent
desktop.
Type: varchar
Length: 16
Time
Description: The time (in 24-hour HH:MM format) when the data is pegged by
the system.
Type: char
Length: 8
Timestamp
Description: The date and time when the data is pegged by the system.
Type: datetime
Length: 8
Call Events
The following table lists the call event types and the field contents for each call
event.
SIP does not support ACD DN, NACD DN, Network statistics, IVRTransfers,
and other IVR elements. Therefore, these call events do not apply in SIP-
enabled Contact Centers.
All further table notes are listed at the end of the table.
Note 1: The values that begin with % in this table are variables that have
different values each time the event is written. The legal values of these
variables is given in the Notes column.
Note 4: %Source = AGT: %AgentId in the case of a local call removed from
queue from agent event. %Source = SK_SET: %SkillsetName in the case of a
local call removed from queue from skillset event.
ATTENTION
If %DequeueReason is UNKNOWN, this indicates an error in
the system.
In networking, a call’s targeted site is known as its Best Node. If for some
reason this node no longer responds to requests made to it to queue calls, or if
requests timeout, a CallDequeue message issues with a
NET_NODE_BLOCKED reason.
Note 5: %Value = YES if this is the first time queued to a skillset, otherwise it is
NO.
ATTENTION
If %ReturnToQueueReason is UNKNOWN, this indicates an
error in the system.
%Reason can be any of the following depending on the particular reason for the
DN call:
NORMAL
OUTBOUND CAMPAIGN
UNKNOWN
ATTENTION
If %Reason is UNKNOWN, this indicates an error in the
system.
ATTENTION
If %GiveRouteToReason is UNKNOWN, this indicates an
error in the system.
UNKNOWN
ATTENTION
If %Reason is UNKNOWN, this indicates an error in the
system.
If the caller abandons in the middle of an IVR Session, if the caller finishes the
transfer in the middle of an IVR Session, or if an agent becomes available in the
middle of an IVR Session, an IVR Call Session Interrupted with reason
CANCELLED occurs.
Note 14: In certain switch environments, the dialed number information is not
available and therefore does not peg. For example, DIALED#:N/A appears in
the Event data column.
Note 15: Changes for Give IVR and Returned from IVR with regard to SIP are
listed in the following table.
eIVRPortLoginStat view
Requirements
Fulfill the following requirements:
Define IVR ports on Contact Center Manager.
Configure the server to collect IVR port statistics (see the Contact Center
Manager Administrator’s Guide). Statistics are collected for all IVR ports;
you cannot configure the system to collect statistics for selected ports.
Database view
IVR port logon and logoff statistics use the eIVRPortLoginStat view.
Field descriptions
The field descriptions for this view are described in this section.
Event Type
Description: A unique identifier for an IVR event.
Valid values:
login (LI)
logout (LO)
Type: char
Length: 2
FirstEventTimeStamp
Description: The timestamp of the first event for this agent.
Type: datetime
Length: 8
IVRPortID
Description: A unique number assigned by the server to identify an IVR port
when the voice port is defined.
Type: varchar
Length: 30
SequenceNumber
Description: The sequence identifier of this event.
Type: Int
Length: 4
Site
Description: The configured name of this Contact Center Manager site.
Type: varchar
Length: 30
SiteID
Description: A unique number assigned by the system to identify this Contact
Center Manager site. The assigned SiteID remains unique over time even if a
configured site is deleted and another one is added with the same name. The
SiteID can be used in custom reports to identify statistics applicable to this site.
Time
Description: The time (in 24-hour HH:MM format) when the data is pegged by
the system.
Type: char
Length: 5
Timestamp
Description: The date and time when the data is pegged by the system.
Type: datetime
Length: 4
In this section
Overview of configuration views 376
AccessRights view 377
ActivityCode view 381
Agent view 382
Application view 387
ApplicationByScript view 389
ApplicationThresholdTemplate view 392
CDN view 394
CodeToMessage view 396
ContactType view 397
DNISThresholdTemplate view 401
Formula view 402
HistoricalStatCollection view 404
HistoricalStatDuration view 408
HistoricalStatStorage view 410
IVRPort view 411
IVRQueue view 413
IVRThresholdTemplate view 415
NCCConfig view 417
NCCNetworkSkillset view 418
NCCRanking view 420
NCCRemoteApplication view 422
NCCSite view 424
AccessRights view
This view lists all desktop users and their access levels.
Field descriptions
The field descriptions for this view are described in this section.
Comment
Description: Additional information about the Access Class, if any.
Type: varchar
Length: 127
CreateDeleteAccess
Description: Shows whether the user can add or remove objects of this type.
Type: char
Length: 1
CreateDeleteAgentAccess
Description: Shows whether the user can add or remove agents.
Type: char
Length: 1
CreateDeleteAllAgentAccess
Description: Shows whether the user can add or remove all agents.
Type: char
Length: 1
ExecuteAccess
Description: Shows whether the user can run objects of this type.
Type: char
Length: 1
ExecuteAgentAccess
Description: Shows whether the user can run objects of this type to process his
or her reporting or associated agents.
Type: char
Length: 1
ExecuteAllAgentAccess
Description: Shows whether the user can run objects of this type for all agents.
Type: char
Length: 1
GivenName
Description: The desktop user’s first or given name.
Type: varchar
Length: 64
GroupName
Description: The access class to which the desktop user belongs.
Type: varchar
Length: 40
ObjectKey
Description: A unique identifier for a function for which the user is assigned
access rights.
Type: varchar
Length: 40
ObjectName
Description: A function for which the user is assigned access rights.
Type: varchar
Length: 40
PCLoginName
Description: The desktop user’s userid.
Type: varchar
Length: 30
ReadAccess
Description: Shows whether the user has view access for this function.
Type: char
Length: 1
ReadAgentAccess
Description: Shows whether the user has view access for his or her reporting or
associated agents.
Type: char
Length: 1
ReadAllAgentAccess
Description: Shows whether the user has view access for all agents.
Type: char
Length: 1
SurName
Description: The desktop user’s last or surname.
Type: varchar
Length: 64
WriteAccess
Description: Shows whether the user has modify access for this function.
Type: char
Length: 1
WriteAgentAccess
Description: Shows whether the user has modify access for his or her agents.
Type: char
Length: 1
WriteAllAgentAccess
Description: Shows whether the user has modify access for all agents.
Type: char
Length: 1
ActivityCode view
This view lists all of the activity codes and their assigned names.
Field descriptions
The field descriptions for this view are described in this section.
ActivityCode
Description: The number assigned to the activity code.
Type: nvarchar
Length: 32
Name
Description: The name assigned to the activity code.
Type: varchar
Length: 30
Agent view
Field descriptions
The field descriptions for this view are described in this section.
AlternateCallAnswer
Description: Communication Server 1000/Meridian 1 PBX switch only. Shows
whether the agent can put a DN call on hold to answer an incoming call. This
option is defined for the call presentation class to which the agent belongs.
Type: char
Length: 1
CallForceOption
Description: Communication Server 1000/Meridian 1 PBX switch only. Shows
whether the call force option is enabled for the call presentation class to which
this agent belongs.
Type: char
Length: 1
CallForceDelayTimer
Description: Communication Server 1000/Meridian 1 PBX switch only. The
time that elapses before a call is automatically presented to an agent. This option
is defined for the call presentation class to which the agent belongs.
Type: int
Length: 4
Comment
Description: Additional information about the agent, if any.
Type: varchar
Length: 127
Department
Description: The department to which the agent belongs.
Type: varchar
Length: 64
GivenName
Description: The agent’s first or given name.
Type: varchar
Length: 64
NROSDN
Description: Communication Server 2x00/DMS switch only. Shows whether
agents can receive calls while active on an outgoing call on their secondary DN.
Type: char
Length: 1
PersonalDN
Description: Communication Server 1000/Meridian 1 PBX switch only. The
agent’s personal DN, if any.
Type: varchar
Length: 32
ReturnToQueueMode
Description: The mode of the agent’s phoneset after returning a call to the
queue.
Type: varchar
Length: 80
ReturnToQueueOnNoAnswer
Description: Shows whether unanswered calls are returned to the queue.
Type: char
Length: 1
ReturnToQueueWaitInterval
Description: The time before an unanswered call is returned to the queue.
Type: smallint
Length: 2
SecondaryDN
Description: Communication Server 2x00/DMS switch only. The secondary
DN configured on the phoneset at which the agent is logged on.
Type: varchar
Length: 16
SurName
Description: The agent’s last or surname.
Type: varchar
Length: 64
SwitchID
Description: The switch ID of the phoneset at which the agent is logged on,
received from the switch.
Type: int
Length: 4
SwitchPortAddress
Description: The switch port address of the phoneset at which the agent is
logged on, received from the switch.
Type: varchar
Length: 30
SwitchPortName
Description: The switch port name of the phoneset at which the agent is logged
on, as received from the switch.
Type: varchar
Length: 30
TelsetLoginID
Description: The numeric ID that the agent uses to log in to the phoneset or
agent desktop.
Type: varchar
Length: 16
TelsetShowReserve
Description: NSBR option only. Shows whether an agent’s phoneset can show
that the agent is reserved for an NSBR call.
Type: char
Length: 1
TemplateID
Description: A unique number assigned by the server to identify the agent’s call
presentation class when the call presentation class is added. It determines how
calls are presented to the agent.
Type: varchar
Length: 30
TemplateName
Description: The call presentation class assigned to the agent. The call
presentation class determines how calls are presented to the agent.
Type: varchar
Length: 30
ThresholdTemplateID
Description: A unique number assigned by the server to identify the agent’s
threshold class when the threshold class is added.
Type: varchar
Length: 30
ThresholdTemplateName
Description: The threshold class assigned to the agent.
Type: varchar
Length: 30
Title
Description: The agent’s title.
Type: varchar
Length: 64
UnionBreakTimer
Description: Communication Server 1000/Meridian 1 PBX switch only. The
length of the break period allowed between calls. This option is defined for the
call presentation class to which the agent belongs.
Type: smallint
Length: 2
UserID
Description: A unique number assigned by the server to identify the agent when
the agent is added.
Type: binary
Length: 16
VariableWrap
Description: Communication Server 2x00/DMS switch only. Shows whether
the agent is put into Variable Wrap state after a call. Calls are not presented to
agents while they are in Variable Wrap state. This option is defined for the call
presentation class to which the agent belongs.
Type: char
Length: 1
Valid values:
0 (variable wrap configured with an interval of 0)
1 (variable wrap configured with an interval greater than zero)
2 (release guard configured)
Application view
The Application view lists all applications (Master and primary scripts) and their
service level. The view also indicates whether the server collects call-by-call
statistics for the application.
Field descriptions
The field descriptions for this view are described in this section.
ApplicationID
Description: A unique number assigned by the server to identify the application
when the application is defined.
Type: int
Length: 4
CallByCall
Description: Shows whether the collection of call-by-call statistics for this
application is enabled.
Type: tinyint
Length: 1
Name
Description: The name of the application.
Type: varchar
Length: 30
ServiceLevelThreshold
Description: The service level threshold for the threshold class to which this
application belongs.
Type: varchar
Length: 30
TemplateID
Description: A unique number assigned by the server to identify the
application’s threshold class when the threshold class is added.
Type: int
Length: 4
ApplicationByScript view
Field descriptions
The field descriptions for this view are described in this section.
ChildComment
Description: Not used in this version.
Type: varchar
Length: 80
ChildName
Description: The name of the referenced script.
Type: varchar
Length: 30
ChildStatus
Description: The status of the referenced script.
Type: varchar
Length: 80
ChildUserFirstName
Description: The first or given name of the user who created the referencing
script.
Type: varchar
Length: 30
ChildUserLastName
Description: The family or surname of the user who created the referencing
script.
Type: varchar
Length: 30
ParentComment
Description: Not used in this version.
Type: varchar
Length: 80
ParentName
Description: The name of the referencing script.
Type: varchar
Length: 30
ParentStatus
Description: The status of the referencing script.
Type: varchar
Length: 80
ParentUserFirstName
Description: The first or given name of the user who created the referencing
script.
Type: varchar
Length: 30
ParentUserLastName
Description: The family or surname of the user who created the referencing
script.
Type: varchar
Length: 30
ApplicationThresholdTemplate view
Field descriptions
The field descriptions for this view are described in this section.
Field
Description: A field for which a threshold is defined in the threshold class to
which the application belongs.
Type: varchar
Length: 80
Level1
Description: The low end of the normal range for the field.
Type: int
Length: 4
Level2
Description: The high end of the normal range for the field.
Type: int
Length: 4
Name
Description: The name of the threshold class to which this application belongs.
Type: varchar
Length: 30
ServiceLevelThreshold
Description: The service level threshold for the threshold class.
Type: int
Length: 4
TemplateID
Description: A unique number assigned by the server to identify the threshold
class when the threshold class is added.
Type: int
Length: 4
CDN view
The CDN view lists the CDNs and their assigned names and statuses.
Field descriptions
The field descriptions for this view are described in this section.
Acquire
Description: Shows whether there is a request to acquire the CDN.
Type: char
Length: 1
CDN
Description: The number assigned to the CDN.
Type: varchar
Length: 7
Name
Description: The name assigned to the CDN.
Type: varchar
Length: 30
Status
Description: The status of the CDN.
Type: varchar
Length: 80
Type
Description: The call type.
Valid values:
Local
MCDN Network
Landing Pad
DNIS Network
Type: varchar
Length: 80
CodeToMessage view
Field descriptions
The field descriptions for this view are described in this section.
Category
Description: A system-defined classification for the status code.
Type: varchar
Length: 30
Code
Description: The numeric status code value.
Type: int
Length: 4
Msg
Description: The corresponding message text.
Type: varchar
Length: 80
ContactType view
Contact types are the media types by which contacts arrive into (inbound) and
are sent from (outbound) a contact center. Voice is the traditional contact type
by which contacts are received by the contact center. Other standard contact
types include Web Communications, e-mail, and Outbound.
Field descriptions
The field descriptions for this view are described in this section.
ContactID
Description: A unique number assigned by the server to identify the contact
type when the contact type is added.
Type: int
Length: 4
Description
Description: Additional information regarding the contact type.
Type: varchar
Length: 60
Name
Description: Name of the contact type.
Type: varchar
Length: 30
Prefix
Description: First 3 letters of the name. It is the prefix used to link skillsets to
that contact type.
Type: varchar
Length: 3
ProviderID
Description: Link to the provider table for reference to get the name of the
provider associated with the contact type.
Type: int
Length: 4
SkillsetName
Description: Default skillset for this contact type.
Type: varchar
Length: 30
DNIS view
The DNIS view lists the DNIS numbers and their properties.
Field descriptions
The field descriptions for this view are described in this section.
DNIS
Description: A unique number used to identify a DNIS, which the server
assigns when the DNIS is defined.
Type: varchar
Length: 16
DNIS_PREFIX
Description: Stores the prefix of a DNIS number. You can sort, filter, and
report on individual DNIS 800 numbers.
Type: varchar
Length: 16
Name
Description: The name of a DNIS.
Type: varchar
Length: 30
ServiceLevelThreshold
Description: The service level threshold for the DNIS.
Type: int
Length: 4
TemplateID
Description: A unique identifier for the threshold class assigned to this DNIS.
The system contains a single, system-defined DNIS threshold class.
Type: int
Length: 4
DNISThresholdTemplate view
Field descriptions
The field descriptions for this view are described in this section.
Name
Description: The system-defined name of the threshold class.
Type: varchar
Length: 30
ServiceLevelThreshold
Description: The service level threshold for the threshold class.
Type: int
Length: 4
TemplateID
Description: A unique number assigned by the server to identify the threshold
class.
Type: int
Length: 4
Formula view
The Formula view lists all of the customized formulas and their definitions. You
can use formulas to create customized real-time statistics fields by combining
existing statistics fields with mathematical operators.
Field descriptions
The field descriptions for this view are described in this section.
Class
Description: The class to which the formula belongs.
Type: varchar
Length: 80
Comment
Description: Additional information about the formula, if any.
Type: varchar
Length: 127
Definition
Description: The standard formulas used to create the custom formula.
Type: varchar
Length: 255
Format
Description: The display format for the formula.
Type: varchar
Length: 80
FormulaID
Description: A unique number assigned by the server to identify a formula
when the formula is added.
Type: int
Length: 4
Name
Description: The name of the formula.
Type: varchar
Length: 30
HistoricalStatCollection view
The HistoricalStatCollection view lists all of the data types Contact Center
Manager can collect and, for each one, indicates whether it is selected.
Field descriptions
The field descriptions for this view are described in this section.
ActivityCode
Description: Shows whether statistics in the activity code statistics group are
collected.
Type: char
Length: 1
AgentByApplication
Description: Shows whether statistics in the agent by application statistics
group are collected.
Type: char
Length: 1
AgentLogin
Description: Shows whether statistics in the agent logon and logoff statistics
group are collected.
Type: char
Length: 1
AgentPerformance
Description: Shows whether statistics in the agent performance statistics group
are collected.
Type: char
Length: 1
Application
Description: Shows whether statistics in the application statistics group are
collected.
Type: char
Length: 1
CDN
Description: Shows whether statistics in the CDN statistics group are collected.
Type: char
Length: 1
DNIS
Description: Shows whether statistics in the DNIS statistics group are collected.
Type: char
Length: 1
IVR
Description: Shows whether statistics in the IVR statistics group are collected.
Type: char
Length: 1
IVRPort
Description: Shows whether statistics in the IVR port statistics group are
collected.
Type: char
Length: 1
IVRPortLogin
Description: Shows whether statistics in the IVR port login and logout statistics
group are collected.
Type: char
Length: 1
NetworkCall
Description: NSBR option only. Shows whether statistics in the network call
statistics group are collected.
Type: char
Length: 1
NetworkOutCall
Description: NSBR option only. Shows whether statistics in the network
outcall statistics group are collected.
Type: char
Length: 1
RANMusicRoute
Description: Shows whether statistics in the RAN/Music route statistics group
are collected.
Type: char
Length: 1
Route
Description: Communication Server 1000/Meridian 1 PBX switch only. Shows
whether statistics in the route statistics group are collected.
Type: char
Length: 1
Skillset
Description: Shows whether statistics in the skillset statistics group are
collected.
Type: char
Length: 1
SkillsetByAgent
Description: Shows whether statistics in the agent by skillset statistics group
are collected.
Type: char
Length: 1
SkillsetState
Description: Not used in this version.
Trunk
Description: Communication Server 1000/Meridian 1 PBX switch only. Shows
whether statistics in the trunk statistics group are collected.
Type: char
Length: 1
HistoricalStatDuration view
The HistoricalStatDuration view shows the length of time the server keeps
statistics for each collection period and event type.
Field descriptions
The field descriptions for this view are described in this section.
BusinessDaysPerWeek
Description: The number of business days per week for which the system
collects historical statistics data.
Type: smallint
Length: 2
BusinessHoursPerDay
Description: The number of hours per business day that the system collects
historical statistics data.
Type: smallint
Length: 2
DaysofAgentLogin
Description: The number of days agent logon statistics are stored by the
system.
Type: smallint
Length: 2
DaysOfCallByCall
Description: The number of days call-by-call statistics are stored by the system.
Type: smallint
Length: 2
DaysOfDaily
Description: The number of days daily statistics are stored by the system.
Type: smallint
Length: 2
DaysOfInterval
Description: The number of days interval statistics are stored by the system.
Type: smallint
Length: 2
DaysofIVRPortLogin
Description: The number of days IVR port logon statistics are stored by the
system.
Type: smallint
Length: 2
DaysOfSkillsetState
Description: Not used in this version.
FirstDayOfWeek
Description: The day defined as the first day of the business week. This day is
the day that weekly statistics are accumulated for the previous week.
Type: varchar
Length: 80
MonthsOfMonthly
Description: The number of months monthly statistics are stored by the system.
Type: smallint
Length: 2
WeeksOfWeekly
Description: The number of weeks weekly statistics are stored by the system.
Type: smallint
Length: 2
HistoricalStatStorage view
Field descriptions
The field descriptions for this view are described in this section.
Configured
Description: The value for this parameter that is used to calculate the required
database size (for example, estimated number of activity codes).
Type: int
Length: 4
Parameter
Description: The name of the parameter.
Type: varchar
Length: 80
Purchased
Description: The maximum number you can configure on the system.
Type: int
Length: 4
System
Description: The maximum number that can be defined on the largest possible
configuration of the system, if all available options are installed.
Type: int
Length: 4
IVRPort view
The IVRPort view lists the voice ports. For each port, it provides the switch
configuration information.
Field descriptions
The field descriptions for this view are described in this section.
Acquire
Description: Shows whether there is a request to acquire the voice port.
Type: char
Length: 1
IVRPortID
Description: A unique number assigned by the server to identify the voice port
when the port is added.
Type: varchar
Length: 16
IVRQueueID
Description: The threshold class to which the IVR queue is assigned.
Type: varchar
Length: 7
Name
Description: The name of the voice port.
Type: varchar
Length: 30
Status
Description: The status of the voice port.
Type: varchar
Length: 80
SwitchID
Description: The switch ID of an IVR port, as received from the switch.
Type: int
Length: 4
SwitchPortAddress
Description: The switch address of the IVR port, as received from the switch.
Type: varchar
Length: 40
SwitchPortName
Description: The name assigned to the IVR port on the switch, as received from
the switch.
Type: varchar
Length: 30
IVRQueue view
The IVRQueue view lists the IVR ACD-DNs and their properties.
Field descriptions
The field descriptions for this view are described in this section.
Acquire
Description: Shows whether there is a request to acquire the IVR ACD-DN.
Type: char
Length: 1
IVRQueueID
Description: A unique number assigned by the server to identify the IVR ACD-
DN when the IVR ACD-DN is added.
Type: varchar
Length: 7
Name
Description: The name of the IVR ACD-DN.
Type: varchar
Length: 30
ServiceLevelThreshold
Description: The service level threshold for the threshold class to which the
IVR ACD-DN belongs.
Type: int
Length: 4
Status
Description: The status of the IVR ACD-DN.
Type: varchar
Length: 80
TemplateID
Description: The name of the threshold class to which the IVR ACD-DN
belongs.
Type: int
Length: 4
IVRThresholdTemplate view
The IVRThresholdTemplate view lists the IVR threshold classes and their
threshold levels.
Field descriptions
The field descriptions for this view are described in this section.
Field
Description: The name of the field for which a threshold is defined in the
threshold class.
Type: varchar
Length: 80
FieldID
Description: A unique number assigned by the server to identify the field when
you define a threshold value for the field.
Type: int
Length: 4
Level1
Description: The low end of the normal range for the field.
Type: int
Length: 4
Level2
Description: The high end of the normal range for the field.
Type: int
Length: 4
Name
Description: The name of the IVR threshold class.
Type: varchar
Length: 30
ServiceLevelThreshold
Description: The service level threshold for this threshold class.
Type: int
Length: 4
TemplateID
Description: A unique number assigned by the server to identify the threshold
class when the threshold class is added.
Type: int
Length: 4
NCCConfig view
Network Control Center option only. The NCCConfig view is not used in this
version.
Field descriptions
The field descriptions for this view are described in this section.
NumBestNodes
Description: Not used in this version.
Type: int
Length: 4
StaleDataRatio
Description: Not used in this version.
Type: int
Length: 4
UpdateRate
Description: Not used in this version.
Type: int
Length: 4
NCCNetworkSkillset view
Network Control Center option only. The NCCNetworkSkillset view lists all the
network skillsets and, for each one, indicates the routing table method utilized
for the network skillset.
A routing table defines how calls are queued to the sites on the network. Each
site has a routing table for each network skillset at that site. When you create a
network skillset, you choose the routing table type for that skillset. Two types of
routing tables are available.
Round robin
The server queues the first call to the first, second, and third site in the routing
table for the network skillset. When an agent becomes available at one of these
sites, the server reserves the agent, and the call is presented to the agent.
When the second call arrives, the server queues it to the second, third, and fourth
site in the routing table. When the third call arrives, the server queues it to the
third, fourth, and fifth site—and so on.
This type of routing table distributes calls most evenly among the sites.
Sequential
Whenever a call arrives, the server queues it to the first three sites in the routing
table. When an agent becomes available at one of these sites, the server reserves
the agent, and the call is presented to the agent.
This type of routing table minimizes the number of trunks used to network calls.
Field descriptions
The field descriptions for this view are described in this section.
Comment
Description: Additional information about the network skillset, if any.
Type: int
Length: 4
IdleAgentsPriority
Description: Not used in this release.
Type: smallint
Length: 2
NetworkSkillset
Description: The name of the network skillset.
Type: varchar
Length: 30
NetworkSkillsetID
Description: A unique number assigned by the server to identify the network
skillset when the network skillset is added.
Type: int
Length: 4
UseBestNode
Description: Not used in this release.
Type: char
Length: 1
UseRoundRobin
Description: The routing table method used for the network skillset.
Type: char
Length: 1
Valid values:
0 (sequential)
1 (round robin)
NCCRanking view
Network Control Center option only. The NCCRanking view provides a listing
of the sites in your network. For each site, it lists the networked skillsets at that
site. For each skillset, it lists the possible destination sites and their ranking
preference. The ranking preference determines the destination site to which
skillset calls are routed.
Field descriptions
The field descriptions for this view are described in this section.
DstSiteID
Description: A unique number assigned by the server to identify a destination
site when the site is configured on the Network Control Center.
Type: int
Length: 4
DstSiteName
Description: The name of a site to which calls for the network skillset can be
routed.
Type: varchar
Length: 30
NetworkSkillsetID
Description: A unique number assigned by the server to identify a network
skillset when the skillset is configured on the Network Control Center.
Type: int
Length: 4
NetworkSkillsetName
Description: The name of a network skillset defined on the source site.
Type: varchar
Length: 30
Rank
Description: The ranking of the destination site in the routing table.
Type: smallint
Length: 2
SrcSiteID
Description: A unique number assigned by the server to identify a source site
when the site is configured on the Network Control Center.
Type: int
Length: 4
SrcSiteName
Description: The name of the source site.
Type: varchar
Length: 30
NCCRemoteApplication view
Network Control Center option only. The NCCRemoteApplication view lists all
applications (Master and primary scripts) and their service level. The view also
indicates whether the server collects call-by-call statistics for the application.
Field descriptions
The field descriptions for this view are described in this section.
CallByCall
Description: Shows whether the collection of call-by-call statistics for this
application is enabled.
Type: tinyint
Length: 1
Valid values:
0 (none)
1 (local)
2 (network)
3 (local and network)
Name
Description: The name of the application.
Type: varchar
Length: 30
RemoteApplicationID
Description: A unique number assigned by the server to identify the application
when the application is defined.
Type: int
Length: 4
ServiceLevelThreshold
Description: The service level threshold for the threshold class to which this
application belongs.
Type: int
Length: 4
SiteID
Description: A unique number assigned by the system to identify this Contact
Center Manager site. The assigned SiteID remains unique over time even if a
configured site is deleted and another one is added with the same name. The
SiteID can be used in custom reports to identify statistics applicable to this site.
SiteName
Description: The name of the Contact Center Manager site, as assigned during
installation.
Type: varchar
Length: 30
NCCSite view
Network Control Center option only. The NCCSite view lists each site in the
network and, for each one, shows its properties.
Field descriptions
The field descriptions for this view are described in this section.
Comment
Description: Additional information about the site, if any.
Type: varchar
Length: 127
ContactNumber
Description: The phone number of the contact person.
Type: varchar
Length: 30
ContactPerson
Description: The contact person name for the site.
Type: varchar
Length: 30
LandingPadOptions
Description:
Valid values:
0 to 7
Value Description
1 DNIS is selected.
Value Description
2 CDN is selected.
4 MCDN is selected.
OutOfServiceTimer
Description: The amount of time the site is filtered from the routing table when
the maximum retry limit is reached.
Type: int
Length: 4
RelativeGMT
Description: The time difference (in hours) between GMT and the time zone in
which the site is located.
Type: int
Length: 4
SiteID
Description: A unique number assigned by the system to identify this Contact
Center Manager site. The assigned SiteID remains unique over time even if a
configured site is deleted and another one is added with the same name. The
SiteID can be used in custom reports to identify statistics applicable to this site.
NetworkConfig view
NSBR option only. This view contains the name of the Network Control Center
for the server.
Field descriptions
The field description for this view is described in this section.
NCCSite
Description: The name of the Network Control Center, as defined when the
server is installed. You can view the Network Control Center name from the
Network Communication Parameters dialog box.
Type: varchar
Length: 30
NetworkRankingAssignment view
Field descriptions
The field descriptions for this view are described in this section.
AssignName
Description: The name of the table routing assignment, as defined when the
assignment is configured on the Network Control Center.
Type: varchar
Length: 30
Comment
Description: Additional information, if any.
Type: varchar
Length: 127
ErrorCode
Description: A numeric value for the error encountered when the assignment
last ran, if any.
Type: int
Length: 4
DestSiteID
Description: A unique number assigned by the server to identify a destination
site when the site is configured on the Network Control Center.
Type: int
Length: 4
DestSiteName
Description: A destination site for this network skillset, as defined in the
routing table.
Type: varchar
Length: 30
NetworkSkillsetID
Description: A unique number assigned by the server to identify the network
skillset when the network skillset is configured on the Network Control Center.
Type: int
Length: 4
NetworkSkillsetName
Description: The name of a network skillset included in this table routing
assignment.
Type: varchar
Length: 30
Rank
Description: The ranking of the site in the routing table.
Type: smallint
Length: 2
RankingAssignID
Description: A unique number assigned by the server to identify the table
routing assignment when the assignment is configured on the Network Control
Center.
Type: int
Length: 4
SrcSiteID
Description: A unique number assigned by the server to identify the source site
when the site is configured on the Network Control Center.
Type: int
Length: 4
SrcSiteName
Description: The source site for which the table routing assignment is defined.
Type: varchar
Length: 30
Status
Description: The current status for this table routing assignment.
Type: varchar
Length: 80
NetworkSkillsetStatus view
Field descriptions
The field descriptions for this view are described in this section.
FilterStatus
Description: Indicates whether the skillset is filtered.
Type: smallint
Length: 2
Valid values:
11 (Server communication failure)
12 (Dialable DN is not configured correctly)
13 (NACD package restriction at destination)
14 (Maximum number of retries reached)
15 (Trunk allocation problem, server suspended)
16 (Incompatible server versions)
any other value (Undefined)
FlowControlStatus
Description: Indicates whether the skillset is rejecting calls because too many
calls are queued.
Type: smallint
Length: 2
Valid values:
0 (Off)
1 (Max Request)
2 (Out of Service)
3 (Unknown Skillset)
any other value (Undefined)
NetworkSkillset
Description: The name of the network skillset.
Type: varchar
Length: 30
NetworkSkillsetID
Description: A unique number assigned by the server to identify the network
skillset when the network skillset is configured on the Network Control Center.
Type: int
Length: 4
SiteName
Description: The destination site.
Type: varchar
Length: 30
NetworkThresholdTemplate view
Field descriptions
The field descriptions for this view are described in this section.
Field
Description: The name of the field for which a threshold is defined in the
threshold class.
Type: varchar
Length: 80
Level1
Description: The low end of the normal range for the field.
Type: int
Length: 4
Level2
Description: The high end of the normal range for the field.
Type: int
Length: 4
Name
Description: The name of the IVR threshold class.
Type: varchar
Length: 30
ServiceLevelThreshold
Description: The service level threshold for this threshold class.
Type: int
Length: 4
TemplateID
Description: A unique number assigned by the server to identify the threshold
class when the threshold class is added.
Type: int
Length: 4
PhonesetDisplay view
Communication Server 1000/Meridian 1 PBX switch only. This view lists the
configured display types, the width of each display, and the number of rows in
each display.
Field descriptions
The field descriptions for this view are described in this section.
DisplayTypeName
Description: The type of display the phoneset uses.
Valid values:
1 x 40 Alphanumeric
1 x 16 Alphanumeric
1 x 18 or 1 x 24 Alphanumeric
1 x 12 Numeric
Type: varchar
Length: 80
FieldName
Description: The name of the field displayed on the phoneset.
Type: varchar
Length: 80
Row
Description: The row in which the field appears.
Type: smallint
Length: 2
Width
Description: The display width for the field.
Type: smallint
Length: 2
Provider view
Field descriptions
The field descriptions for this view are described in this section.
Description
Description: Additional information regarding the provider.
Type: varchar
Length: 60
Name
Description: Name of the provider.
Type: varchar
Length: 30
ProviderID
Description: A unique number assigned by the server to identify the provider
when the provider is added.
Type: int
Length: 4
Ranking view
NSBR option only. The Ranking view provides a listing of the sites in your
network. For each site, it lists the networked skillsets at that site. For each
skillset, it lists the possible destination sites and their ranking preference. The
ranking preference determines the destination site to which skillset calls are
routed.
Field descriptions
The field descriptions for this view are described in this section.
DstSiteID
Description: A unique number assigned by the server to identify a destination
site when the site is configured on the Network Control Center.
Type: int
Length: 4
DstSiteName
Description: The name of a site to which calls for the network skillset can be
routed.
Type: varchar
Length: 30
NetworkSkillsetID
Description: A unique number assigned by the server to identify the network
skillset when the network skillset is configured on the Network Control Center.
Type: int
Length: 4
NetworkSkillsetName
Description: The name of a network skillset defined on the source site.
Type: varchar
Length: 30
Rank
Description: The ranking of the destination site in the routing table.
Type: smallint
Length: 2
SrcSiteID
Description: A unique number assigned by the server to identify a source site
when the site is configured on the Network Control Center.
Type: int
Length: 4
SrcSiteName
Description: The name of the source site.
Type: varchar
Length: 30
RealTimeColumn view
The RealTimeColumn view lists the real-time display definitions and their
column definitions.
Field descriptions
The field descriptions for this view are described in this section.
Column
Description: The column number of a field that appears on a real-time display
definition.
Type: smallint
Length: 2
Format
Description: The format of the column.
Valid values:
text
numeric
time
bar chart
Type: varchar
Length: 80
FormulaID
Description: A unique number assigned by the server to identify the formula
used in this column when the formula is added.
Type: int
Length: 4
Label
Description: The label of the column, as it appears on the real-time display.
Type: varchar
Length: 80
TemplateID
Description: A unique number assigned by the server to identify a real-time
display definition when the real-time display definition is added.
Type: int
Length: 4
ScaleFrom
Description: For columns with bar format only. The minimum scale value to
report in this column.
Type: smallint
Length: 2
ScaleTo
Description: For columns with bar format only. The maximum scale value to
report in this column.
Type: smallint
Length: 2
RealTimeStatCollection view
Interval-to-date mode
In interval-to-date mode, statistics are collected only for the current interval.
When the interval is over, data fields initialize to zero and collection begins for
the next interval.
Field descriptions
The field descriptions for this view are described in this section.
IntervalDuration
Description: The interval duration for collecting real-time statistics (applies
only to statistics collected in interval-to-date mode).
Type: smallint
Length: 2
IntervalStartTime
Description: The interval start time for collecting real-time statistics.
Type: char
Length: 8
ITDAgent
Description: Shows whether agent statistics appear using the interval-to-date
format.
Type: char
Length: 1
ITDApplication
Description: Shows whether application statistics appear using the interval-to-
date format.
Type: char
Length: 1
ITDIVR
Description: Shows whether IVR statistics appear using the interval-to-date
format.
Type: char
Length: 1
ITDNetworkCall
Description: NSBR option only. Shows whether network call statistics appear
using the interval-to-date format.
Type: varchar
Length: 80
ITDNodalCall
Description: NSBR option only. Shows whether contact center summary
statistics appear using the interval-to-date format.
Type: int
Length: 4
ITDRoute
Description: Communication Server 1000/Meridian 1 PBX switch only. Shows
whether route statistics appear using the interval-to-date format.
Type: varchar
Length: 80
ITDSkillset
Description: Shows whether skillset statistics appear using the interval-to-date
format.
Type: varchar
Length: 80
MinRefreshRate
Description: The minimum interval between refreshes of real-time statistics
appears.
Type: varchar
Length: 80
MWAgent
Description: Shows whether agent statistics appear using the interval-to-date
format.
Type: char
Length: 1
MWApplication
Description: Shows whether application statistics appear using the moving
window format.
Type: char
Length: 1
MWIVR
Description: Shows whether IVR statistics appear using the moving window
format.
Type: char
Length: 1
MWNetworkCall
Description: NSBR option only. Shows whether network call statistics appear
using the moving window format.
Type: varchar
Length: 80
MWNodalCall
Description: NSBR option only. Shows whether contact center summary
statistics appear using the moving window format.
Type: int
Length: 4
MWRoute
Description: Communication Server 1000/Meridian 1 PBX switch only. Shows
whether route statistics appear using the moving window format.
Type: varchar
Length: 80
MWSkillset
Description: Shows whether skillset statistics appear using the moving window
format.
Type: varchar
Length: 80
RealTimeTemplate view
The RealTimeTemplate view lists the real-time display definitions and their
general properties.
Field descriptions
The field descriptions for this view are described in this section.
Class
Description: The class to which the real-time display definition belongs.
Type: varchar
Length: 80
Name
Description: The name of the real-time display definition.
Type: varchar
Length: 30
RefreshRate
Description: The refresh rate defined for the real-time display definition.
Type: int
Length: 4
TemplateID
Description: A unique number assigned by the server to identify a real-time
display definition when the real-time display definition is added.
Type: int
Length: 4
ViewMode
Description: The view mode defined for the real-time display definition.
Valid values:
Moving Window
Interval To Date
Type: varchar
Length: 80
RemoteApplication view
NSBR option only. The RemoteApplication view lists all applications defined in
the network except those defined at the local site.
Field descriptions
The field descriptions for this view are described in this section.
CallByCall
Description: Shows whether the collection of call-by-call statistics for this
application is enabled.
Type: tinyint
Length: 1
Valid values:
0 (none)
1 (local)
2 (network only)
3 (local and network)
Name
Description: The name of the application.
Type: varchar
Length: 30
RemoteApplicationID
Description: A unique number assigned by the server to identify the application
when the application is defined.
Type: int
Length: 4
ServiceLevelThreshold
Description: The service level threshold for the threshold class to which this
application belongs.
Type: int
Length: 4
SiteID
Description: A unique number assigned by the system to identify this Contact
Center Manager site. The assigned SiteID remains unique over time even if a
configured site is deleted and another one is added with the same name. The
SiteID can be used in custom reports to identify statistics applicable to this site.
SiteName
Description: The name of the Contact Center Manager site, as assigned during
installation.
Type: varchar
Length: 30
Route view
Communication Server 1000/Meridian 1 PBX switch only. The Route view lists
the routes and their properties.
Field descriptions
The field descriptions for this view are described in this section.
Acquire
Description: Shows whether there is a request to acquire or release the route.
Type: char
Length: 1
Name
Description: The name of the route.
Type: varchar
Length: 30
RouteID
Description: The route number.
Type: int
Length: 4
Status
Description: The status of the route.
Type: varchar
Length: 80
TemplateID
Description: A unique number assigned by the server to identify the threshold
class to which the route belongs when the threshold class is added.
Type: int
Length: 4
RouteThresholdTemplate view
Field descriptions
The field descriptions for this view are described in this section.
Field
Description: The name of the field for which a threshold is defined in the
threshold class.
Type: varchar
Length: 80
FieldID
Description: A unique number assigned by the server to identify the field when
you define a threshold value for the field.
Type: int
Length: 4
Level1
Description: The low end of the normal range for the field.
Type: int
Length: 4
Level2
Description: The high end of the normal range for the field.
Type: int
Length: 4
Name
Description: The name of the route threshold class.
Type: varchar
Length: 30
TemplateID
Description: A unique number assigned by the server to identify the threshold
class when the threshold class is added.
Type: int
Length: 4
ScheduledSkillsetAssignment view
Field descriptions
The field descriptions for this view are described in this section.
AssignID
Description: A unique number assigned by the server to identify the assignment
when the assignment is added.
Type: int
Length: 4
AssignName
Description: The name of the agent to skillset assignment.
Type: varchar
Length: 64
Comment
Description: Additional information about the agent, if any.
Type: varchar
Length: 127
ErrorCode
Description: A numeric value for the error encountered when the assignment
last ran, if any.
Type: int
Length: 4
Priority
Description: The agent’s priority for this skillset.
Range: 1–48 where 1 is the highest priority and 48 is the lowest priority.
Type: tinyint
Length: 1
SkillsetID
Description: A unique identifier for the skillset to which the agent is assigned
when this assignment is run. This identifier the server assigns when the skillset
is added.
Type: int
Length: 4
SkillsetName
Description: The name of the skillset to which the agent is assigned when the
assignment is run.
Type: varchar
Length: 64
SkillsetState
Description: The current state of the skillset.
Valid values:
Standby
Active
Type: varchar
Length: 80
Status
Description: The status of the agent to skillset assignment.
Valid values:
Edited/Saved
Ran OK
Ran with error
Scheduled
Never scheduled
Type: varchar
Length: 80
UserGivenName
Description: The given or first name of the agent.
Type: varchar
Length: 64
UserID
Description: A unique number assigned by the server to identify the agent when
the agent is added.
Type: binary
Length: 16
UserSurName
Description: The family or surname of the agent.
Type: varchar
Length: 64
UserTelsetLogin
Description: The numeric ID the agent uses to log in to the phoneset or agent
desktop.
Type: varchar
Length: 16
ScheduledSupervisorAssignment view
Field descriptions
The field descriptions for this view are described in this section.
AgentID
Description: A unique number assigned by the server to identify the agent when
the agent is added.
Type: binary
Length: 16
AssignID
Description: A unique number assigned by the server to identify the assignment
when the assignment is added.
Type: int
Length: 4
AssignName
Description: The name of the agent to supervisor assignment.
Type: varchar
Length: 64
AssignType
Description: The assignment type.
Type: varchar
Length: 80
Comment
Description: Additional information about the Supervisor, if any.
Type: varchar
Length: 127
ErrorCode
Description: A numeric value for the error encountered when the assignment
last ran, if any.
Type: int
Length: 4
Status
Description: The status of the agent to supervisor assignment.
Valid values:
Edited/Saved
Ran OK
Scheduled
Never scheduled
Type: varchar
Length: 80
SupervisorGivenName
Description: The given or first name of the supervisor to which the user is
assigned when this assignment is run.
Type: varchar
Length: 64
SupervisorID
Description: A unique number assigned by the server to the supervisor when
the supervisor is added.
Type: binary
Length: 16
SupervisorSurName
Description: The family or surname of the supervisor to which the user is
assigned when this assignment is run.
Type: varchar
Length: 64
Type
Description: The assignment type.
Valid values:
P (Reporting)
S (Associated)
Type: char
Length: 1
Script view
The Script view lists the scripts and their properties. For more information about
scripting, refer to the Contact Center Manager Scripting Guide for
Communication Server 1000/Meridian 1 PBX or the Contact Center Manager
Scripting Guide for Communication Server 2X00/DMS.
Field descriptions
The field descriptions for this view are described in this section.
Comment
Description: Additional information about the script, if any.
Type: varchar
Length: 30
GivenName
Description: The first or given name of the user who performed the most recent
action on the script.
Type: varchar
Length: 30
LastModified
Description: The date when the most recent action is performed on the script.
Type: datetime
Length: 8
Name
Description: The name of the script.
Type: varchar
Length: 30
Owner
Description: The name of the user who created the script.
Type: varchar
Length: 80
ScriptID
Description: A unique number assigned by the server to identify the script
when the script is added.
Type: int
Length: 4
Status
Description: The status of the variable.
Valid values:
Activated
Deactivated
Type: varchar
Length: 80
SurName
Description: The last or surname of the user who performed the most recent
action on the script.
Type: varchar
Length: 30
Type
Description: The type of script.
Valid values:
Local Master
Network
Primary
Secondary
Type: varchar
Length: 80
ScriptVariableProperties view
The ScriptVariableProperties view lists the script variables and their properties.
For more information about scripting, refer to the Contact Center Manager
Scripting Guide for Communication Server 1000/Meridian 1 PBX or the Contact
Center Manager Scripting Guide for Communication Server 2X00/DMS.
Field descriptions
The field descriptions for this view are described in this section.
Class
Description: The name of the variable class to which this variable belongs.
Valid values:
Item
Set Of Values
Type: varchar
Length: 80
Comment
Description: Not used.
Grouping
Description: The name of the variable group to which this variable belongs.
Valid values:
Global Variable
Call Variable
Type: varchar
Length: 80
Name
Description: The name of the script variable.
Type: varchar
Length: 30
Status
Description: The status of the variable.
Valid values:
Activated
Deactivated
Type: varchar
Length: 80
Type
Description: The data type of the variable. For more information about
variables, refer to the Contact Center Manager Scripting Guide for
Communication Server 1000/Meridian 1 PBX or the Contact Center Manager
Scripting Guide for Communication Server 2X00/DMS.
Type: varchar
Length: 80
ScriptVariables view
The ScriptVariables view lists the script variables. For each variable, it provides
the variable status and type, and the name, status, and type of any scripts that use
that variable. For more information about scripting, refer to the Contact Center
Manager Scripting Guide for Communication Server 1000/Meridian 1 PBX or
the Contact Center Manager Scripting Guide for Communication Server 2X00/
DMS.
Field descriptions
The field descriptions for this view are described in this section.
Script
Description: The name of a script that uses this variable.
Type: varchar
Length: 32
ScriptStatus
Description: The status of the script.
Valid values:
Edited
Validated
Activated
Type: varchar
Length: 80
ScriptType
Description: The type of script.
Valid values:
Local Master
Network
Primary
Secondary
Type: varchar
Length: 80
Variable
Description: The name of the script variable.
Type: varchar
Length: 30
VariableStatus
Description: The status of the variable.
Valid values:
Activated
Deactivated
Type: varchar
Length: 80
VariableType
Description: The data type of the variable. For more information about
variables, refer to the Contact Center Manager Scripting Guide for
Communication Server 1000/Meridian 1 PBX or the Contact Center Manager
Scripting Guide for Communication Server 2X00/DMS.
Type: varchar
Length: 80
Site view
NSBR option only. The Site view lists the sites and their properties.
Field description
The field descriptions for this view are described in this section.
Comment
Description: Additional information about the site, if any.
Type: varchar
Length: 127
ContactNumber
Description: The phone number of the contact person.
Type: varchar
Length: 30
ContactPerson
Description: The name of the contact person for the site.
Type: varchar
Length: 30
HeteroNetworking
Description:
Type: int
Valid values:
0 (Universal Networking disabled)
1 (Universal Networking enabled)
Length: 1
LandingPadOptions
Description:
Valid values:
0 to 7
Value Description
IsLocal
Description: Specifies whether the site is the local site or a remote site.
Valid values:
0 (remote)
1 (local)
Type: char
Length: 1
Name
Description: The name of the site.
Type: varchar
Length: 30
OutOfServiceTimer
Description: The amount of time the site is filtered from the routing table when
the maximum retry limit is reached.
Type: int
Length: 4
RelativeGMT
Description: The time difference (in hours) between GMT and the time zone in
which the site is located.
Type: int
Length: 4
SiteID
Description: A unique number assigned by the system to identify this Contact
Center Manager site. The assigned SiteID remains unique over time even if a
configured site is deleted and another one is added with the same name. The
SiteID can be used in custom reports to identify statistics applicable to this site.
SwtichType
Description:
Type:
Valid values:
1 (CS 1000/M1 switch)
4 (CS 2x00/DMS switch)
TemplateID
Description: Not used in this version.
Type: char
Length: 1
TemplateName
Description: Not used in this version.
Type: varchar
Length: 30
Skillset view
The Skillset view lists all skillsets and their general properties.
Field descriptions
The field descriptions for this view are described in this section.
ActivityCode
Description: Communication Server 1000/Meridian 1 PBX switch only. The
default activity code for the skillset.
Type: varchar
Length: 32
CallAgePreference
Description: The call age preference for a skillset.
Valid values:
18 (Oldest)
19 (First in Queue)
Type: smallint
Length: 2
CallSourcePreference
Description: NSBR option only. The call source preference for a skillset.
Valid values:
15 (Local)
16 (Network)
17 (None)
Type: smallint
Length: 2
CallRequestQueueSize
Description: The maximum number of calls that can be queued to this skillset.
Type: int
Length: 4
CallRequestQueueSizeThreshold
Description: The number by which queued calls should decrease before more
calls are queued to this skillset.
Type: int
Length: 4
Comment
Description: Additional information about the skillset, if any.
Type: varchar
Length: 127
DN
Description: The ACD-DN number for which calls peg to this skillset.
Type: varchar
Length: 7
IdleAgentsPriority
Description: The agent idle time preference defined on the Global Settings
dialog box.
Type: smallint
Length: 2
IsNetworked
Description: NSBR option only. Shows whether a skillset is networked.
Type: char
Length: 1
MinShortCallDelay
Description: The short call threshold for the threshold class to which the skillset
belongs. Calls with a talk time less than this value are considered short calls.
Type: int
Length: 4
NetworkSkillsetComment
Description: NSBR option only.
Type: varchar
Length: 127
NetworkSkillsetID
Description: NSBR option only.
Type: int
Length: 4
NetworkSkillsetName
Description: NSBR option only.
Type: varchar
Length: 30
NightServiceType
Description: The night service type for a skillset.
Valid values:
20 (Transition)
21 (Night)
Type: smallint
Length: 2
ServiceLevelThreshold
Description: The service level for the threshold class to which the skillset
belongs.
Type: int
Length: 4
Skillset
Description: The name of the skillset.
Type: varchar
Length: 30
SkillsetID
Description: A unique number assigned by the server to identify the skillset
when the skillset is added.
Type: int
Length: 4
TemplateID
Description: A unique number assigned by the server to identify the threshold
class to which the skillset belongs.
Type: int
Length: 4
UseBestNode
Description: Not used.
UseRoundRobin
Description: NSBR option only.
Type: char
Length: 1
Valid values:
0 (round robin)
1 (sequential)
SkillsetByAgent view
The SkillsetByAgent view lists the skillsets and the agents assigned to them. For
each assigned agent, it shows the agent priority for the skillset.
Field descriptions
The field descriptions for this view are described in this section.
Priority
Description: The agent’s priority for this skillset.
Range: 1–48, where 1 is the highest priority and 48 is the lowest priority.
Type: tinyint
Length: 1
SkillsetID
Description: A unique number assigned by the server to identify the skillset
when the skillset is added.
Type: int
Length: 4
SkillsetState
Description: The skillset state.
Valid values:
Standby
Active
Type: varchar
Length: 80
UserID
Description: A unique number assigned by the server to identify an agent
assigned to this skillset.
Type: binary
Length: 16
SkillsetByAssignment view
Field descriptions
The field descriptions for this view are described in this section.
AssignID
Description: A unique number assigned by the server to identify the assignment
when the assignment is added.
Type: int
Length: 4
AssignName
Description: The name of the agent to skillset assignment.
Type: varchar
Length: 64
Comment
Description: The comments defined by the supervisor, if any.
Type: varchar
Length: 127
ErrorCode
Description: A numeric value for the error encountered when the assignment
last ran, if any.
Type: int
Length: 4
Priority
Description: The agent’s priority for this skillset.
Range: 1–48, where 1 is the highest priority and 48 is the lowest priority.
Type: tinyint
Length: 1
SkillsetID
Description: A unique number assigned by the server to identify the skillset
when the skillset is added.
Type: int
Length: 4
SkillsetName
Description: The name of the skillset to which the agent is assigned when the
assignment is run.
Type: varchar
Length: 64
SkillsetState
Description: The current state of the skillset.
Valid values:
Standby
Active
Type: varchar
Length: 80
Status
Description: The status of the agent to skillset assignment.
Valid values:
Edited/Saved
Ran OK
Scheduled
Never scheduled
Type: varchar
Length: 80
UserGivenName
Description: The given or first name of the agent.
Type: varchar
Length: 64
UserID
Description: A unique number assigned by the server to identify the agent when
the agent is added.
Type: binary
Length: 16
UserSurName
Description: The family or surname of the agent.
Type: varchar
Length: 64
UserTelsetLoginID
Description: The numeric ID the agent uses to log in to the phoneset or agent
desktop.
Type: varchar
Length: 16
SkillsetThresholdTemplate view
The SkillsetThresholdTemplate view lists the skillset threshold classes and their
threshold levels.
Field descriptions
The field descriptions for this view are described in this section.
Field
Description: The name of the field for which a threshold is defined in the
threshold class.
Type: varchar
Length: 80
FieldID
Description: A unique number assigned by the server to identify the field when
you define a threshold value for the field.
Type: int
Length: 4
Level1
Description: The low end of the normal range for the field.
Type: int
Length: 4
Level2
Description: The high end of the normal range for the field.
Type: int
Length: 4
MinShortCallDelay
Description: The length of a short call for this threshold class.
Type: int
Length: 4
Name
Description: The name of the skillset threshold class.
Type: varchar
Length: 30
ServiceLevelThreshold
Description: The service level threshold for this threshold class.
Type: int
Length: 4
TemplateID
Description: A unique number assigned by the server to identify the threshold
class when the threshold class is added.
Type: int
Length: 4
SummaryThresholdTemplate view
The SummaryThresholdTemplate view lists the thresholds defined for the Nodal
threshold class.
Field descriptions
The field descriptions for this view are described in this section.
Field
Description: The name of the field for which a threshold is defined in the
threshold class.
Type: varchar
Length: 80
FieldID
Description: A unique number assigned by the server to identify the field when
you define a threshold value for the field.
Type: int
Length: 4
Level1
Description: The low end of the normal range for the field.
Type: int
Length: 4
Level2
Description: The high end of the normal range for the field.
Type: int
Length: 4
Name
Description: The name of the nodal threshold class.
Type: varchar
Length: 30
TemplateID
Description: A unique number assigned by the server to identify the threshold
class when the threshold class is added.
Type: int
Length: 4
Supervisor view
The Supervisor view lists all of the Contact Center Manager supervisors and
their general properties.
Field descriptions
The field descriptions for this view are described in this section.
Comment
Description: Additional information about the supervisor, if any.
Type: varchar
Length: 127
Department
Description: The department to which the supervisor belongs.
Type: varchar
Length: 64
GivenName
Description: The given or first name of the supervisor.
Type: varchar
Length: 64
PCLoginName
Description: The supervisor’s desktop user ID.
Type: varchar
Length: 40
PersonalDN
Description: Communication Server 1000/Meridian 1 PBX switch only. The
supervisor’s personal directory number.
Type: varchar
Length: 32
SurName
Description: The family or surname of the supervisor.
Type: varchar
Length: 64
SwitchID
Description: The switch ID of the phoneset at which the supervisor is logged
on, received from the switch.
Type: int
Length: 4
SwitchPortAddress
Description: The switch port address of the phoneset at which the supervisor is
logged on, received from the switch.
Type: varchar
Length: 30
SwitchPortName
Description: The switch port name of the phoneset at which the supervisor is
logged on, as received from the switch.
Type: varchar
Length: 30
TelsetLoginID
Description: The numeric ID the supervisor uses to log in to the phoneset or
agent desktop.
Type: varchar
Length: 16
TemplateID
Description: A unique number assigned by the server to identify the access
class, which the supervisor belongs to, when the access class is added.
Type: int
Length: 4
TemplateName
Description: The name of the access class to which the supervisor belongs.
Type: nvarchar
Length: 30
ThresholdTemplateID
Description: A unique number assigned by the server to identify the threshold
class to which the supervisor belongs, when the threshold class is added.
Type: int
Length: 4
ThresholdTemplateName
Description: The name of the threshold class to which the supervisor belongs.
Type: nvarchar
Length: 30
Title
Description: The supervisor’s title.
Type: varchar
Length: 64
UserID
Description: A unique number assigned by the server to identify the supervisor
when the supervisor is added.
Type: binary
Length: 16
SupervisorAgentAssignment view
This view shows all agents and their supervisor assignments (both reporting and
associated). The view contains a record for each agent-supervisor relationship.
For example, if an agent has a reporting and two associated supervisors, the
view contains three records for that agent.
Field descriptions
The field descriptions for this view are described in this section.
AgentGivenName
Description: The first or given name of an assigned agent.
Type: varchar
Length: 64
AgentSurName
Description: The family or surname of the agent.
Type: varchar
Length: 64
AgentTelsetLoginID
Description: The numeric ID that the agent uses to log in to the phoneset or
agent desktop.
Type: varchar
Length: 16
AgentUserID
Description: A unique number assigned by the server to identify the agent when
the agent is added.
Type: binary
Length: 16
SupervisorGivenName
Description: The first or given name of the supervisor.
Type: varchar
Length: 64
SupervisorSurname
Description: The surname or family name of the supervisor.
Type: varchar
Length: 64
SupervisorTelsetLoginID
Description: The numeric ID the supervisor uses to log in at the phoneset or
agent desktop.
Type: varchar
Length: 16
SupervisorUserID
Description: A unique number assigned by the server to identify the supervisor
when the supervisor is added.
Type: binary
Length: 16
Type
Description: Shows whether the supervisor is the reporting or associated
supervisor for an agent.
Type: char
Length: 1
Valid values:
P (Reporting)
S (Associated)
SupervisorByAssignment view
Field descriptions
The field descriptions for this view are described in this section.
AgentID
Description: A unique number assigned by the server to identify the agent when
the agent is added.
Type: binary
Length: 16
AssignID
Description: A unique number assigned by the server to identify the assignment
when the assignment is added.
Type: int
Length: 4
AssignName
Description: The name of the agent to supervisor assignment.
Type: varchar
Length: 64
AssignType
Description: The assignment type.
Type: varchar
Length: 80
Comment
Description: Additional information, if any.
Type: varchar
Length: 127
ErrorCode
Description: A numeric value for the error encountered when the assignment
last ran, if any.
Type: int
Length: 4
Status
Description: The status of the agent to supervisor assignment.
Valid values:
Edited/Saved
Ran OK
Scheduled
Never scheduled
Type: varchar
Length: 80
SupervisorGivenName
Description: The given or first name of the supervisor to which the user is
assigned when this assignment is run.
Type: varchar
Length: 64
SupervisorID
Description: A unique number assigned by the server to identify the supervisor
to which the user is assigned to when this assignment is run, when the supervisor
is added.
Type: binary
Length: 16
SupervisorSurName
Description: The family or surname of the supervisor to which the user is
assigned when this assignment is run.
Type: varchar
Length: 64
Type
Description: The assignment type.
Valid values:
P (Reporting)
S (Associated)
Type: varchar
Length: 80
SwitchPort view
SwitchPort view lists phoneset ports and their switch configuration information.
Field descriptions
The field descriptions for this view are described in this section.
Acquire
Description: Shows whether there is a request to acquire or deacquire the route.
Type: char
Length: 1
Name
Description: The switch port name of the phoneset at which the agent is logged
on, as received from the switch.
Type: varchar
Length: 30
PortAddress
Description: The switch port address of the phoneset at which the agent is
logged on, as received from the switch.
Type: varchar
Length: 30
PositionID
Description: Communication Server 1000/Meridian 1 PBX switch only. A
unique identifier for the agent’s position ID, as received from the switch.
Type: int
Length: 4
SecondaryDN
Description: Communication Server 2x00/DMS switch only. The secondary
DN defined on the phoneset.
Type: int
Length: 4
Status
Description: The status of the phoneset.
Type: varchar
Length: 80
SwitchID
Description: The switch ID of the phoneset at which the agent is logged on,
received from the switch.
Type: int
Length: 4
Type
Description: The phoneset type.
Type: varchar
Length: 80
TargetSwitchComm view
Field descriptions
The field descriptions for this view are described in this section.
AgentReserveTimer
Description: The amount of time an agent at this site is reserved for an NSBR
call.
Type: int
Length: 4
DialableDN
Description: The number your switch dials to connect to the destination site.
Type: varchar
Length: 32
LandingPadOptions
Description:
Valid values:
0 to 7
Value Description
Value Description
MultiMediaNetworkURI
Description:
Type: varchar
Length: 255
NumRetries
Description: The number of times your switch attempts to connect to the
destination site, if a connection attempt is unsuccessful.
Type: smallint
Length: 2
RetryTimer
Description: The time that elapses between retry attempts.
Type: int
Length: 4
SiteID
Description: A unique number assigned by the system to identify this Contact
Center Manager site. The assigned SiteID remains unique over time even if a
configured site is deleted and another one is added with the same name. The
SiteID can be used in custom reports to identify statistics applicable to this site.
SiteName
Description: The name of the Contact Center Manager site, as assigned during
installation.
Type: varchar
Length: 30
UserTemplate view
The UserTemplate view lists the agent call presentation classes and their
properties.
Field descriptions
The field descriptions for this view are described in this section.
AlternateCallAnswer
Description: Communication Server 1000/Meridian 1 PBX switch only. Shows
whether the agent can put a DN call on hold to answer an incoming call. This
option is defined for the call presentation class to which the agent belongs.
Type: char
Length: 1
CallForceOption
Description: Communication Server 1000/Meridian 1 PBX switch only. Shows
whether the call force option is enabled for the call presentation class to which
this agent belongs.
Type: char
Length: 1
CallForceDelayTimer
Description: Communication Server 1000/Meridian 1 PBX switch only. The
time that elapses before a call is automatically presented to an agent. This option
is defined for the call presentation class to which the agent belongs.
Type: int
Length: 4
NROSDN
Description: Communication Server 2x00/DMS switch only. Shows whether
the agent can receive calls while active on their secondary DN.
Type: char
Length: 1
ReturnToQueueMode
Description: The mode of the agent’s phoneset after returning a call to the
queue.
Type: varchar
Length: 80
ReturnToQueueOnNoAnswer
Description: Shows whether unanswered calls are returned to the queue.
Type: char
Length: 1
ReturnToQueueWaitInterval
Description: The time before an unanswered call is returned to the queue.
Type: smallint
Length: 2
TelsetShowReserve
Description: NSBR option only. Shows whether an agent’s phoneset can show
that the agent is reserved for an NSBR call.
Type: char
Length: 1
Template
Description: The name of the call presentation class.
Type: varchar
Length: 30
TemplateID
Description: A unique number assigned by the server to identify the call
presentation class when the call presentation class is added.
Type: int
Length: 4
UnionBreakTimer
Description: Communication Server 1000/Meridian 1 PBX switch only. The
length of the break period allowed between calls. This option is defined for the
call presentation class to which the agent belongs.
Type: smallint
Length: 2
VariableWrap
Description: Communication Server 2x00/DMS switch only. Shows whether
the agent is put into Variable Wrap state after a call. Calls are not presented to
agents while they are in Variable Wrap state. This option is defined for the call
presentation class to which the agent belongs.
Type: char
Length: 1
UserThresholdTemplate view
The UserThresholdTemplate view lists the agent threshold classes and their
properties.
Field descriptions
The field descriptions for this view are described in this section.
FieldID
Description: A unique number assigned by the server to identify the field when
you define a threshold value for the field.
Type: int
Length: 4
Level1
Description: The low end of the normal range for the field.
Type: int
Length: 4
Level2
Description: The high end of the normal range for the field.
Type: int
Length: 4
Name
Description: The name of the agent threshold class.
Type: varchar
Length: 30
ThresholdTemplateID
Description: A unique number assigned by the server to identify the threshold
class when the threshold class is added.
Type: int
Length: 4
Views view
The View view lists all of the database views available in the Contact Center
Manager database.
Field descriptions
The field descriptions for this view are described in this section.
ColumnName
Description: The name of a field in the view. This name is not necessarily the
same as the field label printed on the report.
Type: varchar
Length: 30
Length
Description: The length of the field, in characters.
Type: tinyint
Length: 1
Name
Description: The name of the view.
Type: varchar
Length: 30
Type
Description: The field type.
Type: varchar
Length: 30
In this section
Overview of access and partition management views 500
Access Classes view 501
Report Groups view 503
User Defined Partitions view 505
Users view 508
The data for these reports is generated from the proprietary API developed for
the Contact Center Manager Administration Server. The data for these reports is
extracted from ADAM (active directory) and is stored in the temporary MS
Access database files for every user report session. The reports are run using
these temporary MS Access database files as the data source. When the report
session is closed by the user, the temporary MS Access database files are
removed from the server. The file name is:
UserID_DateTime_APMReport.MDB. For example,
User1_08122005041256_APMReport.MDB stored under directory folder:
\Program Files\Nortel Networks\WClient\Apps\Reporting\Historical\tmpData.
The Microsoft Access database file contains four tables that are used by the
reports.
Field descriptions
The field descriptions for this view are described in this section.
AccessClass
Description: Name of the access class.
Type: text
Length: 120
AccessLevel
Description: Access levels, such as Run and Import, Report Creation, Edit, or
View.
Type: text
Length: 60
EleDesc
Description: Access Class, for example, Historical Reporting or Real-time.
Type: text
Length: 100
FirstName
Description: First name of user.
Type: text
Length: 30
Group2
Description: Group header contains titles such as Members or Access Class
Properties.
Type: text
Length: 120
Group3
Description: Group header field for displaying Contact Center Manager Server.
Type: text
Length: 120
UserName
Description: Logon ID of user.
Type: text
Length: 30
LastName
Description: Surname of user.
Type: text
Length: 30
Field descriptions
The field descriptions for this view are described in this section.
EleDesc
Description: Contains the name of the report groups, user reports, and user-
defined partition names.
Type: text
Length: 60
Group2
Description: Contains report group header titles:
List of report groups
Standard_Outbound
Standard_Multimedia
Standard_Networking
Standard_Others
Standard_Configuration
Standard_CallByCall
Type: text
Length: 120
Group3
Description: Contains header titles:
User Defined Partitions
User Defined Report Groups
User Reports
Type: text
Length: 120
LastModified
Description: Last modified date of the user report.
Type: text
Length: 50
Owner
Description: User ID of the report owner.
Type: text
Length: 100
ServerName
Description: Name of the Contact Center Manager Server.
Type: text
Length: 120
The name of the Microsoft Access database table is PartitionsReport. The data in
the view is for each user-defined partition, configured elements (Agents,
Skillsets report groups, Applications, DNIS and CDN) per contact center
manager server, members assigned to the user-defined partition (Contact Center
Manager Administration users), and component-level access for the each of the
members, such as for Contact Center Management, Real Time Reporting, and
Historical Reporting.
Field descriptions
The field descriptions for this view are described in this section.
CCM
Description: Partition access (True or False) for Contact Center Manager
application.
Type: text
Length: 5
EleDesc
Description: Contains names of agents, skillsets, report groups, applications,
CDNs (Route Points), and DNISs.
Type: text
Length: 120
EleID
Description: Contains the Agent Login ID, CDN ID, and DNIS ID.
Type: text
Length: 50
FirstName
Description: First name of user.
Type: text
Length: 30
Group2
Description: Contains header titles:
Member
Contact Center Manager Server name
Type: text
Length: 120
Group3
Description: Contains partition element header titles:
Agents
Skillsets
Report groups
Applications
CDNs (Route Points)
DNISs
Type: text
Length: 120
HR
Description: Partition access (True or False) for Historical Reporting (HR)
application.
Type: text
Length: 5
LastName
Description: Surname of user.
Type: text
Length: 30
PartitionName
Description: Name of the user defined partition.
Type: text
Length: 120
RTR
Description: Partition access (True or False) for Real Time Reporting (RTR)
application.
Type: text
Length: 5
UserName
Description: Logon ID of user.
Type: text
Length: 30
Users view
The name of the Microsoft Access database table is UsersReport. The data in the
view is for each user, such as user's basic access rights, access classes allocated
to the user, full data access (yes/no), standard partitions, and reporting agents
data per configured Contact Center Manager Server and defined partition
assigned to the user.
Field descriptions
The field descriptions for this view are described in this section.
EleDesc
Description: Contains the name of the report groups, user reports, and user-
defined partition names.
Type: text
Length: 60
Group2
Description: Contains report group header titles:
List of report groups
Standard_Outbound
Standard_Multimedia
Standard_Networking
Standard_Others
Standard_Configuration
Standard_CallByCall
Type: text
Length: 120
Group3
Description: Contains header titles:
User Defined Partitions
LastModified
Description: Last modified date of user report.
Type: text
Length: 50
Owner
Description: User ID of report owner.
Type: text
Length: 100
ServerName
Description: Name of Contact Center Manager Server.
Type: text
Length: 120
In this chapter
Overview 512
Access rights by view 515
Section A: Summarized historical statistics 517
Section B: Event statistics 587
Overview
The Contact Center Manager database is an open database. You can access the
data in this database with any SQL- or ODBC-compliant application. You can
use the data in many ways, including the following:
Import it into a spreadsheet for manipulation.
Import it into your corporate database.
Develop customized reports using Report Creation Wizard, Crystal
Reports, or another reporting application.
Types of data
This chapter describes the following types of data:
Summarized historical statistics—statistics accumulated over a period of
time (15-minute interval, daily, weekly, or monthly).
Event statistics—statistics that report each occurrence of an event.
Resource usage
When you generate reports or export data from the database, you use system
resources, including server CPU and LAN bandwidth. To calculate resource
requirements for a specific application, use the Capacity Assessment Tool
(CapTool) application.
Default applications
There are five default applications that ship with Contact Center Manager:
Master_Script, Network_Script, ACD-DN, NACD-DN, and System. In some
views, activity code statistics peg against these default applications.
Application Description
The following tables lists the access rights needed to run reports, depending on
what view you are accessing.
Historical reports
The following table lists the access rights needed to run historical reports.
Run these reports run from the Network Control Center server.
You must configure users with these permissions on the Network Control Center
server and all Contact Center Manager Servers associated with the Network
Control Center server.
User permissions for the these views work on Contact Center Manager Server
6.0 only. If the Network Control Center server has a Symposium Call Center
Server 5.0 server configured, the users do not possess adequate permissions to
retrieve data from these views.
Event reports
The following table lists the access rights needed to run this event reports
In this section
Overview of summarized historical statistics 518
Types of views 519
ApplicationConStat views 522
CDNConStat views 546
DNISConStat views 551
NetworkInCallConStat 559
NetworkOutConStat views 566
SkillsetConStat views 573
These statistics are used in standard and user-defined reports. You can include
these statistics in your Report Creation Wizard-created and user-created reports.
You can enable or disable data collection for one of these groups at any time
while the system runs.
The number and type of statistics you choose to collect affects the amount of
disk space required for the database.
Storage duration
When you configure the Historical Statistics Collection, you can choose how
long to store different types of statistics. The duration you choose determines the
amount of disk space required for the database.
For more information about configuring the Historical Statistics Collection, see
the Contact Center Manager Administrator's Guide.
Types of views
Interval views
The server accumulates interval statistics for 15 minutes. The statistics
accumulate in the server RAM until the end of the 15-minute interval. The
server then creates a new record in the database for each entity (or combination
of entities). The new record contains the summarized statistics for that entity for
that interval. (The statistics collected depend on the type of entity.) The
Timestamp field of the new record is in the format YYYY/MM/DD
HH:MM:00:00, where MM is 00, 15, 30, or 45.
For example, to record agent by skillset statistics, the server creates a record for
each skillset for which an agent answered calls during the interval just ended.
ATTENTION
Interval statistics are not available until after the interval ends.
If you shut down the server without properly shutting down
the Contact Center Manager services, data for the current
interval is lost.
Daily views
Immediately after the end of the business day (after 12:00 midnight), the server
sums all of the interval records for the day, and creates corresponding daily
records. The Timestamp field of the daily records is in the format YYYY/MM/
DD 00:00:00:00.
Current day statistics are not available until the beginning of the next day (after
12:00 midnight).
Weekly views
After the end of the first day of the week (after 12:00 midnight), the server
creates weekly records that contain each of the daily totals. After the end of each
subsequent day in the week, the server adds the day total to the fields in the
weekly records. The Timestamp field of the weekly records is in the format
YYYY/MM/DD 00:00:00:00, where DD is the first day of the week.
Weekly statistics are not available until the beginning of the next week. You can
configure the first day of the week in the Historical Statistics Configuration.
Monthly views
Immediately after the end of the first day of the month (after 12:00 midnight),
the server creates monthly records that contain each of the daily totals. After the
end of each subsequent day in the month, the server adds the day total to the
fields in the monthly record. The Timestamp field of the monthly records is in
the format YYYY/MM/DD 00:00:00:00, where DD is 01.
Monthly statistics are not available until after 12:00 midnight of the first day in
the next month.
daily immediately after the end of the day (after 12:00 midnight)
weekly immediately after the end of the week (after 12:00 midnight
on the first day of the next business week)
monthly immediately after the end of the month (after 12:00 midnight
on the first day of the next month)
ApplicationConStat views
Statistics peg against a given application only for those intervals in which a
contact arrives for that application. Except for DNOutExtCallsTalkTime and
DNOutIntCallsTalkTime, these statistics do not include DN calls.
Definition: Application
An application is a logical entity that represents a script for reporting purposes.
The Master script and each script it references (that is, each primary script) has
an application with a name that is the same as the script name.
Requirements
Configure the servers to collect application statistics (see the Contact Center
Manager Administration online Help). Statistics are collected for all
applications; you cannot configure the system to collect statistics for selected
applications.
Database views
Application statistics use the following views:
iAppConStat
dAppConStat
wAppConStat
mAppConStat
Pegging
Incoming NSBR contacts peg against the Network_Script application.
Contact Center Manager does not have access to abandoned events and delay
statistics for ACD and NACD calls; therefore, these statistics are not applicable
to ACD_DN and NACD_DN applications.
ACD and NACD calls are not applicable to the SIP-enabled contact center.
Pegging thresholds
You can define application threshold classes with different values for the service
level threshold and short call length. Thus, the value for service level and short
call length can vary from one application to another. For more information about
threshold classes, see the Contact Center Manager Administrator's Guide and
Contact Center Manager Administration online Help.
SIP enabled contact center does not differentiate between ISDN and non-ISDN
trunks. All calls are pegged on non-ISDN calls.
Field descriptions
The field descriptions for this view are described in this section.
The delay time includes any time that the caller spends going through menus and
listening to announcements in this application.
Pegging: For local contacts and outgoing NSBR contacts, delays begin when
the Master_Script hands off the contact to a primary application. For incoming
NSBR contacts, delays begin when the contact is logically queued to this site.
Delays end when the caller disconnects.
Type: int
Length: 4
For voice calls, the delay time includes any time that the caller spends going
through menus and listening to announcements in this application.
Pegging: For local contacts and outgoing NSBR contacts, delays begin when
the Master_Script hands off the contact to a primary application. For incoming
NSBR contacts, delays begin when the contact is logically queued to this site.
Delays end when the call is answered or contact is accepted.
Type: int
Length: 4
Application
Description: The name of the application.
Type: varchar
Length: 30
ApplicationID
Description: A unique number assigned by the server to identify an application
when the application is defined. This field is used for linking tables in data
queries.
Type: int
Length: 4
CallsAbandoned
Description: The number of contacts—excluding DN calls, ACD, and NACD
calls—that entered the application and are released before the calls are
answered. This statistic includes calls abandoned during treatment such as IVR
or Broadcast Announcement.
Pegging: This statistic pegs when a caller disconnects while still in queue or
receiving treatment.
This statistic includes calls that receive the Give IVR treatment and are
presented with a messaging system voice menu, if the menu options are
programmed with EM (to go to a mailbox).
Type: int
Length: 4
CallsAbandonedAftThreshold
Description: The number of contacts—excluding DN calls, ACD, and NACD
calls—abandoned for this application after a wait greater than or equal to the
service level threshold for the threshold class to which the application belongs.
Triggers: For local contacts and outgoing NSBR contacts, delays begin when
the Master_Script hands off the contact to a primary application. For incoming
NSBR contacts, delays begin when the contact is logically queued to this site.
Delays end when the caller disconnects.
Type: int
Length: 4
CallsAbandonedDelay
Description: The wait time experienced by all contacts—excluding DN calls,
ACD, and NACD calls— that are abandoned by callers.
The delay time includes any time that the caller spends reviewing menus and
listening to announcements in this application. DNIS delay times include up
front menu time. Application delay times do not.
Triggers: For local contacts and outgoing NSBR contacts, delays begin when
the Master_Script hands off the contact to a primary application. For incoming
NSBR contacts, delays begin when the contact is logically queued to this site.
Delays end when the caller disconnects.
iAppConStat int 4
dAppConStat int 4
wAppConStat numeric 6
mAppConStat numeric 6
CallsAnswered
Description: The number of contacts, excluding DN calls, answered or
accepted for this application.
Pegging: Voice calls peg upon answer. Multimedia contacts peg upon
acceptance. ACD calls peg against the ACD_DN_Application, and NACD calls
against the NACD_DN_Application.
Type: int
Length: 4
CallsAnsweredAftThreshold
Description: The number of contacts—excluding DN calls, ACD and NACD
calls—answered or accepted after a wait greater than or equal to the service
level threshold for the threshold class to which the application belongs.
Triggers: For local and outgoing NSBR contacts, delays begin when the
Master_Script hands off the contact to a primary application. For incoming
NSBR voice contacts, delays begin when the contact is logically queued to this
site. Delays end when the contact is answered or the contact is accepted.
Type: int
Length: 4
CallsAnsweredDelay
Description: The wait time experienced by all contacts—excluding DN calls,
ACD and NACD calls—answered or accepted for this application.
This statistic includes Contact Center Multimedia Web Communication and text
chat contacts presented to the agent even if the customer abandons the contact.
Triggers: For local and outgoing NSBR contacts, delays begin when the
Master_Script hands off the contact to a primary application. For incoming
NSBR contacts, delays begin when the contact is logically queued to this site.
Delays end when the contact is answered or the contact is accepted.
iApplConStat int 4
dAppConStat int 4
wAppConStat numeric 6
mAppConStat numeric 6
CallsAnsweredDelayAtSkillset
Description: The total wait time experienced in the skillset queue by all
contacts answered or accepted for this application.
Triggers: Delays begin when the contact is queued against the first skillset and
end when the contact is answered.
iAppConStat int 4
dAppConStat int 4
wAppConStat numeric 6
mAppConStat numeric 6
CallsConferencedIn
Description: The number of local Contact Center Manager calls, SIP calls, and
incoming NSBR calls conferenced to this application.
Type: int
Length: 4
CallsConferencedOut
Description: The number of local Contact Center Manager calls, SIP calls,
incoming NSBR calls, ACD calls, and NACD calls conferenced out of this
application.
Type: int
Length: 4
CallsGivenBroadcast
Description: Communication Server 1000/Meridian 1 PBX switch only. The
number of local Contact Center Manager calls, SIP calls, and incoming NSBR
calls given broadcast treatment for this application.
CallsGivenDefault
Description: The number of local Contact Center Manager contacts, SIP calls,
multimedia contacts, and incoming NSBR contacts given default treatment as
the result of an error condition.
This statistic does not include calls given default treatment by the switch.
Contact Center Manager is unaware of these calls.
Pegging: Contacts are given default treatment under the following conditions:
The script fails or end of script is reached before controlling treatment is
given to the contact.
A QUIT command or end of script is reached and the contact is not queued
or routed.
The script contains illegal first statements.
An error condition has occurred from which the script executor cannot
recover.
CallsGivenForceBusy
Description: The number of local Contact Center Manager calls and SIP calls
given Force Busy treatment for this application.
Pegging: This statistic pegs when the Give Busy script command is executed.
Type: int
Length: 4
CallsGivenForceDisconnect
Description: The number of local Contact Center Manager calls SIP calls, and
multimedia contacts and incoming NSBR calls given Force Disconnect
treatment for this application.
This statistic also includes any Contact Center Outbound contacts that are
removed from the system when an outbound campaign ends.
Pegging: This statistic pegs when the Disconnect script command is executed.
Type: int
Length: 4
CallsGivenForceOverflow
Description: The number of local Contact Center Manager calls and SIP calls
given Force Overflow treatment for this application.
Pegging: This statistic pegs when the Give Overflow script command is
executed.
Type: int
Length: 4
CallsGivenHostLookup
Description: The number of local contacts and incoming NSBR contacts for
which data is obtained from a remote host through Host Data Exchange (HDX)
for this application.
Pegging: This statistic pegs when the Send Request script command is
executed.
Restriction: The count is not increased if the same contact receives this
treatment more than once.
Type: int
Length: 4
CallsGivenIVR
Description: The number of local Contact Center Manager calls and incoming
NSBR calls given IVR treatment for this application.
Pegging: This statistic pegs when the Give IVR script command is executed.
Restriction: The count is not increased if the same call receives this treatment
more than once.
Type: int
Length: 4
CallsGivenMusic
Description: The number of local Contact Center Manager calls, SIP voice
calls, and incoming NSBR calls given music treatment through a music route for
this application.
Pegging: This statistic pegs when the Give Music script command is executed.
Restriction: The count is not increased if the same call receives this treatment
more than once.
Type: int
Length: 4
CallsGivenNACD
Description: Communication Server 1000/Meridian 1 PBX switch only. The
number of local Contact Center Manager calls given Network ACD (NACD)
treatment. This treatment sends calls to a switch that does not use the Contact
Center Manager NSBR feature.
CallsGivenRAN
Description: The number of local Contact Center Manager calls, SIP calls, and
incoming NSBR calls given recorded announcement (RAN) treatment for this
application.
Pegging: This statistic pegs when the Give RAN script command is executed.
Restriction: The count is not increased if the same call receives this treatment
more than once.
Type: int
Length: 4
CallsGivenRouteTo
Description: The number of Contact Center Manager calls, SIP calls, and
incoming NSBR contacts given Route Call treatment for this application.
Pegging: This statistic pegs when the Route Call script command is executed.
Type: int
Length: 4
CallsNACDOut
Description: Communication Server 1000/Meridian 1 PBX switch only. The
number of local Contact Center Manager calls networked out through an NACD
queue and answered at remote switches. NACD is used to send calls to a switch
that does not use the Contact Center Manager NSBR feature.
CallsOffered
Description: The number of local contacts, incoming NSBR contacts, ACD
calls, and NACD calls offered to this application.
Pegging: Local Contact Center Manager contacts peg against the Master_Script
application upon arrival, and against a primary application when the
Master_Script application hands over control. ACD and NACD calls peg when
the call is answered. After answer, ACD calls peg against the
ACD_DN_Application and NACD calls against the NACD_DN_Application.
This statistic includes calls that receive the Give IVR treatment and are
presented with a messaging system voice menu, if the menu options are
programmed with either CL (to go to a mailbox through a DN) or Call
Answering (to go to a mailbox).
Type: int
Length: 4
CallsTransferredIn
Description: Communication Server 1000/Meridian 1 PBX switch only. The
number of local and incoming NSBR contacts transferred to this application.
This statistic does not include Contact Center Multimedia contacts transferred to
an agent or skillset.
Pegging: This statistic pegs as soon as the transfer is initiated, regardless of
whether the transfer is completed.
Type: int
Length: 4
CallsTransferredOut
Description: The number of local contacts, incoming NSBR contacts, ACD
calls, and NACD calls transferred out of this application.
This statistic does not include Contact Center Multimedia contacts that are
transferred out of this application.
Pegging: This statistic pegs when the transfer is completed.
If the agent aborts the transfer before it is complete, this statistic does not peg.
Type: int
Length: 4
ContactType
Description: The type of contact determined by the name of this application.
This applies to SIP-enabled contact centers, MCS 5100 contact centers, if
Contact Center Multimedia, or if Contact Center Outbound is installed and this
application name begins with one of the configured prefixes as described in
“Associating contact types with applications and skillsets” on page 186.
DNOutExtCallsTalkTime
Description: Communication Server 1000/Meridian 1 PBX switch only. The
total time spent by agents on outgoing external DN calls (see “Internal versus
External DN calls” on page 181 for a definition of external DN calls), including
hold time, for this application. This statistic does not include the time spent on
the DN outcall part of a Contact Center Outbound contact.
Triggers: DNOutExtCallsTalkTime begins when the call is answered and the
agent's previous contact was handled by this application. Talk time ends when
the caller disconnects or the agent releases the call.
Type: int
Length: 4
DNOutIntCallsTalkTime
Description: Communication Server 1000/Meridian 1 PBX switch only. The
total time spent by agents on outgoing internal DN calls (see “Internal versus
External DN calls” on page 181 for a definition of internal DN calls), including
hold time, for this application. This statistic does not include the time spent on
the DN outcall part of a Contact Center Outbound contact.
Triggers: DNOutIntCallsTalkTime begins when the call is answered and the
agent's previous contact was handled by this application. Talk time ends when
the caller disconnects or the agent releases the call.
Type: int
Length: 4
IVRAbandoned
Description: The number of local Contact Center Manager calls and incoming
NSBR calls abandoned during IVR treatment.
Type: int
Length: 4
IVRTerminated
Description: The number of local Contact Center Manager calls and incoming
NSBR calls that received and completed the IVR treatment in this application.
This statistic includes calls transferred by IVR.
Type: int
Length: 4
IVRTransferred
Description: The number of local Contact Center Manager calls and incoming
NSBR calls transferred from an IVR session for this application.
MaxCallsAbandonedDelay
Description: The wait time experienced by the contact—excluding DN calls,
ACD, and NACD calls—that waited the longest before the caller abandoned it.
Triggers: For local contacts and outgoing NSBR calls, delays begin when the
Master_Script hands off the contact to a primary application. For incoming
NSBR contacts, delays begin when the contact is logically queued to this site.
Delays end when the caller disconnects.
Type: int
Length: 4
MaxCallsAnsDelay
Description: The wait time experienced by the local contact, incoming NSBR
contact, or outgoing NSBR contact—excluding DN calls, ACD and NACD
calls—that waited the longest before the contact is answered or accepted.
Triggers: For local contacts and outgoing NSBR contacts, delays begin when
the Master_Script hands off the contact to a primary application. For incoming
NSBR contact, delays begin when the contact is logically queued to this site.
Delays end when the contact is answered or accepted.
Type: int
Length: 4
MaxCallsAnsDelayAtSkillset
Description: The wait time experienced by the contact that waited the longest in
the skillset queue before the contact is answered or accepted.
Triggers: Delays begin when the contact is queued against the first skillset and
end when the contact is answered or accepted for this application.
Type: int
Length: 4
MaxNetOutCallsAbandonedDelay
Description: NSBR option only. The wait time experienced by the outgoing
NSBR contact routed by this application that waited the longest before the
contact is abandoned at the destination site.
Length: 4
MaxNetOutCallsAnsweredDelay
Description: NSBR option only. The wait time experienced by the outgoing
NSBR contact routed by this application that waited the longest before the
contact is answered or terminated at the destination site.
Triggers: Delays begin when the Master_Script hands off the contact to a
primary application at the source site and end when the contact is answered or
accepted by an agent, answered by IVR, or terminated at the destination site.
Type: int
Length: 4
NetOutCalls
Description: NSBR option only. The number of outgoing NSBR contacts
successfully routed by this application to another site. This statistic includes
contacts answered (or accepted) or abandoned at the destination site, as well as
calls terminating on non-ISDN trunks and calls blocked by an all trunks busy
condition.
NetOutCallsAbandoned
Description: NSBR option only. The number of outgoing NSBR contacts,
excluding Contact Center Multimedia contacts, sent by this application and
abandoned at the destination sites.
NetOutCallsAbandonedDelay
Description: NSBR option only. The total time delay experienced by outgoing
NSBR contacts sent by this application and abandoned at the destination sites.
Triggers: Delays begin when the Master_Script hands off the contact to a
primary application at the source site and end when the caller disconnects.
The delay time includes any time that the caller spends going through menus and
listening to announcements in this application.
iAppConStat int 4
dAppConStat int 4
wAppConStat numeric 6
mAppConStat numeric 6
NetOutCallsAnswered
Description: NSBR option only. The number of outgoing NSBR contacts
routed by this application and answered or accepted at the destination site.
This includes contacts that arrive at the destination site, but the reserved agent
logs off or becomes unavailable, and the contact receives one of the following
treatments:
Disconnect
Route
Give Recorded announcement (RAN)
Give IVR
Give Music
NetOutCallsAnsweredDelay
Description: NSBR option only. The total wait time experienced by all
outgoing NSBR contacts routed by this application and answered or accepted at
the destination site.
The delay time includes any time that the caller spends going through menus and
listening to announcements in this application.
iAppConStat int 4
dAppConStat int 4
wAppConStat numeric 6
mAppConStat numeric 6
NetOutCallsReachNonISDN
Description: NSBR option only. The number of outgoing NSBR calls sent by
this application that reached a non-ISDN trunk on the way to its destination.
PostCallProcessingTime
Description: This data is the total time agents spent performing post-contact
processing. Normally, agents use this time to complete any work related to the
contact just completed, such as filling in forms or filing papers.
Triggers: Post-call processing time begins when an agent presses Not Ready
after releasing any contact, except DN calls, and ends when the agent presses
Not Ready again, places or receives a DN call, or logs out.
Post Call Processing Time is calculated for the first Not Ready period after a
contact is closed. If the agent enters another state after the call (for example, by
answering or receiving a DN call or logging out of the skillset), and then enters
Not Ready state, the Not Ready time does not peg against
PostCallProcessingTime. Also, if the agent interrupts the Not Ready period to
enter another state, and then returns to Not Ready state, the second Not Ready
period does not peg against PostCallProcessingTime.
Pegging: This statistic pegs against the last application for which the agent
handled a contact.
Type: int
Length: 4
Site
Description: The configured name of this Contact Center Manager site.
Type: varchar
Length: 30
SiteID
Description: A unique number assigned by the system to identify this Contact
Center Manager site. The assigned SiteID remains unique over time even if a
configured site is deleted and another one is added with the same name. The
SiteID can be used in custom reports to identify statistics applicable to this site.
TalkTime
Description: The total time that agents spent handling contacts (excluding DN
calls) in this interval, that were handled by this application. This statistic
includes hold time.
Triggers: The follow items trigger this statistic:
For voice calls, talk time begins when the agent answers the call.
For the Communication Server 1000/Meridian 1 PBX switch, talk time
ends when the caller disconnects or the agent releases or transfers the call.
For the Communication Server 2x00 switch, talk time ends when the agent
releases or transfers the call.
For multimedia contacts, talk time begins when the agent accepts the
contact and ends when the agent closes or transfers the contact.
For Contact Center Outbound contacts, talk time begins when the agent
accepts the contact, includes the time the agent is on the DN call, and ends
when the agent releases the DN call and closes the contact.
Type: int
Length: 4
Time
Description: The time (in 24-hour HH:MM format) when the data is pegged by
the system.
Type: char
Length: 5
TimeBeforeDefault
Description: The total time spent in the system by local Contact Center
Manager calls, SIP voice calls, multimedia contacts, and incoming NSBR
contacts that received default treatment for this application.
Pegging: For local contacts, pegging begins when the Master_Script is initiated.
For incoming NSBR contacts, pegging begins when the contact is queued to the
site. Pegging ends when treatment is given.
Type: int
Length: 4
TimeBeforeForceBusy
Description: The total time spent in the system by local Contact Center
Manager calls, SIP calls, and incoming NSBR calls that received Force Busy
treatment for this application.
Pegging: For local calls, pegging begins when the Master_Script is initiated.
For incoming NSBR calls, pegging begins when the contact is queued to the site.
Pegging ends when Give Busy treatment is given.
Type: int
Length: 4
TimeBeforeForceDisconnect
Description: The total time spent in the system by local Contact Center
Manager calls, SIP calls, multimedia contacts, and incoming NSBR calls that
received Force Disconnect treatment for this application.
Pegging: For local contacts, pegging begins when the Master_Script is initiated.
For incoming NSBR calls, pegging begins when the contact is queued to the site.
Pegging ends when Give Disconnect treatment is given.
Type: int
Length: 4
TimeBeforeForceOverflow
Description: The total time spent in the system by local Contact Center
Manager calls, SIP calls, and incoming NSBR calls that received Force
Overflow treatment for this application.
Pegging: For local Contact Center Manager calls, pegging begins when the
Master_Script is initiated. For incoming NSBR calls, pegging begins when the
contact is queued to the site. Pegging ends when Give Overflow treatment is
given.
Type: int
Length: 4
TimeBeforeInterflow
Description: The total amount of time that local contacts and outgoing NSBR
contacts spent in the Master_Script application before the contact is passed to a
primary application. For the Master_Script application, this is the total time
spent in the Master_Script by all contacts. For primary applications, this is the
total time spent in the Master_Script application by all contacts answered for the
primary application.
Pegging: Pegging begins when the Master_Script is initiated, and ends when
the contact is handed off to a primary application.
Type: int
Length: 4
TimeBeforeIVRTransferred
Description: The total time spent in the system by local Contact Center
Manager calls and incoming NSBR calls transferred to an IVR session for this
application.
TimeBeforeNACDOut
Description: The total time spent in the system by local Contact Center
Manager calls networked out through the NACD queue and answered at remote
nodes. NACD calls are sent to other switches without using the Contact Center
Manager NSBR feature.
TimeBeforeNetOut
Description: NSBR option only. The total time spent in the system by outgoing
NSBR contacts networked out by this application.
Pegging: Pegging begins when the contact arrives at the site and ends when the
contact is routed to the destination.
Type: int
Length: 4
TimeBeforeReachNonISDN
Description: NSBR option only. The total time spent in the system by outgoing
NSBR Contact Center Manager calls before they reached a non-ISDN trunk.
Pegging: Pegging begins when the call arrives at the site and ends when the call
is routed to a non-ISDN trunk.
Type: int
Length: 4
TimeBeforeRouteTo
Description: The total time spent in the system by local Contact Center
Manager calls, SIP voice calls, SIP video calls, and incoming NSBR calls that
received Route Call treatment.
Pegging: For local Contact Center Manager calls, pegging begins when the
Master_Script is initiated. For incoming NSBR calls, pegging begins when the
contact is queued to the site. Pegging ends when Route Call treatment is given.
Type: int
Length: 4
Timestamp
Description: The date and time when the data pegged. For more information
about the format of the Timestamp in interval, daily, weekly, or monthly views,
see “Overview of summarized historical statistics” on page 518. This field is
used for linking tables in data queries.
Type: smalldatetime
Length: 4
WaitTime
Description: The total time agents spend waiting for a contact after releasing a
voice call or closing a multimedia contact handled by this application.
Triggers: WaitTime begins when the agent goes into Idle state, for example, if:
an agent releases a voice call or closes a multimedia contact, and the
agent’s call presentation class is not configured for Break time or Variable
Wrap
an agent’s Break or Variable Wrap timer elapses after a contact is released
or closed
an agent presses the Not Ready key a second time after entering Not Ready
state
WaitTime ends when the agent leaves the Idle state. If the agent handles another
contact from the same application as the most recently handled contact,
WaitTime resumes against that application when the agent returns to the Idle
state. If the agent handles a contact from a different application than the most
recently handled contact, WaitTime begins against the new application when the
agent returns to the Idle state.
For more information, see “How is WaitTime pegged if the agent puts a DN call
on hold and uses alternate call answer to accept another contact?” on page 117.
Pegging: WaitTime pegs against the last application for which the agent
handled a contact during this login. If the agent has not yet handled a contact
associated with an application, WaitTime is not pegged.
Type: int
Length: 4
CDNConStat views
Statistics peg only for those intervals in which there are contacts coming into the
contact center through a CDN or Route Point. Incoming ACD, NACD, and DN
calls are not routed through CDNs or Route Points and are not included in these
statistics.
Definition: CDN
A Control Directory Number (CDN) is a number configured in the switch as the
entry point for voice contacts into Contact Center Manager. You can configure
multiple CDNs in the switch and associate them with the Master script of
Contact Center Manager.
Requirements
Fulfill the following requirements:
Define CDNs and Route Points on Contact Center Manager.
Configure the server to collect CDN statistics (see the Contact Center
Manager Administrator’s Guide). Statistics are collected for all CDNs and
Route Points; you cannot configure the system to collect statistics for only
selected CDNs or Route Points.
Database views
Control Directory Number (CDN) statistics use the following views:
iCDNConStat
dCDNConStat
wCDNConStat
mCDNConStat
Field descriptions
The field descriptions for this view are described in this section.
CallsAbandoned
Description: The number of local contacts and incoming NSBR calls
abandoned from this CDN or Route Point. This includes local contacts
networked out through the NSBR feature and abandoned or terminated at the
destination site.
This statistic includes contacts that receive the Give IVR treatment and are
presented with a messaging system voice menu, if the menu options are
programmed with CA (to go to a mailbox).
int
Length: 4
CallsAnswered
Description: The number of local contacts and incoming NSBR contacts
answered by this CDN or Route Point. This includes local contacts that are
networked out through the NSBR feature and answered or accepted by an agent
or IVR at the destination site.
Pegging: Voice calls peg upon answer and multimedia contacts peg upon
acceptance.
A contact pegs as answered if, when it arrives at the destination site, the reserved
agent logs out or becomes unavailable and it receives one of the following
treatments:
Disconnect
Route
Give Recorded announcement (RAN)
Give IVR
Give Music
Type: int
Length: 4
CallsOffered
Description: The number of local contacts and incoming NSBR contacts
offered to this CDN or Route Point.
This statistics include voice calls that receive the Give IVR treatment and are
presented with a messaging system voice menu, if the menu options are
programmed with either CL (to go to a mailbox through a DN) or CA (to go to a
mailbox).
Type: int
Length: 4
CallsTerminated
Description: The number of local contacts and incoming NSBR contacts for
this CDN or Route Point, which are terminated under one of the following
conditions:
This statistic includes voice calls that receive the Give IVR treatment and are
presented with a messaging system voice menu, if the menu options are
programmed with CL (to go to a mailbox through a DN).
Type: int
Length: 4
CallsWithDigitsCollected
Description: Communication Server 2x00/DMS switch only. The number of
voice calls that received IVR treatment and arrived at this CDN accompanied by
data collected during the IVR session.
Type: int
Length: 4
CDN
Description: A unique number to identify this CDN or Route Point, which the
server assigns when the CDN or Route Point is added.
Type: varchar
Length: 30
CDNName
Description: The name of this CDN as configured when it is added.
Type: varchar
Length: 30
Site
Description: The configured name of this Contact Center Manager site.
Type: varchar
Length: 30
SiteID
Description: A unique number assigned by the system to identify this Contact
Center Manager site. The assigned SiteID remains unique over time even if a
configured site is deleted and another one is added with the same name. The
SiteID can be used in custom reports to identify statistics applicable to this site.
Time
Description: The time (in 24-hour HH:MM format) when the data is pegged by
the system.
Type: char
Length: 5
Timestamp
Description: The date and time when the data is pegged by the system. For
more information about the format of the Timestamp in interval, daily, weekly,
or monthly views, see “Overview of summarized historical statistics” on page
518.
Type: smalldatetime
Length: 4
URI
Description: The name of this Route Point as configured when it is added.
Type: varchar
Length: 255
DNISConStat views
Definition: DNIS
DNIS is an optional service to identify the dialed number for calls entering the
contact center. Typically, DNIS numbers are used for 1-800 numbers. For
example, a company might give customers different 1-800 numbers for sales and
customer service calls.
Requirements
Fulfill the following requirements:
Define DNISs on Contact Center Manager.
Configure the servers to collect DNIS statistics (see the Contact Center
Manager Administrator’s Guide). Statistics are collected for all DNISs;
you cannot configure the system to collect statistics for selected DNISs.
Database views
Dialed Number Identification Service (DNIS) statistics use the following views:
iDNISConStat
dDNISConStat
wDNISConStat
mDNISConStat
Field descriptions
The field descriptions for this view are described in this section.
CallsAbandoned
Description: The number of local Contact Center Manager calls and incoming
NSBR calls abandoned for a DNIS number.
Type: int
Length: 4
CallsAbandonedAftThreshold
Description: The number of local Contact Center Manager calls and incoming
NSBR calls abandoned that experienced a delay greater than or equal to the
service level threshold for the DNIS number.
Triggers: For local Contact Center Manager calls, delays begin when the
Master_Script is initiated. For incoming NSBR calls, delays begin when the call
is logically queued to this site.
Type: int
Length: 4
CallsAbandonedDelay
Description: The total wait time experienced by all local Contact Center
Manager calls and incoming NSBR calls abandoned for a DNIS number.
Triggers: For local Contact Center Manager calls, delays begin when the
Master_Script is initiated. For incoming NSBR calls, delays begin when the call
is logically queued to this site.
The delay time includes any time that the caller spends navigating menus and
listening to announcements before it is queued to a skillset.
Type: int
Length: 4
CallsAnswered
Description: The number of local Contact Center Manager calls and incoming
NSBR calls answered for a DNIS number.
Pegging: Calls peg upon answer.
Type: int
Length: 4
CallsAnsweredAftThreshold
Description: The number of local Contact Center Manager calls and incoming
NSBR calls answered that experienced a delay greater than or equal to the
service level threshold for the DNIS number.
Triggers: For local Contact Center Manager calls, delays begin when the
Master_Script is initiated. For incoming NSBR calls, delays begin when the call
is logically queued to this site.
Type: int
Length: 4
CallsAnsweredDelay
Description: The wait time experienced by all local Contact Center Manager
calls and incoming NSBR calls answered for a DNIS number.
Triggers: For local Contact Center Manager calls, delays begin when the
Master_Script is initiated. For incoming NSBR calls, delays begin when the call
is logically queued to this site.
The delay time includes any time that the caller spends navigating menus and
listening to announcements before it is queued to a skillset.
Type: int
Length: 4
CallsGivenDefault
Description: The number of local Contact Center Manager calls and incoming
NSBR calls given default treatment for a DNIS number.
Type: int
Length: 4
CallsGivenForceBusy
Description: The number of local Contact Center Manager calls and incoming
NSBR calls given Force Busy treatment for a DNIS number.
Pegging: This statistic pegs when the Give Busy script command is executed.
Type: int
Length: 4
CallsGivenForceDisconnect
Description: The number of local Contact Center Manager calls and incoming
NSBR calls given Force Disconnect treatment for a DNIS number.
Pegging: This statistic pegs when the Disconnect script command is executed.
Type: int
Length: 4
CallsGivenForceOverflow
Description: The number of local Contact Center Manager calls and incoming
NSBR calls given Force Overflow treatment for a DNIS number.
Pegging: This statistic pegs when the Give Overflow script command is
executed.
Type: int
Length: 4
CallsGivenRouteTo
Description: The number of local Contact Center Manager calls and incoming
NSBR calls given Route Call treatment for a DNIS number.
Pegging: This statistic pegs when the Route Call script command is executed.
Type: int
Length: 4
CallsNACDOut
Description: Communication Server 1000/Meridian 1 PBX switch only. The
number of local Contact Center Manager calls networked out through an NACD
queue and answered at remote sites.
CallsNetworkedOut
Description: NSBR option only. The number of local Contact Center Manager
calls routed to a remote site and answered or abandoned.
CallsOffered
Description: The number of local Contact Center Manager calls and incoming
NSBR calls offered to this server with this DNIS number.
Pegging: Calls peg upon arrival.
Type: int
Length: 4
CallsReachNonISDN
Description: NSBR option only. The number of local Contact Center Manager
calls that reached a non-ISDN trunk while it is routed to a remote site.
Pegging: SIP-enabled contact center does not differentiate between ISDN and
non-ISDN trunks. All calls are pegged on non-ISDN calls.
Restriction: If a call encounters a non-ISDN trunk while it is networked to
another Contact Center Manager site, the call information that normally travels
with the call does not reach the destination site. This means the destination site
cannot tell that the call came from the Contact Center Manager network. At the
destination site, the networked call is treated as a new call. At the source site, the
NSBR call is terminated.
Type: int
Length: 4
DNIS
Description: A unique number used to identify a DNIS, which the server
assigns when the DNIS is defined.
Type: varchar
Length: 16
DNISName
Description: The name of a DNIS.
Type: varchar
Length: 30
DNIS_Prefix
Description: Stores the prefix of a DNIS number. You can sort, filter, and
report on individual DNIS 800 numbers.
Type: varchar
Length: 16
IVRTransferred
Description: The number of local Contact Center Manager calls and incoming
NSBR calls transferred from an IVR session for a DNIS number.
MaxAbandonedDelay
Description: The wait time experienced by the local Contact Center Manager
calls or incoming NSBR call that waited the longest before it is abandoned.
Triggers: For local Contact Center Manager calls, delays begin when the
Master_Script is initiated. For incoming NSBR calls, delays begin when the call
is logically queued to this site.
Type: int
Length: 4
MaxAnsweredDelay
Description: The wait time experienced by the local Contact Center Manager
calls or incoming NSBR call that waited the longest before it is answered.
Triggers: For local Contact Center Manager calls, delays begin when the
Master_Script is initiated. For incoming NSBR calls, delays begin when the call
is logically queued to this site.
Type: int
Length: 4
NetworkCDN
Description: For future use. Not valid in this release.
Type: varchar
Length: 30
Site
Description: The configured name of this Contact Center Manager site.
Type: varchar
Length: 30
SiteID
Description: A unique number assigned by the system to identify this Contact
Center Manager site. The assigned SiteID remains unique over time even if a
configured site is deleted and another one is added with the same name. The
SiteID can be used in custom reports to identify statistics applicable to this site.
TalkTime
Description: The total time spent by all agents on local Contact Center Manager
calls and incoming NSBR calls for a DNIS number, including hold time.
Triggers:
Communication Server 1000/Meridian 1 PBX switch: The call pegs
when the caller disconnects or the agent releases the call.
Communication Server 2x00/DMS switch: The time pegs when the agent
releases the call.
Pegging: Talk time pegs at the end of the interval (for calls that are active at the
end of an interval), and when the call terminates.
Type: int
Length: 4
Time
Description: The time (in 24-hour HH:MM format) when the data is pegged by
the system.
Type: char
Length: 5
Timestamp
Description: The date and time when the data is pegged by the system. For
more information about the format of the Timestamp in interval, daily, weekly,
or monthly views, see “Overview of summarized historical statistics” on page
518.
Type: smalldatetime
Length: 4
Type
Description: Distinguishes between local and landing-pad DNIS.
Type: tinyint
Length: 1
URI
Description: For future use. Not valid in this release.
Type: varchar
Length: 255
NetworkInCallConStat
NSBR option only. Network call statistics provide information that can be used
to monitor contact distribution and handling in a network environment. They
record statistics for all incoming NSBR contacts received at a site.
Network statistics only report on contacts that are controlled by the server (that
is, Contact Center Manager contacts and multimedia contacts). They do not
report on DN, ACD, or NACD calls.
Requirements
Configure the server to collect network call statistics (see the Contact Center
Manager Administrator’s Guide). Statistics are collected for all applications;
you cannot configure the system to collect statistics for selected applications.
Restrictions
Network call statistics generated on the server are collected on the destination
site only. To report on network contact handling at all sites, generate a network-
wide report from the Network Control Center.
Database views
Network call statistics use the following views:
iNetworkInCallStat
dNetworkInCallStat
wNetworkInCallStat
mNetworkInCallStat
Field descriptions
The field descriptions for this view are described in this section.
CallsAbandoned
Description: The number of incoming NSBR contacts abandoned at the local
site.
Type: int
Length: 4
CallsAbandonedAftThreshold
Description: The number of incoming NSBR contacts abandoned at the local
site after a wait that exceeds the service level threshold for the application.
Type: int
Length: 4
CallsAbandonedDelay
Description: The total wait time experienced by all incoming NSBR contacts
abandoned at the local site.
Triggers: Delays begin when the Master_Script is initiated at the source site and
end when the contact is abandoned at the local site.
The delay time includes any time that the caller spends going through menus and
listening to announcements before it is queued to a skillset.
iNetworkInCallStat int 4
dNetworkInCallStat int 4
wNetworkInCallStat numeric 6
mNetworkInCallStat numeric 6
CallsAbandonedDelayAtDest
Description: The total wait time experienced at the local site by all incoming
NSBR contacts abandoned at the local site.
Triggers: Delays begin when the Master_Script is initiated and end when the
contact is abandoned at the local site.
iNetworkInCallStat int 4
dNetworkInCallStat int 4
wNetworkInCallStat numeric 6
mNetworkInCallStat numeric 6
CallsAnswered
Description: The number of incoming NSBR contacts answered or accepted at
the local site.
Type: int
Length: 4
CallsAnsweredAftThreshold
Description: The number of incoming NSBR contacts answered or accepted at
the local site after a wait greater than or equal to the service level threshold for
the application. The delay begins when a contact enters the local site. The
service level threshold is set during system configuration of the local site.
Type: int
Length: 4
CallsAnsweredDelay
Description: The total wait time experienced by all incoming NSBR contacts
answered or accepted at the local site.
Triggers: Delays begin when the Master_Script is initiated at the source site and
end when the contact is answered or accepted at the local site.
The delay time includes any time that the caller spends going through menus and
listening to announcements in this application.
iNetworkInCallStat int 4
dNetworkInCallStat int 4
wNetworkInCallStat numeric 6
mNetworkInCallStat numeric 6
CallsAnsweredDelayAtDest
Description: The total wait time experienced at the local site by all incoming
NSBR contacts answered or accepted at the local site.
Triggers: Delays begin when the contact is queued to the local site and end
when the contact is answered or accepted at the local site.
iNetworkInCallStat int 4
dNetworkInCallStat int 4
wNetworkInCallStat numeric 6
mNetworkInCallStat numeric 6
CallsOffered
Description: The number of incoming NSBR contacts offered to the local site.
Type: int
Length: 4
DstApplication
Description: The name of the destination application. This name is always
Network_Script.
Type: varchar
Length: 30
DstApplicationID
Description: A unique number assigned by the server to identify the
Network_Script application.
Type: int
Length: 4
DstSite
Description: The name of the local Contact Center Manager site, as defined on
the Network Control Center.
Type: varchar
Length: 30
DstSiteID
Description: A unique number assigned by the server to identify the local
Contact Center Manager site when the site is defined on the Network Control
Center.
Type: int
Length: 4
MaxCallAbandonedDelay
Description: The wait time experienced by the incoming NSBR contact that
waited the longest before it is abandoned at the local site.
Triggers: Delays begin when the Master_Script is initiated at the source site and
end when the contact is abandoned at the local site.
Type: int
Length: 4
MaxCallAbandonedDelayAtDest
Description: The wait time experienced by the contact that waited the longest at
the local site before it is abandoned.
Triggers: Delays begin when a contact is logically queued to the local site and
end when the contact is abandoned.
Type: int
Length: 4
MaxCallAnsweredDelay
Description: The total wait time experienced by all calls answered or contacts
accepted at the local site.
Triggers: Delays begin when the Master_Script is initiated at the source site and
end when the call is answered or contact is accepted at the local site.
Type: int
Length: 4
MaxCallAnsweredDelayAtDest
Description: The wait time experienced by the contact that waited the longest at
the local site before it is answered or accepted.
Triggers: Delays begin when a contact is logically queued to the local site and
end when the contact is answered or accepted.
Type: int
Length: 4
SrcApplication
Description: The name of the source application.
Type: varchar
Length: 30
SrcApplicationID
Description: A unique number assigned by the server to identify the source
application when the application is defined.
Type: int
Length: 4
SrcSite
Description: The name of the source Contact Center Manager site, as assigned
when the site is defined on the Network Control Center.
Type: varchar
Length: 30
SrcSiteID
Description: The unique identifier for the source Contact Center Manager site
where a call originated.
Type: int
Length: 4
Time
Description: The time (in 24-hour HH:MM format) when the data is pegged by
the system.
Type: char
Length: 5
Timestamp
Description: The date and time when the data is pegged by the system, in local
(destination) site time. For more information about the format of the Timestamp
in interval, daily, weekly, or monthly views, see “Overview of summarized
historical statistics” on page 518. This field is used for linking tables in data
queries.
Type: smalldatetime
Length: 4
NetworkOutConStat views
Requirements
Configure the server to collect network outcall statistics (see the Contact Center
Manager Administrator’s Guide).
Restrictions
At each Contact Center Manager site, the historical network outgoing contact
statistics are only collected against the local site. These statistics contain
network outgoing contact traffic and handling information for contacts for
which the local site is the source.
Database views
Network outgoing contact statistics use the following views:
iNetworkOutConStat
dNetworkOutConStat
wNetworkOutConStat
mNetworkOutConStat
Field descriptions
The field descriptions for this view are described in this section.
CallsAbandoned
Description: The number of contacts abandoned at the destination site.
Type: int
Length: 4
CallAbandonedDelayAtDest
Description: The total wait time experienced at the destination site by all
contacts from the local site abandoned at the destination site.
Triggers: Delays begin when the contact is queued to the destination site and
end when the contact is abandoned.
iNetworkOutConStat int 4
dNetworkOutConStat int 4
wNetworkOutConStat numeric 6
mNetworkOutConStat numeric 6
CallsAnswered
Description: The number of contacts answered or accepted by an agent,
answered by IVR, or terminated at the destination site.
Pegging: A contact pegs as answered if, when it arrives at the destination site,
the reserved agent logs off or becomes unavailable and it receives one of the
following treatments:
Disconnect
Route
Give Recorded announcement (RAN)
Give IVR
Give Music
Type: int
Length: 4
CallAnsweredDelayAtDestination
Description: The total wait time experienced at the destination site by all
contacts from the local site answered or accepted by an agent, answered by IVR,
or terminated at the destination site.
Triggers: Delays begin when the contact is queued to the destination site and
end when the contact is answered or accepted.
iNetworkOutConStat int 4
dNetworkOutConStat int 4
wNetworkOutConStat numeric 6
mNetworkOutConStat numeric 6
CallsOffered
Description: The number of contacts offered to the destination site.
Type: int
Length: 4
DstApplication
Description: The name of the destination application (this is always
Network_Script).
Type: varchar
Length: 30
DstApplicationID
Description: A unique number assigned by the server to identify the destination
application.
Type: int
Length: 4
DstSite
Description: The name of the destination Contact Center Manager site, as
defined when the site is configured on the Network Control Center.
Type: varchar
Length: 30
DstSiteID
Description: A unique number assigned by the server to identify a destination
site when the site is configured on the Network Control Center.
Type: int
Length: 4
MaxCallAbandonedDelay
Description: The wait time experienced by the contact originating at the local
site that waited the longest before it is abandoned at the destination site.
Triggers: Delays begin when the Master_Script is initiated at the local site and
end when the contact is abandoned.
Type: int
Length: 4
MaxCallAbandonedDelayAtDest
Description: The wait time experienced by the contact originating at the local
site that waited the longest at the destination site before it is abandoned.
Triggers: Delays begin when the contact is queued to the destination site and
end when the contact is abandoned.
Type: int
Length: 4
MaxCallAnsweredDelay
Description: The wait time experienced by the contact originating at the local
site that waited the longest before it is answered or accepted by an agent,
answered by IVR, or terminated at the destination site.
Triggers: Delays begin when the Master_Script is initiated at the local site and
end when the contact is answered or accepted.
Type: int
Length: 4
MaxCallAnsweredDelayAtDest
Description: The wait time experienced by the contact originating at the local
site that waited the longest at the destination site before it is answered or
accepted by an agent, answered by IVR, or terminated.
Triggers: Delays begin when the contact is logically queued to the destination
site and end when the contact is answered or accepted.
Type: int
Length: 4
SrcApplication
Description: The name of the source application.
Type: varchar
Length: 30
SrcApplicationID
Description: A unique number assigned by the server to identify the source
application when the application is defined.
Type: int
Length: 4
SrcSite
Description: The name of the local site, as defined when the site is defined on
the Network Control Center.
Type: varchar
Length: 30
SrcSiteID
Description: A unique number assigned by the server to identify a source
Contact Center Manager site where a call originated when the site is defined on
the Network Control Center.
Type: int
Length: 4
Time
Description: The time (in 24-hour HH:MM format) when the data is pegged by
the system.
Type: char
Length: 5
Timestamp
Description: The date and time when the data is pegged by the system, in local
(source) site time. For more information about the format of the Timestamp in
interval, daily, weekly, or monthly views, see “Overview of summarized
historical statistics” on page 518. This field is used for linking tables in data
queries.
Type: smalldatetime
Length: 5
TotalCallAbandonedDelay
Description: The total wait time experienced by all contacts from the local site
abandoned at the destination site.
Triggers: Delays begin when the Master_Script is initiated at the local site and
end when the contact is abandoned.
iNetworkOutConStat int 4
dNetworkOutConStat int 4
wNetworkOutConStat numeric 6
mNetworkOutConStat numeric 6
TotalCallAnsweredDelay
Description: The total wait time experienced by all contacts from the local site
answered or accepted by an agent, answered by IVR, or terminated at the
destination site.
Triggers: Delays begin when the Master_Script is initiated at the local site and
end when the contact is answered.
iNetworkOutConStat int 4
dNetworkOutConStat int 4
wNetworkOutConStat numeric 6
mNetworkOutConStat numeric 6
SkillsetConStat views
Statistics peg for a given skillset only for those intervals in which the skillset is
staffed.
Only contacts queued to a skillset are included in these statistics (if a skillset is
mapped to an ACD DN or NACD DN, calls to that DN are included). Except for
DNOutExtCallsTalkTime and DNOutIntCallsTalkTime, these statistics do not
include DN calls.
Requirements
Configure the server to collect skillset statistics (see the Contact Center
Manager Administrator’s Guide). Statistics are collected for all skillsets; you
cannot configure the system to collect statistics for selected skillsets.
Pegging
All statistics peg against a specific skillset and application combination and
either the local or originating site.
Local contacts
Local Contact Center Manager contacts peg against the Master_Script or
primary application (depending on the location of the call in the system) and
against the answering skillset, or the Agent Queue To skillset (if the contact is
queued to a specific agent for the contact's contact type).
Closed contacts that are pulled for additional processing by the agent are pegged
against the Agent Queue To skillset for the contact’s contact type. New and New
Reply contacts that are pulled while already within Contact Center Manager are
pegged against the skillset they are queuing in, if any, up to the time they are
pulled, and then against the Agent Queue To skillset for the contact type. Local
contacts peg against the local site.
ACD calls
ACD calls peg against the ACD_DN_Application and either the skillset to
which this ACD-DN is mapped (if defined) or the Default_ACD skillset. ACD
calls peg against the local site.
NACD calls
NACD calls peg against the NACD_DN_Application and either the skillset to
which this Network ACD-DN is mapped (if defined) or the Default_NACD
skillset. NACD calls peg against the local site.
Pegging thresholds
You can define skillset threshold classes with different values for the service
level threshold and the length (talk time, handling time) of a short call or
contact. Thus, the value for service level and short call length can vary from one
skillset to another. For more information about threshold classes, refer to the
Contact Center Manager Administrator’s Guide.
For ACD calls, the server does not record information about call activity on the
switch. ACD calls are tracked from the time they are answered at a phoneset
acquired by Contact Center Manager.
Database views
Skillset statistics use the following views:
iSkillsetConStat
dSkillsetConStat
wSkillsetConStat
mSkillsetConStat
Field descriptions
The field descriptions for this view are described in this section.
ActiveTime
Description: The amount of time a skillset is in service. A skillset is in service
when it is not in Out of Service mode and at least one agent is logged on.
AllAgentBusyTime
Description: The total time that all agents assigned to this skillset are busy with
contacts or no agents are logged on.
Pegging: This field pegs only against the System_Application.
Type: int
Length: 4
Application
Description: The name of the application that queued the contact to this skillset.
Type: varchar
Length: 30
ApplicationID
Description: A unique number assigned by the server to identify an application
when the application is defined. This field is used for linking tables in data
queries.
Type: int
Length: 4
CallsAnswered
Description: The number of local contacts (excluding DN calls), incoming
NSBR calls, ACD calls, and NACD calls answered or accepted by agents in this
skillset.
CallsAnsweredAfterThreshold
Description: The number of local contacts (excluding DN, ACD and NACD
calls) and incoming NSBR contacts answered or accepted after a wait greater
than or equal to the service level threshold for the threshold class to which the
skillset belongs.
CallsAnsweredDelay
Description: The wait time experienced by all local contacts—excluding DN,
ACD, and NACD calls—and incoming NSBR contacts answered or accepted for
this skillset.
CallsOffered
Description: The number of contacts—excluding DN, ACD, and NACD
calls—offered to this skillset, regardless of whether the contacts are answered or
accepted for this skillset. This statistic is not incremented if the same contact is
offered to this skillset again.
Triggers: Contacts peg against the Master_Script application upon arrival, and
against a primary application when the Master_Script application hands over
control.
ContactType
Description: The type of contact determined by the name of this skillset. This
applies to SIP-enabled contact centers, MCS 5100 contact centers, if Contact
Center Multimedia, or if Contact Center Outbound is installed and this skillset
name begins with one of the configured prefixes as described in “Associating
contact types with applications and skillsets” on page 186.
DNOutExtCallsTalkTime
Description: Communication Server 1000/Meridian 1 PBX switch only. The
total time spent by agents on outgoing external DN calls (see “Internal versus
External DN calls” on page 181 for a definition of external DN calls), including
hold time, for this skillset. This statistic does not include the time spent on the
DN outcall part of a Contact Center Outbound contact.
Triggers: DNOutExtCallsTalkTime begins when the call is answered and the
agent's previous contact was queuing in this skillset. Talk time ends when the
caller disconnects or the agent releases the call. For a three-way conference call,
talk time ends only when the agent releases the call.
Type: int
Length: 4
DNOutIntCallsTalkTime
Description: Communication Server 1000/Meridian 1 PBX switch only. The
total time spent by agents on outgoing internal DN calls (see “Internal versus
External DN calls” on page 181 for a definition of internal DN calls), including
hold time, for this skillset. This statistic does not include the time spent on the
DN outcall part of a Contact Center Outbound contact.
Triggers: DNOutIntCallsTalkTime begins when the call is answered and the
agent's previous contact was queuing for this skillset. Talk time ends when the
caller disconnects or the agent releases the call. For a three-way conference call,
talk time ends only when the agent releases the call.
Type: int
Length: 4
MaxAnsweredDelay
Description: The wait time experienced by the local contact—excluding DN,
ACD, and NACD calls—or incoming NSBR contact that waited the longest
before it is answered or accepted.
MaxSkillsetAbandonedDelay
Description: The wait time experienced by the local contact—excluding DN,
ACD, and NACD calls—or incoming NSBR contact queued to this skillset that
waited the longest before it is abandoned.
NetCallsAnswered
Description: NSBR option only. The number of incoming NSBR contacts
answered or accepted for this skillset.
Type: int
Length: 4
PostCallProcessingTime
Description: This data is the total time agents spent performing post-contact
processing. Normally, agents use this time to complete any work related to the
contact just completed, such as filling in forms or filing papers.
Triggers: Post-call processing time begins when an agent presses Not Ready
after releasing any contact, except DN calls, and ends when the agent presses
Not Ready again, places or receives a DN call, or logs out.
Post Call Processing Time is calculated for the first Not Ready period after a
contact is closed. If the agent enters another state after the call (for example, by
answering or receiving a DN call or logging out of the skillset), and then enters
Not Ready state, the Not Ready time does not peg against
PostCallProcessingTime. Also, if the agent interrupts the Not Ready period to
enter another state, and then returns to Not Ready state, the second Not Ready
period does not peg against PostCallProcessingTime.
Pegging: This statistic pegs against the last skillset for which the agent handled
a contact.
Type: int
Length: 4
OriginatingSite
Description: The configured name of the originating Contact Center Manager
site that the fields are applicable to.
OriginatingSiteID
Description: A unique number assigned by the system to identify the Contact
Center Manager site that the fields are applicable to. The assigned
OriginatingSiteID remains unique over time even if a configured site is deleted
and another one is added with the same name. The OriginatingSiteID can be
used in custom reports to identify statistics applicable to a particular site.
Type: int
Length: 4
Skillset
Description: The name of the skillset.
Type: varchar
Length: 30
SkillsetAbandoned
Description: The number of contacts abandoned while queuing in this skillset.
This statistic does not include contacts abandoned while being presented to an
agent.
Type: int
Length: 4
SkillsetAbandonedDelay
Description: The total wait time experienced by contacts abandoned while
queuing in this skillset.
Triggers: The delay begins when the contact is queued to this skillset and ends
when the contact is abandoned.
Type: int
Length: 4
SkillsetAbandonedAftThreshold
Description: The number of contacts abandoned while queuing in this skillset
after a wait greater than or equal to the service level threshold for the threshold
class to which the skillset belongs.
Type: int
Length: 4
SkillsetID
Description: A unique number assigned by the server to identify this skillset
when the skillset is added. For network skillsets, this is the ID as it appears on
the local site.
Type: int
Length: 4
TalkTime
Description: The total time that agents spent handling contacts (excluding DN
calls) in this interval, that were queuing in this skillset. This statistic includes
hold time.
Triggers: The follow items trigger this statistic:
For voice calls, talk time begins when the agent answers the call.
For the Communication Server 1000/Meridian 1 PBX switch, talk time
ends when the caller disconnects or the agent releases or transfers the call.
For the Communication Server 2x00 switch, talk time ends when the agent
releases or transfers the call.
For multimedia contacts, talk time begins when the agent accepts the
contact and ends when the agent closes or transfers the contact.
For Contact Center Outbound contacts, talk time begins when the agent
accepts the contact, includes the time the agent is on the DN call, and ends
when the agent releases the DN call and closes the contact.
Type: int
Length: 4
TerminatingSite
Description: The configured name of the terminating Contact Center Manager
site that the fields are applicable to.
TerminatingSiteID
Description: A unique number assigned by the system to identify the Contact
Center Manager site that the fields are applicable to. The assigned
TerminatingSiteID remains unique over time even if a configured site is deleted
and another one is added with the same name. The TerminatingSiteID can be
used in custom reports to identify statistics applicable to a particular site.
Type: int
Length: 4
Time
Description: The time (in 24-hour HH:MM format) when the data is pegged by
the system.
Type: int
Length: 5
Timestamp
Description: The date and time when the data is pegged by the system. For
more information about the format of the Timestamp in interval, daily, weekly,
or monthly views, see “Overview of summarized historical statistics” on page
518. This field is used for linking tables in data queries.
Type: smalldatetime
Length: 4
TotalStaffedTime
Description: The amount of logon time for all agents belonging to this skillset.
Pegging: This field pegs only against the System_Application.
Triggers: The logon time begins when an agent logs on to the skillset or is
reassigned (while logged on) to the skillset and ends when the agent logs off or
is reassigned out of the skillset.
Type: int
Length: 4
VirtualCallsAbandoned
Description: The number of contacts abandoned while queuing in this skillset,
provided that:
VirtualCallsOffered
Description: The number of contacts offered in this skillset that are:
answered or accepted by an agent in this skillset and on this site.
or
abandoned and originated on this site and, if queued to multiple skillsets
simultaneously, this skillset is the first listed skillset in the script.
WaitTime
Description: The total time agents spend waiting for a contact after releasing a
voice call or closing a multimedia contact handled that was queuing in this
skillset.
Triggers: WaitTime begins when the agent goes into Idle state, for example, if:
an agent releases a voice call or closes a multimedia contact, and the
agent’s call presentation class is not configured for Break time or Variable
Wrap
an agent’s Break or Variable Wrap timer elapses after a contact is released
or closed
an agent presses the Not Ready key a second time after entering Not Ready
state
WaitTime ends when the agent leaves the Idle state. If the agent handles another
contact from the same skillset as the most recently handled contact, WaitTime
resumes against that skillset when the agent returns to the Idle state. If the agent
handles a contact from a different skillset than the most recently handled
contact, WaitTime begins against the new skillset when the agent returns to the
Idle state.
For more information, see “How is WaitTime pegged if the agent puts a DN call
on hold and uses alternate call answer to accept another contact?” on page 117.
Pegging: WaitTime pegs against the last skillset for which the agent handled a
contact during this login. If the agent has not yet handled a contact that was
queuing in a skillset, WaitTime is not pegged.
Type: int
Length: 4
In this section
Overview of event statistics 588
eNetCallByCallStat views 589
Event statistics are collected on a per-event basis rather than accumulated over a
period of time.
You can enable or disable the data collection option at any time while the system
is running.
eNetCallByCallStat views
For example, a contact may arrive at the source at 13:00:00 local time and be
answered at the destination 5 seconds later, at 14:00:05 local time. If Time Zone
Relative to GMT is configured correctly for both sites, the answer time pegs as
13:00:05 in the eNetCallByCallStat view, and the events appear in chronological
order, regardless of time zone.
Server times are not synchronized automatically. If server times are not
synchronized, events may appear in the wrong order. For example, if the source
site clock is several seconds behind the destination site clock, a contact may
arrive at the source site at 13:15:05 and be answered at the destination site at
13:14:57.
Changing the Time Zone Relative to GMT for a site (for example, for a change
to or from daylight saving time) affects pegging of contacts that are networked
out but not answered. All events at the source site peg with the old time, and all
events at the destination site peg with the new time.
If you change the call-by-call statistics collection option at the source site, the
change is effective only for calls arriving after the change is propagated through
the network. Propagation can take several minutes.
Restrictions
The amount of data generated for call-by-call statistics is very large, and the
time required to generate a report using call-by-call statistics is much longer
than the time required to generate a report using summarized statistics.
Field descriptions
The field descriptions for this view are described in this section.
Associated Data
Description: Associated data is information associated with a specific event,
such as:
the other extension, trunk ID, or outside phone number associated with a
call that is conferenced with another party, transferred to another party,
or put on hold while another call is placed
the DNIS number for an incoming call
Type: varchar
Length: 40
CallEvent
Description: A unique identifier for the type of event.
Type: int
Length: 4
CallEventName
Description: The type of event. For a complete list of events that can be
collected, refer to “Call Events” on page 355.
Type: varchar
Length: 80
CallID
Description: A number assigned by the Communication Server 1000/Meridian
1 PBX and Communication Server 2x00/DMS for every call. It is unique only
for the life of the call and may be reused later for new calls.
When the Call ID range is exhausted, new contacts are assigned previously used
Call IDs. On systems with very high traffic, different contacts may be assigned
the same Call ID within a single reporting interval.
Destination
Description: The location where a contact is directed during an event. The
destination could be identified by, for example, a dialed number, trunk ID, agent
ID, skillset ID, application ID, IVR queue ID or name, or site ID.
Type: varchar
Length: 40
EventData
Description: The information related to or generated by this event. The data
could be a PIN entered by the caller in response to the collect digits command;
an ANI, CLID, site ID, or activity code; or reasons for the event.
Type: varchar
Length: 40
FirstEventTimestamp
Description:
Type: datetime
Length: 8
NodeID
Description: (Communication Server 2x00/DMS switch only) A unique
identifier for the switch.
Type: varchar
Length: 40
SequenceNumber
Description:
Type: int
Length: 4
Site
Description: The configured name of this Contact Center Manager site.
Type: varchar
Length: 30
SiteID
Description: A unique number assigned by the system to identify this Contact
Center Manager site. The assigned SiteID remains unique over time even if a
configured site is deleted and another one is added with the same name. The
SiteID can be used in custom reports to identify statistics applicable to this site.
Source
Description: The location of this contact before this event occurred. The source
could be identified by, for example, a dialed number, trunk ID, agent ID, skillset
ID, application ID, IVR queue ID or name, or site ID.
SourceSiteID
Description: A unique number that identifies the switch on the network, as
received from the switch.
SQL does not support signed integers. Therefore, site IDs can appear negative in
the database views.
Type: int
Length: 4
TelsetLoginID
Description: The numeric ID the agent uses to log in to the phoneset or agent
desktop.
Type: varchar
Length: 16
Time
Description: The time (in 24-hour HH:MM format) when the data is pegged by
the system. If Time Zone Relative to GMT is configured correctly for the source
and destination sites, this time is in the time zone of the source site.
Type: char
Length: 5
Timestamp
Description: The date and time when the data is pegged by the system. The
time is in the time zone of the source site.
Type: datetime
Length: 4
Call events
These call events are the same as the Call events in the table for the
eCallByCallStat view, except that no DN call event information pegs to the
eNetCallByCallStat view. See “Call Events” on page 355.
In this chapter
Overview 596
Custom Contact Center Multimedia reports and searches 600
Section A: Database tables 601
Section B: Database views 745
Overview
You access data through database views. Database views are used to organize
the information in the database for your use. You can access the underlying
tables, but it is read-only access. This chapter provides definitions for all the
Contact Center Multimedia database tables, fields, and views available.
When creating data-warehouse applications, you use these database views. The
database views contain all the information for customized reporting and queries,
and are created on top of the database tables.
You can access the data in this database with any SQL- or OLE DB-compliant
application. You can use the data in many ways, including the following:
import it into a spreadsheet for manipulation
import it into your corporate database
generate customized reports to store and evaluate the data using Report
Creation Wizard, Crystal Reports, or another third-party reporting
application
For more information about creating reports for Contact Center Multimedia, see
the Contact Center Manager Supervisor’s Guide.
The following table shows the relationship between the Object Oriented
terminology and the SQL relational terminology.
Class Table
Property Field
Object Record
The Caché database can expose the data in either a class view or a SQL
relational view. This chapter describes the only the SQL relational view of the
database.
Within SQL and the relational environment, some of the tables contain fields
that are themselves tables. These are called embedded tables. This is seen within
the field definitions where the Type information lists another table (a table has
the prefix cls). These fields can be used in a number of ways.
The following examples use the Status field from the cls.Contacts table. The
Status field is actually a link to the cls.CodeMappings table.
Field
In the simplest form, the Status field contains the ID value of the related record.
SELECT STATUS FROM CLS.CONTACTS
Pointer
If you are using a third-party ODBC compliant client with plain SQL, you can
use the Status field as a pointer to the data in the cls.CodeMappings table. A
pointer is a value that contains the address of another value, such as in an index.
This is a less complex form of the preceding script example.
Note the arrow (->) symbol used to point to the related data. This is a Caché
SQL extension, but is valid to use through ODBC.
Field types
The following table describes the field types used in the database tables in this
chapter. For each type, it provides a range of valid values and a size.
Example
The cls.Addresses table contains the field FullAddress. This field contains all of
the address information concatenated together without any spaces. It is used
internally when an agent searches on the address of a customer because the
system is required to search on one field, FullAddress, rather than searching all
the individual fields for the string that the user typed in.
When you create custom Contact Center Multimedia reports, limitations exist
when searching on String field types and password fields.
Password fields
When you search on password fields, the expected results are not returned as the
data is encrypted in the database.
In this section
Actions 604
Addresses 612
Administrators 615
Answers 617
ArchiveNotes 619
Attachments 621
Audits 624
AutoResponses 627
AutoResponseAttachments 629
BarredOutBoundAddresses 631
CallBarrings 632
Campaigns 634
CampaignScripts 640
CodeMappings 642
Contacts 644
ContactTypes 654
CustomFields 656
Customers 660
Debugs 664
DispositionCodes 665
Durations 668
EmailAddresses 669
EmailAddressGroups 671
HolidayHours 672
Inboxes 674
InvalidXMLAudits 677
InvalidXMLChrs 679
InvalidXMLFields 680
KeyWordGroups 681
Licenses 682
Migrations 683
MigrationNotes 684
OnHoldURLs 685
OutOfHoursRules 687
PageChange 688
PagePushes 689
PagePushURLs 690
PhoneNumbers 692
Phrases 695
Preferences 697
Questions 699
RegularHours 702
Restores 704
RestoredAudits 707
RoutePoints 709
Rules 710
RuleAdmins 713
RuleKeywordGroups 715
Servers 717
Services 719
Sessions 721
Sites 722
SiteComponents 725
SiteParameters 726
Skillsets 728
SkillsetOnHoldURLs 732
Updates 733
Users 735
UserResets 738
WebCommsMessages 739
WebCommsSessions 741
Additional tables 743
Actions
The Actions table stores the conversation between the customer and the contact
center. Each cls.Actions record is linked to a cls.Contacts record through the
Contact field. The cls.Contacts record contains header type information for the
contact. The contact detail is stored in the cls.Actions records. One cls.Contacts
record can have many cls.Actions records.
Field descriptions
This sections provides descriptions for each of the cls.Actions fields.
Agent
Description: The Agent field links to the cls.Users record that contains details
of the current or last agent who is dealing with this action. This field is
applicable to both Outbound and e-mail.
Type: Integer
Attempt
Description: The Attempt field stores the number of attempts made to send this
cls.Actions record. This field is applicable to both Outbound and e-mail.
Type: Integer
CallBackMedia
Description: The CallBackMedia field is an embedded table
(cls.CodeMappings). It can be selected either as a field or as a pointer. As a
field, it returns the ID value of the cls.CodeMappings record related to this
cls.Actions record. As a pointer, it refers to the fields on the cls.CodeMappings
record.
For more information about querying data from fields that are embedded tables,
see “About the Caché database” on page 597. This field is applicable to both
Outbound and e-mail.
Type: Integer
CallBackStatus
Description: The CallBackStatus field is an embedded table
(cls.CodeMappings). It can be selected either as a field or as a pointer. As a
field, it returns the ID value of the cls.CodeMappings record related to this
cls.Actions record. As a pointer, it refers to the fields on the cls.CodeMappings
record.
For more information about querying data from fields that are embedded tables,
see “About the Caché database” on page 597. This field is applicable to both
Outbound and e-mail.
Type: Integer
CallBackTime
Description: The date and time that the agent should contact the customer. This
field is applicable to both Outbound and e-mail.
Type: TimeStamp
CallEndTime
Description: The end date and time of the contact. This field is applicable to
both Outbound and e-mail.
Type: TimeStamp
CallStartTime
Description: The start date and time of the contact. This field is applicable to
both Outbound and e-mail.
Type: TimeStamp
CharSet
Description: The CharSet field stores the character set for the cls.Actions
records. This field is applicable to both Outbound and e-mail.
Type: String
Length: 50
ClosedReasonCode
Description: The ClosedReasonCode field is an embedded table
(cls.CodeMappings). It can be selected either as a field or as a pointer. As a
field, it returns the ID value of the cls.CodeMappings record related to this
cls.Actions record. As a pointer, it refers to the fields on the cls.CodeMappings
record.
For more information about querying data from fields that are embedded tables,
see “About the Caché database” on page 597. This field is applicable to both
Outbound and e-mail.
Type: Integer
ClosedTime
Description: The date and time that the cls.Actions record is closed. This field
is applicable to both Outbound and e-mail.
Type: TimeStamp
Comment
Description: Any comments from this agent. This field is applicable to both
Outbound and e-mail.
Type: String
Length: 255
Contact
Description: This is an embedded table (cls.Contacts). It can be selected either
as a field or as a pointer. As a field, it returns the ID value of the cls.Contacts
record related to this cls.Actions record. As a pointer, it refers to the fields on the
cls.Contacts record.
As a field, it can be used in an SQL relational join to the cls.Contacts record. For
a list of fields, refer to “Contacts” on page 644.
For more information about querying data from fields that are embedded tables,
see “About the Caché database” on page 597. This field is applicable to both
Outbound and e-mail.
Type: Integer
ContactID
Description: Relational link to the cls.Contacts record that this action relates to.
This field is applicable to both Outbound and e-mail.
Type: Integer
CreationTime
Description: The date and time this cls.Actions record is created. For the first
action this is the same as the cls.Contacts.ArrivalTime. This field is applicable
to both Outbound and e-mail.
Type: TimeStamp
CustomFields
Description: This is an embedded table (cls.CustomFields). It can be selected
either as a field or as a pointer. As a field, it returns the ID value of the
cls.CustomFields record related to this cls.Actions record. As a pointer, it refers
to the fields on the cls.CustomFields record.
For more information about querying data from fields that are embedded tables,
see “About the Caché database” on page 597. This field is applicable to both
Outbound and e-mail.
Type: Integer
DialEndTime
Description: The dial end date and time of the contact. This field is applicable
to both Outbound and e-mail.
Type: TimeStamp
DialStartTime
Description: The dial start date and time of the contact. This field is applicable
to both Outbound and e-mail.
Type: TimeStamp
DispositionCode
Description: This is an embedded table (cls.DispositionCodes). It can be
selected either as a field or as a pointer. As a field, it returns the ID value of the
cls.DispositionCodes record related to this cls.Actions record. As a pointer, it
refers to the fields on the cls.DispositionCodes record.
For more information about querying data from fields that are embedded tables,
see “About the Caché database” on page 597. This field is applicable to
Outbound only.
Type: Integer
HistoryFlag
Description: The action history flag. This indicates whether or not each action
should contain details from previous actions. 1 = Yes. This field is applicable to
both Outbound and e-mail.
Type: Boolean
ID
Description: This is the primary key for the table. The value for this field is
automatically generated by the database when the record is created and cannot
be updated at any time. This field is applicable to both Outbound and e-mail.
Type: Integer
MailBCC
Description: The e-mail addresses that this action is blind copied to. This field
is applicable to both Outbound and e-mail.
Type: String
Length: 32767
MailCC
Description: The e-mail addresses that this action is copied to. This field is
applicable to both Outbound and e-mail.
Type: String
Length: 32767
MailFrom
Description: The e-mail address that appears as the From address to the
recipient of this action. This is usually the same as a cls.Mailbox table record.
This field is applicable to both Outbound and e-mail.
Type: String
Length: 255
MailTo
Description: The e-mail address that this action is sent to. This field is
applicable to both Outbound and e-mail.
Type: String
Length: 255
NumberUsed
Description: The telephone number used to contact the customer. This field is
applicable to both Outbound and e-mail.
Type: String
Length: 255
OpenTime
Description: The date and time this cls.Actions record is opened. This field is
applicable to both Outbound and e-mail.
Type: TimeStamp
Source
Description: This is an embedded table (cls.CodeMappings). It can be selected
either as a field or as a pointer. As a field, it returns the ID value of the
cls.CodeMappings record related to this cls.Actions record. As a pointer, it
refers to the fields on the cls.CodeMappings record.
For more information about querying data from fields that are embedded tables,
see “About the Caché database” on page 597. This field is applicable to both
Outbound and e-mail.
Type: Integer
Subject
Description: The subject for this action. This field is applicable to both
Outbound and e-mail.
Type: String
Length: 255
TemplateLocation
Description: Location of any templates used on this action. This field is
applicable to both Outbound and e-mail.
Type: String
Length: 255
Text
Description: The full text for this action. It may or may not contain text from
other actions, depending upon the history flag. This field is applicable to both
Outbound and e-mail.
Type: Stream
TextHTML
Description: The same as the text field, but in HTML. This field is applicable to
both Outbound and e-mail.
Type: Stream
TimeAllocated
Description: How long, in seconds, this action is worked upon. This is the
difference between the OpenTime and the ClosedTime expressed in seconds.
This field is applicable to both Outbound and e-mail.
Type: Integer
Type
Description: This is an embedded table (cls.ContactTypes). It can be selected
either as a field or as a pointer. As a field, it returns the ID value of the
cls.ContactTypes record related to this cls.Actions record. As a pointer, it refers
to the fields on the cls.ContactTypes record.
For more information about querying data from fields that are embedded tables,
see “About the Caché database” on page 597. This field is applicable to both
Outbound and e-mail.
Type: Integer
Indexes
The following table lists the indexes used by the cls.Actions table.
Unique
Index name Fields indexed Type 1 = Yes Description
Addresses
This table stores address details for customers. The address details are linked to
the relevant cls.Customers record through the customer field. Several
cls.Addresses records can be linked to the same cls.Customers record.
Field descriptions
The field descriptions for this table are described in this section.
Country
Description: The country information for this address. This field is applicable
to both Outbound and e-mail.
Type: String
Length: 255
Customer
Description: This is an embedded table (cls.Customers). It can be selected
either as a field or as a pointer. As a field, it returns the ID value of the
cls.Customers record related to this cls.Addresses record. As a pointer, it refers
to the fields on the cls.Customers record.
For more information about querying data from fields that are embedded tables,
see “About the Caché database” on page 597. This field is applicable to both
Outbound and e-mail. This field is applicable to both Outbound and e-mail.
Type: Integer
Default
Description: Flag that indicates this address is used as the default. 1 = Yes. This
field is applicable to both Outbound and e-mail.
Type: Boolean
FullAddress
Description: For internal use only. It contains all the address fields
concatenated together, which assists with searching. This field is applicable to
both Outbound and e-mail.
Type: String
Length: 1785
ID
Description: This is the primary key for the table. The value for this field is
automatically generated by the database when the record is created and cannot
be updated at any time. This field is applicable to both Outbound and e-mail.
Type: Integer
Imported
Description: Flag to indicate that this address should be used as the default for
the customer. 1 = Yes.
Type: Boolean
Line1
Description: First line of the address information. This field is applicable to
both Outbound and e-mail.
Type: String
Length: 255
Line2
Description: Second line of the address information. This field is applicable to
both Outbound and e-mail.
Type: String
Length: 255
Line3
Description: Third line of the address information. This field is applicable to
both Outbound and e-mail.
Type: String
Length: 255
Line4
Description: Fourth line of the address information. This field is applicable to
both Outbound and e-mail.
Type: String
Length: 255
Line5
Description: Fifth line of the address information. This field is applicable to
both Outbound and e-mail.
Type: String
Length: 255
ZipCode
Description: Zip code or postal code information for the address. This field is
applicable to both Outbound and e-mail.
Type: String
Length: 255
Indexes
The following table lists the indexes used by the cls.Addresses table.
Unique
Index name Fields indexed Type 1 = Yes Description
Administrators
This table stores details of the administrator user account used to access the
multimedia administration application.
Field descriptions
The field descriptions for this table are described in this section.
AdminRole
Description: Not used at present.
Type: String
Length: 20
DN
Description: The administrator’s phone number.
Type: String
Length: 32
EmailAddress
Description: The administrator’s e-mail address.
Type: String
Length: 255
FaxNumber
Description: The administrator’s FAX number, if available.
Type: String
Length: 32
FirstName
Description: The administrator’s first name.
Type: String
Length: 50
ID
Description: This is the primary key for the table. The value for this field is
automatically generated by the database when the record is created and cannot
be updated at any time.
Type: Integer
LogonID
Description: The administrator’s logon name.
Type: String
Length: 50
Password
Description: The password that should be used with the LogonID information.
Type: String
Length: 20
Status
Description: Indicates whether or not the administrator is logged on or not. 1=
logged on, 0 = logged off.
Type: Integer
Surname
Description: The administrators last name (surname).
Type: String
Length: 50
Indexes
The are no indexes used by the cls.Administrators table.
Answers
This table stores the list of answers relating to an Outbound contact record. They
are linked to the Contact record through the Contact field. There may be
multiple answer records with the same contact value.
Field descriptions
The field descriptions for this table are described in this section.
Answer
Description: The actual textual answer. This is usually taken from the list of
possible answers that relate to the question. This field is applicable to Outbound
only.
Type: String
Length: 255
Contact
Description: This is an embedded table (cls.Contacts). It can be selected either
as a field or as a pointer. As a field, it returns the ID value of the cls.Contacts
record related to this cls.Answers record. As a pointer, it refers to the fields on
the cls.Contacts record.
As a field, it can be used in an SQL relational join to the cls.Contacts record. For
a list of fields, refer to “Contacts” on page 644.
For more information about querying data from fields that are embedded tables,
see “About the Caché database” on page 597. This field is applicable to
Outbound only.
Type: Integer
DateCreated
Description: Date and time the answer record was created. This field is
applicable to Outbound only.
Type: TimeStamp
FreeText
Description: If FreeText is allowed for the question, the text is entered here.
This field is applicable to Outbound only.
Type: String
Length: 255
ID
Description: This is the primary key for the table. The value for this field is
automatically generated by the database when the record is created and cannot
be updated at any time. This field is applicable to Outbound only.
Type: Integer
QuestionID
Description: Relational link to the question that this answer relates to. This
field is applicable to Outbound only.
Type: Integer
Indexes
The following table lists the indexes used by the cls.Answers table.
Unique
Index name Fields indexed Type 1 = Yes Description
ArchiveNotes
This table is used internally by the archive functionality. For internal use only.
Field descriptions
The field descriptions for this table are described in this section.
ArchiveComplete
Description: Internal use only.
Type: Boolean
ArchivedAudits
Description: Internal use only.
Type: Integer
ArchivedContacts
Description: Internal use only.
Type: Integer
AuditRestoreComplete
Description: Internal use only.
Type: Boolean
ContactRestoreComplete
Description: Internal use only.
Type: Boolean
DateTimeStamp
Description: Internal use only.
Type: TimeStamp
NoteText
Description: Internal use only.
Type: String
Length: 255
RestoredAudits
Description: Internal use only.
Type: Integer
RestoredContacts
Description: Internal use only.
Type: Integer
TotalContacts
Description: Internal use only.
Type: Integer
Indexes
The are no indexes used by the cls.ArchiveNotes table.
Attachments
This table stores details relating to any file attachments that are either received
from the customer or sent out to the customer. The direction field holds
information relating to whether the file was received or sent. They are linked to
action records as it is possible that the customer could send an attachment
(action 1) and the contact center agent could reply with another attachment
(action 2).
Field descriptions
The field descriptions for this table are described in this section.
Action
Description: This is an embedded table (cls.Actions). It can be selected either
as a field or as a pointer. As a field, it returns the ID value of the cls.Actions
record related to this cls.Attachements record. As a pointer, it refers to the fields
on the cls.Actions record.
As a field, it can be used in an SQL relational join to the cls.Actions record. For
a list of fields, refer to “Actions” on page 604.
For more information about querying data from fields that are embedded tables,
see “About the Caché database” on page 597. This field applies to both
Outbound and e-mail.
Type: cls.Actions
Direction
Description: This is an embedded table (cls.CodeMappings). It can be selected
either as a field or as a pointer. As a field, it returns the ID value of the
cls.CodeMappings record related to this cls.Attachements record. As a pointer, it
refers to the fields on the cls.CodeMappings record.
For more information about querying data from fields that are embedded tables,
see “About the Caché database” on page 597. This field applies to both
Outbound and e-mail.
Type: cls.CodeMappings
DisplayFileName
Description: The display name for the attached file. This is usually the name of
the file without any folder information. This field applies to both Outbound and
e-mail.
Type: String
Length: 255
FileContents
Description: Internal use only. If a redundant server is configured, this field is
used to copy the contents of the file from the Primary server to the redundant
server. After the contents of the file is copied across, this field is cleared again.
So under normal circumstances this field is blank. This field applies to both
Outbound and e-mail.
Type: Stream
ID
Description: This is the primary key for the table. The value for this field is
automatically generated by the database when the record is created and cannot
be updated at any time. This field applies to both Outbound and e-mail.
Type: Integer
InternalFileName
Description: The full path and name for the attached file. This field applies to
both Outbound and e-mail.
Type: String
Length: 255
Indexes
The following table lists the indexes used by the cls.Attachments table.
Unique
Index name Fields indexed Type 1 = Yes Description
Audits
This table stores audit details for customers, contacts, actions, and campaigns.
The details include when the information changed, what changed, and who
changed it. Not all the fields populate on each record, only the relevant fields.
Field descriptions
The field descriptions for this table are described in this section.
ActionId
Description: Relational link to the cls.Actions record that this cls.Audits record
relates to. This field applies to both Outbound and e-mail.
Type: Integer
AgentId
Description: Relational link to the cls.Users record who updated the customer,
contact, action, or campaign. This field applies to both Outbound and e-mail.
Type: Integer
CampaignId
Description: Relational link to the cls.Campaigns record that this cls.Audits
record relates to. This field applies to both Outbound and e-mail.
Type: Integer
CampaignUserName
Description: Campaign user name that created the cls.Audits record. This field
applies to both Outbound and e-mail.
Type: String
ContactId
Description: Relational link to the cls.Contacts record that this cls.Audits
relates to. This field applies to both Outbound and e-mail.
Type: Integer
CustomerId
Description: Relational link to the cls.Customers record that this cls.Audits
record relates to. This field applies to both Outbound and e-mail.
Type: Integer
DateTimeStamp
Description: The date and time that this cls.Audits record is created. This field
applies to both Outbound and e-mail.
Type: TimeStamp
ID
Description: This is the primary key for the table. The value for this field is
automatically generated by the database when the record is created and cannot
be updated at any time. This field applies to both Outbound and e-mail.
Type: Integer
NewValue
Description: This is an embedded table (cls.CodeMappings). It can be selected
either as a field or as a pointer. As a field, it returns the ID value of the
cls.CodeMappings record related to this cls.Audits record. As a pointer, it refers
to the fields on the cls.CodeMappings record.
For more information about querying data from fields that are embedded tables,
see “About the Caché database” on page 597. This field applies to both
Outbound and e-mail.
Type: cls.CodeMappings
OldValue
Description: This is an embedded table (cls.CodeMappings). It can be selected
either as a field or as a pointer. As a field, it returns the ID value of the
cls.CodeMappings record related to this cls.Audits record. As a pointer, it refers
to the fields on the cls.CodeMappings record.
For more information about querying data from fields that are embedded tables,
see “About the Caché database” on page 597. This field applies to both
Outbound and e-mail.
Type: cls.CodeMappings
Type
Description: This is an embedded table (cls.CodeMappings). It can be selected
either as a field or as a pointer. As a field, it returns the ID value of the
cls.CodeMappings record related to this cls.Audits record. As a pointer, it refers
to the fields on the cls.CodeMappings record.
For more information about querying data from fields that are embedded tables,
see “About the Caché database” on page 597. This field applies to both
Outbound and e-mail.
Type: cls.CodeMappings
Indexes
The are no indexes used by the cls.Audits table.
AutoResponses
This table stores predefined AutoResponses that can be sent to the customer.
Field descriptions
The field descriptions for this table are described in this section.
Attachments
Description: This is an embedded table (cls.AutoResponseAttachments). It can
be selected either as a field or as a pointer. As a field, it returns the ID value of
the cls.AutoResponseAttachments record related to this cls.AutoResponses
record. As a pointer, it refers to the fields on the cls.AutoResponseAttachments
record.
For more information about querying data from fields that are embedded tables,
see “About the Caché database” on page 597. This field applies to e-mail only.
Type: cls.AutoResponseAttachments
Body
Description: The acknowledgement text itself. This field applies to e-mail only.
Type: String
Length: 4095
ID
Description: This is the primary key for the table. The value for this field is
automatically generated by the database when the record is created and cannot
be updated at any time. This field applies to e-mail only.
Type: Integer
Name
Description: The name displayed to reference this acknowledgement. This field
applies to e-mail only.
Type: String
Length: 255
Subject
Description: The subject displayed for this acknowledgement. This field
applies to e-mail only.
Type: String
Length: 255
Indexes
The are no indexes used by the cls.AutoResponses table.
AutoResponseAttachments
This table stores information relating to any file attachments that are sent out
with an AutoResponse record.
Field descriptions
The field descriptions for this table are described in this section.
AutoResponse
Description: This is an embedded table (cls.AutoResponses). It can be selected
either as a field or as a pointer. As a field, it returns the ID value of the
cls.AutoResponses record related to this cls.AutoResponseAttachments record.
As a pointer, it refers to the fields on the cls.AutoResponses record.
For more information about querying data from fields that are embedded tables,
see “About the Caché database” on page 597. This field applies to e-mail only.
Type: cls.AutoResponses
DisplayFileName
Description: The name as it appears to an end user. Usually it is the file name.
This field applies to e-mail only.
Type: String
Length: 255
FileContents
Description: Temporary location for the actual contents of the file. This is used
to ensure that the file is correctly copied over to the shadow server. When at the
shadow server, the file is copied back out to disk and this field is blanked. This
field applies to e-mail only.
ID
Description: This is the primary key for the table. The value for this field is
automatically generated by the database when the record is created and cannot
be updated at any time. This field applies to e-mail only.
Type: Integer
InternalFileName
Description: The full folder and file name for the attachment. This is needed by
the system to locate where to get the attachment. This field applies to e-mail
only.
Type: String
Length: 255
Indexes
The following table lists the indexes used by the cls.AutoResponseAttachement
table.
Unique
Index name Fields indexed Type 1 = Yes Description
BarredOutBoundAddresses
This table stores an e-mail addresses that should not be used for outbound
campaigns.
Field descriptions
The field descriptions for this table are described in this section.
EmailAddress
Description: A link to an address field. This field applies to both Outbound and
e-mail.
Type: String
Length: 255
ID
Description: This is the primary key for the table. The value for this field is
automatically generated by the database when the record is created and cannot
be updated at any time. This field applies to both Outbound and e-mail.
Type: Integer
Indexes
The are no indexes used by the cls.BarredOutBoundAddresses table.
CallBarrings
Field descriptions
The field descriptions for this table are described in this section.
Agent
Description: The agent.
Type: Users
AgentComment
Description: Any comments that the agent has.
Type: String
Length: 255
Customer
Description: This is an embedded table (cls.Customers). It can be selected
either as a field or as a pointer. As a field, it returns the ID value of the
cls.Customers record related to this cls.CallBarrings record. As a pointer, it
refers to the fields on the cls.Customers record.
For more information about querying data from fields that are embedded tables,
see “About the Caché database” on page 597.
Type: cls.Customers
ExpiryDate
Description: The date and time that the details within this record expire.
Type: TimeStamp
ID
Description: This is the primary key for the table. The value for this field is
automatically generated by the database when the record is created and cannot
be updated at any time.
Type: Integer
Indexes
The are no indexes used by the cls.CallBarrings table.
Campaigns
Field descriptions
The field descriptions for this table are described in this section.
AutoDialTimeOut
Description: How long to wait in seconds before timing out when trying to dial
a phone number. This field applies to Outbound only.
Type: Integer
CampaignScript
Description: This is an embedded table (cls.CampaignScripts). It can be
selected either as a field or as a pointer. As a field, it returns the ID value of the
cls.CampaignScripts record related to this cls.Campaigns record. As a pointer, it
refers to the fields on the cls.CampaignScripts record.
For more information about querying data from fields that are embedded tables,
see “About the Caché database” on page 597. This field applies to Outbound
only.
Type: cls.CampaignScripts
CustomFields
Description: This is an embedded table (cls.CustomFields). It can be selected
either as a field or as a pointer. As a field, it returns the ID value of the
cls.CustomFields record related to this cls.Campaigns record. As a pointer, it
refers to the fields on the cls.CustomFields record.
For more information about querying data from fields that are embedded tables,
see “About the Caché database” on page 597. This field applies to Outbound
only.
Type: cls.CustomFields
DailyEndTime
Description: The end time to use in conjunction with the DailyStartTime. This
field applies to Outbound only.
Type: TimeStamp
DailyStartTime
Description: The time during the day that this campaign becomes active. If this
is populated, then the campaign does not become active until this time during
the day. For example, this is used for campaigns that can run during office hours
only. This field applies to Outbound only.
Type: TimeStamp
DateCreated
Description: The date and time that this campaign was created on the system.
This field applies to Outbound only.
Length: TimeStamp
Description
Description: The textual description for this campaign. This field applies to
Outbound only.
Type: String
Length: 32768
DialingPrefix
Description: The dialing prefix that should be used for this campaign. This is
used if there is a specific prefix that agents should use for calling customers on
this campaign. This field applies to Outbound only.
Type: String
Length: 10
DispositionCodes
Description: This is an embedded table (cls.DispositionCodes). It can be
selected either as a field or as a pointer. As a field, it returns the ID value of the
cls.DispositionCodes record related to this cls.Campaigns record. As a pointer, it
refers to the fields on the cls.DispositionCodes record.
For more information about querying data from fields that are embedded tables,
see “About the Caché database” on page 597. This field applies to Outbound
only.
Type: cls.DispositionCodes
EndDateTime
Description: The date and time that this campaign expires. This is used by the
Contact Center Multimedia Outbound Scheduler Service to determine when to
change the status values for Contacts records linked to this campaign. This field
applies to Outbound only.
Type: TimeStamp
ID
Description: This is the primary key for the table. The value for this field is
automatically generated by the database when the record is created and cannot
be updated at any time. This field applies to Outbound only.
Type: Integer
LastLoadedDate
Description: The date and time that contacts were last loaded into the system
for this campaign. Internal use only. This field applies to Outbound only.
Type: TimeStamp
LoadContactsPerInterval
Description: Number of contacts to load each time the LoadInterval elapses.
This field applies to Outbound only.
Type: Integer
LoadInterval
Description: Amount of time to wait before loading the next set of contacts into
the system. This field applies to Outbound only.
Type: Integer
Locked
Description: Flag to indicate if the campaign is locked by another process.
Internal use only. This field applies to Outbound only.
Type: Boolean
LockedBy
Description: Used with Locked field to indicate who has the lock out. Internal
use only. This field applies to Outbound only.
Type: String
Length: 50
LockedDateTime
Description: Used with Locked field to indicate the date and time that the lock
was taken out. Internal use only. This field applies to Outbound only.
Type: TimeStamp
MinimumRingTime
Description: How long, in seconds, that the phone is allowed to ring in this
campaign. This field applies to Outbound only.
Type: Integer
Name
Description: Title for this campaign. This field applies to Outbound only.
Type: String
Length: 255
NumberOfContacts
Description: The number of contacts in this campaign. This field applies to
Outbound only.
Type: Integer
NumberOfContactsProcessed
Description: The number of contacts processed for this campaign. This number
updates when the status on a contact is changed. This field applies to Outbound
only.
Type: Integer
Owner
Description: The owner of this campaign. This is the name of the person who
created this campaign. This person is not necessarily an agent or supervisor who
is registered on the system. That is why the information is stored here as a
simple string. This field applies to Outbound only.
Type: String
Length: 255
PreviousStatus
Description: This is an embedded table (cls.CodeMappings). It can be selected
either as a field or as a pointer. As a field, it returns the ID value of the
cls.CodeMappings record related to this cls.Campaigns record. As a pointer, it
refers to the fields on the cls.CodeMappings record.
For more information about querying data from fields that are embedded tables,
see “About the Caché database” on page 597. This field applies to Outbound
only.
Type: cls.CodeMappings
Priority
Description: The priority of this campaign. This field applies to Outbound only.
Type: Integer
Skillset
Description: This is an embedded table (cls.Skillsets). It can be selected either
as a field or as a pointer. As a field, it returns the ID value of the cls.Skillsets
record related to this cls.Campaigns record. As a pointer, it refers to the fields on
the cls.Skillsets record.
As a field, it can be used in an SQL relational join to the cls.Skillsets record. For
a list of fields, refer to “Skillsets” on page 728.
For more information about querying data from fields that are embedded tables,
see “About the Caché database” on page 597. This field applies to Outbound
only.
Type: cls.Skillsets
StartDateTime
Description: The date and time this campaign becomes active. This is used by
the Contact Center Multimedia Outbound Scheduler Service to determine when
to change the status values for Contacts records linked to this campaign. This
field applies to Outbound only.
Type: TimeStamp
StartOfRun
Description: Internal use only. This field applies to Outbound only.
Type: Boolean
Status
Description: This is an embedded table (cls.CodeMappings). It can be selected
either as a field or as a pointer. As a field, it returns the ID value of the
cls.CodeMappings record related to this cls.Campaigns record. As a pointer, it
refers to the fields on the cls.CodeMappings record.
For more information about querying data from fields that are embedded tables,
see “About the Caché database” on page 597. This field applies to Outbound
only.
Type: cls.CodeMappings
Indexes
The are no indexes used by the cls.Campaigns table.
CampaignScripts
This table stores campaign scripts that are used by cls.Campaigns records to
prompt agents with questions that they ask the customer. The actual questions
are stored in the cls.Questions table.
Field descriptions
The field descriptions for this table are described in this section.
Conclusion
Description: Textual conclusion for the cls.CampaignScripts record. This field
applies to Outbound only.
Type: String
Length: 1024
DateCreated
Description: The date and time this cls.CampaignScripts record is created. This
field applies to Outbound only.
Type: TimeStamp
ID
Description: This is the primary key for the table. The value for this field is
automatically generated by the database when the record is created and cannot
be updated at any time. This field applies to Outbound only.
Type: Integer
Introduction
Description: Textual introduction for the cls.CampaignScripts record. This
field applies to Outbound only.
Type: String
Length: 1024
Name
Description: Textual description for the cls.CampaignScripts record. This field
applies to Outbound only.
Type: String
Length: 255
Questions
Description: This is an embedded table (cls.Questions). It can be selected either
as a field or as a pointer. As a field, it returns the ID value of the cls.Questions
record related to this cls.CampaignScripts record. As a pointer, it refers to the
fields on the cls.Questions record.
For more information about querying data from fields that are embedded tables,
see “About the Caché database” on page 597. This field applies to Outbound
only.
Type: cls.Questions
Indexes
The are no indexes used by the cls.CampaignScripts table.
CodeMappings
This is a reference table that contains all the text values for the various integer
codes that are used in other tables.
Field descriptions
The field descriptions for this table are described in this section.
FieldName
Description: Contains what type of code is this. This is usually the table and
field name concatenated together. For example, for Status values from the
Contact table the FieldName is ContactStatus. This field applies to both
Outbound and e-mail.
Type: String
Length: 50
ID
Description: This is the primary key for the table. The value for this field is
automatically generated by the database when the record is created and cannot
be updated at any time. This field applies to both Outbound and e-mail.
Type: Integer
Icon
Description: Currently not used, but may be used in the future to store icon
details representing the code. This field applies to both Outbound and e-mail.
Type: String
Length: 50
NumericValue
Description: Numeric value for the code. For example, closed contacts have a
numeric value of 3. This field applies to both Outbound and e-mail.
Type: Integer
TextValue
Description: Text description of the code, such as Closed. This field applies to
both Outbound and e-mail.
Type: String
Length: 50
Indexes
The are no indexes used by the cls.CodeMappings table.
Contacts
This table stores customer contact information. This is the header type
information for the contact. The details of the contact are stored in the
cls.Actions records. Each time the customer contacts the contact center, a new
cls.Contacts record is created. Each cls.Contacts record is linked to a
cls.Customers record through the Customer field. Multiple cls.Contacts records
can be linked to the same cls.Customers record.
Field descriptions
The field descriptions for this table are described in this section.
AcquiredTime
Description: The first date and time that the contact is acquired by an agent.
When this is set, it is not updated again. This shows the delay between the
ArrivalTime of the contact and the time that the contact was acted upon. This
field applies to both Outbound and e-mail.
Type: TimeStamp
Agent
Description: The agent field contains an embedded table (cls.Users). It can be
selected either as a field or as a pointer. As a field, it returns the ID value of the
cls.Answers record related to this cls.Users record. As a pointer, it refers to the
fields on the cls.Users record.
As a field, it can be used in an SQL relational join to the cls.Users record. For a
list of fields, refer to “Users” on page 735.
For more information about querying data from fields that are embedded tables,
see “About the Caché database” on page 597. This field applies to both
Outbound and e-mail.
Type: cls.Users
Answers
Description: This is an embedded table (cls.Answers). It can be selected either
as a field or as a pointer. As a field, it returns the ID value of the cls.Answers
record related to this cls.Contacts record. As a pointer, it refers to the fields on
the cls.Answers record.
As a field, it can be used in an SQL relational join to the cls.Answers record. For
a list of fields, refer to “Answers” on page 617.
For more information about querying data from fields that are embedded tables,
see “About the Caché database” on page 597. This field applies to both
Outbound and e-mail.
Type: cls.Answers
ArrivalTime
Description: The date and time that this cls.Contacts record is created on the
system. This field applies to both Outbound and e-mail.
Type: TimeStamp
AutoResponse
Description: Link to the cls.Acknowledgements record that contains the details
of the acknowledgement sent to the customer for this contact. This field applies
to both Outbound and e-mail.
Type: cls.AutoResponses
CMFStatus
Description: This is an embedded table (cls.CodeMappings). It can be selected
either as a field or as a pointer. As a field, it returns the ID value of the
cls.CodeMappings record related to this cls.Contacts record. As a pointer, it
refers to the fields on the cls.CodeMappings record.
For more information about querying data from fields that are embedded tables,
see “About the Caché database” on page 597. This field applies to both
Outbound and e-mail.
Type: cls.CodeMappings
CallID
Description: The contact call ID. This field applies to both Outbound and
e-mail.
Type: Integer
Campaign
Description: This is an embedded table (cls.Campaigns). It can be selected
either as a field or as a pointer. As a field, it returns the ID value of the
cls.Campaigns record related to this cls.Contacts record. As a pointer, it refers to
the fields on the cls.Campaigns record.
For more information about querying data from fields that are embedded tables,
see “About the Caché database” on page 597. This field applies to Outbound
only.
Type: cls.Campaigns
CampaignRetryCount
Description: Number of times this outbound campaign contact is retried. This
field applies to Outbound only.
Type: Integer
CharSet
Description: The contact character set. This field applies to both Outbound and
e-mail.
Type: String
Length: 50
ClickStreamText
Description: The URLs the customer visited prior to submitting this contact.
This field applies to both Outbound and e-mail.
Type: String
Length: 32767
ClosedReasonCode
Description: This is an embedded table (cls.CodeMappings). It can be selected
either as a field or as a pointer. As a field, it returns the ID value of the
cls.CodeMappings record related to this cls.Contacts record. As a pointer, it
refers to the fields on the cls.CodeMappings record.
For more information about querying data from fields that are embedded tables,
see “About the Caché database” on page 597. This field applies to both
Outbound and e-mail.
Type: cls.CodeMappings
ClosedTime
Description: The date and time the contact was last closed. This field applies to
both Outbound and e-mail.
Type: TimeStamp
CustomFields
Description: This is an embedded table (cls.CustomFields). It can be selected
either as a field or as a pointer. As a field, it returns the ID value of the
cls.CustomFields record related to this cls.Campaigns record. As a pointer, it
refers to the fields on the cls.CustomFields record.
For more information about querying data from fields that are embedded tables,
see “About the Caché database” on page 597. This field applies to both
Outbound and e-mail.
Type: cls.CustomFields
Customer
Description: This is an embedded table (cls.Customers). It can be selected
either as a field or as a pointer. As a field, it returns the ID value of the
cls.Customers record related to this cls.Contacts record. As a pointer, it refers to
the fields on the cls.Customers record.
For more information about querying data from fields that are embedded tables,
see “About the Caché database” on page 597. This field applies to both
Outbound and e-mail.
Type: cls.Customers
CustomerID
Description: Relational link to the cls.Customers record that owns this contact.
This field applies to both Outbound and e-mail.
Type: Integer
DispositionCode
Description: This is an embedded table (cls.DispositionCodes). It can be
selected either as a field or as a pointer. As a field, it returns the ID value of the
cls.DispositionCodes record related to this cls.Contacts record. As a pointer, it
refers to the fields on the cls.DispositionCodes record.
For more information about querying data from fields that are embedded tables,
see “About the Caché database” on page 597. This field applies to Outbound
only.
Type: cls.DispositionCodes
ID
Description: This is the primary key for the table. The value for this field is
automatically generated by the database when the record is created and cannot
be updated at any time. This field applies to both Outbound and e-mail.
Type: Integer
MailCC
Description: The e-mail addresses this contact is copied to, in addition to being
sent to the contact center. This field applies to both Outbound and e-mail.
Type: String
Length: 255
MailFrom
Description: The e-mail address this contact is received from. This field applies
to both Outbound and e-mail.
Type: String
Length: 255
MailTo
Description: The e-mail address that this contact is sent to. This should match
up with the cls.Mailbox table record. This field applies to both Outbound and
e-mail.
Type: String
Length: 255
NNCCApplicationId
Description: The contact center application ID. This field applies to both
Outbound and e-mail.
Type: Integer
OpenDuration
Description: The length of time, in seconds, the contact is open. This value is
updated each time the contact is closed. If there is already a value present in this
field, it is added to so that it contains the total time in seconds that this contact is
open. This field applies to both Outbound and e-mail.
Type: Integer
OpenTime
Description: The date and time the contact is opened. This is not necessarily the
first time that the contact is opened. If the contact is opened again, then this
value is reset. This field applies to both Outbound and e-mail.
Type: TimeStamp
OriginalSubject
Description: The original contact subject text. This field applies to both
Outbound and e-mail.
Type: String
Length: 255
OutBoundOriginator
Description: The Outbound originator’s e-mail address. This field applies to
both Outbound and e-mail.
Type: String
Length: 255
PreferredCallBackMedia
Description: This is an embedded table (cls.ContactTypes). It can be selected
either as a field or as a pointer. As a field, it returns the ID value of the
cls.ContactTypes record related to this cls.Contacts record. As a pointer, it refers
to the fields on the cls.ContactTypes record.
For more information about querying data from fields that are embedded tables,
see “About the Caché database” on page 597. This field applies to both
Outbound and e-mail.
Type: cls.ContactTypes
Priority
Description: The contact’s priority.
Type: Integer
Rule
Description: This is an embedded table (cls.Rules). It can be selected either as a
field or as a pointer. As a field, it returns the ID value of the cls.Rules record
related to this cls.Contacts record. As a pointer, it refers to the fields on the
cls.Rules record.
As a field, it can be used in an SQL relational join to the cls.Rules record. For a
list of fields, refer to “Rules” on page 710.
For more information about querying data from fields that are embedded tables,
see “About the Caché database” on page 597. This field applies to both
Outbound and e-mail.
Type: cls.Rules
Skillset
Description: This is an embedded table (cls.Skillsets). It can be selected either
as a field or as a pointer. As a field, it returns the ID value of the cls.Skillsets
record related to this cls.Contacts record. As a pointer, it refers to the fields on
the cls.Skillsets record.
As a field, it can be used in an SQL relational join to the cls.Skillsets record. For
a list of fields, refer to “Skillsets” on page 728.
For more information about querying data from fields that are embedded tables,
see “About the Caché database” on page 597. This field applies to both
Outbound and e-mail.
Type: cls.Skillsets
Source
Description: This is an embedded table (cls.CodeMappings). It can be selected
either as a field or as a pointer. As a field, it returns the ID value of the
cls.CodeMappings record related to this cls.Contacts record. As a pointer, it
refers to the fields on the cls.CodeMappings record.
For more information about querying data from fields that are embedded tables,
see “About the Caché database” on page 597. This field applies to both
Outbound and e-mail.
Type: cls.CodeMappings
Status
Description: This is an embedded table (cls.CodeMappings). It can be selected
either as a field or as a pointer. As a field, it returns the ID value of the
cls.CodeMappings record related to this cls.Contacts record. As a pointer, it
refers to the fields on the cls.CodeMappings record.
For more information about querying data from fields that are embedded tables,
see “About the Caché database” on page 597. This field applies to both
Outbound and e-mail.
Type: cls.CodeMappings
SubStatus
Description: This is an embedded table (cls.CodeMappings). It can be selected
either as a field or as a pointer. As a field, it returns the ID value of the
cls.CodeMappings record related to this cls.Contacts record. As a pointer, it
refers to the fields on the cls.CodeMappings record.
For more information about querying data from fields that are embedded tables,
see “About the Caché database” on page 597. This field applies to both
Outbound and e-mail.
Type: cls.CodeMappings
TimeZone
Description: The contact’s time zone. This field applies to both Outbound and
e-mail.
Type: Integer
Type
Description: This is an embedded table (cls.ContactTypes). It can be selected
either as a field or as a pointer. As a field, it returns the ID value of the
cls.ContactTypes record related to this cls.Contacts record. As a pointer, it refers
to the fields on the cls.ContactTypes record.
For more information about querying data from fields that are embedded tables,
see “About the Caché database” on page 597. This field applies to both
Outbound and e-mail.
Type: cls.ContactTypes
Indexes
The following table lists the indexes used by the cls.Contacts table.
Unique
Index name Fields indexed Type 1 = Yes Description
ContactTypes
This table is populated with additional entries from Contact Center Manager
Server. If they are subsequently deleted from Contact Center Manager Server,
the MarkAsDeleted flag on this record is set. This is because it is likely there are
contact records that link to cls.ContactType records, which means the
information cannot be deleted.
Field descriptions
The field descriptions for this table are described in this section.
DefaultSkillset
Description: This is an embedded table (cls.Skillsets). It can be selected either
as a field or as a pointer. As a field, it returns the ID value of the cls.Skillsets
record related to this cls.ContactTypes record. As a pointer, it refers to the fields
on the cls.Skillsets record.
As a field, it can be used in an SQL relational join to the cls.Skillsets record. For
a list of fields, refer to “Skillsets” on page 728.
For more information about querying data from fields that are embedded tables,
see “About the Caché database” on page 597. This field applies to both
Outbound and e-mail.
Type: cls.Skillsets
DeletionTimeStamp
Description: The date and time this record is marked as deleted. This field
applies to both Outbound and e-mail.
Type: TimeStamp
ID
Description: This is the primary key for the table. The value for this field is
automatically generated by the database when the record is created and cannot
be updated at any time. This field applies to both Outbound and e-mail.
Type: Integer
MarkAsDeleted
Description: Flag to indicate whether this media type is deleted. This flag is
necessary because the actual details arrive from the main contact center database
and the historic information must be kept here as a Contact may still have this
MediaType. 1 = Yes. This field applies to both Outbound and e-mail.
Type: Boolean
NumericValue
Description: The numeric value for this type. This it populated by OAM or set
to 0 for types that are relevant only within the multimedia environment. This
field applies to both Outbound and e-mail.
Type: Integer
Parent
Description: Link to the cls.ContactTypes record that is the parent record for
this contact type. This is a circular reference back to this table. It is primarily
used to assist in sending the correct type to Contact Center Manager Server and
to assist in grouping for reporting purposes.
If this is a type from Contact Center Manager Server, then the parent field is a
circular reference to the same record, for example, the e-mail entry has a parent
of e-mail as well. This field applies to both Outbound and e-mail.
Type: cls.ContactTypes
TextValue
Description: The text value of the type. This field applies to both Outbound and
e-mail.
Type: String
Length: 50
Indexes
The are no indexes used by the cls.ContactTypes table.
CustomFields
This table is used by other tables that need to define custom fields.
Implementing it this way allows other tables to have as many custom fields as
needed.
Field descriptions
The field descriptions for this table are described in this section.
Action
Description: This is an embedded table (cls.Actions). It can be selected either
as a field or as a pointer. As a field, it returns the ID value of the cls.Actions
record related to this cls.CustomFields record. As a pointer, it refers to the fields
on the cls.Actions record.
As a field, it can be used in an SQL relational join to the cls.Actions record. For
a list of fields, refer to “Actions” on page 604.
For more information about querying data from fields that are embedded tables,
see “About the Caché database” on page 597. This field applies to both
Outbound and e-mail.
Type: cls.Actions
Campaign
Description: This is an embedded table (cls.Campaigns). It can be selected
either as a field or as a pointer. As a field, it returns the ID value of the
cls.Campaigns record related to this cls.CustomFields record. As a pointer, it
refers to the fields on the cls.Campaigns record.
For more information about querying data from fields that are embedded tables,
see “About the Caché database” on page 597. This field applies to both
Outbound and e-mail.
Type: cls.Campaigns
Contact
Description: This is an embedded table (cls.Contacts). It can be selected either
as a field or as a pointer. As a field, it returns the ID value of the cls.Contacts
record related to this cls.CustomFields record. As a pointer, it refers to the fields
on the cls.Contacts record.
As a field, it can be used in an SQL relational join to the cls.Contacts record. For
a list of fields, refer to “Contacts” on page 644.
For more information about querying data from fields that are embedded tables,
see “About the Caché database” on page 597. This field applies to both
Outbound and e-mail.
Type: cls.Contacts
Customer
Description: This is an embedded table (cls.Customers). It can be selected
either as a field or as a pointer. As a field, it returns the ID value of the
cls.Customers record related to this cls.CustomFields record. As a pointer, it
refers to the fields on the cls.Customers record.
For more information about querying data from fields that are embedded tables,
see “About the Caché database” on page 597. This field applies to both
Outbound and e-mail.
Type: cls.Customers
ID
Description: This is the primary key for the table. The value for this field is
automatically generated by the database when the record is created and cannot
be updated at any time. This field applies to both Outbound and e-mail.
Type: Integer
IsTextVisible
Description: Should this field be displayed to the agent. Default is true. 1 =
True. This field applies to both Outbound and e-mail.
Type: Boolean
Name
Description: This describes the type of information in the value field. This field
applies to both Outbound and e-mail.
Type: String
Length: 50
Site
Description: This is an embedded table (cls.Sites). It can be selected either as a
field or as a pointer. As a field, it returns the ID value of the cls.Sites record
related to this cls.CustomFields record. As a pointer, it refers to the fields on the
cls.Rules record.
As a field, it can be used in an SQL relational join to the cls.Sites record. For a
list of fields, refer to “Sites” on page 722.
For more information about querying data from fields that are embedded tables,
see “About the Caché database” on page 597. This field applies to both
Outbound and e-mail.
Type: cls.Sites
Text
Description: The actual value for this instance. This field applies to both
Outbound and e-mail.
Type: String
Length: 255
Indexes
The following table lists the indexes used by the cls.CustomFields table.
Unique
Index name Fields indexed Type 1 = Yes Description
Unique
Index name Fields indexed Type 1 = Yes Description
Customers
Field descriptions
The field descriptions for this table are described in this section.
Addresses
Description: This is an embedded table (cls.Addresses). It can be selected either
as a field or as a pointer. As a field, it returns the ID value of the cls.Addresses
record related to this cls.Customers record. As a pointer, it refers to the fields on
the cls.Addresses record.
For more information about querying data from fields that are embedded tables,
see “About the Caché database” on page 597. This field applies to both
Outbound and e-mail.
Type: cls.Addresses
CustomFields
Description: This is an embedded table (cls.CustomFields). It can be selected
either as a field or as a pointer. As a field, it returns the ID value of the
cls.CustomFields record related to this cls.Customers record. As a pointer, it
refers to the fields on the cls.CustomFields record.
For more information about querying data from fields that are embedded tables,
see “About the Caché database” on page 597. This field applies to both
Outbound and e-mail.
Type: cls.CustomFields
EmailAddresses
Description: This is an embedded table (cls.EmailAddresses). It can be selected
either as a field or as a pointer. As a field, it returns the ID value of the
cls.EmailAddresses record related to this cls.Customers record. As a pointer, it
refers to the fields on the cls.EmailAddresses record.
For more information about querying data from fields that are embedded tables,
see “About the Caché database” on page 597. This field applies to both
Outbound and e-mail.
Type: cls.EmailAddresses
FirstName
Description: The customer’s first name. This field applies to both Outbound
and e-mail.
Type: String
Length: 50
ID
Description: This is the primary key for the table. The value for this field is
automatically generated by the database when the record is created and cannot
be updated at any time. This field applies to both Outbound and e-mail.
Type: Integer
LastName
Description: The customer’s last name (surname). This field applies to both
Outbound and e-mail.
Type: String
Length: 100
LoginPage
Description: This is an embedded table (cls.CodeMappings). It can be selected
either as a field or as a pointer. As a field, it returns the ID value of the
cls.CodeMappings record related to this cls.Customers record. As a pointer, it
refers to the fields on the cls.CodeMappings record.
For more information about querying data from fields that are embedded tables,
see “About the Caché database” on page 597. This field applies to both
Outbound and e-mail.
Type: cls.CodeMappings
Password
Description: The customer’s password, stored in encrypted format. This field
applies to both Outbound and e-mail.
Type: String
Length: 50
PhoneNumbers
Description: This is an embedded table (cls.PhoneNumbers). It can be selected
either as a field or as a pointer. As a field, it returns the ID value of the
cls.PhoneNumbers record related to this cls.Customers record. As a pointer, it
refers to the fields on the cls.PhoneNumbers record.
For more information about querying data from fields that are embedded tables,
see “About the Caché database” on page 597. This field applies to both
Outbound and e-mail.
Type: cls.PhoneNumbers
PreferredAgent
Description: This is an embedded table (cls.Users). It can be selected either as a
field or as a pointer. As a field, it returns the ID value of the cls.Users record
related to this cls.Customers record. As a pointer, it refers to the fields on the
cls.Users record.
As a field, it can be used in an SQL relational join to the cls.Users record. For a
list of fields, refer to “Users” on page 735.
For more information about querying data from fields that are embedded tables,
see “About the Caché database” on page 597. This field applies to both
Outbound and e-mail.
Type: cls.Users
RegisterDate
Description: The date and time that this cls.Customers record is created. This
field applies to both Outbound and e-mail.
Type: TimeStamp
Title
Description: This is for titles such as Mr., Mrs., Miss, and Dr. There is no pre-
defined list of valid values. This field applies to both Outbound and e-mail.
Type: String
Length: 20
UserName
Description: The user name that the customer uses to log on. This field applies
to both Outbound and e-mail.
Type: String
Length: 50
Indexes
The are no indexes used by the cls.Customers table.
Debugs
This table is used to write debug information from any Object Script Routines.
Field descriptions
The field descriptions for this table are described in this section.
Code
Description: Internal use only.
Type: Integer
Component
Description: Internal use only.
Type: String
Severity
Description: Internal use only.
Type: Integer
Text
Description: Internal use only.
Type: String
Length: 255
Time
Description: Internal use only.
Type: TimeStamp
Indexes
The are no indexes used by the cls.Debugs table.
DispositionCodes
Field descriptions
The field descriptions for this table are described in this section.
Deletable
Description: Flag to indicate if the system can delete this cls.DispositionCode
record. 1 = Yes. This field applies to Outbound only.
Type: Boolean
DisplayName
Description: The display name for this cls.DispositionCode record. This field
applies to Outbound only.
Type: String
Length: 50
ID
Description: This is the primary key for the table. The database automatically
generates the value for this field when the record is created. You cannot update
this field at any time. This field applies to Outbound only.
Type: Integer
MarkAsDeleted
Description: Flag to indicate that this cls.DispositionCode record should appear
as deleted. 1 = Yes. This field information must stay in the system for historic
contacts that may link to this cls.DispositionCode record. This field applies to
Outbound only.
Type: Boolean
MaxRetryCount
Description: Number of times a to try a contact with this DispositionCode.
Used in conjunction with RetryTimeout. This field applies to Outbound only.
Type: Integer
Name
Description: The short name for this cls.Disposition Code record. This is
usually used for reporting rather than the cls.DisplayName record. This field
applies to Outbound only.
Type: String
Length: 50
NumericValue
Description: Integer value for this cls.DispositionCode record. Internal use
only. This field applies to Outbound only.
Type: Integer
RetryTimeout
Description: Amount of time to wait, in seconds, before retrying a contact that
has this DispositionCode. This field applies to Outbound only.
Type: Integer
SaveAgentScript
Description: Flag to save the agent script to an action when the contact is
processed. 1 = Yes. This field applies to Outbound only.
Type: Boolean
Type
Description: This is an embedded table (cls.CodeMappings). You can select it
either as a field or as a pointer. As a field, it returns the ID value of the
cls.CodeMappings record related to this cls.DispositionCodes record. As a
pointer, it refers to the fields on the cls.CodeMappings record.
For more information about querying data from fields that are embedded tables,
see “About the Caché database” on page 597. This field applies to Outbound
only.
Type: cls.CodeMappings
Indexes
The are no indexes used by the cls.DispositionCodes table.
Durations
This table contains details of how long the contact is open. There is one entry for
each agent that has worked on the contact.
Field descriptions
The field descriptions for this table are described in this section.
Agent
Description: This is an embedded table (cls.Users). It can be selected either as a
field or as a pointer. As a field, it returns the ID value of the cls.Users record
related to this cls.Durations record. As a pointer, it refers to the fields on the
cls.Users record.
As a field, it can be used in an SQL relational join to the cls.Users record. For a
list of fields, refer to “Users” on page 735.
For more information about querying data from fields that are embedded tables,
see “About the Caché database” on page 597.
Type: cls.Users
Duration
Description: Length of time agent has the contact open.
Type: Integer
ID
Description: This is the primary key for the table. The value for this field is
automatically generated by the database when the record is created and cannot
be updated at any time.
Type: Integer
Indexes
The are no indexes used by the cls.Durations table.
EmailAddresses
This table stores e-mail addresses owned by cls.Customers records. Each record
in this table is linked to a cls.Customers record using the Customer field.
Multiple cls.EmailAddresses records can be linked to the same cls.Customers
record.
Field descriptions
The field descriptions for this table are described in this section.
Address
Description: The e-mail address. This field applies to both Outbound and
e-mail.
Type: String
Length: 255
Customer
Description: This is an embedded table (cls.Customers). It can be selected
either as a field or as a pointer. As a field, it returns the ID value of the
cls.Customers record related to this cls.EmailAddresses record. As a pointer, it
refers to the fields on the cls.Customers record.
For more information about querying data from fields that are embedded tables,
see “About the Caché database” on page 597. This field applies to both
Outbound and e-mail.
Type: cls.Customers
Default
Description: Flag to indicate whether this e-mail address is used as the default
for communicating with the customer. 1 = Yes. This field applies to both
Outbound and e-mail.
Type: Boolean
ID
Description: This is the primary key for the table. The value for this field is
automatically generated by the database when the record is created and cannot
be updated at any time. This field applies to both Outbound and e-mail.
Type: Integer
SearchAddress
Description: This version of the e-mail address is used when searching. This
field applies to both Outbound and e-mail.
Type: String
Length: 255
Indexes
The following table lists the indexes used by the cls.EmailAddresses table.
Unique
Index name Fields indexed Type 1 = Yes Description
EmailAddressGroups
This table stores a list of e-mail addresses that can be compared to an incoming
contact record to trigger the actions of a specific rule. Each rule record can be
linked to one cls.EmailAddressGroup record.
Field descriptions
The field descriptions for this table are described in this section.
Addresses
Description: This contains a space delimited collection of e-mail addresses.
Type: String
Length: 4095
ID
Description: This is the primary key for the table. The value for this field is
automatically generated by the database when the record is created and cannot
be updated at any time.
Type: Integer
Name
Description: User defined e-mail address group name.
Type: String
Length: 255
Indexes
The are no indexes used by the cls.EmailAddressGroups table.
HolidayHours
This table contains details of any holidays that the contact center may have
special working hours for.
Field descriptions
The field descriptions for this table are described in this section.
CloseTime
Description: The time that the contact center closes. If this is blank, then the
contact center is open all day.
Type: String
Length: 5
HolidayDate
Description: The actual date of the holiday.
Type: String
Length: 22
ID
Description: This is the primary key for the table. The value for this field is
automatically generated by the database when the record is created and cannot
be updated at any time.
Type: Integer
Name
Description: The name of the holiday, such as New Year’s Day.
Type: String
Length: 255
OpenTime
Description: The time the contact center opens. This is any time from 00:00 to
23:59.
Type: String
Length: 5
Indexes
The are no indexes used by the cls.HolidayHours table.
Inboxes
This table contains details that relate the e-mail mailboxes used by the Contact
Center Multimedia application.
Field descriptions
The field descriptions for this table are described in this section.
DisplayName
Description: The display name for this inbox.
Type: String
Length: 100
DomainName
Description: The domain where the mailbox is located.
Type: String
Length: 100
Enabled
Description: Flag to indicate whether or not this inbox is enabled. 1 = Yes.
Type: Integer
ID
Description: This is the primary key for the table. The value for this field is
automatically generated by the database when the record is created and cannot
be updated at any time.
Type: Integer
InboundMailThreshold
Description: The number of e-mail message that should be read each time the
mailbox is accessed.
Type: Integer
Name
Description: The name of the inbox. This is concatenated with the at symbol
(@) and the DomainName to get the full e-mail address.
Type: String
Length: 100
OutBoundMailThreshold
Description: The number of e-mail messages that should be sent each time the
mailbox is accessed.
Type: Integer
Password
Description: The password to gain access to the mailbox.
Type: String
Length: 100
SMTPServer
Description: Internal use only.
Type: cls.Servers
Server
Description: This is an embedded table (cls.Servers). It can be selected either as
a field or as a pointer. As a field, it returns the ID value of the cls.Servers record
related to this cls.Inboxes record. As a pointer, it refers to the fields on the
cls.Servers record.
As a field, it can be used in an SQL relational join to the cls.Servers record. For
a list of fields, refer to “Servers” on page 717.
For more information about querying data from fields that are embedded tables,
see “About the Caché database” on page 597.
Type: cls.Servers
SmtpAuthLogon
Description: Internal use only.
Type: String
Length: 64
WinNTAccount
Description: The NT account that should be used to access the mailbox.
Type: String
Length: 100
Indexes
The are no indexes used by the cls.Inboxes table.
InvalidXMLAudits
Field descriptions
The field descriptions for this table are described in this section.
ActionId
Description: Internal use only.
Type: Integer
Char
Description: Internal use only.
Type: Integer
ContactId
Description: Internal use only.
Type: Integer
DateTimeFound
Description: Internal use only.
Type: TimeStamp
Field
Description: Internal use only.
Type: String
Position
Description: Internal use only.
Type: Integer
Indexes
The following table lists the indexes used by the cls.InvalidXMLAudits table.
Unique
Index name Fields indexed Type 1 = Yes Description
InvalidXMLChrs
Field descriptions
The field descriptions for this table are described in this section.
InvalidXMLField
Description: Internal use only.
Type: cls.InvalidXMLFields
New
Description: If populated, this is written into the field in the position the Old
ASCII value is found in. If not populated, the character is removed.
Type: String
Old
Description: ASCII character searched for in the parent field.
Type: Integer
Indexes
The following table lists the indexes used by the cls.InvalidXMLChrs table.
Unique
Index name Fields indexed Type 1 = Yes Description
InvalidXMLFields
Field descriptions
The field descriptions for this table are described in this section.
Characters
Description: Internal use only.
Type: cls.InvalidXMLChrs
Table
Description: Internal use only.
Type: String
Field
Description: Internal use only.
Type: String
Search
Description: Internal use only.
Type: Boolean
Indexes
The are no indexes used by the cls.InvalidXMLFields table.
KeyWordGroups
This table contains groups of key words used to correctly route new contacts.
Field descriptions
The field descriptions for this table are described in this section.
ID
Description: This is the primary key for the table. The value for this field is
automatically generated by the database when the record is created and cannot
be updated at any time.
Type: Integer
Name
Description: The name of the key word group.
Type: String
Length: 64
Query
Description: List of the key words.
Type: String
Length: 4095
Indexes
The are no indexes used by the cls.KeyWordGroups table.
Licenses
This table contains details of the various licenses that relate to the Contact
Center Multimedia application.
Field descriptions
The field descriptions for this table are described in this section.
Enabled
Description: Field to indicate whether a feature has a licence (true) on not
(false). The default value is 0 (false).
Type: Boolean
ID
Description: This is the primary key for the table. The value for this field is
automatically generated by the database when the record is created and cannot
be updated at any time.
Type: Integer
Name
Description: The name of the licensable feature. This corresponds to the name
used in the licence file.
Type: String
Length: 255
Services
Description: Internal use only.
Type: cls.Services
Indexes
The are no indexes used by the cls.Licenses table.
Migrations
This table contains details of the customers and contacts migrated from
Symposium Web Client 4.0 to Contact Center Multimedia 6.0. Internal use only.
Field descriptions
The field descriptions for this table are described in this section.
CustomerName
Description: Internal use only.
Type: String
Length: 255
FromCustomerId
Description: Internal use only.
Type: Integer
Migrated
Description: Internal use only.
Type: Integer
NotMigratedReason
Description: Internal use only.
Type: String
Length: 255
ToCustomerId
Description: Internal use only.
Type: Integer
Indexes
The are no indexes used by the cls.Migrations table.
MigrationNotes
This table contains informational notes that the migration application reads to
provide feedback to the end user during the migration process. Internal use only.
Field descriptions
The field descriptions for this table are described in this section.
DateTimeStamp
Description: Internal use only.
Type: TimeStamp
DebugOnly
Description: Internal use only.
Type: Integer
MigratedCustomers
Description: Internal use only.
Type: Integer
NoteText
Description: Internal use only.
Type: String
Length: 255
TotalCustomers
Description: Internal use only.
Type: Integer
Indexes
The are no indexes used by the cls.MigrationNotes table.
OnHoldURLs
This table contains URL details for use when a customer is on hold. Internal use
only.
Field descriptions
The field descriptions for this table are described in this section.
Description
Description: Internal use only.
Type: String
Length: 255
HoldTime
Description: Internal use only.
Type: Integer
Sequence
Description: Internal use only.
Type: Integer
Tag
Description: Internal use only.
Type: String
Length: 1024
URL
Description: Internal use only.
Type: String
Length: 1024
Indexes
The are no indexes used by the cls.OnHoldURLs table.
OutOfHoursRules
Field descriptions
The field descriptions for this table are described in this section.
AutoResponse
Description: Relational link to the cls.AutoResponses record used by the
cls.OutOfHoursRules record.
Type: Integer
Enabled
Description: Flag to indicate if this out-of-hours rule should be used. 1 = Yes.
Type: Boolean
ID
Description: This is the primary key for the table. The value for this field is
automatically generated by the database when the record is created and cannot
be updated at any time.
Type: Integer
Indexes
The are no indexes used by the cls.OutOfHoursRules table.
PageChange
Field descriptions
The field descriptions for this table are described in this section.
ChangeCounter
Description: Internal use only.
Type: Integer
Name
Description: Internal use only.
Type: String
Length: 255
Indexes
The are no indexes used by the cls.PageChange table.
PagePushes
Field descriptions
The field descriptions for this table are described in this section.
SerialNo
Description: Internal use only.
Type: Integer
Skillset
Description: Internal use only.
Type: cls.Skillsets
URL
Description: Internal use only.
Type: cls.PagePushURLs
Indexes
The are no indexes used by the cls.PagePushes table.
PagePushURLs
This table contains URL details for use when pushing pages to customers.
Field descriptions
The field descriptions for this table are described in this section.
Description
Description: Description for this URL.
Type: String
Length: 255
ID
Description: This is the primary key for the table. The value for this field is
automatically generated by the database when the record is created and cannot
be updated at any time.
Type: Integer
Skillset
Description: This is an embedded table (cls.Skillsets). It can be selected either
as a field or as a pointer. As a field, it returns the ID value of the cls.Skillsets
record related to this cls.PagePushURLs record. As a pointer, it refers to the
fields on the cls.Skillsets record.
As a field, it can be used in an SQL relational join to the cls.Skillsets record. For
a list of fields, refer to “Skillsets” on page 728.
For more information about querying data from fields that are embedded tables,
see “About the Caché database” on page 597.
Type: cls.Skillsets
URL
Description: The full URL.
Type: String
Length: 4095
Indexes
The are no indexes used by the cls.PagePushURLs table.
PhoneNumbers
This table stores phone number details for customers. They are linked to the
relevant cls.Customers record through the cls.Customer field. Multiple
cls.PhoneNumbers records can be linked to the cls.Customers record.
AreaCode
Description: The area code part of the phone number. This field applies to both
Outbound and e-mail.
Type: String
Length: 10
Customer
Description: This is an embedded table (cls.Customers). It can be selected
either as a field or as a pointer. As a field, it returns the ID value of the
cls.Customers record related to this cls.PhoneNumbers record. As a pointer, it
refers to the fields on the cls.Customers record.
For more information about querying data from fields that are embedded tables,
see “About the Caché database” on page 597. This field applies to both
Outbound and e-mail.
Type: cls.Customers
Default
Description: Flag to indicate if this should be used as the default number for
this customer. 1 = Yes. This field applies to both Outbound and e-mail.
Type: Boolean
DoNotCall
Description: Flag to indicate whether or not the customer requested that this
number not be used to for contact. 1 = Do Not Call. This field applies to both
Outbound and e-mail.
Type: Boolean
FullNumber
Description: This field is used internally to store the phone number stripped of
any spaces and non-numeric characters. This is used in conjunction with the
index to aid searching for a particular phone number. This field applies to both
Outbound and e-mail.
Type: String
Length: 32
ID
Description: This is the primary key for the table. The value for this field is
automatically generated by the database when the record is created and cannot
be updated at any time. This field applies to both Outbound and e-mail.
Type: Integer
InternationalCode
Description: The international code part of the phone number. This field applies
to both Outbound and e-mail.
Type: String
Length: 10
Number
Description: The local number part of the phone number. This field applies to
both Outbound and e-mail.
Type: String
Length: 32
Type
Description: This is an embedded table (cls.CodeMappings). It can be selected
either as a field or as a pointer. As a field, it returns the ID value of the
cls.CodeMappings record related to this cls.PhoneNumbers record. As a pointer,
it refers to the fields on the cls.CodeMappings record.
For more information about querying data from fields that are embedded tables,
see “About the Caché database” on page 597. This field applies to both
Outbound and e-mail.
Type: cls.CodeMappings
Indexes
The following table lists the indexes used by the cls.PhoneNumbers table.
Unique
Index name Fields indexed Type 1 = Yes Description
Phrases
This table contains a list of default strings of text that a user can select when
using Web Chat. This means that the user does not have to type the same text
over and over again.
Field descriptions
The field descriptions for this table are described in this section.
ID
Description: This is the primary key for the table. The value for this field is
automatically generated by the database when the record is created and cannot
be updated at any time.
Type: Integer
Skillset
Description: This is an embedded table (cls.Skillsets). It can be selected either
as a field or as a pointer. As a field, it returns the ID value of the cls.Skillsets
record related to this cls.Phrases record. As a pointer, it refers to the fields on the
cls.Skillsets record.
As a field, it can be used in an SQL relational join to the cls.Skillsets record. For
a list of fields, refer to “Skillsets” on page 728.
For more information about querying data from fields that are embedded tables,
see “About the Caché database” on page 597.
Type: cls.Skillsets
Text
Description: Phrase which is linked to skillset and appears in a drop-down box
for the agents to choose from during a chat session.
Type: String
Length: 32767
Indexes
The are no indexes used by the cls.Phrases table.
Preferences
Field descriptions
The field descriptions for this table are described in this section.
Agent
Description: This is an embedded table (cls.Users). It can be selected either as a
field or as a pointer. As a field, it returns the ID value of the cls.Users record
related to this cls.Preferences record. As a pointer, it refers to the fields on the
cls.Users record.
As a field, it can be used in an SQL relational join to the cls.Users record. For a
list of fields, refer to “Users” on page 735.
For more information about querying data from fields that are embedded tables,
see “About the Caché database” on page 597.
Type: cls.Users
Context
Description: Internal use only.
Type: String
Length: 30
ID
Description: This is the primary key for the table. The value for this field is
automatically generated by the database when the record is created and cannot
be updated at any time.
Type: Integer
IdKey
Description: Internal use only.
Type: String
Length: 30
Text
Description: Details of the preferences.
Type: Stream
Indexes
The are no indexes used by the cls.Preferences table.
Questions
This table stores questions that are associated with a cls.CampaignScripts table.
They are linked to the relevant cls.CampaignScripts records through the
CampaignScript field. Multiple cls.Questions records can be linked to one
cls.CampaignScripts record.
Field descriptions
The field descriptions for this table are described in this section.
AllowedAnswers
Description: A comma delimited selection of possible answers. This field
applies to Outbound only.
Type: String
Length: 1024
AllowedFreeText
Description: Flag to indicate whether or not the answer for this question can be
free text or should be selected from the list of AllowedAnswers. 1 = Free text
allowed. This field applies to Outbound only.
Type: Boolean
CampaignScript
Description: This is an embedded table (cls.CampaignScripts). It can be
selected either as a field or as a pointer. As a field, it returns the ID value of the
cls.CampaignScripts record related to this cls.Questions record. As a pointer, it
refers to the fields on the cls.CampaignScripts record.
For more information about querying data from fields that are embedded tables,
see “About the Caché database” on page 597. This field applies to Outbound
only.
Type: cls.CampaignScripts
DefaultAnswer
Description: The default answer for this question. This is one from the list of
AllowedAnswers. This field applies to Outbound only.
Type: String
Length: 255
GUI
Description: This is an embedded table (cls.CodeMappings). It can be selected
either as a field or as a pointer. As a field, it returns the ID value of the
cls.CodeMappings record related to this cls.Questions record. As a pointer, it
refers to the fields on the cls.CodeMappings record.
For more information about querying data from fields that are embedded tables,
see “About the Caché database” on page 597. This field applies to Outbound
only.
Type: cls.CodeMappings
ID
Description: This is the primary key for the table. The value for this field is
automatically generated by the database when the record is created and cannot
be updated at any time. This field applies to Outbound only.
Type: Integer
Question
Description: The name of the question. This field applies to Outbound only.
Type: String
Length: 1024
Indexes
The following table lists the indexes used by the cls.Questions table.
Unique
Index name Fields indexed Type 1 = Yes Description
RegularHours
This table holds information relating to the regular opening hours of the contact
center.
Field descriptions
The field descriptions for this table are described in this section.
CloseTime
Description: The time that the contact center closes. If this field is blank, then
the contact center is open all day.
Type: String
Length: 5
Day
Description: The day that open and close hours apply to. There can be multiple
entries for a given day. For example, this supports Contact Centers that close for
lunch.
Type: String
Length: 50
ID
Description: This is the primary key for the table. The value for this field is
automatically generated by the database when the record is created and cannot
be updated at any time.
Type: Integer
OpenTime
Description: The hours that the contact center opens. This value is in the range
00:00 to 23:59.
Type: String
Length: 5
Indexes
The are no indexes used by the cls.RegularHours table.
Restores
This table stores details relating to any restores performed on the database. This
is through the archive and restore functionality supplied with Contact Center
Multimedia and not through the database backup and restore functionality.
Field descriptions
The field descriptions for this table are described in this section.
FromActionId
Description: Internal use only.
Type: Integer
FromCampaignId
Description: Internal use only.
Type: Integer
FromContactId
Description: Internal use only.
Type: Integer
FromCustomerId
Description: Internal use only.
Type: Integer
FromQuestionId
Description: Internal use only.
Type: Integer
ToActionId
Description: Internal use only.
Type: Integer
ToCampaignId
Description: Internal use only.
Type: Integer
ToContactId
Description: Internal use only.
Type: Integer
ToCustomerId
Description: Internal use only.
Type: Integer
ToQuestionId
Description: Internal use only.
Type: Integer
Indexes
The following table lists the indexes used by the cls.Restores table.
Unique
Index name Fields indexed Type 1 = Yes Description
Unique
Index name Fields indexed Type 1 = Yes Description
RestoredAudits
This table stores a temporary copy of audit records that are being restored,
through the archive and restore functionality, to the database. It is necessary to
keep a temporary copy as all the links within the audit records change upon the
restore and need to be updated on the temporary versions here before being
written to the audit table.
Field descriptions
The field descriptions for this table are described in this section.
ActionId
Description: Link to the cls.Action record that this cls.Audit record relates to.
Type: Integer
AgentId
Description: The agent that made the change. This is link to the cls.UserDetails
table.
Type: Integer
CampaignId
Description: Link to the cls.Campaigns record that this audit record relates to.
Type: Integer
CampaignUserName
Description: Campaign user name that created the audit record.
Type: String
ContactId
Description: Link to the cls.Contacts record that this audit relates to.
Type: Integer
CustomerId
Description: Link to the cls.Customers record that this audit record relates to.
Type: Integer
DateTimeStamp
Description: The date and time that this audit event took place.
Type: TimeStamp
ID
Description: This is the primary key for the table. The value for this field is
automatically generated by the database when the record is created and cannot
be updated at any time.
Type: Integer
NewValue
Description: Contains the new value relevant to the type field. If type is
ContactStatus, then this field holds the old contact status value.
Type: Integer
OldValue
Description: Contains the old value relevant to the type field. If type is
ContactStatus, then this field holds the old contact status value.
Type: Integer
Type
Description: The audit type. This is a link to a record in the cls.CodeMappings
table.
Type: Integer
Indexes
The are no indexes used by the cls.RestoredAudits table.
RoutePoints
This table contains details of the Route Point assigned to a skillset. This table
replaces CDN. It has a MarkAsDeleted flag. Although it may be deleted on
Contact Center Manager Server, it is still be referenced within the Contact
Center Multimedia database on contacts created when the RoutePoint did exist.
Field descriptions
The field descriptions for this table are described in this section.
DeletionTimeStamp
Description: The date and time when this cls.RoutePoints record is deleted.
Type: TimeStamp
ID
Description: This is the primary key for the table. The value for this field is
automatically generated by the database when the record is created and cannot
be updated at any time.
Type: Integer
MarkAsDeleted
Description: Flag to indicate if this RoutePoint is deleted. 1 = Yes.
Type: Boolean
RoutePoint
Description: The name of the cls.RoutePoint record.
Type: String
Length: 32
Indexes
The are no indexes used by the cls.RoutePoints table.
Rules
This table contains the details for a rule used to route a contact to the relevant
skillset.
Field descriptions
The field descriptions for this table are described in this section.
AutoResponseID
Description: Relational link to the cls.Acknowledgement record used by this
rule.
Type: Integer
ContactTypeID
Description: Internal use only.
Type: Integer
EmailAddressGroupID
Description: Relational link to the cls.EmailAddressGroups record used by this
rule.
Type: Integer
ID
Description: This is the primary key for the table. The value for this field is
automatically generated by the database when the record is created and cannot
be updated at any time.
Type: Integer
InboxID
Description: Relational link to the cls.Inboxes record used by this rule.
Type: Integer
IsClosed
Description: Flag to indicate whether this rule is closed or not. 1 = Yes.
Type: Boolean
Name
Description: Textual name for the rule.
Type: String
Length: 64
Priority
Description: The rule’s priority.
Type: Integer
RuleQuery
Description: The text that makes up the body of the rule.
Type: String
Length: 2000
Sequence
Description: The order in which this rule should be used. This applies if there is
more than one rule for a cls.Skillsets record. Lowest sequence numbers are
processed first.
Type: Integer
SkillsetID
Description: Relational link to the cls.Skillsets record used by this rule.
Type: Integer
SkillsetReset
Description: Internal use only.
Type: Boolean
Status
Description: Internal use only.
Type: Integer
Type
Description: Internal use only.
Type: Integer
UseOutOfHoursRule
Description: Flag to indicate whether or not the out-of-hours rule should be
used instead of this rule. 1 = Yes.
Type: Boolean
Indexes
The are no indexes used by the cls.Rules table.
RuleAdmins
Field descriptions
The field descriptions for this table are described in this section.
DefaultPriority
Description: The default priority value for this rule.
Type: Integer
ID
Description: This is the primary key for the table. The value for this field is
automatically generated by the database when the record is created and cannot
be updated at any time.
Type: Integer
LastModifiedTime
Description: The date and time this rule was last modified. If any cls.Rules
record is updated, this field is also updated.
Type: TimeStamp
LastQueryBuildTime
Description: The date and time that the rule query was last built.
Type: TimeStamp
NumberOfCharacters
Description: The number of characters in the last rule query.
Type: Integer
SearchBody
Description: Flag to indicate whether or not the body of the e-mail should be
searched. 1 = Yes.
Type: Boolean
SearchSubject
Description: Flag to indicate whether or not the e-mail subject should be
searched. 1 = Yes.
Type: Boolean
Indexes
The are no indexes used by the cls.RuleAdmins table.
RuleKeywordGroups
This table contains cls.KeyWordGroups records that are used within rules.
Field descriptions
The field descriptions for this table are described in this section.
ID
Description: This is the primary key for the table. The value for this field is
automatically generated by the database when the record is created and cannot
be updated at any time.
Type: Integer
KeyWordGroupID
Description: Link to the internal unique identifier of the cls.KeyWordGroups
record.
Type: Integer
Operator
Description: Descriptions of how this table should be connected to the other
cls.RuleKeyWordGroup records for the rule.
Type: String
Length: 10
RuleID
Description: Link to the internal unique identifier of the cls.Rules record.
Type: Integer
Sequence
Description: The sequence number for this cls.RuleKeyWordGroup record.
Type: Integer
Indexes
The are no indexes used by the cls.RuleKeywordGroups table.
Servers
This table contains a list of the servers required by the Contact Center
Multimedia application.
Field descriptions
The field descriptions for this table are described in this section.
Auth
Description: Internal use only.
Type: Integer
BackUpHost
Description: The name of the back-up server.
Type: String
Length: 255
ID
Description: This is the primary key for the table. The value for this field is
automatically generated by the database when the record is created and cannot
be updated at any time.
Type: Integer
Name
Description: The name of the server. This can also be an IP address.
Type: String
Length: 255
NewType
Description: This is an embedded table (cls.CodeMappings). It can be selected
either as a field or as a pointer. As a field, it returns the ID value of the
cls.CodeMappings record related to this cls.Servers record. As a pointer, it refers
to the fields on the cls.CodeMappings record.
For more information about querying data from fields that are embedded tables,
see “About the Caché database” on page 597.
Type: cls.CodeMappings
Port
Description: The port number to use when connecting to this server.
Type: Integer
Type
Description: Internal use only.
Type: Integer
Indexes
The are no indexes used by the cls.Servers table.
Services
This table contains a list of the services that make up the Contact Center
Multimedia application.
Field descriptions
The field descriptions for this table are described in this section.
ID
Description: This is the primary key for the table. The value for this field is
automatically generated by the database when the record is created and cannot
be updated at any time.
Type: Integer
License
Description: This is an embedded table (cls.Licenses). It can be selected either
as a field or as a pointer. As a field, it returns the ID value of the cls.Licenses
record related to this cls.Services record. As a pointer, it refers to the fields on
the cls.Licenses record.
As a field, it can be used in an SQL relational join to the cls.Licenses record. For
a list of fields, refer to “Licenses” on page 682.
For more information about querying data from fields that are embedded tables,
see “About the Caché database” on page 597.
Type: cls.Licenses
NTName
Description: Name in services, used by cache and the sc Winnt command to
stop the service.
Type: String
Length: 255
ServiceName
Description: Name of the Contact Center Multimedia service. This is used by
Licence Manager to start and stop services.
Type: String
Length: 255
Indexes
The are no indexes used by the cls.Services table.
Sessions
This table contains a session key for each user that is logged on.
Field descriptions
The field descriptions for this table are described in this section.
ID
Description: This is the primary key for the table. The value for this field is
automatically generated by the database when the record is created and cannot
be updated at any time.
Type: Integer
LoginTime
Description: Date and time that the user logged on to the system.
Type: TimeStamp
SessionKey
Description: Session key value for the user.
Type: String
UserID
Description: Link to the unique internal identifier for the user.
Type: String
UserType
Description: Whether the user is an agent or a supervisor.
Type: String
Indexes
The are no indexes used by the cls.Sessions table.
Sites
This table contains details that relate to the site that the Contact Center
Multimedia application is installed on.
Field descriptions
The field descriptions for this table are described in this section.
AccessKey
Description: Internal use only.
Type: String
Length: 20
BuildVersion
Description: The build version of the Contact Center Multimedia application.
Type: String
Length: 20
CompanyName
Description: Name of the company that controls the site.
Type: String
Length: 20
CustomFields
Description: This is an embedded table (cls.CustomFields). It can be selected
either as a field or as a pointer. As a field, it returns the ID value of the
cls.CustomFields record related to this cls.Sites record. As a pointer, it refers to
the fields on the cls.CustomFields record.
For more information about querying data from fields that are embedded tables,
see “About the Caché database” on page 597.
Type: cls.CustomFields
EnableSecurityBanner
Description: Flag to indicate whether or not the security banner should be
displayed. 1 = Yes.
Type: Boolean
ID
Description: This is the primary key for the table. The value for this field is
automatically generated by the database when the record is created and cannot
be updated at any time.
Type: Integer
MMKeyCode
Description: Internal use only.
Type: String
Length: 20
MMSwitchSerialNumber
Description: Internal use only.
Type: String
Length: 12
NNCCSiteName
Description: Internal use only.
Type: String
Length: 255
NNCCSwitchSerialNumber
Description: Internal use only.
Type: String
Length: 12
SecurityBanner
Description: Banner text that should be displayed to the agent when logging
into the Contact Center Agent Desktop.
Type: String
Length: 4095
Site
Description: Name of the site.
Type: String
Length: 10
SkillsetPrefix
Description: Internal use only.
Type: String
Length: 10
Indexes
The are no indexes used by the cls.Sites table.
SiteComponents
This table contains the various components that make up the Contact Center
Multimedia application.
Field descriptions
The field descriptions for this table are described in this section.
Comment
Description: Description for the cls.SiteComponent record.
Type: String
Length: 255
ID
Description: This is the primary key for the table. The value for this field is
automatically generated by the database when the record is created and cannot
be updated at any time.
Type: Integer
Name
Description: The name of the cls.SiteComponent record.
Type: String
Length: 255
Parameters
Description: Internal use only.
Type: cls.SiteParameters
Indexes
The are no indexes used by the cls.SiteComponents table.
SiteParameters
This table contains various parameters that the various Contact Center
Multimedia services use.
Field descriptions
The field descriptions for this table are described in this section.
Comment
Description: Textual description for this cls.SiteParameter record.
Type: String
Length: 255
ID
Description: This is the primary key for the table. The value for this field is
automatically generated by the database when the record is created and cannot
be updated at any time.
Type: Integer
Name
Description: The name of the cls.SiteParameter record.
Type: String
Length: 255
SiteComponent
Description: This is an embedded table (cls.SiteComponents). It can be selected
either as a field or as a pointer. As a field, it returns the ID value of the
cls.SiteComponents record related to this cls.SiteParameters record. As a
pointer, it refers to the fields on the cls.SiteComponents record.
For more information about querying data from fields that are embedded tables,
see “About the Caché database” on page 597.
Type: cls.SiteComponents
Text
Description: The value of the cls.SiteParameter record.
Type: String
Length: 255
Indexes
The following table lists the indexes used by the cls.SiteParameters table.
Unique
Index name Fields indexed Type 1 = Yes Description
Skillsets
This table contains a list of all skillsets that have been on the system. Skillsets
that are no longer current have a flag set to indicate this fact. They are kept on
the system as there may or may not be contacts for those skillsets.
Field descriptions
The field descriptions for this table are described in this section.
ActivityCode
Description: Internal use only.
Type: String
Length: 32
Agents
Description: This is an embedded table (cls.Users). It can be selected either as a
field or as a pointer. As a field, it returns the ID value of the cls.Users record
related to this cls.Skillsets record. As a pointer, it refers to the fields on the
cls.Users record.
As a field, it can be used in an SQL relational join to the cls.Users record. For a
list of fields, refer to “Users” on page 735.
For more information about querying data from fields that are embedded tables,
see “About the Caché database” on page 597.
Type: cls.Users
AutoSignature
Description: Default signature that is appended to any e-mail messages sent out
from this skillset.
Type: String
Length: 4095
CCMSID
Description: The ID from the Contact Center Manager Server.
Type: Integer
DeletionTimeStamp
Description: The date and time this skillset is deleted from the system.
Type: TimeStamp
ID
Description: This is the primary key for the table. The value for this field is
automatically generated by the database when the record is created and cannot
be updated at any time.
Type: Integer
MailBox
Description: This is an embedded table (cls.Inboxes). It can be selected either
as a field or as a pointer. As a field, it returns the ID value of the cls.Inboxes
record related to this cls.Skillsets record. As a pointer, it refers to the fields on
the cls.Inboxes record.
As a field, it can be used in an SQL relational join to the cls.Inboxes record. For
a list of fields, refer to “Inboxes” on page 674.
For more information about querying data from fields that are embedded tables,
see “About the Caché database” on page 597.
Type: cls.Inboxes
Mapping
Description: Internal use only.
Type: String
Length: 50
MarkAsDeleted
Description: Flag to indicate if this skillset is deleted. 1 = Yes.
Type: Boolean
Name
Description: Textual name for this skillset.
Type: String
Length: 50
PagePushURLs
Description: Internal use only.
Type: cls.PagePushURLs
Phrases
Description: Internal use only.
Type: cls.Phrases
RoutePoint
Description: This is an embedded table (cls.RoutePoints). It can be selected
either as a field or as a pointer. As a field, it returns the ID value of the
cls.RoutePoints record related to this cls.Skillsets record. As a pointer, it refers
to the fields on the cls.RoutePoints record.
For more information about querying data from fields that are embedded tables,
see “About the Caché database” on page 597.
Type: cls.RoutePoints
Status
Description: Internal use only.
Type: cls.CodeMappings
Threshold
Description: Internal use only.
Type: Integer
UseOriginalAddress
Description: Internal use only.
Type: Integer
WebDescription
Description: Textual description for this Skillset.
Type: String
Length: 50
Indexes
The are no indexes used by the cls.Skillsets table.
SkillsetOnHoldURLs
This table contains a list of URLs for a skillset that can be used when a customer
is on hold.
Field descriptions
The field descriptions for this table are described in this section.
ID
Description: This is the primary key for the table. The value for this field is
automatically generated by the database when the record is created and cannot
be updated at any time.
Type: Integer
SerialNo
Description: Internal use only.
Type: Integer
Skillset
Description: This is an embedded table (cls.Skillsets). It can be selected either
as a field or as a pointer. As a field, it returns the ID value of the cls.Skillsets
record related to this cls.SkillsetOnHoldURLs record. As a pointer, it refers to
the fields on the cls.Skillsets record.
As a field, it can be used in an SQL relational join to the cls.Skillsets record. For
a list of fields, refer to “Skillsets” on page 728.
For more information about querying data from fields that are embedded tables,
see “About the Caché database” on page 597.
Type: cls.Skillsets
Indexes
The are no indexes used by cls.SkillsetOnHoldURLs table.
Updates
Field descriptions
The field descriptions for this table are described in this section.
CRNumber
Description: The change request (CR) number that this update relates to.
Type: String
Length: 20
Changes
Description: Free form text notes on the update applied.
Type: String
Length: 2000
Date
Description: The date field as taken from the text file.
Type: String
Length: 30
DateTimeStamp
Description: The date and time that this update was applied to the system.
Type: TimeStamp
DeleteFlag
Description: Internal use only.
Type: String
Length: 1
DeployFlag
Description: Internal use only.
Type: String
Length: 1
FileChanged
Description: The name of the file that contains the new code.
Type: String
Length: 200
ID
Description: This is the primary key for the table. The value for this field is
automatically generated by the database when the record is created and cannot
be updated at any time.
Type: Integer
Notes
Description: Any other comments are recorded here.
Type: String
Length: 2000
RequestedBy
Description: Name of person who requested the update.
Type: String
Length: 50
Indexes
The are no indexes used by the cls.Updates table.
Users
Field descriptions
The field descriptions for this table are described in this section.
CCMSID
Description: The Contact Center Multimedia ID of this agent or supervisor.
This comes from Contact Center Manager Server.
Type: Integer
DeletionTimeStamp
Description: Date and time this user was deleted from the system.
Type: TimeStamp
Email
Description: The e-mail address for the user.
Type: String
Length: 255
Fax
Description: The FAX number for the user.
Type: String
Length: 20
FirstName
Description: User’s first name.
Type: String
Length: 50
ID
Description: This is the primary key for the table. The value for this field is
automatically generated by the database when the record is created and cannot
be updated at any time.
Type: Integer
LastName
Description: User’s last name.
Type: String
Length: 50
LogonId
Description: The logon ID used to connect to the Contact Center Agent
Desktop.
Type: String
Length: 50
MarkAsDeleted
Description: Flag to indicate if this user is deleted.
Type: Boolean
Password
Description: Internal use only.
Type: String
Length: 20
RoutePoint
Description: This is an embedded table (cls.RoutePoints). It can be selected
either as a field or as a pointer. As a field, it returns the ID value of the
cls.RoutePoints record related to this cls.Users record. As a pointer, it refers to
the fields on the cls.RoutePoints record.
For more information about querying data from fields that are embedded tables,
see “About the Caché database” on page 597.
Type: cls.RoutePoints
Status
Description: Flag to indicate whether the user is logged on or not. 1 = Logged
in.
Type: Boolean
Supervisor
Description: Link to the user’s cls.Supervisors record.
Type: cls.Users
TelsetLogonId
Description: The logon ID used to access the user’s telephone set.
Type: String
Length: 255
UserClass
Description: Text to describe the user type, which can be agent or supervisor.
Type: String
Length: 20
Indexes
The are no indexes used by the cls.Users table.
UserResets
Field descriptions
The field descriptions for this table are described in this section.
ID
Description: This is the primary key for the table. The value for this field is
automatically generated by the database when the record is created and cannot
be updated at any time.
Type: Integer
PasswordReset
Description: Flag to indicate if the user’s password was reset.
Type: Integer
UserID
Description: Relational link to the cls.User table. This is used by the
administration application.
Type: Integer
Indexes
The are no indexes used by the cls.UserResets table.
WebCommsMessages
This table stores details of messages that are written by either the agent or the
customer during a Web communication session. The messages are linked to a
cls.WebCommsSession record. Multiple cls.WebCommsMessages records can
be linked to the same cls.WebCommsSessions record.
Field descriptions
The field descriptions for this table are described in this section.
ID
Description: This is the primary key for the table. The value for this field is
automatically generated by the database when the record is created and cannot
be updated at any time. This field is applicable for Web communications only.
Type: Integer
Message
Description: Message text from either the agent or customer. This field is
applicable for Web communications only.
Type: String
Length: 255
Session
Description: This is an embedded table (cls.WebCommsSessions). It can be
selected either as a field or as a pointer. As a field, it returns the ID value of the
cls.WebCommsSessions record related to this cls.WebCommsMessages record.
As a pointer, it refers to the fields on the cls.WebCommsSessions record.
For more information about querying data from fields that are embedded tables,
see “About the Caché database” on page 597. This field is applicable for Web
communications only.
Type: cls.WebCommsSessions
WriteTime
Description: The date and time that this message was written. This field is
applicable for Web communications only.
Type: TimeStamp
Indexes
The are no indexes used by the cls.WebCommsMessages table.
WebCommsSessions
Field descriptions
The field descriptions for this table are described in this section. This field is
applicable for Web communications only.
AgentWriting
Description: Flag to indicate if the agent is currently writing. This field is
applicable for Web communications only.
Type: Boolean
ContactID
Description: Relational link to the contact’s unique internal identifier that this
session belongs to. This field is applicable for Web communications only.
Type: String
CustomerWriting
Description: Flag to indicate if the customer is currently writing. This field is
applicable for Web communications only.
Type: Boolean
ID
Description: This is the primary key for the table. The value for this field is
automatically generated by the database when the record is created and cannot
be updated at any time. This field is applicable for Web communications only.
Type: Integer
LastAgentPoll
Description: Internal use only. This field is applicable for Web communications
only.
Type: TimeStamp
LastCustomerPoll
Description: Internal use only. This field is applicable for Web communications
only.
Type: TimeStamp
Messages
Description: Internal use only. This field is applicable for Web communications
only.
Type: cls.WebCommsMessages
Indexes
The following table lists the indexes used by the cls.WebCommsSessions table.
Unique
Index name Fields indexed Type 1 = Yes Description
Additional tables
There are 2 additional tables that are generated specifically for the SQL
representation of the data.
cls.Campaigns_DispositionCodes
The cls.Campaigns and cls.DispositionCodes tables have a many-to-many
relationship. This is the table that links them together.
Fields Description
cls.Skillsets_Agents
The cls.Skillsets and cls.Users tables have a many-to-many relationship. This is
the table that links them together.
Fields Description
In this section
Overview 746
CampaignAgentScriptResult 747
CampaignCallByCallDetails 748
CampaignSummary 751
ContactsByContacts 753
ContactsOutstanding 755
ContactsOutstandingDetail 756
ContactsOutstandingSumm 758
ScriptSummary 759
Overview
This section contains database view information. You access data through
database views, or logical representations of the database. Database views are
used to organize the information in the database for your use. In SQL terms, a
view is a named query in a schema, defined with a CREATE VIEW statement. A
view is not a table, but the result of a view is a table.
This section provides definitions for all the Contact Center Multimedia database
views available.
CampaignAgentScriptResult
This view displays the questions and answers given for campaigns. The results
are sorted by contact. This view is often used to retrieve the details for a
particular campaign. You can use this view to see, by contact, the name and
phone number for the customer and the answers given to the campaign
questions.
The following table lists the view field, source table, and source field, where
applicable, for this view.
ContactID cls.Contacts ID
PhoneNumber cls.Actions NumberUsed
CustomerID cls.Customers ID
FirstName cls.Customers
LastName cls.Customers
Answer cls.Answers
Question cls.Questions
FreeText cls.Answers
AllowedAnswers cls.Questions
CampaignCallByCallDetails
This view provides call by call details for campaigns. This view is used to
retrieve the information relating to one outbound campaign. The view displays
when the contact was opened and closed, when the relevant action was opened
and closed, how long the agent was dialing and talking, and overview
information relating to the campaign in general. The overview information
includes the daily start and end times for the campaign and how many contacts
are in the campaign SQL used to create view
The following table lists the view field, source table, and source field, where
applicable, for this view.
ContactID cls.Contacts ID
Priority cls.Contacts
CallBackStatus cls.Actions
CallBackMedia cls.Actions
ActionID cls.Actions ID
DialStartTime cls.Actions
DialEndTime cls.Actions
TalkStartTime cls.Actions
TalkEndTime cls.Actions
LastName cls.Customers
FirstName cls.Customers
CustomerID cls.Customers ID
CampaignSummary
The following table lists the view field, source table, and source field, where
applicable, for this view.
NumberOfContacts cls.Campaigns
NumberOfContacts cls.Campaigns
Processed
StartDateTime cls.Campaigns
EndDateTime cls.Campaigns
DailyStartTime cls.Campaigns
DailyEndTime cls.Campaigns
Description cls.Campaigns
Owner cls.Campaigns
Priority cls.Campaigns
ContactsByContacts
This view provides details for contacts in a user-friendly format. The view
includes the customer name and the agent name. For Outbound contacts, the
view also shows summary information from the campaign, such as the campaign
name, how many times the customer was called, and the dial and talk time totals.
The following table lists the view field, source table, and source field, where
applicable, for this view.
ContactID cls.Contacts ID
ArrivalTime cls.Skillsets
ClosedReasonCode cls.Skillsets
FirstName cls.Customers
LastName cls.Customers
MailCC cls.Contacts
MailFrom cls.Contacts
MailTo cls.Contacts
OriginalSubject cls.Contacts
Priority cls.Contacts
QueueType cls.Contacts
RuleName cls.Contacts Rule
Source cls.Contacts
Type cls.Contacts
NumberOfContacts cls.Contacts
NumberOfContacts cls.Contacts
Processed
CampaignRetryCount cls.Contacts
ContactsOutstanding
This view provides the number of contacts in the contact center that do not have
a status of Closed. The view includes the arrival time from the contact formatted
in different ways: just the date, date and time (hour only), and the full arrival
time information. This is useful for sorting or using the fields in a where clause
to restrict the data returned to a particular time frame.
The following table lists the view field, source table, and source field, where
applicable, for this view.
Status cls.Contacts
Skillset cls.Contacts
ContactsOutstandingDetail
This view is similar to the ContactsOutstanding view, but also includes the date,
subject, and source information from all the actions related to the outstanding
contacts. For more information, refer to “ContactsOutstanding” on page 755.
The following table lists the view field, source table, and source field, where
applicable, for this view.
ContactNo cls.Contacts ID
Status cls.Contacts
ContactsOutstandingSumm
This view displays the number of contacts for each skillset grouped by the date
they arrived. Only contacts that do not have a status of Closed are included. It
uses the ContactsOutstanding view as the base for the results.
The following table lists the view field, source table, and source field, where
applicable, for this view.
ScriptSummary
This view displays count information related to the questions and answers for an
outbound campaign. It shows the number of times each answer was selected for
each question.
The following table lists the view field, source table, and source field, where
applicable, for this view.
Name cls.CampaignScript
Question cls.Questions
AllowedAnswers cls.Questions
AllowedFreeText cls.Questions
DefaultAnswer cls.Questions
In this chapter
Overview 762
Contact Center Manager entity relationships 763
Contact Center Multimedia entity relationships 779
Overview
The diagrams in this chapter show the relationships among the Contact Center
Manager database views. This chapter contains diagrams illustrating each
statistics group, plus an overall diagram showing all of the relationships within
the database.
The notation convention used for the Contact Center Manager entity relationship
diagrams is IDEF1X.
For more information about interpreting this graphical model, consult FIPS
publication 184, online from the (US) National Institute of Standards and
Technology at http://www.itl.nist.gov.
Entity notation
The following terms are used to describe entities:
Entity—An entity is any person, item, or concept about which information
is kept. In Contact Center Manager, an entity includes Agents as well as
abstract things—such as Applications, Skillsets, CDNs, Activity Codes,
and database views—such as iAgentPerformanceStat. More precisely, an
entity is a set or collection of items called instances. Entities are named by
nouns—for example, agent, application, or skillset. Entities are classified as
independent or dependent entities, depending on how they acquire their
keys.
Entity Name
key area
data area
Entity Name
key area
data area
iApplicationStat
Application
Timestamp
ApplicationID ApplicationID (FK)
Attribute notation
The following terms are used to describe attributes:
Primary key attribute—A primary key is an attribute that, either by itself
or in combination with other primary key attributes, forms the primary key.
Non-primary key attribute—A non-primary key attribute is not part of
the primary key of the entity.
Foreign key—Whenever entities are connected by a relationship, the
relationship contributes a key (or set of keys) to the child entity. Foreign
key attributes are primary key attributes of a parent entity contributed to a
child entity across a relationship. The contributed keys are said to migrate
or propagate from parent to child.
Foreign key attributes are designated in the model by an (FK) following the
attribute name. In the following illustration, ApplicationID is a foreign key.
iApplicationStat
Application
Timestamp
ApplicationID ApplicationID (FK)
Role name—A role name is a new name for a foreign key attribute or
group of foreign key attributes that defines the role the foreign key plays in
the child entity. A role definition is based on the definition of the original
foreign key or keys. Role names take the following format:
role-name.attribute (FK)
iIVRPortStat
IVRPort
Timestamp
SwitchPortAddress IVRPortID.SwitchPortAddress (FK)
IVRQueueID (FK)
Application
ApplicationID
Name (IE1)
Relationship notation
The following terms are used to describe the relationships between entities.
Relationships—Relationships represent connections, links, or associations
between entities. Relationships in an information model are used to
represent some of the business rules that describe the area that is modeled.
IDEF1X, unlike some other modeling languages, insists that all
relationships be binary; that is, they connect exactly two entities.
Child Entity
Parent Entity
parent_key (FK)
parent_key child_key
Child Entity
Parent Entity
child_key
parent_key
parent_key (FK)
Cardinality notation
The following notation is used to show the number of child attributes involved
in the relationship.
One-to-zero-or-more
One-to-one-or-more
P
One-to-zero-or-one
Z
One-to-exactly-N
N
Application statistics
Route statistics
Skillset statistics
Trunk statistics
To view all table entities with definitions, see Chapter 6, “Contact Center
Multimedia Data dictionary.”
Standard reports
In this appendix
Overview 784
Understanding the report descriptions 787
Section A: Agent performance reports 803
Section B: Call by call reports 913
Section C: Configuration reports 921
Section D: Multimedia reports 1017
Section E: Network reports 1035
Section F: Others (Additional CCMA reports) 1075
Section G: Outbound reports 1165
Section H: Administration reports 1179
Section I: Network Control Center reports 1193
Overview
Historical reports
Historical reports provide information related to the statistics, activities, and
performance of the contact center. Two types of historical reports are available:
summarized historical reports—These reports contain totals accumulated
over a period of time (usually, 15-minute interval, daily, weekly, or
monthly).
event (detail) historical reports—These reports contain detailed information
about each event that occurred.
Configuration reports
Configuration reports contain information about how your system is configured.
You can use these reports as a reference when you are planning or making
changes to your system.
The following report templates do not appear when connected to a SIP server:
IVR Port Properties
IVR Queue and Port Properties
Rights required
All reports require access levels to generate the report. To run reports from
Contact Center Manager Administration, your administrator must grant access
rights to the Historical Reporting application for your user account.
When you access Historical Reporting, you can save your reports in the private
report templates folder and to the shared report groups. The access to the shared
report groups is granted by your administrator.
For more information about access rights, see “Selection Criteria” on page 790.
Partitions
In addition to controlling the types of reports users can generate, you can also
limit the data included in their reports. To do so, you use partitions. When you
create a partition, you can choose the agents, skillsets, applications, CDNs,
DNISs, and report groups that are visible to agents who are assigned that
partition. For more information about partitions, see the Contact Center
Manager Administration online Help.
Report groups
You can use report groups to further control access to reports. You can create a
custom report group containing only those reports which a user should access.
Then, you create a partition containing that report group, and assign that
partition to a user. For detailed instructions, see the Contact Center Manager
Administration online Help.
This section describes the contents of the report descriptions in this appendix.
You can use this information to interpret the standard reports, as well as to
create custom reports.
Views
The descriptions of the reports indicate the database view that provides the data
for the report. (For more information about the database views, see Chapter 4,
“Contact Center Manager Data dictionary.” and Chapter 6, “Contact Center
Multimedia Data dictionary.”)
For more information about view, see “Selection Criteria” on page 790.
Templates
For each standard report, the report description identifies the Crystal Reports
template file for the report.
Template files are stored in \\Program Files\Nortel
Networks\WClient\Apps\Reporting\Historical\rpt.
You can use these template files as the basis for customized Contact Center
Manager Server reports. To create a customized Contact Center Manager Server
report based on a standard report template, follow these steps:
1. Copy the standard report template and give it a meaningful name.
2. Modify the new template using Crystal Reports version 10.
3. Import the new template into the server (see “Importing a report created in
Crystal Reports” on page 84).
CAUTION
Selection criteria
This section of the report description indicates the fields on which the report can
be filtered. For example, if a report can be filtered by agent, you can choose the
agents to include in the report.
Statistics
This section of the report contains tables with the following columns:
Column Description
Report field Contains all the fields that appear on the report.
View field/Formula For raw data, contains the view field from which the data
is taken. For calculated fields, this manual provides the
formula used to calculate the field value.
View field/Report The Report Creation Wizard formula that provides this
Creation Wizard statistic. If you want to include this statistic on reports
formula you create with the Report Creation Wizard, use this
formula. (For more information about the formulas, see
Appendix B, “Report Creation Wizard.”)
For more detailed information about the report field, refer to the description of
the field in Chapter 4, “Contact Center Manager Data dictionary.” or Chapter 6,
“Contact Center Multimedia Data dictionary.” For each field, the data dictionary
provides the following information:
a description of the field
the type of data
the length of the field
the events that trigger pegging of this statistic
Where a report contains fields from more than one database view, the field
names are given as view.fieldname. For example,
AgentBySkillsetStat.CallsAnswered represents the calls answered field in the
AgentBySkillsetStat view.
Selection Criteria
The following table shows the selection criteria available for each report in the
standard reports section. The table also shows the database field names. The
selection criteria are the fields shown on the user interface. The database field
names are the filters in the report SQL structure used in the report template.
Identifying these field names is useful for building custom reports with Report
Creation Wizard.
The following table lists all available reports, with selection criteria and field
names, in alphabetical order.
In this section
Activity Code by Agent 804
Agent Average Calls per Hour 807
Agent Average Calls per Hour, Bottom 5 810
Agent Average Calls per Hour, Top 5 813
Agent by Activity Code 816
Agent by Application Performance 819
Agent by Skillset Performance 823
Agent DN Performance 827
Agent DN Performance Calls Answered, Bottom 5 833
Agent DN Performance Calls Answered, Top 5 837
Agent Login/Logout 841
Agent NACD Activity 846
Agent Performance 849
Agent Performance by Supervisor 859
Agent Performance Calls Answered, Bottom 5 875
Agent Performance Calls Answered, Top 5 880
Agent Short Calls 885
Agent Transferred/Conferenced Activity 892
Estimated Revenue by Agent 900
Not Ready Reason Codes by Agent 903
Skillset by Agent Performance 906
With the Activity Code by Agent report you monitor each agent’s work and time
distribution by the types of contacts accepted. During the handling of contacts,
agents can identify the contact type by entering an activity (Line of Business)
code. These codes can identify contacts as sales, service, and support contacts.
On the Communication Server 2x00/DMS switch, agents cannot use the Line of
Business (LOB) key while they are conferenced with another agent.
For more information, see “Understanding the report descriptions” on page 787.
Views
This report uses the ActivityCodeStat view (see page 188.) For more
information about views, see “Access rights by view” on page 156.
Collection frequency
The following collection frequency types are available for this report:
interval
daily
weekly
monthly
Templates
This report uses the following templates:
im-agt15.rpt
dm-agt15.rpt
wm-agt15.rpt
mm-agt15.rpt
Selection criteria
Statistics
Summaries
The report provides totals for each agent, and subtotals for each day, week, or
month (depending on the reporting period selected). For the interval reporting
period, statistics are further broken down by interval. The report also contains a
grand total for all selected agents.
& #$
#$%" # #$ #$ '##(#!
$!*+,(*#$*%" *(& ) ) )
"$ % %
$!*+,(*#$*%" *##(! )
$!*+,(*#$*%" *(& ) - .
"$ $ &'
(!
)*+*!,,%%&$-. -
/
The Agent Average Calls per Hour report shows summarized performance
information about the contacts each agent accepts per hour logged on. The report
provides three hourly averages for the time the agent is logged on: the average
contacts accepted, the average time spent with customers, and the average time
spent in the Not Ready state.
For more information, see “Understanding the report descriptions” on page 787.
Views
This report uses the AgentPerformanceStat view (see page 220.) For more
information about views, see “Access rights by view” on page 156.
Collection frequency
The following collection frequency types are available for this report:
daily
weekly
monthly
Templates
This report uses the following templates:
dm-agt9.rpt
wm-agt9.rpt
mm-agt9.rpt
Selection criteria
Statistics
Summaries
The report provides totals for each agent, and subtotals for each day, week, or
month (depending on the reporting period selected). The report also contains a
grand total for all selected agents.
The Agent Average Calls per Hour, Bottom 5 report shows summarized
performance information for the five agents who accepted the least Contact
Center Manager, ACD, and NACD contacts. It provides details about contacts
accepted, average processing time, and average not ready time.
For more information, see “Understanding the report descriptions” on page 787.
Views
This report uses the AgentPerformanceStat view (see page 220.) For more
information about views, see “Access rights by view” on page 156.
Collection frequency
The following collection frequency types are available for this report:
daily
weekly
monthly
Templates
This report uses the following templates:
dm-agt11.rpt
wm-agt11.rpt
mm-agt11.rpt
Selection criteria
! "# $ "
BestAir
%&
)* ' (
*( "
! " +
"
*( " !
! " + -
" !
! " + -
" !
,
*( " !
! " + -
" !
,-010
" 2&&&
!.!
3)4567267 &2!!
#
The Agent Average Calls per Hour, Top 5 report shows summarized
performance information for the five agents who accepted the most Contact
Center Manager, ACD, and NACD contacts. It provides details about contacts
accepted, average processing time, and average not ready time.
For more information, see “Understanding the report descriptions” on page 787.
Views
This report uses the AgentPerformanceStat view (see page 220.) For more
information about views, see “Access rights by view” on page 156.
Collection frequency
The following collection frequency types are available for this report:
daily
weekly
monthly
Templates
This report uses the following templates:
dm-agt10.rpt
wm-agt10.rpt
mm-agt10.rpt
Selection criteria
! "# $ "
BestAir
%&
)* ' (
*( "# !"
! " +,-$ $ !+ -
"# !"
$
*( #* " "!'!
! " ,/- - + +! !
#* " "!'!
$+
*( #*! ''
$%-.
*( #! "' !'"
)$01
Use the Agent by Activity Code report to monitor each agent’s work and time
distribution by the types of contacts accepted. During the handling of contacts,
agents can identify the contact type by entering an activity (Line of Business)
code. Multiple codes can be used to reflect activities performed on a single
contact
On the Communication Server 2x00/DMS switch, agents cannot use the LOB
key while they are conferenced with another agent.
For more information, see “Understanding the report descriptions” on page 787.
Views
This report uses the ActivityCodeStat view (see page 188.) For more
information about views, see “Access rights by view” on page 156.
Collection frequency
The following collection frequency types are available for this report:
interval
daily
weekly
monthly
Templates
This report uses the following templates:
im-agt19.rpt
dm-agt19.rpt
wm-agt19.rpt
mm-agt19.rpt
Selection criteria
Statistics
Summaries
The report provides totals for each activity code, and subtotals for each day,
week, or month (depending on the reporting period selected). For the interval
reporting period, statistics are further broken down by interval. The report also
contains a grand total for all selected activity codes.
!"# "#$% &$ !"# "#$
BestAir
!"#$%&#
#
'
*
!"# "#$
,-./010
) # # +
( 4(/'/ + ! + ! +
( 5/-/0 3 +# 3 +# +
/0/) # # # #
*
/0/
& &! & &! +
/' 3 &+ 3 &+ +
4 ,-./( + +3 + +3 +
8* 5/-/0 6 $# #6 #
8* 5//0 +
. 5/-/0 & &
; ,-./( + & + &
) 3 $ 3 $
, /' # #
=2
/0/* +$ +$
5//0 & #3 & #3
,9 ,-./45< # ! # ! +
, 5//0 # & # &
!"# "#$
()
"%")*+,+,-. -
$
For more information, see “Understanding the report descriptions” on page 787.
Views
This report uses the AgentByApplicationStat (see page 197.) For more
information about views, see “Access rights by view” on page 156.
Collection frequency
The following collection frequency types are available for this report:
interval
daily
weekly
monthly
Templates
This report uses the following templates:
im-agt16.rpt
dm-agt16.rpt
wm-agt16.rpt
mm-agt16.rpt
Selection criteria
Statistics
Summaries
The report provides totals for each application, and subtotals for each agent. For
each agent, it breaks statistics down by day, week, or month, depending on the
reporting periods selected. For the interval reporting period, statistics are further
broken down by interval. The report also contains a grand total for all selected
applications.
Report (page 1 of 2)
)
' ( (
! "
#$
*
%&
%&"
%&.
%&
%&0
!"#!"$ # +, #+ $ # &# $#
%&34
!"#!"$ + . $, . $,
42($(776
Report (page 2 of 2)
!"#!"$% !"&!"$
BestAir
)
' ( (
%&344
%& 84
%&9
%&.1
(
! "
42($(776
For more information, see “Understanding the report descriptions” on page 787.
Views
This report uses the AgentBySkillsetStat view (see page 208.) For more
information about views, see “Access rights by view” on page 156.
Collection frequency
The following collection frequency types are available for this report:
interval
daily
weekly
monthly
Templates
This report uses the following templates:
im-agt14.rpt
dm-agt14.rpt
wm-agt14.rpt
mm-agt14.rpt
Selection criteria
Statistics
Summaries
The report provides totals for each skillset, and subtotals for each day, week, or
month (depending on the reporting period selected). For the interval reporting
period, statistics are further broken down by interval, and within each interval,
by agent. The report also contains a grand total for all selected skillsets.
!"#!"$% !"&!"$
BestAir
!"#"$
%&'
!"#!"$
)(
2
6
3(
3
.
( " 1 1& &# & "" "9 $4
- & "1 1 #& $1 &# $9 0
)( 1 1" 1 1 " 1 " "" "
# "& 1# 10 "" 9 "4 &# #$
6 1 9 && 9 && 9 &&
# "1 #9 #9 $& 1" 1 $ #
: # $9 #1 11 $& # $ 1 "$
3 # &# $# 19 #1 $ # 1 "&
) 1 " "& "$ 1 "$ 1 " "$ #&
!"#!"$ "1 $ 1 "4 " $ 11 9 #
!"#"$
!""#$%& '""#$%
BestAir
)* +*
( ( +,-
!"#"$
%&'()%!& &
./ !/$%
& $$0
1 & $ $ $3
4 & $$$ 0 $ ! $. $ $ 0 %0
, &$%.' %3 %! 3% 0 ' 0 $
&$ 00 ! $$ 03 % $$ 3' 0 5
&$%.5 3 0$ 0 $! %0 5 %.
)" & 0% $% % 5 0
$ .
) & % $0 3$ $. %5 % 3!
$$
./ !/$% %0 $ $0 *++
./ ./$%
&$%.5
1 & $ $ 3 . % 33 0 3% 3.
)" & $ 0 5 % %% $ %.
$ .
& $$0 $ 3 $ 3
&$ 00 ! $$ $ ! $. 0 3 3
) & . ! % $' 5 %$
$$
4 & $$$ % . %$ 3 0$ $ .
, &$%.' 3 ' % $ $ % $$ 3 '
./ ./$% - % % 5 *,-
!"#"$
* 6+
6(6"**6,66+
62&
3-+
Agent DN Performance
The Agent DN Performance report shows the amount of time that agents spend
on their personal or secondary directory numbers (DN). The report records
incoming and outgoing information, including the total number of DN calls and
the average amount of time spent on DN calls. On the Communication Server
1000\Meridian 1 PBX switch, the report also compares internal and external DN
call activity.
For more information, see “Understanding the report descriptions” on page 787.
Views
This report uses the AgentPerformanceStat view (see page 220.) For more
information about views, see “Access rights by view” on page 156.
Collection frequency
The following collection frequency types are available for this report:
interval
daily
weekly
monthly
Templates
This report uses the following templates:
im-agt5.rpt
dm-agt5.rpt
wm-agt5.rpt
mm-agt5.rpt
Selection criteria
Transfer/conference statistics
Summaries
The report provides totals for each agent, and subtotals for each day, week, or
month (depending on the reporting period selected). For the interval reporting
period, statistics are further broken down by interval. The report also contains a
grand total for all selected agents.
!""#
. . 0 . . ./ .1 / . 0
" , +
$!
&'
(
$!
,-
. 0 . . .
"
!""#
Communication Server 1000/Meridian 1 PBX report
+ 2 "3)24&)25+2)2"26)$22+.78.92*8:%
'
./0
11 2
831
Standard reports
Standard reports Standard 8.11
!!"
-.. , ,
-.-. " / ,,
- % . ##
-.. , , ,
-.-. / / /
#. )- -
!!"
# #$#%
) 0%
01(0+))0'00%
02!
*%
0,2
%3##3#.%)# (
This report uses agent elements, so only the agents assigned to a user appear on
report.
For more information, see “Understanding the report descriptions” on page 787.
Views
This report uses the AgentPerformanceStat view (see page 220.) For more
information about views, see “Access rights by view” on page 156.
Collection frequency
The following collection frequency types are available for this report:
daily
weekly
monthly
Templates
This report uses the following templates:
dm-agt7.rpt
wm-agt7.rpt
mm-agt7.rpt
Selection criteria
+#$! )#! & '( & & '( &
&'
(
,- $ $ $ $ $$$$$$ $ $$$$$$ $ $ $$$$$$ $ $$$$$$
,
&'
(
,- $ $ $ $ $$$$$$ $ $$$$$$ $ $ $$$$$$ $ $$$$$$
" $ $ $ $ $$$$$$ $ $$$$$$ $ $ $$$$$$ $ $$$$$$
" $ $ $ $ $$$$$$ $ $$$$$$ $ $ $$$$$$ $ $$$$$$
" $ $ $ $ $$$$$$ $ $$$$$$ $ $ $$$$$$ $ $$$$$$
2,
&'
(
.,
,- $ $ $ $ $$$$$$ $ $$$$$$ $ $ $$$$$$ $ $$$$$$
" $ $ $ $ $$$$$$ $ $$$$$$ $ $ $$$$$$ $ $$$$$$
+ . "/).0&).1+.).".2)$..+34536.*578%
'
!
56-06-$$*0 7 %-
835
Standard reports
836
Standard reports
BestAir
!"
#$
89::
$ $ $ $ $$$$$$ $ $$$$$$ $ $ $$$$$$ $ $$$$$$
+ . "/).0&).1+.).".2)$..+34536.*578%
'
!
56-06-$$*0 7 --
ATTENTION
This report uses agent elements, so only the agents assigned to
a user appear on report.
For more information, see “Understanding the report descriptions” on page 787.
Views
This report uses the AgentPerformanceStat view (see page 220.) For more
information about views, see “Access rights by view” on page 156.
Collection frequency
The following collection frequency types are available for this report:
daily
weekly
monthly
Templates
This report uses the following templates:
dm-agt6.rpt
wm-agt6.rpt
mm-agt6.rpt
Selection criteria
20
&
'
(
,- + ,$ - +++,) 1 +++)$* $* + ++++++ $* +++,*
3
&
'
,- , + ,+ + ++++++ ,+ +++%)+ $+ ++++1- , ++++%
+ 2 "3)24&)25+2)2"26)$22+.78.92*8:0%
04
-5$15$++#,* . ,$
839
Standard reports
840
Standard reports
+#$! )#! & '( & & '( &
829
* + $# ,, +++1,% ,- +++$$ ,1% # +++++- ,)- ++++),
+ 2 "3)24&)25+2)2"26)$22+.78.92*8:0%
04
-5$15$++#,* . $$
Agent Login/Logout
The Agent Login/Logout report shows logon, logoff, walkaway, return from
walkaway, ready, and not ready occurrences for each agent. The report also
shows the times at which these events occurred.
This report shows how much time agents spend at their stations during the day,
perhaps to help contact center management determine the total hours worked.
ATTENTION
Agent status information is written to the database every 15
minutes. This report shows agent status as of the end of the
last 15-minute interval.
For more information, see “Understanding the report descriptions” on page 787.
Views
This report uses the eAgentLoginStat view (see page 347.) For more information
about views, see “Access rights by view” on page 156.
Templates
Two templates for this report are available. If you have a version of Contact
Center Manager Server that is earlier than SU03, this report uses the
em-agt12.rpt template. If you have Contact Center Manager Server SU03 and
later, this report uses the em-agt12.rpt template found in the subfolder 60.
Selection criteria
Statistics
Date Timestamp
Time Time
Position ID PositionID
Report Creation Wizard formulas are not supported for this report.
Report examples
The first report example was generated on a Contact Center Manager Server 6.0
with an installed release that is earlier than SU03.
The second report example was generated on a Contact Center Manager Server
6.0 with SU03 or later.
e
BestAir
# %
& * # '()&#$ "! #$
!
" $
% ) " &'(%"# ! "#
* ! +,
* -%
-%
,
,+ ! #
+
+,
*
+
,+ ! +,
*
+
,+ -%
*
+
, -%
+, -%
+
! #
+
+, - *! $ $ !"#
%&'() . % #".*
For more information, see “Understanding the report descriptions” on page 787.
Views
This report uses the AgentPerformanceStat view (see page 220.) For more
information about views, see “Access rights by view” on page 156.
Collection frequency
The following collection frequency types are available for this report:
interval
daily
weekly
monthly
Templates
This report uses the following templates:
im-agt17.rpt
dm-agt17.rpt
wm-agt17.rpt
mm-agt17.rpt
Selection criteria
Statistics
Summaries
The report provides totals for each agent, and subtotals for each day, week, or
month (depending on the reporting period selected). For the interval reporting
period, statistics are further broken down by interval. The report also contains a
grand total for all selected agents.
BestAir
!"
#$
"
" '$'
%& %& %& () () () '! '!
'%! & & '%! & & #(
/ . , -
$ %
&
'
, ,
$ $
&(+
,
.
Agent Performance
You can use this report to compare overall productivity, measured by the time
agents spend at their positions and how often they are busy during a shift.
ATTENTION
Compare agents who have similar skillset assignments only,
as different contact types can require different service levels.
For more information, see “Understanding the report descriptions” on page 787.
Views
This report uses the AgentPerformanceStat view (see page 220.) For more
information about views, see “Access rights by view” on page 156.
Collection frequency
The following collection frequency types are available for this report:
interval
daily
weekly
monthly
Templates
This report uses the following templates:
im-agt1.rpt
dm-agt1.rpt
wm-agt1.rpt
mm-agt2.rpt
Selection criteria
Summary statistics
Agent statistics
Summaries
The report provides totals for each agent, and subtotals for each day, week, or
month (depending on the reporting period selected). For the interval reporting
period, statistics are further broken down by interval. The report also contains a
grand total for all selected agents.
!"!#
( 9 3&92%&9,(9&99:&99(4;<4=9)<#>47
-&./0(1(223
855
Standard reports
856
Standard reports
!"!#
( 9 3&92%&9,(9&99:&99(4;<4=9)<#>47
-&./0(1(223
BestAir
!*"
1 ,( *" .
) (" (" * + , , 0+ & (" * *" *
" 2
(
(
(
(
"- "- "- "- *" ! ! ,( /! !
!"#"$
* 9
"90("9+"!**999
9:&
5
(+,-
..)
857
Standard reports
858
!!"#$%& '!!"#$%
Standard reports
BestAir
1 ,( *" . !*"
) (" (" * + , , 0+ & (" * *" *
" 2
(
(
(
(
"- "- "- "- *" ! ! ,( /! !
!"#"$
Communication Server 2x00/DMS report (page 2 of 2)
* 9
"90("9+"!**999
9:&
5
(+,-
..)
For more information, see “Understanding the report descriptions” on page 787.
Views
This report uses the AgentPerformanceStat view (see page 220.) For more
information about views, see “Access rights by view” on page 156.
Collection frequency
The following collection frequency types are available for this report:
interval
daily
weekly
monthly
Templates
This report uses the following templates:
im-agt4.rpt
dm-agt4.rpt
wm-agt4.rpt
mm-agt4.rpt
Selection criteria
Time averages
Summaries
The report provides totals for each supervisor, and subtotals for each agent.
Agent statistics are further broken down by day, week, or month (depending on
the reporting period selected). For the interval reporting period, statistics are
further broken down by interval. The report also contains a grand total for all
selected agents.
& !" # ! !! !$ %" % ! ! & # % " !
'(
## ! % # % $ !% #
/ % # ,0,-1 1---1 !%
## ! % # % $ !% #
'(
! ! % ! ! #! %& !. . !! $ %% !
/ #& %# ,0,-1 1---1 $ !&
! ! % ! ! #! %& !. . !! $ %% !
Communication Server 1000/Meridian 1 PBX report (page 1 of 5)
% 7 ,'7(1'72%7'778'77%39:3;7&:#<$=
865
Standard reports
866
Standard reports
%& 2 1' % +%' 1' ' ' -** . / 01 ' 21(/ %& 1 2 2
'( '( '( % )* '( ' )* ,% -* * 1
" #. %. ! !$ #$ $ #
/ ,0,-1 1---1
3 $6 "6 4 $4 4 !! 3 ! $
! " '
/ %&%&1 1'1
" #. %. ! !$ #$ $ #
& %$ ! # % %& . $ $ !!
/ !# %& ,0,-1 1---1 %
& %$ ! # % %& . $ $ !!
'(
//
/ ,0,-1 1---1
Communication Server 1000/Meridian 1 PBX report (page 2 of 5)
% 7 ,'7(1'72%7'778'77%39:3;7&:#<$=
%& 2 1' % +%' 1' ' ' -** . / 01 ' 21(/ %& 1 2 2
'( '( '( % )* '( ' )* ,% -* * 1
! " ! 3 " $ $
! " '
/ %&%&1 1'1
. ! %% %& # $ ! #& # %# #
/ ! %% %& ,0,-1 1---1 ! #&
. ! %% %& # $ ! #& # %# #
!% %! %% ! % # !
/ ,0,-1 1---1
!% %! %% ! % # !
Communication Server 1000/Meridian 1 PBX report (page 3 of 5)
% 7 ,'7(1'72%7'778'77%39:3;7&:#<$=
867
Standard reports
868
Standard reports
%& 2 1' % +%' 1' ' ' -** . / 01 ' 21(/ %& 1 2 2
'( '( '( % )* '( ' )* ,% -* * 1
! & !" ! % $ % %# #
/ ,0,-1 1---1
! & !" ! % $ % %# #
# " ! # ! . %$ % % . # % % ! #
/ ! !. ,0,-1 1---1 " #
# " ! # ! . %$ % % . # % % ! #
/ ,0,-1 1---1
Communication Server 1000/Meridian 1 PBX report (page 4 of 5)
% 7 ,'7(1'72%7'778'77%39:3;7&:#<$=
%& 2 1' % +%' 1' ' ' -** . / 01 ' 21(/ %& 1 2 2
'( '( '( % )* '( ' )* ,% -* * 1
" $5 $$ ! $5 " !! ! !
! " '
/ %&%&1 1'1
/ %$ !& ,0,-1 1---1 !
'
& !" # ! !! !$ %" % ! ! & # % " !
Communication Server 1000/Meridian 1 PBX report (page 5 of 5)
% 7 ,'7(1'72%7'778'77%39:3;7&:#<$=
869
Standard reports
870
Agent Performance By Supervisor Sample
BestAir
!!"#$%& '!!"#$%
Standard reports
! " ' ( " " " ! #" !$%%## &"%"$% ""%' %" ""%""%"" ""%""%"" %$%$# ""%""%"" &% !%#$
)*% + #
! " ' ( " " " ! #" !$%%## &"%"$% ""%' %" ""%""%"" ""%""%"" %$%$# ""%""%"" &% !%#$
)*%,
* +
$ " 1 ( " " " $(%""%"" $%%$ ""% %$ ""%""%"" ""%""%"" " % #%$' ""%""%"" "%'#%$!
.
%" %"%" /0
%""%""%"" 00
%""%" %$(
$1 $1
23 3$%
"
.
(
*
*"
*
$ " 1 ( " " " $(%""%"" $%%$ ""% %$ ""%""%"" ""%""%"" " % #%$' ""%""%"" "%'#%$!
)*%2. + (
" " " " " " !% %' 1%##%$" ""%"% ( ""%""%"" ""%""%"" ""% %" ""%""%"" ""%$ % (
Communication Server 2x00/DMS report (page 1 of 5)
.
%"% 1%$( /0
%""%""%"" 00
%""%" %$'
4 4$ %5 $ % $ $ % 5 4
23 3$%
"
.
$ 4$ (
*
*"
*
4
( 6
"6)*"6."!((666
67&
18
BestAir
!!"#$%& '!!"#$%
$ % 42 %5 % $2 $ % %% 1 2
2323$%
"
.
11 (
*
*"
*
$ %2
" " " " " " !% %' 1%##%$" ""%"% ( ""%""%"" ""%""%"" ""% %" ""%""%"" ""%$ % (
& " " " " " " " '% $%'" % '% ' ""%"%( ""%""%"" ""%""%"" " %$$%' ""%""%"" "% %#(
.
%""%$% /0
%""%""%"" 00
%""%"&%#
% 5 $ 1$ 1 %2 5 4% $2 %5 %' %
23 3$%
"
.
%' 4' (
*
*"
*
% 1
& " " " " " " " '% $%'" % '% ' ""%"%( ""%""%"" ""%""%"" " %$$%' ""%""%"" "% %#(
)*%
+
#& " $ ' " " " $ $"%%'( #$% &%'1 ""% $%' ""%""%"" ""%""%"" "% %$$ ""%""%"" "%$%"!
Communication Server 2x00/DMS report (page 2 of 5)
.
%""%'1%"( /0
%""%""%"" 00
%""%"#%$"
4 4 1 $ 5 $$ %2 1 % $ 4 $ $ 1 %
23 3$%
"
.
$$ 45 (
*
*"
*
4 %4
( 6
"6)*"6."!((666
67&
18
871
Standard reports
872
Agent Performance By Supervisor Sample
BestAir
Standard reports
% 4 $1 $$ 45 5 $ $ 4$ 14 '
2323$%
"
.
1 4 4 (
*
*"
*
$ 2
#& " $ ' " " " $ $"%%'( #$% &%'1 ""% $%' ""%""%"" ""%""%"" "% %$$ ""%""%"" "%$%"!
)*% + #
" " " " " " " $(%""%"" $1%$"%#! ""%""%( ""%""%"" ""%""%"" ""%"%"$ ""%""%"" ""% &%$!
.
%$1%$"%#! /0
%""%""%"" 00
%""%"%"$
$1 $1
23 3$%
"
.
(
*
*"
*
$ $1 $4 1 4' $2 $ 1 5 1'
2323$%
"
.
$4 1 4' (
*
*"
*
$ 1
" " " " " " " $(%""%"" $1%$"%#! ""%""%( ""%""%"" ""%""%"" ""%"%"$ ""%""%"" ""% &%$!
)*%40* + ##
$ " # # " " " " $(%""%"" $'% $% ""%"#% ""%""%"" ""%""%"" ""%' %" ""%""%"" " %#%"
Communication Server 2x00/DMS report (page 3 of 5)
.
%"#% #%' /0
%""%""%"" 00
%""%"#%$"
$ $ $ $1 $$ 1 44 1 $$ 1' 15
23 3$%
"
.
4 1 $$ (
*
*"
*
4 5
( 6
"6)*"6."!((666
67&
18
BestAir !!"#$%& '!!"#$%
$1 $$ 44 42 4 $2 4 1% 1%
2323$%
"
.
4 4 $4 (
*
*"
*
1 1
$ " # # " " " " $(%""%"" $'% $% ""%"#% ""%""%"" ""%""%"" ""%' %" ""%""%"" " %#%"
$ " " " " " " '%"$%& $% %" ""%""%$' ""%""%"" ""%""%"" ""%1%'# ""%""%"" ""%$%$&
.
%"&%"%$& /0
%""%""%"" 00
%""%"&%'(
1 2 1 1 1 $4 1% $ %4 $1 15
23 3$%
"
.
%5 % (
*
*"
*
5 %2
5 $4 4' 5 $4 4'
2323$%
"
.
(
*
*"
*
$ " " " " " " '%"$%& $% %" ""%""%$' ""%""%"" ""%""%"" ""%1%'# ""%""%"" ""%$%$&
)*%
+'(!
!' " " " " " $"%(%1 1%!%$1 ""% '%'$ ""%""%"" ""%""%"" "'%'"%# ""%""%"" "'%'$%"#
Communication Server 2x00/DMS report (page 4 of 5)
.
%""% 1% /0
%""%""%"" 00
%""%"#%$
%1 2 5 $2 $ % 1 2 %1 4 ' $ %% 4
23 3$%
"
.
4 (
*
*"
*
4 $
( 6
"6)*"6."!((666
67&
18
873
Standard reports
874
Agent Performance By Supervisor Sample
BesstAir !!"#$%& '!!"#$%
Standard reports
1 4 4 $ $1 $1 $ % $$ $ %2 4$
2323$%
"
.
$% $2 (
*
*"
*
1 '
!' " " " " " $"%(%1 1%!%$1 ""% '%'$ ""%""%"" ""%""%"" "'%'"%# ""%""%"" "'%'$%"#
! ! " ' ( " " " ! #" !$%%## &"%"$% ""%' %" ""%""%"" ""%""%"" %$%$# ""%""%"" &% !%#$
"
! " ' ( " " " ! #" !$%%## &"%"$% ""%' %" ""%""%"" ""%""%"" %$%$# ""%""%"" &% !%#$
Communication Server 2x00/DMS report (page 5 of 5)
( 6
"6)*"6."!((666
67&
18
The Agent Performance Calls Answered, Bottom 5 report is a daily report that
shows summarized performance information for the five agents who accepted
the lowest number of Contact Center Manager contacts.
For more information, see “Understanding the report descriptions” on page 787.
Views
This report uses the AgentPerformanceStat view (see page 220.) For more
information about views, see “Access rights by view” on page 156.
Collection frequency
This report contains data that is collected daily.
Templates
This report uses the dm-agt3.rpt template.
Selection criteria
% ' &( ) &(
.% .% .% &% &( &( .%
% & % & % % ) *+ % & % , - /. % 0.1- . . 0
*)
*)
0
) ### %2'-(% ### ### ### ### %%%%%% %%%%%% ###
! "
" 2 3 $ 2 24 5
% % % % % % % % % % % %2'%& %2'-(% %%%&%% %%%%%% %%%%%% %%%%%% %%%%%% %%%%%% %%&$',
) ### %2'-(% ### ### ### ### %%%%%% %%%%%% ###
*)
0
) ### %2&%, ### ### ### ### %%%%%% %%%%%% ###
! "
2 "5 2 "5
% % % % % % % % % % % %2&%, %2&%, %%%%%% %%%%%% %%%%%% %%%%%% %%%%%% %%%%%% %%%%%%
) ### %2&%, ### ### ### ### %%%%%% %%%%%% ###
Communication Server 1000 report/Meridian 1 PBX (page 1 of 2)
877
Standard reports
878
Standard reports
% ' &( ) &(
.% .% .% &% &( &( .%
% & % & % % ) *+ % & % , - /. % 0.1- . . 0
*)
5
% % % % % % % % % & % '1$( '1$( %%%%%% %%%%%% %%%%%% %%%%%% %%%%%% %%%%%% %%%%%%
) ### '1$( ### ### ### ### %%%%%% %%%%%% ###
! "
2 ! "4 "$ ! "4 "$
% % % % % % % % % & % '1$( '1$( %%%%%% %%%%%% %%%%%% %%%%%% %%%%%% %%%%%% %%%%%%
) ### '1$( ### ### ### ### %%%%%% %%%%%% ###
7
*)
5
% % % % % % % % % & % '(%%%% '1$2 %%%%%% %%%%%% %%%%%% %%%%%% %%%%%% %%%%%% %%%%%'
) ### '1$2 ### ### ### ### %%%%%% %%%%%% ###
! "
2 $ ! "4 "
% % % % % % % % % & % '(%%%% '1$2 %%%%%% %%%%%% %%%%%% %%%%%% %%%%%% %%%%%% %%%%%'
) ### '1$2 ### ### ### ### %%%%%% %%%%%% ###
789
% % % % % % % % % ' % 2$%'& ,(12'2 %%%&%% %%%%%% %%%%%% %%%%%% %%%%%% %%%%%% '(&$'2
) ### ,(12'2 ### ### ### ### %%%%%% %%%%%% ###
Communication Server 1000 report/Meridian 1 PBX (page 2 of 2)
BestAir
!!"#$%& '!!"#$%
) *
-" -" -" (" (
( -" 0
" (
" " "
* ! " (
" + , .-/,
-
- . .
+)
,
!# * % % % $ ## !# & % !&%%%% !$$$!# %%##$! %%%%%% %%%%%% %##'! %%%%%% %$'!(
23 3$%
$1 $1
2323$%
1 $ 1 2 $1 2 $$ 1 $1 4 1% $ %4 1'
!# * % % % $ ## !# & % !&%%%% !$$$!# %%##$! %%%%%% %%%%%% %##'! %%%%%% %$'!(
) &&& %#%$%# &&& &&& %%%%%% %%%#!& &&& &&&
-)
+)
0
Communication Server 2x00/DMS report
!& $% % % % % #$ !& $# % $!'('' #$!!& %%#%#$ %%%%%% %%%%%% %#!$!$ %%%%%% %/*
) &&& %%#* &&& &&& %%%%%% %%%$%& &&& &&&
23 3$%
4$ ' 5 4$ ' 12 14 5 5 4$ 1% 1 $$ 2
2323$%
5 5 5 $ 5 % 44 $ 4$ 4 1 4 % $ 4% 1
!& $% % % % % #$ !& $# % $!'('' #$!!& %%#%#$ %%%%%% %%%%%% %#!$!$ %%%%%% %/*
) &&& %%#* &&& &&& %%%%%% %%%$%& &&& &&&
-,12
&( $* % % % $ $' &( $( % *$'('' %&$( %%$#'/ %%%%%% %%%%%% %$/$* %%%%%% %(#!!
) &&& %%'*#% &&& &&& %%%%%% %%%#( &&& &&&
( 6
"6/-"6,"!((666
67&
48
3
&4$$4$%%#$#% #
#
879
Standard reports
Standard reports Standard 8.11
The Agent Performance Calls Answered, Top 5 report is a daily report that
shows contact center managers summarized performance information for the
five agents who accepted the highest number of Contact Center Manager
contacts.
For more information, see “Understanding the report descriptions” on page 787.
Views
This report uses the AgentPerformanceStat view (see page 220.) For more
information about views, see “Access rights by view” on page 156.
Collection frequency
This report contains data that is collected daily.
Templates
dm-agt2.rpt
Selection criteria
Summaries
The fields in this report are identical to those in the Agent Performance report
(see page 827), except that they are for the five agents who accepted the highest
number of Contact Center Manager contacts. Statistics are summarized in the
same way as for the Agent Performance report.
% ' &( ) &(
.% .% .% &% &( &( .%
% & % & % % ) *+ % & % , - /. % 0.1- . . 0
+
!,
& ( & & & & ' & & ( & ''$#(% &$&#$& &''(* &&&&&& &&&%* &&&&&& &&&&&& &((#$' &%($$
+ ### &&&$%) ### ### ### ### &&&&&& &&&(# ###
! "
" 2 " 22 !3 $ ! 3 ! 2 2" " $ 3 !2 $ ! "!
& ( & & & & ' & & ( & ''$#(% &$&#$& &''(* &&&&&& &&&%* &&&&&& &&&&&& &((#$' &%($$
+ ### &&&$%) ### ### ### ### &&&&&& &&&(# ###
+
!,
% $ & & & & & & % $ & &*$%'% &'%(' &'&$'* &&&&&& &&&%' &&&&&& &&&&&& &$()$$ &(&$$%
+ ### &&&($( ### ### ### ### &&&&&& &&&%$) ###
! "
$" ! $" ! !$ 2$ 2 "$ 2 2 ! 2 $ 2" ! 4 !! ! !$
% $ & & & & & & % $ & &*$%'% &'%(' &'&$'* &&&&&& &&&%' &&&&&& &&&&&& &$()$$ &(&$$%
+ ### &&&($( ### ### ### ### &&&&&& &&&%$) ###
+
!,
%( ( & & & & & & %( ( & &*&#&( &(&%$ &&$/ &&&&&& &&&%( &&&&&& &&&&&& &$&/%% &'/$%
+ ### &&&$&& ### ### ### ### &&&&&& &&&%() ###
! "
$ $ 3 " $! "" !5 $ " ! 5 $$ 2 "5 !$
%( ( & & & & & & %( ( & &*&#&( &(&%$ &&$/ &&&&&& &&&%( &&&&&& &&&&&& &$&/%% &'/$%
+ ### &&&$&& ### ### ### ### &&&&&& &&&%() ###
Communication Server 1000/Meridian 1 PBX report (page 1 of 2)
0,*1(%1(&&/'/% '
(
% ' &( ) &(
.% .% .% &% &( &( .%
% & % & % % ) *+ % & % , - /. % 0.1- . . 0
2+
%' ' & & & & & ' %' ' & &)/( &((/% &'&(# &&&&&& &&&$) &&&&&& &&&&&& &('&') &(&'*
+ ### &&&$$ ### ### ### ### &&&&&& &&&$'' ###
! "
$2 2 2 $2 2 4 "5 " 5 "$ 2 "3 " !4 2 24 2 "
%' ' & & & & & ' %' ' & &)/( &((/% &'&(# &&&&&& &&&$) &&&&&& &&&&&& &('&') &(&'*
+ ### &&&$$ ### ### ### ### &&&&&& &&&$'' ###
+
!,
$* & & & & & & & $* & & &*(*% &'(/( &&%&# &&&&&& &&&%(# &&&&&& &&&&&& &%'%# &'%(%
+ ### &&&(') ### ### ### ### &&&&&& &&&/%% ###
! "
! ! "$ 2 5 " "$ 3 $ 3 $ 2" $3 2 $" $
$* & & & & & & & $* & & &*(*% &'(/( &&%&# &&&&&& &&&%(# &&&&&& &&&&&& &%'%# &'%(%
+ ### &&&(') ### ### ### ### &&&&&& &&&/%% ###
456
('/ * & & & & ' ' ('/ * & %%%)# ''&$(& &''$& &&&&&& &&(%$% &&&&&& &&&&&& '(#% '(''($
+ ### &&&$&% ### ### ### ### &&&&&& &&&%'* ###
Communication Server 1000/Meridian 1 PBX report (page 2 of 2)
0,*1(%1(&&/'/% (
(
883
Standard reports
884
Agent Performance Calls Answered Top 5
Standard reports
BestAir
!!"#$%& '!!"#$%
) *
-" -" -" (" (
( -" 0
" (
" " "
* ! " (
" + , .-/,
-
- . .
,
$& %' ' ' ' ' (% $& %( ' %$)#)) (%$$& ''('(% '''''' '''''' '($%$% '''''' '+*
45 5$%
1$ ' 2 1$ ' 34 31 2 2 1$ 3% 3 $$ 4
4545$%
2 2 2 $ 2 % 11 $ 1$ 1 3 1 % $ 1% 3
$& %' ' ' ' ' (% $& %( ' %$)#)) (%$$& ''('(% '''''' '''''' '($%$% '''''' '+*
&&& ''(* &&& &&& '''''' '''%'& &&& &&&
-
/
Communication Server 2x00/DMS report
$( * ' ' ' % (( $( & ' $&'''' $%%%$( ''((%$ '''''' '''''' '(()$ '''''' '%)$#
45 5$%
$3 $3
4545$%
3 $ 3 4 $3 4 $$ 3 $3 1 3% $ %1 3'
$( * ' ' ' % (( $( & ' $&'''' $%%%$( ''((%$ '''''' '''''' '(()$ '''''' '%)$#
&&& '('%'( &&& &&& '''''' '''($& &&& &&&
/12
&# %* ' ' ' % %) &# %# ' *%)#)) '&%# ''%()+ '''''' '''''' '%+%* '''''' '#($$
&&& '')*(' &&& &&& '''''' '''(# &&& &&&
( 6
"6/-"6,"!((666
67&
$8
03
&4%%4%''(%))'. (
(
The Agent Short Calls report shows summarized information about short call
performance, grouping the data into supervisor and agent summaries.
This report also itemizes Contact Center Manager and ACD calls that are
answered, transferred, conferenced, and returned to queue.
For more information, see “Understanding the report descriptions” on page 787.
A large number of short calls may suggest a need for further training.
Views
This report uses the AgentPerformanceStat view (see page 220.) For more
information about views, see “Access rights by view” on page 156.
Collection frequency
The following collection frequency types are available for this report:
interval
daily
weekly
monthly
Templates
This report uses the following templates:
im-agt8.rpt
dm-agt8.rpt
wm-agt8.rpt
mm-agt8.rpt
Selection criteria
Statistics
Summaries
The report provides totals for each supervisor, and subtotals for each agent.
Agent statistics are further broken down by day, week, or month (depending on
the reporting period selected). For the interval reporting period, statistics are
further broken down by interval. The report also contains a grand total for all
selected agents.
%&' -' -' -' * ' &,&, *)
'( '( & ' )** +& '( ,** '( & '
!
"
*.
*.
! " / ! / ! ! /
*'
Communication Server 1000/Meridian 1 PBX report
"*&
(+),+)-. - /# / 0
889
Standard reports
890
Agent Short Calls Sample
!!"#$%& '!!"#$%
Standard reports
BestAir
()" ," ," ," ! ) !+
"* "* )
"
+!! "* !
! "* )
"
!
"#$
!- (' '' ('
"#$)!
!- (' '' ('
./ /$%
././$% 0 $ 0 .
(' '' ('
!" (' '' ('
Communication Server 2x00/DMS report (page 1 of 2)
) 1
"1*,"1-"!))111
12&
.3
+
!,%-$.
//0'$$+* +' 1
()" ," ," ," ! ) !+
"* "* )
"
+!! "* !
! "* )
"
!
"#$2!
!2 ,&('(
!- ( ' ( '
Communication Server 2x00/DMS report (page 2 of 2)
) 1
"1*,"1-"!))111
12&
.3
+
!,%-$.
//0'$$+* + 1
891
Standard reports
Standard reports Standard 8.11
This report helps managers identify agents who may have difficulty with a
specific skill. It can also highlight agents who need additional training or
reassignment to a different skillset.
For more information, see “Understanding the report descriptions” on page 787.
Views
This report uses the AgentPerformanceStat view (see page 220.) For more
information about views, see “Access rights by view” on page 156.
Collection frequency
The following collection frequency types are available for this report:
interval
daily
weekly
monthly
Templates
This report uses the following templates:
im-agt18.rpt
dm-agt18.rpt
wm-agt18.rpt
mm-agt18.rpt
Selection criteria
Summaries
The report provides totals for each agent, and subtotals for each day, week, or
month (depending on the reporting period selected). For the interval reporting
period, statistics are further broken down by interval. The report also contains a
grand total for all selected agents.
+% &' ' +% &' ' % % % % & & & & &%* % &
% % % & & & &' ' &' () &' ' &' () (* (*
! "
! " - -
Communication Server 1000/Meridian 1 PBX report
!!"#$%& '!!"#$%
e BestAirstAir
*" ( *" (
"
"
"
" ( ( ( (
" (
"
"
" ( ( ( ( ( ) ( ( ) ! !
! ! ! "# ! " ! ! ! ! ! ! ! "$ ! "$
%&'(
!+ ! ! ! # ! , ! ! ! ! ! ! ! - ! -
%&'
!+ ! ! ! "! ! , ! ! ! ! ! ! ! ", ! ",
! ! ! "# ! " ! ! ! ! ! ! ! "$ ! "$
( .
"./*".+"!((...
.0&
,1
899
Standard reports
Standard reports Standard 8.11
The Estimated Revenue by Agent report shows the amount of revenue each
agent generates based on the total number of contacts accepted and the number
of times a specified activity code is recorded.
For user-defined reports that use this report as a template, you can set a dollar
value to multiply against activity code occurrences. This report is a useful
feature for contact centers that offer revenue-based incentives.
ATTENTION
This report does not include Not Ready reason codes.
For standard reports, localized currency is used.
For more information, see “Understanding the report descriptions” on page 787.
Views
This report uses the ActivityCodeStat view (see page 188.) For more
information about views, see “Access rights by view” on page 156.
Collection frequency
The following collection frequency types are available for this report:
daily
weekly
monthly
Templates
This report uses the following templates:
dm-agt13.rpt
wm-agt13.rpt
mm-agt13.rpt
Selection criteria
Statistics
Summaries
The report provides totals for each agent, and subtotals for each activity code.
For each activity code, statistics are further broken down by day, week, or
month, depending on the reporting period selected. The report also contains a
grand total for all selected agents.
BestAir ! "#$ %! "#
)(
&'( '*
With the Not Ready Reason Codes by Agent report you monitor why agents
went into Not Ready state. You can define Not Ready reason codes in Contact
Center Manager Administration. When an agent goes into Not Ready state and
enters one of these codes, the incident pegs in the ActivityCodeStat view.
For more information, see “Understanding the report descriptions” on page 787.
Views
This report uses the ActivityCodeStat view (see page 188.) For more
information about views, see “Access rights by view” on page 156.
Collection frequency
The following collection frequency types are available for this report:
interval
daily
weekly
monthly
Templates
This report uses the following templates:
im-agt20.rpt
dm-agt20.rpt
wm-agt20.rpt
mm-agt20.rpt
Selection criteria
Statistics
Summaries
The report provides totals for each agent, and subtotals for each day, week, or
month (depending on the reporting period selected). For the interval reporting
period, statistics are further broken down by interval. The report also contains a
grand total for all selected agents.
' )
"$!%" ( &##'#!
+"$+,)'+!+%" * * * *
"$
'$ $ #
+"$+,)'+!+%" * -
"$ $ #
For more information, see “Understanding the report descriptions” on page 787.
Views
This report uses the AgentBySkillsetStat view (see page 208.) For more
information about views, see “Access rights by view” on page 156.
Collection frequency
The following collection frequency types are available for this report:
interval
daily
weekly
monthly
Templates
This report uses the following templates:
im-agt21.rpt
dm-agt21.rpt
wm-agt21.rpt
mm-agt21.rpt
Selection criteria
Statistics
Summaries
The report provides totals for each agent, and subtotals for each day, week, or
month (depending on the reporting period selected). For the interval reporting
period, statistics are further broken down by interval, and within each interval,
by agent. The report also contains a grand total for all selected skillsets.
Report (page 1 of 4)
!"#!"$% !"&!"$
BestAir
! "
#$%
&'
, $ $# $#% $'
!"#!"$
(*)/ # ". #- #- $& . #0 $1
!"#!"$ # ". #- #- $& . #0 $1
"(
)*&'
, $ #$ % '%'
!"#!"$
(*)/ # $- #. .. $& 1 & 1
!"#!"$ # $- #. .. $& 1 & 1
++
&'
, % %%
!"#!"$
(*)/ . " "& "$ . . && ".
!"#!"$ . " "& "$ . . && ".
&'
, $ %$ ' $
!"#!"$
(*)/ # "& .# .1 "" . .# $
!"#!"$ # "& .# .1 "" . .# $
,-.&'$
,
!"#!"$
(*)/ "0 ."
!"#!"$ "0 ."
/&'$'
, %''
!"#!"$
(*)/ &1 $1
!"#!"$ &1 $1
0
1.
23%3#$, %
Report (page 2 of 4)
!"#!"$% !"&!"$
BestAir
-
4
5&'%
,
!"#!"$
(*)/ .. ." $$
!"#!"$ .. ." $$
-4.
&'#
, $ %$$ #$ #
!"#!"$
(*)/ # &# $# .- #. 0 $- "
!"#!"$ # &# $# .- #. 0 $- "
!"#!"$
(*)/ .# "$ $"
!"#!"$ .# "$ $"
8
64&'$
, #%#
!"#!"$
(*)/ - &" "-
!"#!"$ - &" "-
,
&'%
, $
!"#!"$
(*)/ . # .0
!"#!"$ . # .0
!"#!"$
(*)/ . $- &
!"#!"$ . $- &
0
1.
23%3#$, %
Report (page 3 of 4)
!"#!"$% !"&!"$
BestAir
811-4
&'
, #%% %$
!"#!"$
(*)/ . - && &#
!"#!"$ . - && &#
4&''
, % %$
!"#!"$
(*)/ " . .& &# ". $
!"#!"$ " . .& &# ". $
71
&'%$
, % $% %
!"#!"$
(*)/ & ". . #& $. ". &
!"#!"$ & ". . #& $. ". &
2
04&'%%
, %%%
!"#!"$
(*)/ $ &0 &&
!"#!"$ $ &0 &&
+40
&''
,
!"#!"$
(*)/ . " .
!"#!"$ . " .
+400&'$
, $%
!"#!"$
(*)/ . ." . . " #" &.
!"#!"$ . ." . . " #" &.
0
1.
23%3#$, $%
Report (page 4 of 4)
!"#!"$% !"&!"$
BestAir
! "
#$%
0
1.
23%3#$, %%
In this section
Call by Call Statistics 914
For each contact, the Call by Call Statistics report shows detailed information
including time, event, agent, source, and destination.
You can collect contact information from the time the contact is initiated until
the time it leaves Contact Center Manager control. You can collect statistics for
all of the events defined in Historical Statistics Collection.
For additional Call by Call details about outbound campaign contacts, see
“Campaign Call by Call Details” on page 1166.
The Call by Call Statistics report includes event information from a specific day.
The report can be generated for a maximum one–hour period on that day.
Call by Call Statistics reports contain a large amount of data. Consequently, they
take much longer to generate than other types of reports. Event information is
written to the database every 15 minutes.
For more information, see “Understanding the report descriptions” on page 787.
Views
This report uses the following views:
eCallByCallStatYYYYMMDD (see page 351)
Agent (see page 382)
For more information about views, see “Access rights by view” on page 156.
Collection frequency
This report contains interval data.
Templates
Two templates for this report are available. If you have a version of Contact
Center Manager Server that is earlier than SU03, this report uses the em-res9.rpt
template. If you have Contact Center Manager Server SU03 and later, this report
uses the em-res9.rpt template found in the subfolder 60.
Selection criteria
none eCallByCallStatYYYYMMDD.TelsetLoginID
*= Agent.TelsetLoginID
eCallByCallStatYYYYMMDD.Timestamp
Statistics
Grouping
Events in the Call by Call Statistics report are grouped by call ID.
Report examples
The first report example that follows was generated on a Contact Center
Manager Server 6.0 with an installed release that is earlier than SU03.
The second report example that follows was generated on a Contact Center
Manager Server 6.0 with SU03 or later.
! (
) ) * (
3 # * ,) 5+ 1(;34--+ 6
4 #* ,) 5+ '
")/ 011
2 **
' ) 011 #
3435-3- 1677
'6) '
1)#
* 011 (
8
#
3435-3-
3435-3- #1
34-
'(66>
+
")/ 011
+ 2 **
' ) 011 #
3435-3- 1677
'6) '
+ 1)#
* 011 (
8
#
3435-3-
3435-3- #1
34
/92 **:: 011
/92 **:: 011
) :9* 011 1677
'6) 1677
'#26
>*/ 011 1677
'#26 86(
'#266/ 7
6'(6>0(0(66
8(
&(
+
011 1677
'#26 (
5
' ) 011 1677
'#26 (
5
#!* 011 (
1677
'#26 0
+
4 1)#" * * 011
+
4
' )#!* 011 (
1677
'#26 0
3
917
Standard reports
918
!
BestAir
Standard reports
+
")/ 011
+
2 **
' ) 011 #
3435-3 1677
'6) '
+
1)#
* 011 (
8
#
3435-3
3435-3 #1
34
+
/92 **:: 011
+
+
/92 **:: 011
+
+
+
) :9* 011 1677
'6) 1677
'#26'67#
+
>*/ 011 1677
'#26'67# 86(
'#26'6##6/ 7
6'(6>0(0(66
8(
&(
+
011 1677
'#26'67# (
+
3
#!* 011 (
1677
'#26'67# 0
+
-
' ) 011 1677
'#26'67# (
+
- #7 * 011
+
- =*!/ 011 86(
'#26'6##6/ 7
(
7(((
'(66>
-
+
' )#!* 011 (
1677
'#26'67# 0
+
1)# 9* A !'+ 86(
'#26'6##6/
+
1)#* A !'+ '
+
")/ 011
+ 2 **
' ) 011 #
3435-3 1677
'6) '
+ 1)#
* 011 (
8
#
3435-3
34355 #1
34
#7 * 011
Call By Call report – example 1(page 15 of 16)
! (
) ) * (
5
3
")/ 011
5
3 2 **
' ) 011 #
3435-3- 1677
'6) '
5
3 1)#
* 011 (
8
#
3435-3-
3435-3- #1
34
5
+ #7 * 011
5+
5
+ /92 **:: 011
5
+ /92 **:: 011
5
+ ) :9* 011 1677
'6) 1677
'#26
5
+ =*!/ 011 86(
'#266/ 7
(
7(((
919
Standard reports
920
Standard reports
!"
#
" '% $ %&$ #
$
$0#449
,
1 /% (& 6 24#
0#4'4) "
,
/%& 6 *0
In this section
Activity Code Properties 923
Agent by Supervisor Properties 925
Agent Properties 928
Agent Skillset Assignment 935
Agent Skillset Properties 938
Agent Supervisor Assignment 942
Application Script Properties 945
Application Template Properties 948
CDN (Route Point) Properties 951
Database View Definitions 954
DNIS Properties 958
Formula Properties 961
Historical and Real Time Statistics Properties 964
IVR Port Properties 976
IVR Queue and Port Properties 979
Logged In Agent Position ID 983
Crosstab - Network Incoming Calls 1045
Route Properties 990
Script Variable by Script 993
Script Variable Properties 996
Skillset Properties 999
Supervisor Properties 1004
Telephone Display Properties 1008
The Activity Code Properties report lists all of the activity codes and their
assigned names.
For more information, see “Understanding the report descriptions” on page 787.
Views
This report uses the ActivityCode view (see page 381.) For more information
about views, see “Access rights by view” on page 156.
Templates
This report uses the config8.rpt template.
Selection criteria
Statistics
BestAir
!"#$$
$"
!"%&"
&
"'("
"
"'("
"
* !"%&"
)
+$
+
,& +-
+.. +.
$+/
+.+
012+34567
The Agent by Supervisor Properties report lists agents and the supervisors to
whom they are assigned.
ATTENTION
Agents created from the Classic Client on Symposium
Contact Center Client 5.0 can have a primary supervisor
and reporting supervisors. Agents created in Contact Center
Manager Administration cannot. Therefore, an agent
created in Classic Client may appear multiple times in the
report.
For more information, see “Understanding the report descriptions” on page 787.
Views
This report uses the SupervisorAgentAssignment view (see page 482.) For more
information about views, see “Access rights by view” on page 156.
Templates
This report uses the config31.rpt template.
Selection criteria
Statistics
BestAir
!
"
#
4
5
4
2+4/
44
4
%44 3
6$37485#*(39
%&
'
&%$$($)(*++,,+",)-
$$
Agent Properties
For more information, see “Understanding the report descriptions” on page 787.
Views
This report uses the following views:
Agent (see page 382)
SupervisorAgentAssignment (see page 482)
For more information about views, see “Access rights by view” on page 156.
Templates
This report uses the config5.rpt template.
Selection criteria
General fields
Phoneset fields
Supervisor fields
Agent capabilities
BestAir
7
88/
&
! 9
"
#$
%
&
#
%
'
( :;
)$
*
/!
&
./
,
-$
+
*
*
0
( 12
#
*
//
#
*
#
*
(
*
0
( !
=
=
#$='
==
=.
== :
>):?=&(7@A
! "
##
//*+,-
)
#
)
#
)
!).0
2-
!
"#$
&'
&' (&
'
%
$
7
#$
#$1
*+,-
(&
' 4564-4*+,-
($#&& *+,-
($#
!).0 3
($ 2
#$1
'
+25+
)8#
8"8 '
)
)
8(
88#8) 9:#
!"#!"$% ""
The Agent Skillset Assignment report lists scheduled changes of agents and
their skillset assignments.
For more information, see “Understanding the report descriptions” on page 787.
Views
This report uses the ScheduledSkillsetAssignment view (see page 451.) For
more information about views, see “Access rights by view” on page 156.
Templates
This report uses the config24.rpt template.
Selection criteria
Statistics
BestAir
!
" #
$
)* #
# '
$
)* #
# '
#
)* #
# '
)* #
# '
!
" #
2
3
,
4
$
)* #
# /
$
)* #
# /
#
)* #
# /
)* #
# /
5
6
5
)5.
53353
5+
535 /
74/85 96:;'1<
! "##$%$"
The Agent Skillset Properties report lists general agent information and skillset
assignments. General information includes department, title, and assigned
templates. Skillset information includes the skillset name and the agent’s priority
within the skillset.
For more information, see “Understanding the report descriptions” on page 787.
Views
This report uses the following views:
Agent (see page 382)
SkillsetByAgent (see page 471)
Skillset (see page 467)
For more information about views, see “Access rights by view” on page 156.
Templates
This report uses the config29.rpt template.
Selection criteria
Statistics
BestAir
#
!!
"
#$
&
' %
('#) &
' %
)
&!
&
' %
* %+ &
' %
* + &
' %
&
' %
$
' &
' %
* &
' %
* %+ &
' %
* + &
' %
&
' %
$
' &
' %
* &
' %
, &
' %
, &
' %
* &
' %
* &
' %
,- &
' %
,- &
' %
.
/
.
).0
.""."
.1
&.". 2
3*24.(/,5%67
!"#"#$!%& '
&&
!
""#
!
! %
& $
!"#
!
""#
!
! %
& $
"!((
""#
' %
& $
) * #"
!
""#
%
& $
(
()( *
+
&(%
(((!',-
%,-
"..//!!(
For more information, see “Understanding the report descriptions” on page 787.
Views
This report uses the following views:
ScheduledSupervisorAssignment (see page 454)
SupervisorAgentAssignment (see page 482)
For more information about views, see “Access rights by view” on page 156.
Templates
This report uses the config23.rpt template.
Selection criteria
Statistics
BestAir
!"
(
(
$$
$$
34
4 #*4/4445
44.666 7-.849 :;,+<
!"!##$%%%&' '
For more information, see “Understanding the report descriptions” on page 787.
Views
This report uses the ApplicationByScript view (see page 389.) For more
information about views, see “Access rights by view” on page 156.
Templates
This report uses the config14.rpt template.
Selection criteria
Statistics
BestAir
!""!
#$#
%!&'(#
)*+
(')- #/
!
The Application Template Properties report lists all your applications. For each
application, it provides the service level threshold, threshold class, and threshold
levels.
For more information, see “Understanding the report descriptions” on page 787.
Views
This report uses the following views:
Application (see page 387)
ApplicationThresholdTemplate (see page 392)
For more information about views, see “Access rights by view” on page 156.
Templates
This report uses the config15.rpt template.
Selection criteria
Statistics
BestAir
&'"(
' )*'+''%(',
''!!! -./'#01 2%"
!"#!"$$#%&'#"
''
The CDN (Route Point) report lists the CDNs and their assigned names.
For more information, see “Understanding the report descriptions” on page 787.
Definition: CDN
A Controlled Directory Number (CDN) is a number configured on the switch as
the entry point for voice contacts into Contact Center Manager. You can
configure multiple CDNs in the switch and associate them with the Master script
of Contact Center Manager.
Views
This report uses the CDN (Route Point) view (see page 394.) For more
information about views, see “Access rights by view” on page 156.
Templates
This report uses the config7.rpt template.
Selection criteria
CDN CDN.CDN
CDN Name
Statistics
BestAir
!"#$
% &! '
$
% &! '
$!
() *+,-! ./
#$!01
2.-.
"
$2.
+.'$23
2455$25.
-2
$.
#2.52
6 275
827"9):
! "!#$$%#%%$#&
The Database View Definitions report generates a complete list of the database
views available in the Contact Center Manager database. You can use these
views to design user-created reports.
The Database View Definition report does not include views from the Contact
Center Multimedia database.
For each database view, the report lists the fields in the view. For each field, the
report provides the field type and length.
For more information, see “Understanding the report descriptions” on page 787.
Views
This report uses the Views view (see page 497.) For more information about
views, see “Access rights by view” on page 156.
Templates
This report uses the config34.rpt template.
Selection criteria
none none
Statistics
BestAir
0"!(0 !" #
0", !" #
" " !" #
'"03''(0 " !" #
405"6" .
'"03''$7", .
!7 +
7 +
0"!" +
"07 +
83''' ,"!"
83'' ,"!" #
4"7 " #
07 ,"!" #
,"!" -
!10" ,"!" -
!10" " ,"!" -
!"#
$
!"#
!"#
$
$
%& '
% ( )*
+# ( ',
-$+ ( ',
# ( .'
( ( .'
$+ ( */
+(
#
+0##+
*
#
+0## 1( *
1 '
1 '
+
1 '
21 .
+ ( .
+1 ( .
( ),
-+ ( ),
-+ ( ),
+
( ),
( .'
# ( .'
( ( .'
$ 3-+
3++43+#$
$(333-
3$
1)'5-
!""!"##$%$$" &
%'"
DNIS Properties
The DNIS Properties report lists each DNIS and its assigned name. It also lists
the service level threshold.
For more information, see “Understanding the report descriptions” on page 787.
Definition: DNIS
Dialed Number Identification Service (DNIS) identifies the dialed number for
calls coming into the contact center. Typically, DNIS numbers are used for 1-800
numbers. For example, a company might give customers different 1-800
numbers for sales and customer service calls.
Views
This report uses the DNIS view (see page 397.) For more information about
views, see “Access rights by view” on page 156.
Templates
This report uses the config10.rpt template.
Selection criteria
DNIS DNIS.DNIS
DNIS Name
Statistics
BestAir
!"#$##%&'' !"
!(#)#%&'' !(
!#$#)#*+&'' !
!,#$$&'' !,
Formula Properties
The Formula Properties report lists all of the custom formulas and their
definitions as they appear in real-time displays. You can use formulas to create
custom real-time statistics fields by combining existing statistics fields with
mathematical operators.
For more information, see “Understanding the report descriptions” on page 787.
Views
This report uses the Formula view (see page 402.) For more information about
views, see “Access rights by view” on page 156.
ATTENTION
The Formula view contains the raw formula data. For
example, formula definitions include the variable codes.
This report uses an internal API call to convert formula
variables to variable names and stores them in the
temporary CUSTFORM.MDB file at run time. The report is
run from both the database view (Formula) and the .mdb
file (CustForm.mdb).
Templates
This report uses the config17.rpt template.
Selection criteria
none none
Statistics
BestAir
!
"#
"!
#$
"
!
##
"!
#
%
"$
"
#
"
!"#
&'(
"!
#$
"
!
##
"!
#
)*+
) "%),))(+)-
)) .#)/&012(*
$%&'()'(**)+,-)-. /1
The Historical and Real Time Statistics Properties report lists the historical and
real-time statistics you configured Contact Center Manager to collect.
For more information, see “Understanding the report descriptions” on page 787.
Views
This report uses the following views:
HistoricalStatCollection (see page 404)
HistoricalStatDuration (see page 408)
HistoricalStatStorage (see page 410)
RealTimeStatCollection (see page 440)
For more information about views, see “Access rights by view” on page 156.
Templates
This report uses the config1.rpt template.
Selection criteria
none none
Moving Window The Moving Window fields The Moving Window fields
indicate whether statistics in each indicate whether statistics in each
of the following statistics groups of the following statistics groups
can be displayed in moving can be displayed in moving
window mode: window mode:
application statistics application statistics
(RealTimeStatCollection.MW (RealTimeStatCollection.MW
Application) Application)
skillset statistics skillset statistics
(RealTimeStatCollection.MW (RealTimeStatCollection.MW
Skillset) Skillset)
agent statistics agent statistics
(RealTimeStatCollection.MW (RealTimeStatCollection.MW
Agent) Agent)
network call network call
(RealTimeStatCollection.MW (RealTimeStatCollection.MW
NetworkCall); NSBR option NetworkCall); NSBR option
IVR IVR
(RealTimeStatCollection.MWI (RealTimeStatCollection.MWI
VR) VR)
route route
(RealTimeStatCollection.MW (RealTimeStatCollection.MW
Route); Communication Route); Communication
Server 1000/Meridian 1 PBX Server 1000/Meridian 1 PBX
switch switch
contact center summary contact center summary
(RealTimeStatCollection.MW (RealTimeStatCollection.MW
NodalCall) NodalCall)
Interval to Date The Interval To Date fields The Interval To Date fields
indicate whether statistics in each indicate whether statistics in each
of the following statistics groups of the following statistics groups
can be displayed in interval-to- can be displayed in interval-to-
date mode: date mode:
application application
(RealTimeStatCollection.ITD (RealTimeStatCollection.ITD
Application) Application)
skillset skillset
(RealTimeStatCollection.ITD (RealTimeStatCollection.ITD
Skillset) Skillset)
agent agent
(RealTimeStatCollection.ITD (RealTimeStatCollection.ITD
Agent) Agent)
network call network call
(RealTimeStatCollection.ITD (RealTimeStatCollection.ITD
NetworkCall); NSBR option NetworkCall); NSBR option
IVR IVR
(RealTimeStatCollection.ITDI (RealTimeStatCollection.ITDI
VR) VR)
route route
(RealTimeStatCollection.ITD (RealTimeStatCollection.ITD
Route); Communication Route); Communication
Server 1000/Meridian 1 PBX Server 1000/Meridian 1 PBX
switch switch
contact center summary contact center summary
(RealTimeStatCollection.ITD (RealTimeStatCollection.ITD
NodalCall) NodalCall)
BestAir
,#-
'
*+
!
"#$
"#$
)*)
'($
'(
'( )*)
%
% &
#&!', ./
#&!# 0
+3&!+3# 40
#&!'((
) 4
#&!)-) 4
5"#&!31 +-#
"
# 6
/
"#
1
#&!"# ./
!!!"!#$ %
BestAir
#
', 8/
', @ 4
+!3 8
!!!"!#$
BestAir
+#,
&
)*
!
"#$
"#$
()(
&'$
&'
&'()(
%
%
7
7% 7#+777
7
&/8
!"
!
BestAir
"#$% &
#
#
&' &'
,
% %
&+ 56 55 55
&+
56 /1 55
*!3 0
7
7% 7#+777
7
&/8
!"
Communication Server 2x00/DMS switch only. The IVR Port Properties report
lists the name and properties of all voice ports.
For more information, see “Understanding the report descriptions” on page 787.
Views
This report uses the IVRPort view (see page 411.) For more information about
views, see “Access rights by view” on page 156.
Templates
This report uses the config11.rpt template.
Selection criteria
Statistics
!
"##$
#!
%#!!
!
"###
%#!
%#&&
!
"##!
%#&
%#$$
!
"##&
%#$
'(')'*
'++'+','+'
&-##.
/'
0(1!!2
The IVR Queue and Port Properties report lists the name, number, and threshold
class for each Interactive Voice Response (IVR) system queue (ACD-DN), as
well as the voice ports assigned to the queue.
For more information, see “Understanding the report descriptions” on page 787.
Views
This report uses the following views:
IVRQueue (see page 413)
IVRPort (see page 411)
IVRThresholdTemplate (see page 415)
For more information about views, see “Access rights by view” on page 156.
Templates
This report uses the config11.rpt template.
Selection criteria
Statistics
Report (page 1 of 2)
BestAir
!
"# $
"#
% 34.3+53-%(3"3(4333%*!!!67*83%9.:**;
!"""!#!$%#&' (!
Report (page 2 of 2)
BestAir
% 34.3+53-%(3"3(4333%*!!!67*83%9.:**;
!"""!#!$%#&' !!
The Agent Position ID report lists agents and provides, for each one, logon ID
and position ID, and (on the Communication Server 1000/Meridian 1 PBX
switch) personal DN.
ATTENTION
Agent status information is written to the database every 15
minutes. This report shows agent status as of the end of the
last 15-minute interval.
For more information, see “Understanding the report descriptions” on page 787.
Views
This report uses the following views:
Agent (see page 382)
eAgentLoginStat (see page 347)
For more information about views, see “Access rights by view” on page 156.
Templates
This report uses the config32.rpt template.
Selection criteria
Statistics
BestAir
"# ! $ !
& !% %$*%* $ !%
+ "+,#+-+..+.+(/+.+*01*2+3"&%4
BestAir
- 4
45)4.0%-
-34+44
4-
( 6
The Real Time Template Properties report lists each real-time display definition
and describes its properties.
For more information, see “Understanding the report descriptions” on page 787.
Views
This report uses the following views:
RealTimeTemplate (see page 444)
RealTimeColumn (see page 438)
Formula (see page 402)
For more information about views, see “Access rights by view” on page 156.
Templates
This report uses the config21.rpt template.
Selection criteria
none none
Statistics
BestAir
&
!"# #$%"
'
7
!"# +$*
/
7
!"# #$%"
; ;".;%;;;1';;72#73;-+8&74
!"#!"$$#%$&%'(
)1
Route Properties
The Route Properties report lists each route, the assigned route name, and the
assigned threshold class name. It also lists the threshold times set for each
template.
For more information, see “Understanding the report descriptions” on page 787.
Views
This report uses the following views:
Route (see page 448)
RouteThresholdTemplate (see page 449)
For more information about views, see “Access rights by view” on page 156.
Templates
This report uses the Config9.rpt template.
Selection criteria
Route ID Route.RouteID
Route Name
Statistics
BestAir
!
!
!
%
&
!
'%
()
!
*+
,!-
, )$,./,&,/-,#
,,*000 1"*2,345 6!
For each script, the Script Variable by Script report lists the script type and
status, along with the names of the script variables used. For each variable, it
provides the status and type.
For more information about scripting, refer to the Contact Center Manager
Scripting Guide for Communication Server 1000/Meridian 1 PBX or the Contact
Center Manager Scripting Guide for Communication Server 2X00/DMS.
For more information, see “Understanding the report descriptions” on page 787.
Views
This report uses the ScriptVariables view (see page 462.) For more information
about views, see “Access rights by view” on page 156.
Templates
This report uses the config36.rpt template.
Selection criteria
Statistics
BestAir
The Script Variable Properties report lists the group, type, status, and class of
each variable.
For more information about scripting, refer to the Contact Center Manager
Scripting Guide for Communication Server 1000/Meridian 1 PBX or the Contact
Center Manager Scripting Guide for Communication Server 2X00/DMS.
For more information, see “Understanding the report descriptions” on page 787.
Views
This report uses the following views:
ScriptVariableProperties (see page 460)
ScriptVariables (see page 462)
For more information about views, see “Access rights by view” on page 156.
Templates
This report uses the config35.rpt template.
Selection criteria
Statistics
BestAir
"#$
! %
& &
'
())*+)+),+)++)-+).+).+).,+)+)/+))+)-+).0+)-1+)-)+).+
+),
23 "#$ 42
23 "#$ 42
3'3 "#$ $!
Skillset Properties
The Skillset Properties report describes all skillset properties, including the
skillset type (local or network) and the service level threshold defined for the
threshold class to which the skillset belongs.
For more information, see “Understanding the report descriptions” on page 787.
Views
This report uses the following views:
Agent (see page 382)
Skillset (see page 467)
SkillsetByAgent (see page 471)
For more information about views, see “Access rights by view” on page 156.
Templates
This report uses the config16.rpt template.
Selection criteria
Statistics
BestAir
$,
%
,
-$-".
*+
0
-"$
*/
-
$,
%
1 "
3"$.
)##
4#
5
*
@&$"$
(
@"$
3"$@?
@11@1"$
@
"$
%@$1@ *
A0*B@C(>*D&
BestAir BestAir
",
- #
+&&' #
. '
'*
/ 11#/2# 3
113453 3
6
1143#4 )
' 115#44 )
",
- #
+&&' #
. '
'*
7
118/84 3
1194:8 3
$
1194/8 3
;
1153<9 3
Supervisor Properties
The Supervisor Properties report lists all Contact Center Manager supervisors by
name and threshold class. The report includes port information, personal or
secondary directory number, logon information, comments, and all names of the
agents assigned to the supervisor.
For more information, see “Understanding the report descriptions” on page 787.
Views
This report uses the following views:
SupervisorAgentAssignment (see page 482)
Supervisor (see page 479)
For more information about views, see “Access rights by view” on page 156.
Templates
This report uses the config4.rpt template.
Selection criteria
Statistics
BestAir
!
"
!
"
#$
%
&
$
"'
($)
%
*+
,--.-.
'
/
/
34
!
$
8
94
&
$
8
9
/
'
$
<
3
<
!4<=
<<
<>
"<< +
(9+)<?3#:,@
!
"#$%#$%&&&'()
BestAir
!"
"
#
$% '(()
#
$" '*++
%&
'(()
,
/
&
0
$
"6
7%
7#/7 ,
7$
77%7"1*%
!
"##$$%&$'(
The Telephone Display Properties report lists the configured display types, the
width of the display, and the number of rows in the display.
For more information, see “Understanding the report descriptions” on page 787.
Views
This report uses the PhoneSetDisplay view (see page 434.) For more
information about views, see “Access rights by view” on page 156.
Templates
This report uses the config6.rpt template.
Selection criteria
none none
Statistics
BestAir
!
!
"
#
"$
%&'('
&'
'&%
&&'
(&)
'
*&'&%
+, -&%.#/01
"#!
$%$&&%!'!&(
The User Access Privilege report lists all of the access classes defined in the
system. For each class, the report lists all of the privileges assigned to that class
and all the desktop users belonging to that class.
ATTENTION
For users access privileges for the Contact Center Manager
Administration server, run the Access and Partition
Management reports. For more information, see Section H:
“Administration reports,” on page 1179.
For more information, see “Understanding the report descriptions” on page 787.
Views
This report uses the AccessRights view (see page 377.) For more information
about views, see “Access rights by view” on page 156.
Templates
This report uses the config42.rpt template.
Selection criteria
none none
Statistics
Report (page 1 of 4)
BestAir
!
!"#$%&
!'
(' )*'+''',
''"--- ."/'0(1 %#2
Report (page 2 of 4)
BestAir
!'
(' )*'+''',
''"--- ."/'0(1 %#2
Report (page 3 of 4)
BestAir
(
6
,
5
8
3
6
!'
(' )*'+''',
''"--- ."/'0(1 %#2
Report (page 4 of 4)
BestAir
!'
(' )*'+''',
''"--- ."/'0(1 %#2
In this section
Contacts Closed by Reason Code 1018
Contacts Closed by Skillset 1020
Contacts Details 1022
Contacts Outstanding Detail 1027
Contacts Outstanding Summary 1030
Contacts Received by Skillset 1033
The Contacts Closed by Reason Code report contains summaries of the contacts
closed by reason codes on a per-date basis.
Views
This report uses the ContactsbyContacts view.
Collection frequency
The following collection frequency types are available for this report:
daily
weekly
monthly
Selection criteria
You can apply a filter to any of the fields in the view. For example you can
apply a filter to specific skillsets, contact ID, or customer ID.
Data Range
You can use the data range to restrict the report to a specific date.
Templates
This report uses the ClosedReasonCodesReport.rpt template.
Summaries
This report is located under the Multimedia group. The report groups the
contacts closed by disposition code on a per-day basis. The report also lists the
grand total of contacts closed, and the total for each day.
!"#$%#&#!'#()*+,#*#*#-
#
"$
1019
Standard reports
Standard reports Standard 8.11
Views
This report uses the ContactsbyContacts view.
Collection frequency
The following collection frequency types are available for this report:
daily
weekly
monthly
Selection criteria
You can apply a filter to any of the fields in the view. For example, you can
apply a filter to specific skillsets, contact ID, or customer ID.
Data Range
You can use the data range to restrict the report to a specific date.
Templates
This report uses the MM Contacts Closed by Skillset.rpt template.
Summaries
The report is located under the Multimedia group. The report groups the closed
contacts by skillset on a per-day basis. The report also lists the grand total of
contacts closed, the total for each day and the total for each skillset.
!"#
$% !"#
& !"#
'
(
*+,-#*."#*& */#* ,*0#1**!234* 1##256"#7
!
"
# $ "
1021
Standard reports
Standard reports Standard 8.11
Contacts Details
Views
This report uses the ContactsbyContacts view.
Collection frequency
The following collection frequency types are available for this report:
interval
daily
weekly
monthly
Selection criteria
You can apply a filter to any of the fields in the view. For example, you can
apply a filter to to specific skillsets, contact ID, or contact status.
Data Range
You can use the data range to restrict the report to a specific date.
Templates
This reports use the ContactByContactDetails.rpt template.
Summaries
The report is located under the Multimedia group. The report displays grand
total and average information for all contacts, and then displays total and
average information for contacts grouped by skillset.
The grand total and average information for all contacts and is divided into the
following sections.
The report also provides information for contact details grouped by skillset. For
each skillset the report provides the following information where applicable:
Contact Status
Total
Closed
Open
New
Waiting
Average
Total
Average
Dial Duration
Talk Duration
Call Duration
The report also displays the contacts for each particular day and lists the
following information where applicable:
Closed Date
Contact ID
Arrival Date/Time
Waiting Duration
Open Time
Closed Time
Open Duration
Agent ID-Name
Closed Reason Code
Mail From
Disposition Code
Campaign Name
Call Duration
Contact Status
! .
!"#!$%%& '(
)(*
Page 1 of 4
- .
-
0,
-
-
'+,
/,
,
,
1 (' 1
(
#
(
#
(
# -, % /!!0$! "
- .
-
0,
-
-
'+,
/,
,
,
' ( '1
(-# 1
(-# 1
(-# -, % /!!0$!
! .
!"1!$%%& 2(
)(*
-
-
-
0,
-
,,
/,
,
,
' ( '1
1
1# 1
# 1
'# -, + %0
' (( '1
1
1#
1
-# 1
('# -, + %0
67%8 6". 6+ 6# 6 %69 !66346 !:) !* $
2! ! ! 3& ! !" 4
0',
-
22! 0! ! ", *
5$$ !
,&0
4
-2678
9-, !$%!$%%&$75:75%4' ! ",&
, *
$
4
")5
222& !+ % !!
-,
0
-,
3
1025
Standard reports
1026
! " #$
! .
!"5!$%%& '(
)(*
Standard reports
- .
-
0,
-
-
'+,
Page 2 of 4
/,
,
,
( (
#
#
'# -, ! /!!0$
( (
7
7
7 -, % /!!0$!
( - (
1
'7
1
'7
1
'7 -, % /!!0$!
( 1 (
(
7
(
7
(
7 -, % /!!0$!
( (
'
'7
'
'7
'
'7 -, % /!!0$!
( (
'(
'7
'(
'7
'(
'7 -, % /!!0$!
( (
7
7
7 -, % /!!0$!
( (
7
7
7 -, % /!!0$!
( ( (
-7
-7
-7 -, % /!!0$!
( ' (
7
7
7 -, % /!!0$!
( (
(
''7
(
''7
(
''7 -, % /!!0$!
( (
'
(7
'
(7
'
(7 -, % /!!0$!
( - (
1
7
1
7
1
7 -, % /!!0$!
( 1 (
(
(17
(
(17
(
(17 -, % /!!0$!
( ( ((
1
7 (
1
7 (
1
7 -, % /!!0$!
( ( ((
7 (
7 (
7 -, % /!!0$!
! .
!"5!$%%& 2(
)(*
-
-
-
0,
-
,,
/,
,
,
( 1 (
'
'-#
'
(#
'
'# -, !0 &
( (
'
'-#
'
#
'
-# -, !0 &
67%8 6". 6+ 6# 6 %69 !66346 !:) !* $
2! ! ! 3& ! !" 4
0',
-
22! 0! ! ", *
5$$ !
,&0
4
-2678
9-, !$%!$%%&$75:75%4' ! ",&
, *
$
4
$)5
222& !+ % !!
-,
0
-,
3
The Contacts Outstanding Detail Report contains the details of each contact that
is left outstanding on a per-skillset basis.
ATTENTION
Report Creation Wizard formulas are not supported for this
report.
For more information, see “Understanding the report descriptions” on page 787.
Views
This report uses the ContactsOutstandingDetail view.
Collection frequency
The following collection frequency types are available for this report:
interval
daily
weekly
monthly
Selection Criteria
You can apply a filter to any of the fields in the view. For example, you can
apply a filter to specific skillsets, contact ID range, or date range.
Data Range
You can use the data range to restrict the report to a specific date.
Templates
This report uses the ContactsOutstandingDetailReport.rpt template.
Summaries
The report is located under the Multimedia group. The report groups the
outstanding contacts by skillset and lists the following details:
Contact Id
Arrival Time
Status
Type
Agent
Customer
For each skillset group, both the count and the percentage of total outstanding
contacts relating to that skillset are listed. The report also lists the grand total of
outstanding contacts.
$%
#
1029
Standard reports
Standard reports Standard 8.11
ATTENTION
Report Creation Wizard formulas are not supported for this
report.
For more information, see “Understanding the report descriptions” on page 787.
Views
This report uses the ContactsOutstanding view.
Collection frequency
The following collection frequency types are available for this report:
interval
daily
weekly
monthly
Selection Criteria
You can apply a filter to any of the fields in the view. For example, you can
apply a filter to specific skillsets.
Data Range
You can use the data range to restrict the report to a specific date.
Templates
This report uses the ContactsOutstandingReport.rpt template.
Summaries
The report is located under the Multimedia group. The report lists the number of
contacts left outstanding each day on a per-skillset basis, as well as a grand total
of contacts outstanding across all skillsets.
!"
#
$ %
Views
This report uses the ContactsbyContacts view.
Collection frequency
The following collection frequency types are available for this report:
daily
weekly
monthly
Selection criteria
You can apply a filter to any of the fields in the view. For example, you can
apply a filter to specific skillsets, contact ID, or contact status.
Data Range
You can use the data range to restrict the report to a specific date.
Templates
This reports use the MM Contacts Received by Skillset.rpt template.
Summaries
The report is located under the Multimedia group. The report groups the
received contacts by skillset on a per-day basis. The report also lists the grand
total of contacts received, the total for each day and the total for each skillset.
Standard reports
!"
#$ !"
%
!"
&
'
(
)*+,")-!")%
).")+)/"0)) 12
3)
0"0145!"6
$
%
&#'%
!! "#
In this section
Overview of network reports 1036
Network Site and Application Properties 1037
Network Skillset Routing Properties 1041
Crosstab - Network Incoming Calls 1045
Network Application Performance 1051
Network Application Performance 1051
Network DNIS Statistics 1055
Network Incoming Calls 1060
Network Outgoing Calls 1064
Network Route Performance 1067
Network Skillset Performance 1070
This section lists the networking reports that you can generate when logged on
to a server on the network. In some cases, these reports are similar to
non-network reports, but they use a different view or contain additional fields.
NSBR option only. The Network Site and Application Properties report lists all
of the sites in the network, and for each one, shows
the site’s properties (as configured on the Network Control Center)
the remote switch parameters for the site (as configured on the local server)
the applications at that site
For each application, it includes the service level threshold and whether local
and network call-by-call statistics are collected for the application.
ATTENTION
User-defined reports using this standard report as a template
cannot be scheduled.
For more information, see “Understanding the report descriptions” on page 787.
Views
This report uses the following views:
RemoteApplication (see page 446)
Site (see page 464)
TargetSwitchComm (see page 489)
For more information about views, see “Access rights by view” on page 156.
Templates
This report uses the config28.rpt template.
Selection criteria
Application properties
Grouping
Application information is grouped by site.
BestAir
!
" #
Shannon' ) ()
Galway ) ('
Dublin ) ()
: Dublin
#
+" ++ ,
"
-
."/
"
Shannon' ) ) '
Galway 01)2' ) ) '
Dublin ) ) '
&1
#
$%&'%(!!)&&)'(*+
The Network Skillset Routing Properties report lists all the network skillsets and
indicates the routing table method used for the network skillset.
For more information, see “Understanding the report descriptions” on page 787.
Views
This report uses the following views:
NetworkSkillsetStatus (see page 430)
Ranking (see page 436)
Skillset (see page 467)
For more information about views, see “Access rights by view” on page 156.
Templates
This report uses the config39.rpt template.
Selection criteria
Site fields
BestAir
Shannon "##
Galaway "##
Dublin "##
$ 3
33*$322323%1323$04'053$"6,789
!"
##
The Crosstab - Network Incoming Calls report provides you with an at-a-glance
view of inbound contact activity (contacts offered, contacts accepted, and
contacts abandoned) for several days. You can use this report to compare
network activity for the same reporting period on different days.
ATTENTION
Report Creation Wizard formulas are not supported for this
report.
For more information, see “Understanding the report descriptions” on page 787.
Views
This report uses the iNetworkInCallStat view (see page 299.) For more
information about views, see “Access rights by view” on page 156.
Collection frequency
This report contains interval data.
Templates
This report uses the icross_net_in_calls.rpt template.
Selection criteria
Statistics
Summaries
The report provides totals for each selected source site for the selected intervals.
Also, totals for the selected intervals are shown grouped by day.
BestAir
February 2008
!
"# $
Galway
/ /
/
0
&1 2 / /
2 / /
!
!
1047
Standard reports
Standard reports Standard 8.11
The Crosstab - Network Outgoing Calls report provides you with an at-a-glance
view of outgoing contact activity (contacts offered, contacts accepted, and
contacts abandoned) for several days. You can use this report to compare
network activity for the same reporting period on different days.
ATTENTION
Report Creation Wizard formulas are not supported for this
report.
For more information, see “Understanding the report descriptions” on page 787.
Views
This report uses the iNetworkOutCallStat view (see page 308.) For more
information about views, see “Access rights by view” on page 156.
Collection frequency
This report contains interval data.
Templates
This report uses the icross_net_out_calls.rpt template.
Selection criteria
Statistics
Summaries
The report provides totals for each selected source site for the selected intervals.
Also, totals for the selected intervals are shown grouped by day.
BestAir
!"
#$%&
Standard reports
Galway
0
1
" 0 1
1
For each application, the report provides information about the number of
outgoing network contacts that are accepted, delayed, and abandoned. It can be
particularly useful in determining the efficiency of your network configuration.
For more information, see “Understanding the report descriptions” on page 787.
Views
This report uses the ApplicationStat view (see page 249.) For more information
about views, see “Access rights by view” on page 156.
Collection frequency
The following collection frequency types are available for this report:
interval
daily
weekly
monthly
Templates
This report uses the following templates:
inetapp1.rpt
dnetapp1.rpt
wnetapp1.rpt
mnetapp2.rpt
Selection criteria
Summaries
The report provides totals for each application, and subtotals for each day, week,
or month, depending on the reporting period selected. For the interval reporting
period, statistics are further broken down by interval. The report also contains a
grand total for all selected applications.
! "
BestAir
Standard reports
#$ %
! !"
&'( )(&
%+ ! !"
4 3 4 4"
! !"
#$ %
! !"
The Network DNIS Statistics report lists the total voice contact volume to each
Dialed Number Identification Service (DNIS) number. The report lists the total
calls answered, total voice contacts accepted, the percentage of voice contacts
that abandoned after the service level threshold defined for the DNIS, and the
total number of voice contacts networked out.
You can use this report to track network performance for a particular DNIS
number.
For more information, see “Understanding the report descriptions” on page 787.
Views
This report uses the DNISStat view (see page 280.) For more information about
views, see “Access rights by view” on page 156.
Collection frequency
The following collection frequency types are available for this report:
interval
daily
weekly
monthly
Templates
This report uses the following templates:
inetres6.rpt
dnetres6.rpt
wnetres6.rpt
mnetres6.rpt
Selection criteria
DNIS iDNISStat.DNIS
DNIS Name iDNISStat.Timestamp
Call statistics
Summaries
The report provides totals for each DNIS, and subtotals for each day, week, or
month, depending on the reporting period selected. For the interval reporting
period, statistics are further broken down by interval. The report also contains a
grand total for all selected DNISs.
!$!!% !" "#
&
"#'(
')*+,"#
), -! $% -!
&
"'
'
.
+,"
), - !$!!% - !" "#
- !$!!% - !" "#
1059
Standard reports
Standard reports Standard 8.11
The Network Incoming Calls report provides statistics about incoming network
contacts for your site. It contains information about the number of incoming
network contacts offered, accepted, and abandoned at your site. The report also
provides statistics about the number of contacts agents accepted or abandoned
after the service level threshold and the delays experienced by customers.
For more information, see “Understanding the report descriptions” on page 787.
Views
This report uses the NetworkInCallStat view (see page 299.) For more
information about views, see “Access rights by view” on page 156.
Collection frequency
The following collection frequency types are available for this report:
interval
daily
weekly
monthly
Templates
This report uses the following templates:
inet-10.rpt
dnet-10.rpt
wnet-10.rpt
mnet-10.rpt
Selection criteria
Summaries
The report provides totals for each source site and subtotals for each day, week,
or month, depending on the reporting period selected. For the interval reporting
period, statistics are further broken down by interval. The report also contains a
grand total for all selected destination sites.
!" '""
# # $ )* $ )* $ )* $ )*
,-- &##" !" $% %" '"" $% %" ( ( ( (
Galway # ! !" ## !! $" % # &
*+Dublin
Galway # ! !" ## !! $" % # &
0
1 1!$!$/$&,2 ,3
1063
Standard reports
Standard reports Standard 8.11
The Network Outgoing Calls report provides statistics about outgoing network
contacts for your site. The report contains information about the number of
outgoing network contacts offered, accepted, and abandoned at the source and
destination sites.
For more information, see “Understanding the report descriptions” on page 787.
Views
This report uses the NetworkOutStat view (see page 308.) For more information
about views, see “Access rights by view” on page 156.
Collection frequency
The following collection frequency types are available for this report:
interval
daily
weekly
monthly
Templates
This report uses the following templates:
inet-11.rpt
dnet-11.rpt
wnet-11.rpt
mnet-11.rpt
Selection criteria
Statistics
Summaries
The report provides totals for each destination site, and subtotals for each day,
week, or month, depending on the reporting period selected. For the interval
reporting period, statistics are further broken down by interval and application.
The report also contains a grand total for all selected destination sites.
BestAir
!"#$%
%&'& $((! ')"! ' !!
Galway
%&
For more information, see “Understanding the report descriptions” on page 787.
Views
This report uses the RouteStat view (see page 319.) For more information about
views, see “Access rights by view” on page 156.
Collection frequency
The following collection frequency types are available for this report:
interval
daily
weekly
monthly
Templates
This report uses the following templates:
inetres2.rpt
dnetres2.rpt
wnetres2.rpt
mnetres2.rpt
Selection criteria
Route ID iRouteStat.RouteID
Route Name iRouteStat.Timestamp
Call statistics
Summaries
The report provides totals for each route, and subtotals for each day, week, or
month, depending on the reporting period selected. For the interval reporting
period, statistics are further broken down by interval. The report also contains a
grand total for all selected routes.
BestAir
!" %&!'#(! %&!'()
!" +
#"$ #$
!"#"$ *
!" #"$
!"#"$
!
"# &
$ !
, ,
- -
.
!
By indicating the volume of contacts and the delay times customers experienced,
along with the amount of time agents are busy servicing contacts to the skillset,
the report indicates whether the skillset has the number of agents required to
service customers. If a particular skillset is not performing well, you may need
to consult the agent reports.
For more information, see “Understanding the report descriptions” on page 787.
Views
This report uses the SkillsetStat view (see page 325.) For more information
about views, see “Access rights by view” on page 156.
Collection frequency
The following collection frequency types are available for this report:
interval
daily
weekly
monthly
Templates
This report uses the following templates:
inet-12.rpt
dnet-12.rpt
wnet-12.rpt
mnet-12.rpt
Selection criteria
Agent statistics
Summaries
The report provides totals for each selected skillset and for each application/site
combination. Statistics are further broken down by day, week, or month,
depending on the reporting period selected. For the interval reporting period,
statistics are further broken down by interval. The report also contains a grand
total for all selected skillsets.
# '"#$ "#$ ""* " "* "*
-+"+ -+ "#$ "#$ "%&&$ "%&&$ () "* .-/ %%$ "+ ,%"*
! $% !"#!#$ !!#! #& !!#!!#$' '"#$ #$$ '&#&#$ "& #!'#$( "
#)*+ ,
-/ ! $% !"#!#$ !!#! #& !!#!!#$' '"#$ #$$ '&#&#$ "& #!'#$( "
4#$*5(* Galway 120 0 0 13
! $ !"#!#$ !!#! #& !!#!!#$' '"#$ #$$ '&#&#$ "& #!'#$( "
! $% !"#!#$ !!#! #& !!#!!#$' '"#$ #$$ '&#&#$ "& #!'#$( "
-
*.#.*
$$/$ /"!!'#!#"
0
$$
1073
Standard reports
Standard reports Standard 8.11
In this section
Activity Code by Application 1077
Application by Activity Code 1080
Application by Skillset 1083
Application Call Treatment 1087
Application Delay Before Abandon 1095
Application Delay Before Answer 1099
Application Performance 1103
CDN (Route Point) Statistics 1107
Crosstab - Application Performance 1112
Crosstab - CDN (Route Point) Statistics 1115
Crosstab - DNIS Statistics 1119
Crosstab - Route Performance 1122
Crosstab - Skillset Performance 1125
Crosstab - Trunk Performance 1129
DNIS Statistics 1132
IVR Port First Login/Last Logout 1137
IVR Port Statistics 1139
IVR Queue Statistics 1143
Music/RAN Route Statistics 1146
Route Performance 1149
Skillset by Application 1153
Skillset Performance 1156
With the Activity Code by Application report you monitor activity time for each
application on your system. The Activity Code by Application report includes
all activity time and occurrences for an application.
ATTENTION
This report does not include Not Ready reason codes.
On the Communication Server 2x00/DMS switch, agents
cannot use the LOB key while they are conferenced with
another agent.
For more information, see “Understanding the report descriptions” on page 787.
Views
This report uses the ActivityCodeStat view (see page 188.) For more
information about views, see “Access rights by view” on page 156.
Collection frequency
The following collection frequency types are available for this report:
interval
daily
weekly
monthly
Templates
This report uses the following templates:
im-app8.rpt
dm-app8.rpt
wm-app8.rpt
mm-app8.rpt
Selection criteria
Statistics
Summaries
The report provides totals for each application, and subtotals for each day, week,
or month (depending on the reporting period selected). For the interval reporting
period, statistics are further broken down by interval. The report also contains a
grand total for all selected applications.
%
&'
!" #
! !"# () * * * *) *)(
+
,,
#-.-/0/0.1" 1 (
Use the Application by Activity Code report to monitor each agent’s work and
time distribution by the types of contacts accepted. During contacts, agents can
identify the contact type by entering an activity (Line of Business) code.
Multiple codes can be used to reflect activities performed on a single contact.
ATTENTION
This report does not include Not Ready reason codes.
On the Communication Server 2x00/DMS switch, agents
cannot use the LOB key while they are conferenced with
another agent.
For more information, see “Understanding the report descriptions” on page 787.
Views
This report uses the ActivityCodeStat view (see page 188.) For more
information about views, see “Access rights by view” on page 156.
Collection frequency
The following collection frequency types are available for this report:
interval
daily
weekly
monthly
Templates
This report uses the following templates:
im-app9.rpt
dm-app9.rpt
wm-app9.rpt
mm-app9.rpt
Selection criteria
Statistics
Summaries
The report provides totals for each activity code, and subtotals for each
application. For each activity code, statistics are broken down by day, week, or
month, depending on the reporting period selected. For the interval reporting
period, statistics are further broken down by interval. The report also contains a
grand total for all selected agents.
!
"
#
$%& '
(
#
$"((**)++
$"((**)*+
$"((**).+*
%
/
010%
22
3
4+ 4'
5
Application by Skillset
ATTENTION
This report does not contain statistics for the
System_Application.
For more information, see “Understanding the report descriptions” on page 787.
Views
This report uses the SkillsetStat view (see page 325.) For more information
about views, see “Access rights by view” on page 156.
Collection frequency
The following collection frequency types are available for this report:
interval
daily
weekly
monthly
Templates
This report uses the following templates:
imskill3.rpt
dmskill3.rpt
wmskill3.rpt
mmskill3.rpt
Selection criteria
Statistics
Summaries
The report provides totals for each skillset, and subtotals for each application.
For each application, statistics are further broken down by day, week, or month
(depending on the reporting period selected). For the interval reporting period,
statistics are further broken down by interval, and within each interval, by
application. The report also contains a grand total for all selected skillsets.
!"#
$ %&'(
)*
-)
!"#
$ %&'(, '-
-)
+
!"
)
-)
!
!"#
) &
.
%.&-
/ "/
0, 0'
1
This report measures other treatments within the call script, including
commands such as Give Force Busy, Give Route To, or Give Force Disconnect.
You can keep a count of the number of customers who receive a specific
treatment and service.
For more information, see “Understanding the report descriptions” on page 787.
Views
This report uses the ApplicationStat view (see page 249.) For more information
about views, see “Access rights by view” on page 156.
Collection frequency
The following collection frequency types are available for this report:
interval
daily
weekly
monthly
ATTENTION
If you use the interval data type, remember that a call offered
at one interval could be given treatment at another interval.
Templates
This report uses the following templates:
im-app7.rpt
dm-app7.rpt
wm-app7.rpt
mm-app7.rpt
Selection criteria
Overflowed statistics
Defaulted statistics
Routed statistics
Disconnected statistics
Offered statistics
Answered statistics
Abandoned statistics
Summaries
The report provides totals for each application, and subtotals for each day, week,
or month, depending on the reporting period selected. For the interval reporting
period, statistics are further broken down by interval. The report also contains a
grand total for all selected applications.
'
"#$% #&% '(&)* &% )% "##% )$% %%
)+,&
-&*
!"
#
./012
#
#
/#
$ %&'() '
!"
#
/)3
!"
#
./012
#
#
85 55 6 7
./012 4 4 4 4 949 !!!! 745 479 4
-&*
!"
#
./012
#
#
43
-&*
!"
#
./012
#
#
/#
&
*+
%*&
,",
-) -'
.
For more information, see “Understanding the report descriptions” on page 787.
Views
This report uses the ApplicationStat view (see page 249.) For more information
about views, see “Access rights by view” on page 156.
Collection frequency
The following collection frequency types are available for this report:
interval
daily
weekly
monthly
Templates
This report uses the following templates:
im-app5.rpt
dm-app5.rpt
wm-app5.rpt
mm-app6.rpt
Selection criteria
Statistics
Summaries
The report provides totals for each application, and subtotals for each day, week,
or month, depending on the reporting period selected. For the interval reporting
period, statistics are further broken down by interval. The report also contains a
grand total for all selected applications.
%%
!!"#"$! !!"!#"! !!"!!"$!
"
& '()* (+
,)
%%
!!"#"$! !!"!#"! !!"!!"$!
$), /&$-0*-
,#% 1 2 1 2 3 3 1 11 12 2 1 2 1 2 3 1 1 6
!
$
!
!
!!
!
!
# #
!
$ $ $
!
! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! !
!!
1 2 3 31 32 1 1 1 2 4 5 3 4 5 3 4 5 3 12
)%!!!6
%%
!!"#"$! !!"!#"! !!"!!"$!
"
'+
,,!!#
#"!$"
-* -(
By keeping delays to a minimum, the contact center shows respect for customers
and inspires the confidence that brings repeat business.
For more information, see “Understanding the report descriptions” on page 787.
Views
This report uses the ApplicationStat view (see page 249.) For more information
about views, see “Access rights by view” on page 156.
Collection frequency
The following collection frequency types are available for this report:
interval
daily
weekly
monthly
Templates
This report uses the following templates:
im-app3.rpt
dm-app3.rpt
wm-app3.rpt
mm-app4.rpt
Selection criteria
Statistics
Summaries
The report provides totals for each application, and subtotals for each day, week,
or month, depending on the reporting period selected. For the interval reporting
period, statistics are further broken down by interval. The report also contains a
grand total for all selected applications.
##
!
"" "! #
$ %&'( &)
)$
##
!
"" "! #
"#$) .#,%/'%
)*"
0 1 0 1 2 2 0 00 01 1 0 1 0 1 2 0 0 5
*
!
*
*
"*
*
*
* !
#
!
*
0 1 2 20 21 0 0 0 1 3 4 2 3 4 2 3 4 2 01
$"!!!5
##
!
"" "! #
%
+
+%)
,,!
!
-( -&
Application Performance
ATTENTION
For the Network_Script, service level is based on network
calls answered at this site and network calls that abandon after
it is sent to this site. Call wait times are calculated from the
time the call arrives at the destination site.
By showing the volume of contacts accepted in a given period, along with the
average delay customers experienced, the report can identify the level of service
customers received on a specific type of contact or activity.
For more information, see “Understanding the report descriptions” on page 787.
Views
This report uses the ApplicationStat view (see page 249.) For more information
about views, see “Access rights by view” on page 156.
Collection frequency
The following collection frequency types are available for this report:
interval
daily
weekly
monthly
Templates
This report uses the following templates:
im-app1.rpt
dm-app1.rpt
wm-app1.rpt
mm-app2.rpt
Selection criteria
Statistics
ATTENTION
For the Network_Script application, the service level
calculation is based on network contacts accepted at this site
and network contacts that are abandoned after it is routed to
this site.
Summaries
The report provides totals for each application, and subtotals for each day, week,
or month, depending on the reporting period selected. For the interval reporting
period, statistics are further broken down by interval. The report also contains a
grand total for all selected applications.
Standard reports
!"!#
$%&'()'
!"!#
The CDN (Route Point) Statistics report details summarized contact volume
information for the CDNs (Route Points) configured on the server. The report
lists the total number of contacts offered to the CDN (Route Point) and the total
number of contacts accepted. The report also provides terminated and
abandoned contact information.
For more information, see “Understanding the report descriptions” on page 787.
Definition: CDN
A Controlled Directory Number (CDN) is a number configured in the switch as
the entry point for calls into Contact Center Manager. You can configure
multiple CDNs in the switch and associate them with the Master script of
Contact Center Manager.
Views
This report uses the CDNStat view (see page 275.) For more information about
views, see “Access rights by view” on page 156.
Collection frequency
The following collection frequency types are available for this report:
interval
daily
weekly
monthly
Templates
This report uses the following templates:
im-res7.rpt
dm-res7.rpt
wm-res7.rpt
mm-res7.rpt
Selection criteria
CDN iCDNStat.CDN
CDN Name iCDNStat.Timestamp
Statistics
Summaries
The report provides totals for each selected CDN and subtotals for each day,
week, or month, depending on the reporting period selected. For the interval
reporting period, statistics are further broken down by interval. The report also
contains a grand total for all selected CDNs.
!
BestAir
() ()
!
"#$
%& '(&&
)
*+ * *
!
"#$
'
+'
!)
*+ , ,
!
"#$-
.&
+/
'
01
'23 ) 4*
*+ , 4
50
+67$.
6+!
88 $ $9 /
%
3(
3'4 3- 3)33(
35$6/(
*+,-).!
//+'00!(!*" *1/2
ATTENTION
Report Creation Wizard formulas are not supported for this
report.
For more information, see “Understanding the report descriptions” on page 787.
Views
This report uses the iApplicationStat view (see page 249.) For more information
about views, see “Access rights by view” on page 156.
Collection frequency
This report contains interval data.
Templates
This report uses the icross_Application.rpt template.
Selection criteria
Statistics
Summaries
The report provides totals for each selected application for the selected intervals.
Also, totals for the selected intervals are shown grouped by day.
BestAir
Standard reports
$%!
"&&"#
"#
The Crosstab - CDN (Route Point) Statistics report provides you with an at-a-
glance view of CDN (Route Point) Statistics (contacts accepted, contacts
answered, contacts terminated, and contacts abandoned) for several days. You
can use this report to compare CDN (Route Point) Statistics for the same
reporting period on different days.
ATTENTION
Report Creation Wizard formulas are not supported for this
report.
For more information, see “Understanding the report descriptions” on page 787.
Views
This report uses the iCDNStat view (see page 275.) For more information about
views, see “Access rights by view” on page 156.
Collection frequency
This report contains interval data.
Templates
This report uses the icross_CDN.rpt template.
Selection criteria
CDN iCDNStat.CDN
CDN Name iCDNStat.Timestamp
Statistics
Summaries
The report provides totals for each selected CDN for the selected intervals. Also,
totals for the selected intervals are shown grouped by day.
BestAir
!"
!
$
%
&
+ + %
'
'
#
, !
Communication Server 1000/Meridian 1 PBX report
+
+
1117
Standard reports
1118
Standard reports
#
#"$%&%
*
'(')*+'+ *
Communication Server 2x00/DMS report
" *
*
#"$%""
'
'(')*+' (
The Crosstab - DNIS Statistics report provides you with an at-a-glance view of
DNIS statistics (contacts accepted, contacts answered, and contacts abandoned)
for several days. You can use this report to compare DNIS statistics for the same
reporting period on different days.
ATTENTION
Report Creation Wizard formulas are not supported for this
report.
For more information, see “Understanding the report descriptions” on page 787.
Views
This report uses the iDNISStat view (see page 280.) For more information about
views, see “Access rights by view” on page 156.
Collection frequency
This report contains interval data.
Templates
This report uses the icross_DNIS.rpt template.
Selection criteria
DNIS iDNISStat.DNIS
DNIS Name iDNISStat.Timestamp
Statistics
Summaries
The report provides totals for each selected DNIS for the selected intervals.
Also, totals for the selected intervals are shown grouped by day.
February 2008
BestAir
!"
#
1121
Standard reports
Standard reports Standard 8.11
When reviewing the report, be aware that the value NUMBER OF ATB
PERIODS is increased by one at the beginning of each all-trunks-busy period
within the reporting interval. If an all-trunks-busy period spans two or more
intervals, it is counted only against the interval in which it began.
Use the Crosstab - Route Performance report in conjunction with other reports to
interpret the cause of all-trunks-busy periods. This report can help you
determine the best action to reduce the number of all-trunks-busy periods. For
example, a change in your operating procedures may move contacts through
faster and free up your lines. Or you may find you need to lease extra trunk lines
during your busiest periods.
ATTENTION
Contacts blocked by all-trunks-busy statistics peg against the
route attempted.
Report Creation Wizard formulas are not supported for this
report.
For more information, see “Understanding the report descriptions” on page 787.
Views
This report uses the iRouteStat view (see page 319.) For more information about
views, see “Access rights by view” on page 156.
Collection frequency
This report contains interval data.
Templates
This report uses the icross_route.rpt template.
Selection criteria
Route ID iRouteStat.RouteID
Route Name iRouteStat.Timestamp
Statistics
Summaries
The report provides totals for each selected route for the selected intervals. Also,
totals for the selected intervals are shown grouped by day.
!
"
BestAir
Standard reports
Route 5
+
+
!
+
!
(
,*
-. ,
/
& ,0(,1 ,
-,
%,,(2#3,(4'456*
!"
#$
"%&#%#' (
ATTENTION
Report Creation Wizard formulas are not supported for this
report.
For more information, see “Understanding the report descriptions” on page 787.
Views
This report uses the iSkillsetStat view (see page 325.) For more information
about views, see “Access rights by view” on page 156.
Collection frequency
This report contains interval data.
Templates
This report uses the icross_skillset.rpt template.
Selection criteria
Statistics
Summaries
The report provides totals for each selected skillset for the selected intervals.
Also, totals for the selected intervals are shown grouped by day.
Report (page 1 of 2)
*#)
+ *#)
, *#)
+ +
+ +
1127
Standard reports
1128
!
BestAir
Standard reports
-377%
-'%
'-'%
Report (page 2 of 2)
%%
ATTENTION
Report Creation Wizard formulas are not supported for this
report.
For more information, see “Understanding the report descriptions” on page 787.
Views
This report uses the iTrunkStat view (see page 340.) For more information about
views, see “Access rights by view” on page 156.
Collection frequency
This report contains interval data.
Templates
This report uses the icross_trunk.rpt template.
Selection criteria
Trunk ID iTrunkStat.Timestamp
Statistics
Summaries
The report provides totals for each selected trunk for the selected intervals. Also,
totals for the selected intervals are shown grouped by day.
February 2008
BestAir
!"#
!$ %
!$ %
$
+
1131
Standard reports
Standard reports Standard 8.11
DNIS Statistics
The DNIS Statistics report summarizes the total contact volume to each DNIS
number. The DNIS Statistics report lists the total contacts accepted, total
customer wait time, total contacts abandoned, and the percentage of contacts
that are abandoned after a wait greater than or equal to the service level
threshold defined for the DNIS.
You can use this report to track call handling performance on products or
services associated with a particular DNIS number.
For more information, see “Understanding the report descriptions” on page 787.
Definition: DNIS
Dialed Number Identification Service (DNIS) identifies the dialed number for
contacts coming into the contact center. Typically, DNIS numbers are used for
1-800 numbers. For example, a company may give customers different 1-800
numbers for sales and customer service contacts.
Views
This report uses the DNISStat view (see page 280.) For more information about
views, see “Access rights by view” on page 156.
Collection frequency
The following collection frequency types are available for this report:
interval
daily
weekly
monthly
Templates
This report uses the following templates:
im-res6.rpt
dm-res6.rpt
wm-res6.rpt
mm-res6.rpt
Selection criteria
DNIS iDNISStat.DNIS
DNIS Name iDNISStat.Timestamp
Statistics
Summaries
The report provides totals for each DNIS number, and subtotals for each day,
week, or month, depending on the reporting period selected. For the interval
reporting period, statistics are further broken down by interval. The report also
contains a grand total for all selected DNIS numbers.
! /
!" 23 ! ( ! & !* % , - $ 23 & * 1
%&&#$ !"#$ ' ' ' )!) *$ &"$ +$ %+ !&#$ &+$ .+!' #$ ' ' )!) 0
!
+'
1135
Standard reports
1136
!" # !
BestAir
Standard reports
+
$ ./0 & )" ./0 & )
-
&&% $% ' ' '
(( ) &$ &% *' % ' '
(( ,
!""#$%
'
!&"'(#)#%
'
!""#"'"%
'
7 89
8$-8'778)889
8.":109
$*+,)-
..*//$& $0.1
The IVR Port First Login/Last Logout report provides information about the first
logon to and last logoff from the server. The report lists the ports on which the
first logon and last logoff occurred, and the time at which these events occurred.
For more information, see “Understanding the report descriptions” on page 787.
Views
This report uses the eIVRPortLoginStat view (see page 370.) For more
information about views, see “Access rights by view” on page 156.
Templates
This report uses the em-res5.rpt template.
Selection criteria
none (eIVRPortLoginStat.EventType='LI' OR
eIVRPortLoginStat.EventType='LO')
eIVRPortLoginStat.Timestamp
Statistics
!
BestAir
"# !
$%&'
"! %
(
(
(
(
(
(
(
(
(
(
(
(
(
!"
#
The IVR Port Statistics report shows summarized statistical information grouped
by IVR port. The report provides detailed information about specific IVR ports
used within the contact center. For each port specified, the report shows the total
number of contacts accepted, conferenced, and transferred.
The IVR Port Statistics report also indicates the amount of time the port is
available to accept contacts and how much time is spent waiting to receive
contacts. The report helps you determine whether a specific port may be causing
poor performance within an IVR queue.
The report can also be used for troubleshooting, to identify ports that are taken
out of service, or with no application running.
For more information, see “Understanding the report descriptions” on page 787.
Views
This report uses the IVRPortStat view (see page 288.) For more information
about views, see “Access rights by view” on page 156.
Collection frequency
The following collection frequency types are available for this report:
interval
daily
weekly
monthly
Templates
This report uses the following templates:
im-res4.rpt
dm-res4.rpt
wm-res4.rpt
mm-res4.rpt
Selection criteria
Statistics
Summaries
The report provides totals for each IVR port, and subtotals for each day, week, or
month, depending on the reporting period selected. For the interval reporting
period, statistics are further broken down by interval. The report also contains a
grand total for all IVR ports.
Report (page 1 of 2)
!" # !
BestAir
!"!"#"$
%&
'
/,
#"$
(
& ' '''
/, ) )
)
)
)
#"$
(
& ' '''
/, ) )
)
#"$
(
& ' '''
/, ) )
)
#"$
(
)& ' '''
/, ) )
#"$
(
&''''
/, ) )
)
*+",-.
+"!"//
(
0" 1
Report (page 2 of 2)
#"$
(
& ''''
/, ) )
#"$
(
& ' '''
/, )
)
#"$
(
& ' '''
/, )
)
)
)
)
*+",-.
+"!"//
(
0"1
If the report shows you that a particular IVR queue is not performing well, equip
the IVR queue with more IVR ports.
For more information, see “Understanding the report descriptions” on page 787.
Views
This report uses the IVRStat view (see page 293.) For more information about
views, see “Access rights by view” on page 156.
Collection frequency
The following collection frequency types are available for this report:
interval
daily
weekly
monthly
Templates
This report uses the following templates:
im-res3.rpt
dm-res3.rpt
wm-res3.rpt
mm-res3.rpt
Selection criteria
Statistics
Summaries
The report provides totals for each IVR queue, and subtotals for each day, week,
or month, depending on the reporting period selected. For the interval reporting
period, statistics are further broken down by interval. The report also contains a
grand total for all selected IVR queues.
!"#$
%% "#$
The Music/RAN Route Statistics report shows information about music and
recorded announcement (RAN) routes. For each route, the report provides the
number of route accesses and the route access time.
This report can help you pinpoint any routes that may be overloaded.
For more information, see “Understanding the report descriptions” on page 787.
Views
This report uses the RANMusicRouteStat view (see page 316.) For more
information about views, see “Access rights by view” on page 156.
Collection frequency
The following collection frequency types are available for this report:
interval
daily
weekly
monthly
Templates
This report uses the following templates:
im-res8.rpt
dm-res8.rpt
wm-res8.rpt
mm-res8.rpt
Selection criteria
Route ID iRANMusicRouteStat.RouteID
Route Name iRANMusicRouteStat.Timestamp
Statistics
Summaries
The report provides totals for each music and RAN route, and subtotals for each
day, week, or month, depending on the reporting period selected. For the interval
reporting period, statistics are further broken down by interval. The report also
contains a grand total for all selected music and RAN routes.
#
#
!"
#
$%
& $#'"
((
) )*
+
Route Performance
When reviewing the report, be aware that the value NUMBER OF ATB
PERIODS is increased by one at the beginning of each all-trunks-busy period
within the reporting interval. If an all-trunks-busy period spans two or more
intervals, it is counted only against the interval in which it began.
Use the Crosstab - Route Performance report in conjunction with other reports to
interpret the cause of all-trunks-busy periods. The report helps you determine
the best action to reduce the number of all-trunks-busy periods. For example, a
change in your operating procedures may move contacts through faster and free
up your lines. Or you may find you need to lease extra trunk lines during your
busiest periods.
For more information, see “Understanding the report descriptions” on page 787.
Definition: Route
A route is a group of trunks with similar characteristics.
Example
A contact center may direct two routes to each of its contact center skillsets,
depending on the demographics of a particular customer area. Each route is
configured with multiple trunks.
Views
This report uses the RouteStat view (see page 319.) For more information about
views, see “Access rights by view” on page 156.
Collection frequency
The following collection frequency types are available for this report:
interval
daily
weekly
monthly
Templates
This report uses the following templates:
im-res2.rpt
dm-res2.rpt
wm-res2.rpt
mm-res2.rpt
Selection criteria
Route ID iRouteStat.RouteID
Route Name iRouteStat.Timestamp
Statistics
Summaries
The report provides totals for each route, and subtotals for each day, week, or
month, depending on the reporting period selected. For the interval reporting
period, statistics are further broken down by interval. The report also contains a
grand total for all selected routes.
BestAir
#$
#
#$
# %
' (
%
&'($
# %
) * (
%
/
) *+,'+*
-$.$--%
Skillset by Application
The Skillset by Application report shows summarized skillset statistics for each
application under review. The report provides statistics such as the total number
of contacts accepted for a skillset, number of contacts accepted after the service
level threshold for the skillset, all agent staffed time, and average number of
agents.
For more information, see “Understanding the report descriptions” on page 787.
Views
This report uses the SkillsetStat view (see page 325.) For more information
about views, see “Access rights by view” on page 156.
Collection frequency
The following collection frequency types are available for this report:
interval
daily
weekly
monthly
Templates
This report uses the following templates:
imskill4.rpt
dmskill4.rpt
wmskill4.rpt
mmskill4.rpt
Selection criteria
Statistics
Summaries
The report provides totals for each application, and subtotals for each skillset.
For each skillset, statistics are further broken down by day, week, or month
(depending on the reporting period selected). For the interval reporting period,
statistics are further broken down by interval, and within each interval, by
skillset. The report also contains a grand total for all selected applications.
! "#
$%&'()'*
,( ! "#
$%&'(+,
,( ! "
! "#
+&-
%-&*../) /'0
Skillset Performance
By indicating the volume of contacts and the delay times customers experienced,
along with the amount of time agents are busy servicing contacts in the skillset,
the report indicates whether the skillset has the number of agents required to
service customers. If a particular skillset is not performing well, consult the
agent reports.
For network skillsets, see “Network Skillset Performance” on page 1070 for a
report showing all local and incoming NSBR contacts in this skillset. For more
information, see “Understanding the report descriptions” on page 787.
Views
This report uses the SkillsetStat view (see page 325.) For more information
about views, see “Access rights by view” on page 156.
Collection frequency
The following collection frequency types are available for this report:
interval
daily
weekly
monthly
Templates
This report uses the following templates:
imskill1.rpt
dmskill1.rpt
wmskill1.rpt
mmskill2.rpt
Selection criteria
Statistics
Summaries
The report provides totals for each skillset, and subtotals for each day, week, or
month, depending on the reporting period selected. For the interval reporting
period, statistics are further broken down by interval. The report also contains a
grand total for all selected skillsets.
$ ! % & ! # ! ! "#$#
'(
!
! " $ $ $"! !
)*+,(
-
.* $ ! % & ! # ! #! "
!
4$%+5,+ !! 2 2 2 3 2
! !! $ " !$! #!"
1 !
( 6 !2 6
4$%+5,+ 2 2 ! 2 6 2
1 ! # !! " $ !$ $!$
!
4$%+5,+ 26 6 6 ! 23
! " ! $ ! !$$ $ !#
$ ! % ! # ! #! "
$ ! % & ! # ! ! "#$#
.
+/0*/+
1 1!#" 2 ,
1159
Standard reports
Standard reports Standard 8.11
Trunk Performance
The Trunk Performance report helps you understand contact center traffic
patterns. The report lists the total call volume by individual trunk, including total
contacts accepted, answered, and offered.
If specific trunks are under used or consistently backlogged, you can take action
to make these contact center resources more efficient.
For more information, see “Understanding the report descriptions” on page 787.
Views
This report uses the TrunkStat view (see page 340.) For more information about
views, see “Access rights by view” on page 156.
Collection frequency
The following collection frequency types are available for this report:
interval
daily
weekly
monthly
Templates
This report uses the following templates:
im-res1.rpt
dm-res1.rpt
wm-res1.rpt
mm-res1.rpt
Selection criteria
Trunk ID iTrunkStat.Timestamp
Statistics
Summaries
The report provides totals for each trunk, and subtotals for each day, week, or
month, depending on the reporting period selected. For the interval reporting
period, statistics are further broken down by interval. The report also contains a
grand total for all selected trunks.
! " #$
BestAir
('
%
&' (&+* ()* ,--) (&+) ())
!."
/0
/ #
/$ ! /" / /
0
$ ! / /
$ " !0
0
#
/ ! / 0
/0
/# ! ! ! / /
/# " ! $ 0 / /
!
12'3&1+&14
1(&1'15&611
/78/918 :/.2
In this section
Campaign Call by Call Details 1166
Campaign Script Results Details 1169
Campaign Summary 1172
Script Summary 1175
The Campaign Call by Call Report lists a detailed description of each contact,
including the number dialed for a campaign.
ATTENTION
Report Creation Wizard formulas are not supported for this
report.
For more information, see “Understanding the report descriptions” on page 787.
Views
This report uses the CampaignCallByCallDetails view.
Collection frequency
The following collection frequency types are available for this report:
interval
daily
weekly
monthly
Selection Criteria
You can apply a filter to any of the fields in the view. For example, a filter can be
applied to specific disposition codes.
Data Range
You can use the data range to restrict the report to a specific date.
Templates
This report uses the CampaignCallByCallDetailsReport.rpt template
Summaries
The report is in the Outbound group. Any call can be dialed multiple times, in
which case each call attempt is represented by a separate entry.
For example, if the number 091 389123 is dialed initially, and the number is
busy and dialed again later with a successful connection, two entries appear in
the report for this number.
() %& ' $$ "#
!
() %'%'+ $$ "*
() , ' $$ "
() %(/ $$ -+&-.
() ''& $$ "*
!
() 1 $$ ! 0 -.
!
() 20) $$ "*
!
!
() 33&( $$ ! -+&-.
() &(&( ( $$
!
() &(&( ( ! $$
!
() &(&( ( $$ "#
!
() &( ' $$ "
() 5'% ( $$ -.4-('
() 5'% ( $$
!
!
() 5'% ( $$ -.4-('
!
() 5'% ( $$ -.4-('
() 5'% ( $$ -+&-.
() 6 )( $$ "
!
() +9'(( $$ /- 78
!
!
() /&;
( $$ (:
() /&;
( $$
!
!
() /&;
( $$
!
!
() /&;
( $$
!
!
() /&;
( $$ "#
!
() 6& $$ "*
!
() 1( &( $$
!
() 1( &( $$ "#
! () 6 )4-( ! $$ "#
!
() & '&9 $$ "#
!
<,(<:9(<0 <(< </(+<<-)=><?-.- )< 4';(@
%$
'
()*&+*(++),,&-+$
&#&
ATTENTION
Report Creation Wizard formulas are not supported for this
report.
For more information, see “Understanding the report descriptions” on page 787.
Views
This report uses the CampaignAgentScriptResultsCallByCall view.
Collection frequency
The following collection frequency types are available for this report:
interval
daily
weekly
monthly
Selection criteria
You can apply a filter to any of the fields in the view. For example, you can
apply a filter to specific disposition codes.
Data range
You can use the data range to restrict the report to a specific date.
Templates
This report uses the CampaignCallByCallAgentScriptDetailsReport.rpt
template.
Summaries
The report is in the Outbound group. You must include an agent script as part of
the campaign in order for questions and answers to be associated with a contact.
ATTENTION
If you require the data in electronic format, you can use the
OCMT export tool to export campaign data and results to a
text file.
BestAir
"$
"# "
!" #
"$
)
4! "# "
! "#
"$
! 7
"# $
!$
"#
"$
"
4! "# "
!8 8#
"$
$ 5.-
4! "# "
" "#
:#7&:,/&:.
:&::+&)::(-;
<:=(3(-:
0
)'&>
&'
#(#)*+$,+),,*)-*,.' $%$
Campaign Summary
ATTENTION
Report Creation Wizard formulas are not supported for this
report.
For more information, see “Understanding the report descriptions” on page 787.
Views
This report uses the CampaignSummary view.
Collection frequency
The following collection frequency types are available for this report:
interval
daily
weekly
monthly
Selection criteria
You can apply a filter to any of the fields in the view. For example, you can
apply a filter to specific disposition codes.
Data range
You can use the data range to restrict the report to a specific date.
Templates
This report uses the CampaignSummaryReport.rpt template.
Summaries
The report is in the Outbound group.
ATTENTION
If you require the campaign data in electronic format, you
can use the OCMT export tool to export the campaign data
and results to a text file.
BestAir
!
"
"
##+
##+1
##+2
($-(
3 #(
4!#5.46.43 4.4 #4,.$44(*04%(( 4# ()7
*)
!"#$%&$"&&#"'(&() %%
Script Summary
ATTENTION
Report Creation Wizard formulas are not supported for this
report.
For more information, see “Understanding the report descriptions” on page 787.
Views
This report uses the ScriptSummary view.
Collection frequency
The following collection frequency types are available for this report:
interval
daily
weekly
monthly
Selection criteria
You can apply a filter to any of the fields in the view. For example, you can
apply a filter to specific disposition codes.
Data Range
You can use the data range to restrict the report to a specific date.
Templates
This report uses the ScriptSummaryReport.rpt template.
Summaries
The report is in the Outbound group.
ATTENTION
If you require the campaign data and results in electronic
format, you can use the OCMT export tool to export the
campaign data and results to a text file.
BestAir
"#$
%#
"# &
&
!"
*$+$+$,
%#
+
,
!"
*$+$+$+& %#
$&,
+
+ -
&,
*
+&
!#
1
2 034
2 0
)
.# %
5# % 6#
57###
2 03
57
.# 1#
57
!!
86 %#8(0#8. 8#8 8'#88)9:8;/ )8<
,+
$%&!'&$''%($'#)*+ *
! 1
In this section
Overview 1180
Access Classes 1182
Report Groups 1185
User Defined Partitions 1188
Users 1191
Overview
These reports are listed under the new server entry Administration. You cannot
import any user-created report or a Report Creation Wizard report to the
Administration server. However, you can save a user-defined Access and
Partition Management report in the private report templates folder for
scheduling.
ATTENTION
Report Creation Wizard formulas are not supported for
these reports.
Report access
The following users and groups can run these reports:
webadmin
Users with Full data across all servers
Users with All Data for Administration server
Users with Standard Configuration Reports checked for Administration
server
Data source
The data for these reports is generated from the proprietary API developed for
the Contact Center Manager Administration server. The data for these reports is
extracted from ADAM (active directory). The data extracted from ADAM is
stored in the temporary Microsoft Access database file for each user report
session. The reports are run using these temporary Microsoft Access database
files as the data source. When all-trunks-busy the report session is closed, the
temporary Microsoft Access database files are removed from the server. The file
name is UserID_DateTime_APMReport.MDB.
Access Classes
The Access Classes report presents all information concerning access classes
that are configured on the Contact Center Manager Administration server:
Access Class Name—Contains the access class name.
Members—Contains the users assigned to the access class.
Access Class properties—Shows access rights per server.
ATTENTION
Report Creation Wizard formulas are not supported for this
report.
For more information, see “Understanding the report descriptions” on page 787.
Templates
This report uses the APMAcc.rpt template.
Selection criteria
Report (page 1 of 2)
$$
" &'('
"
&()*( &'
"
' &'('
"
+ ', &'('
"
$-.
' &'('
"
(("$
##"' &' '('
"",
" &'('
"
(-""-"
3&*, 4 &'('
"
$
.(
+* &'('
"
5 &'('
"
*" &'('
"
)"2" &' '('
6$"&( &(
6$"$ &' '('
51&
/ &'('
"
%0
* $ , &' '('
,# (". &' '('
,# '1$, &'('
"
&"/)(#$"(".
,*2"$
&"/
$ &' '('
&"/
2*"(".
,*2"$
&* &'('
"
$(12" &'('
"
$( &'('
"
8,"8"%08!
" 8((8&( 86$"8(8
348,$$9&,
,1 of 2
Report (page 2 of 2)
0""
0"" &'('
"
*(-
##"'
" &'('
"
8,"8"%08!
" 8((8&( 86$"8(8
348,$$9&,
,2 of 2
Report Groups
The Report Group report lists information for each Contact Center Manager
Server configured on Contact Center Manager Administration.
ATTENTION
Report Creation Wizard formulas are not supported for this
report.
For more information, see “Understanding the report descriptions” on page 787.
Templates
This report uses the APMRGRP.rpt template.
Selection criteria
Server IP none
Server Name
Report (page 1 of 2)
!!
"
! !
,*-!&.
,*-!&.
"
( !%
!(
!(
"
( !%
!(
!(
"
( !%
!(
"
( !%
/!0#*/!#'!(*/1
#/..*/2.!/3*!"#/./
45/2-.62
!
Report (page 2 of 2)
"
( !%
!(
!(
"
( !%
!(
"
( !%
!(
"
( !%
!(
!(
"
( !%
!(
!(
"
( !%
!(
/!0#*/!#'!(*/1
#/..*/2.!/3*!"#/./
45/2-.62
!
The User Defined Partitions report lists the following information for each
user-defined partition:
Partition Name—Contains the user-defined partition name.
Members—Contains the users assigned to the user-defined partition with
rights on Contact Center Manager, Historical Reporting, and Real Time
Reporting components.
Server Name—Shows data allocated for all Contact Center Manager
Servers for the partition, such as Agents, Skillsets, Report Groups,
Applications, CDN, and DNIS.
ATTENTION
Report Creation Wizard formulas are not supported for this
report.
For more information, see “Understanding the report descriptions” on page 787.
Templates
This report uses the APMPartition.rpt template.
Selection criteria
Report (page 1 of 2)
#$
%
!" ##
())$ #
!
####
&&
+",')'
,'"
-%",))&.'
-%",%%"&.'
-%",/'0
-%",)'
-%", 11%
,2 ),"))'
,%&&'"))
,"))', 3
//,"
45,2 ),"))'
*
,2 ),"))'
'( )*(
67%.8)'6%)-%"'6*
)&611'6/1%&.69'%!)616
:;677%&</7
7.%2
Report (page 2 of 2)
'( )*(
&==,.&72%&!
&==,
))
))
&==,
%&2. %&
&==, )=
&==,-%"&.
&==,'
>'?% 1
>'?% 1
#((&+
,,11)!%&
',!1
,,11)!%&
-%",!1
7
))'
'* "
%
=)'
$ ####
11%
67%.8)'6%)-%"'6*
)&611'6/1%&.69'%!)616
:;677%&</7
7.%2
Users
The Users report lists information for each user configured on Contact Center
Manager Administration.
ATTENTION
Report Creation Wizard formulas are not supported for this
report.
For more information, see “Understanding the report descriptions” on page 787.
Templates
This report uses the APMUser.rpt template.
Selection criteria
User ID none
BestAir
-"".&
/""0""1
In this section
Overview of Network Control Center reports 1194
Network Call by Call Statistics 1196
Network Consolidated Application Performance 1200
Network Consolidated DNIS Statistics 1206
Network Consolidated Incoming Calls 1212
Network Consolidated Outgoing Calls 1219
Network Consolidated Route Performance 1223
Network Consolidated Skillset Call Distribution 1227
Network Consolidated Skillset Performance 1231
Network Site and Application Properties (NCC) 1237
Network Skillset Routing Properties (NCC) 1241
Network Table Routing Assignments (NCC) 1245
Nodal Consolidated Application Delay Before Abandon 1248
Nodal Consolidated Application Delay Before Answer 1254
Nodal Consolidated Application Performance 1260
This section lists the reports that you can generate when logged on to the
Network Control Center. In some cases, these reports are similar to reports that
are available on the server, but they use a different view or contain additional
fields.
ATTENTION
For network consolidated reports, define the same user ID on
the Network Control Center and each server in the network.
(The passwords need not match the password defined on the
Network Control Center.) That user ID needs the rights
required to generate the report. To create a report, log in to the
Network Control Center with that user ID and password.
For information about reports that can be run on other servers in the network,
see Section E: “Network reports,” on page 1035.
If you have servers in different time zones, time zone conversion compares
activity for the same period. For example, if you want to interpret the impact of
a new commercial that is broadcast simultaneously at all sites, you use a
consolidated report based on a particular time at the Network Control Center.
If you want to report on activity at all sites during the same period—for
example, lunch hour—you do not use time zone conversion. (If a site has not
reached the specified time, the report does not contain data for that site. For
example, if the current time at one site is 11:00 a.m., that site is not included in
the report.)
ATTENTION
For time zone conversion to work, the Time Relative to
GMT must be configured for all sites in the Site
Parameters.
Network Control Center option only. For each contact that is networked out, the
Network Call by Call report shows detailed information including time, event,
agent, source, and destination.
ATTENTION
Network Call by Call reports contain a large amount of data.
Consequently, they take much longer to generate than other
types of reports.
You cannot schedule user-defined reports that use this
standard report as a template.
You can generate this report as an ad hoc report.
To run this report, you must select at least one network site.
For example, the administrator of the BestAir Network Control Center wants to
generate a Network Call by Call report to report on contacts networked out from
the Chicago server during the period from 10:00 a.m. to 11:00 a.m., Toronto
time. (Chicago is one hour behind Toronto.) When generating the report, the
administrator identifies Chicago as the source site, and specifies a data
extraction period of 9:00 a.m. to 10:00 a.m.
Views
This report uses the following views:
For more information about views, see “Access rights by view” on page 156.
Collection frequency
This report contains interval data.
Templates
This report uses the netcbc.rpt template.
Selection criteria
none none
Statistics
ATTENTION
To run this report, you must select at least one network site.
For more information, see “Understanding the report descriptions” on page 787.
If you choose not to use the time zone conversion option, the Network Control
Center time is not converted to local time. For example, if the administrator
generates the same report, without time zone conversion, it includes events
occurring at Toronto between 11:00 a.m. and 12:00 noon local time, and at San
Francisco between 11:00 a.m. and 12:00 noon local time.
Views
This report uses the ApplicationStat view (see page 249.) For more information
about views, see “Access rights by view” on page 156.
Collection frequency
The following collection frequency types are available for this report:
interval
daily
weekly
monthly
Templates
This report uses the following templates:
icnetapp1.rpt
dcnetapp1.rpt
wcnetapp1.rpt
mcnetapp2.rpt
Selection Criteria
NACD statistics
Summaries
The report provides totals for each site and application, and subtotals for each
day, week, or month, depending on the reporting period selected. For the
interval reporting period, statistics are further broken down by interval.
Galway
*+,
# $ %$& #' % '() $## #( (' "
-
./0
.
(,
# $ %$& #' % '() $## #( (' "
/
0
1
00
12
0
3
1
0 2
1
1
0/
0
1
2 3
2
1
/
3
1 0
0
3
2
2
12
2
1
1
3
0
2
3
0/
01
2
0
3
3
2
0
0
0
01
2
0
0
1
0
/
1
0
3
0
/ 0
/
0
3 0
/
1
1
0
3
/ 1
0
0
1/
1
1
2 / /
13
3
45-6 4+) 47 4
4
-48 4
4 9!:4$ ;55<5
1
'2( 2# )3%)##0 .%#
BestAir
4
+)'(
+)'( +)'( *-
+)'( + $() # $ $'( %& $'(
+)'( !.(+)'( -+)'( +)'( %&*-
+$, +$, +$, $, %&+)'( $()
45-6 4+) 47 4
4
-48 4
4 9!:4$ ;55<5
1
'2( 2# )3%)##0 .##
1205
Standard reports
Standard reports Standard 8.11
Network Control Center option only. This report contains summarized DNIS
statistics for all sites in the network. For each site, the report lists all DNISs, and
gives total contacts accepted, total contacts abandoned, the percentage of
contacts that abandoned after a wait greater than or equal to the service level
threshold defined for the DNIS, and the total number of contacts networked out.
The report also contains a grand summary section that consolidates the results
for all sites in the network, and provides a roll-up summary for all contact
statistics.
You can use this report to track network performance for a particular DNIS
number.
ATTENTION
To run this report, you must select at least one network site.
For more information, see “Understanding the report descriptions” on page 787.
If you choose not to use the time zone conversion option, the Network Control
Center time is not converted to local time. For example, if the administrator
generates the same report, without time zone conversion, it includes events
occurring at Toronto between 11:00 a.m. and 12:00 noon local time, and at San
Francisco between 11:00 a.m. and 12:00 noon local time.
Views
This report uses the DNISStat view (see page 280.) For more information about
views, see “Access rights by view” on page 156.
Collection frequency
The following collection frequency types are available for this report:
interval
daily
weekly
monthly
Templates
This report uses the following templates:
icnetres6.rpt
dcnetres6.rpt
wcnetres6.rpt
mcnetres6.rpt
Selection criteria
Summaries
The report provides totals for each DNIS number, and subtotals for each day,
week, or month, depending on the reporting period selected. For the interval
reporting period, statistics are further broken down by interval. The report also
contains a grand summation for all selected DNIS numbers.
BestAir
# #
##
&' ( + . # /# #0# # /#
)1 #( '$0
1
Report (page 1 of 2)
!" # $ $!" # $ $!" % '' ) * ( * !" ,* - (- (- (- (- (- * * (
Galway
!" ! ! $% # ! ! "
&''()*
)
+##''(
*-
' $% '
2
&'',)*
)*-
-+##'',
*-
!! ! ! $% ( ! ! "
5607 5
)1 58
5# 5
059
'5
5:;5<<=26
.
/0/
!!1!1'2'!(3!4* 4-!5"
# #
##
&' ( + . # /# #0# # /#
)1 #( '$0
1
Report (page 2 of 2)
!" # $ $!" # $ $!" % '' ) * ( * !" ,* - (- (- (- (- (- * * (
467
(
5607 5
)1 58
5# 5
059
'5
5:;5<<=26
.
/0/
!!1!1'2'!(3!4* 4-'5"
1211
Standard reports
Standard reports Standard 8.11
Network Control Center option only. This report contains incoming contact
statistics for all sites in the network. It consists of information about the number
of network contacts originating at each site, that are offered, accepted, and
abandoned at the site. The report provides statistics about the number of contacts
agents accepted or rejected after the service level threshold and the delays
experienced by contacts. It also provides a grand summary section that
consolidates the results for all sites in the network and a roll-up summary for all
contacts statistics.
ATTENTION
To run this report, you must select at least one network site.
For more information, see “Understanding the report descriptions” on page 787.
If you choose not to use the time zone conversion option, the Network Control
Center time is not converted to local time. For example, if the administrator
generates the same report, without time zone conversion, it includes events
occurring at Toronto between 11:00 a.m. and 12:00 noon local time, and at San
Francisco between 11:00 a.m. and 12:00 noon local time.
Views
This report uses the NetworkInCallStat view (see page 299.) For more
information about views, see “Access rights by view” on page 156.
Collection frequency
The following collection frequency types are available for this report:
interval
daily
weekly
monthly
Templates
This report uses the following templates:
icnet-10.rpt
dcnet-10.rpt
wcnet-10.rpt
mcnet-10.rpt
Selection criteria
Statistics
Summaries
The report provides totals for each source site, and subtotals for each day, week,
or month, depending on the reporting period selected. For the interval reporting
period, statistics are further broken down by interval.
BestAir
! " !"
"
!#
(
(
(
!# (
Report (page 1 of 3)
)*!* %##" ! " $ $ " !" " $ $ " &' &' !& !& &' &' !& !&
Galway
!"#
%* *% + % $%& %$ %%' % ())* )(%( ()%%& )(*$
,-./
)'
%* *% + % $%& %$ %%' % ())* )(%( ()%%& )(*$
)* %* *% + % $%& %$ %%' % ())* )(%( ()%%& )(*$
34
25 3
313! 3
236
*337839:4
0
((1( 1*$*($*-2 -(3%
! " !"
"
!#
(
(
(
!# (
Report (page 2 of 3)
)*!* %##" ! " $ $ " !" " $ $ " &' &' !& !& &' &' !& !&
-./
!"#
%* *% + % $%& %$ %%' % ())* )(%( ()%%& )(*$
)'
%* *% + % $%& %$ %%' % ())* )(%( ()%%& )(*$
)* %* *% + % $%& %$ %%' % ())* )(%( ()%%& )(*$
34
25 3
313! 3
236
*337839:4
0
((1( 1*$*($*-2 -*3%
1217
Standard reports
1218
Standard reports
! " !"
"
!#
(
(
(
!# (
Report (page 3 of 3)
)*!* %##" ! " $ $ " !" " $ $ " &' &' !& !& &' &' !& !&
4
,
! " !"
"
%##" ! " !#$ $
" !"
" !#$ $
"
) ) (&
()
&' ()&' &'!&
&'!&
((( %$ '() %
%*&$* )(%( %*'( )(*$
34
25 3
313! 3
236
*337839:4
0
((1( 1*$*($*-2 -%3%
Network Control Center option only. This report contains outgoing contact
statistics for all sites in the network. It contains information about the number of
outgoing network contacts offered, accepted, and abandoned at the source and
destination sites. The report also contains a grand summary section that
consolidates the results for all sites in the network, and provides a roll-up
summary for all contact statistics.
ATTENTION
To run this report, you must select at least one network site.
For more information, see “Understanding the report descriptions” on page 787.
If you choose not to use the time zone conversion option, the Network Control
Center time is not converted to local time. For example, if the administrator
generates the same report, without time zone conversion, it includes events
occurring at Toronto between 11:00 a.m. and 12:00 noon local time, and at San
Francisco between 11:00 a.m. and 12:00 noon local time.
Views
This report uses the NetworkOutStat view (see page 308.) For more information
about views, see “Access rights by view” on page 156.
Collection frequency
The following collection frequency types are available for this report:
interval
daily
weekly
monthly
Templates
This report uses the following templates:
icnet-11.rpt
dcnet-11.rpt
wcnet-11.rpt
mcnet-11.rpt
Selection criteria
Statistics
Summaries
The report provides totals for each source site, and subtotals for each destination
site. Statistics are further broken down by day, week, or month, depending on
the reporting period selected. For the interval reporting period, statistics are
further broken down by interval.
: BestAir
Galway
!"
Dublin
+
"
,-*. ,
,/" ,& , *,0 %,,"1#2,+"34-
&
'(')
**+*+,-,*.-#/ #*0.
Network Control Center option only. This report contains route performance
statistics for all sites in the network. For each site, the report lists all routes, and
indicates how often and how long all trunks within the route are busy. The report
lists the total number of contacts that are unable to reach another site because all
trunks within the route are busy. It also contains a grand summary section that
consolidates the results for all sites in the network, and provides a roll-up
summary for all contact statistics.
ATTENTION
Calls blocked by all-trunks-busy signal peg against the
Default_Route, 999.
To run this report, you must select at least one network site.
For more information, see “Understanding the report descriptions” on page 787.
If you choose not to use the time zone conversion option, the Network Control
Center time is not converted to local time. For example, if the administrator
generates the same report, without time zone conversion, it includes events
occurring at Toronto between 11:00 a.m. and 12:00 noon local time, and at San
Francisco between 11:00 a.m. and 12:00 noon local time.
Views
This report uses the RouteStat view (see page 319.) For more information about
views, see “Access rights by view” on page 156.
Collection frequency
The following collection frequency types are available for this report:
interval
daily
weekly
monthly
Templates
This report uses the following templates:
icnetres2.rpt
dcnetres2.rpt
wcnetres2.rpt
mcnetres2.rpt
Selection criteria
Call statistics
Summaries
The report provides totals for each site, and subtotals for each route. Statistics
are further broken down by day, week, or month, depending on the reporting
period selected. For the interval reporting period, statistics are further broken
down by interval.
: BestAir
%& ()
&*#
+&, ()
&*+-, %& %.%
# $ #$%& # $
'& # $ & # $
BestAir2
!" # #$!%! ##&''#
()$)*
+$#
$
# # #$!%! ##&''#
/0
/
/
/
/
0
/0 ! # # #$!,& #$!,&
00
0
00 $ # # ####'% ####$-
# # #$!%! ##&''#
()).+---
$
# !" # ###### ######
0
/
0 # & # ###### ######
/
/
/
0
/
# !& # ###### ######
# !" # ###### ######
12
.3 1
)
& 14 1% 1
.15
+11 6781 !!92
Page 1 of 1
/
*0*
#-1#"1$##'!!#&#%
Network Control Center option only. This report contains skillset call
distribution statistics for all sites in the network. For each skillset, the report lists
the total local and incoming network contacts accepted by agents at each site,
the percentage of contacts agents accepted that are local and incoming network
contacts, and the average delay a customer experienced. The report contains a
skillset summary that consolidates the results for all sites for each skillset, and a
grand summary section that consolidates the results for all sites in the network
and provides a roll-up summary for all contact statistics.
For more information, see “Understanding the report descriptions” on page 787.
Views
This report uses the SkillsetConStat view (see page 325.) For more information
about views, see “Access rights by view” on page 156.
Collection frequency
The following collection frequency types are available for this report:
interval
daily
weekly
monthly
Templates
This report uses the following templates:
icsnet_cd-12.rpt
dcsnet_cd-12.rpt
wcsnet_cd-12.rpt
mcsnet_cd-12.rpt
Selection criteria
Summaries
The report provides totals for each skillset, and subtotals for each site. Statistics
are further broken down by day, week, or month, depending on the reporting
period selected. For the interval reporting period, statistics are further broken
down by interval.
Network Control Center option only. This report contains skillset performance
statistics for all sites in the network. For each site, the report lists the total local
and incoming network contacts accepted by agents for the skillset, the number
and percentage of contacts agents accepted after a predefined threshold, the
maximum delay a customer experienced, and the total time all agents are busy
servicing contacts to the skillset. The report also contains a grand summary
section that consolidates the results for all sites in the network, and provides a
roll-up summary for all contact statistics.
ATTENTION
To run this report, you must select at least one network site.
For more information, see “Understanding the report descriptions” on page 787.
If you choose not to use the time zone conversion option, the Network Control
Center time is not converted to local time. For example, if the administrator
generates the same report, without time zone conversion, it includes events
occurring at Toronto between 11:00 a.m. and 12:00 noon local time, and at San
Francisco between 11:00 a.m. and 12:00 noon local time.
Views
This report uses the SkillsetStat view (see page 325.) For more information
about views, see “Access rights by view” on page 156.
Collection frequency
The following collection frequency types are available for this report:
interval
daily
weekly
monthly
Templates
This report uses the following templates:
icnet-12.rpt
dcnet-12.rpt
wcnet-12.rpt
mcnet-12.rpt
Selection criteria
Agent statistics
Summaries
The report provides totals for each site, and subtotals for each skillset and site-
application combination. Statistics are further broken down by day, week, or
month, depending on the reporting period selected. For the interval reporting
period, statistics are further broken down by interval.
BestAir
! % !" !" ' '
'-
)+
+
)+
!" !" #$ $" #$ $" & ' () *
##"
+
,# '
Report (page 1 of 2)
Galway
!"#$
%&' )* (')' %+ ), ,() )) ,%+'+)% (+ ,)- (
6!"'' 3451 /0. 1
.
.
1
/2
%&' ) (')' %+ ), ,() )) ,%+'+)% (+ ,)- (
78'9
7! 7:
7 7
'73
+77;<7=-8
1
22
))3) 3(,(('('4 )'
1235
Standard reports
1236
Standard reports
! % !" !" ' '
'-
)+
+
)+
!" !" #$ $" #$ $" & ' () *
##"
+
,# '
Report (page 2 of 2)
5.
!"#$
)*
78'9
7! 7:
7 7
'73
+77;<7=-8
1
22
))3) 3(,(('('4 ('
Network Control Center option only. The Network Site and Application
Properties (NCC) report lists each site in the network and, for each one, shows
its properties.
ATTENTION
User-defined reports using this standard report as a template
cannot be scheduled.
For more information, see “Understanding the report descriptions” on page 787.
Views
This report uses the following views:
NCCSite (see page 424)
NCCRemoteApplication (see page 422)
For more information about views, see “Access rights by view” on page 156.
Templates
This report uses the config38.rpt template.
Selection criteria
Sites properties
Application properties
Grouping
Applications are grouped by site.
Report (page 1 of 2)
BestAir
Galway !
Dublin !
Shannon !
Belfast !
*%
*+,*-**%*$ **./.0*'&123
!!"# $
%
Report (page 2 of 2)
BestAir
56
$
&'
77 8
&5$#4) 49##.
&5) 4#.9#
#.
% 8 8
#.
. 8
#.
. 8
#.
: 8
#.
1 8
#.
; 8
#.
8
#.
< 8
#.
= 8
#.
2 8
#.
> 8
#.9#
% 8 8
&5
%
8 8
77 8
+, 8
# 8
*%
*+,*-**%*$ **./.0*'&123
!!"# $
Network Control Center option only. The Network Skillset Properties (NCC)
report lists all the network skillsets and indicates the routing table method
utilized for the network skillset.
A routing table defines how contacts are queued to the sites on the network.
Each site has a routing table for each network skillset at that site. When you
create a network skillset, you choose the routing table type for that skillset. Two
types of routing tables are available.
ATTENTION
User-defined reports using this standard report as a template
cannot be scheduled.
For more information, see “Understanding the report descriptions” on page 787.
Round robin
The server queues the first contact to the first, second, and third site in the
routing table for the network skillset. When an agent becomes available at one
of these sites, the server reserves the agent, and the contact is presented to the
agent.
When the second contact arrives, the server queues it to the second, third, and
fourth site in the routing table. When the third contact arrives, the server queues
it to the third, fourth, and fifth site—and so on.
This type of routing table distributes contact most evenly among the sites.
Sequential
Whenever a contact arrives, the server queues it to the first three sites in the
routing table. When an agent becomes available at one of these sites, the server
reserves the agent, and the contact is presented to the agent.
This type of routing table minimizes the number of trunks used to network
contacts.
Views
This report uses the following views:
NCCNetworkSkillset (see page 418)
NCCRanking (see page 420)
For more information about views, see “Access rights by view” on page 156.
Templates
This report uses the config26.rpt template.
Selection criteria
Statistics
Grouping
Network skillsets are grouped by source site.
BestAir
Galway
'!
#
() Shannon
,-, Shannon
! ( Shannon
#,
Shannon
#*(
+ Shannon
.)#*(
+ Shannon
/
,.' #
Shannon
01 # Shannon
01 !0 Shannon
-
)
Shannon
,++( Shannon
! ( Shannon
! (0
Shannon
#*(
+ Shannon
Shannon
)
Shannon
"20! Shannon
#,,'
Dublin
#/
,((
Dublin
#/
!(
Dublin
#/
"(
Dublin
#5
,((
Dublin
#5
!(
Dublin
#5
"(
Dublin
#60#-#
#60#-#
#60#-#
/!
Dublin
#60#-#
#60#-#
++
+
( Dublin
3
1(
Dublin
!"
#$%&$%'(%%'() *
(1
Network Control Center option only. The Network Table Routing Assignments
(NCC) report provides a listing of the Network Control Center table routing
assignments. For each assignment, the report provides status, source site,
comments, and the routing table.
For more information, see “Understanding the report descriptions” on page 787.
Views
This report uses the following views:
NCCNetworkSkillset (see page 418)
NetworkRankingAssignment (see page 427)
For more information about views, see “Access rights by view” on page 156.
Templates
This report uses the config25.rpt template.
Selection criteria
Statistics
Grouping
Assignments are grouped by AssignName and NetworkSkillsetName.
BestAir
!
"
#
$ %&
'
(
&
#%& Belfast
, Shannon
#%& Belfast
, Shannon
!"#"$%%&'$'()
*
Network Control Center option only. This report is similar to the Application
Delay Before Abandon report, but it contains statistics for all applications in the
network. Application statistics are consolidated across all sites.
This report helps you to gauge service quality by determining how many
customers disconnect (abandon) before reaching an agent. The spectrum shows
how long customers typically wait before abandoning, whether the customers
abandon before or after the service level threshold for the application, and the
percentage of contacts that are abandoned.
ATTENTION
To run this report, you must select at least one network site.
For more information, see “Understanding the report descriptions” on page 787.
Views
This report uses the ApplicationStat view (see page 249.) For more information
about views, see “Access rights by view” on page 156.
Collection frequency
The following collection frequency types are available for this report:
interval
daily
weekly
monthly
Templates
This report uses the following templates:
inodapp5.rpt
dnodapp5.rpt
wnodapp5.rpt
mnodapp6.rpt
Selection criteria
Statistics
Summaries
The report provides totals for each site, and subtotals for each application.
Statistics are further broken down by day, week, or month, depending on the
reporting period selected. For the interval reporting period, statistics are further
broken down by interval.
BestAir
Galway
Report (page 1 of 48)
,*
#%'& #%'& )+
.-
,*
)+
0
)
/-01
21-2
,*
)+
0
)
12-3
1&4 15
1 1
-16
11 7!81!#)2202
2 &3%*3%,##$#(
/ 0.#$&
1251
Standard reports
1252
Standard reports
BestAir
/
#4 5!
Report (page 2 of 48)
,*
'* %% ' ()*+ %% ,& $(
%)*,
)!9:;)#
,$ = / = / . . = == =/ / = / = / . = = ?
# # #
#)
)&
)
)$
)%
)
= / . .= ./ = = = / > . > . > . =/
)* ?
%%* ,
,$ = / = / . . = == =/ / = / = / . = = ?
# # #
#)
)&
)
)$
)%
)
= / . .= ./ = = = / > . > . > . =/
)* ?
.> . 0>
/
=
'* %% ' ()* %% ,& $(
12-3
1&4 15
1 1
-16
11 7!81!#)2202
2 &3%*3%,##$#(
/ 0.%$&
BestAir
Report (page 48 of 48)
0/-1
0&. 02
0 0
-03
00 4!50!#)//6/
& ((%%' %& & "
) *+
1253
Standard reports
Standard reports Standard 8.11
Network Control Center option only. This report is similar to the Application
Delay Before Answer report, but it contains statistics for all applications in the
network. Application statistics are consolidated across all sites.
This report helps you to gauge service quality by determining how long
customers wait before connecting to an agent. The report also indicates whether
the delay occurred after the skillset received the contact.
ATTENTION
To run this report, you must select at least one network site.
For more information, see “Understanding the report descriptions” on page 787.
Views
This report uses the ApplicationStat view (see page 249.) For more information
about views, see “Access rights by view” on page 156.
Collection frequency
The following collection frequency types are available for this report:
interval
daily
weekly
monthly
Templates
This report uses the following templates:
inodapp3.rpt
dnodapp3.rpt
wnodapp3.rpt
mnodapp4.rpt
Selection criteria
Statistics
Summaries
The report provides totals for each site, and subtotals for each application.
Statistics are further broken down by day, week, or month, depending on the
reporting period selected. For the interval reporting period, statistics are further
broken down by interval.
BestAir
Galway
,+
+%
-+./
0/+0
+%
01,2
0#' 03
0 0
,04
00 5!60!-$11781
1 0 &2%(2%'##&%&
- .,#''
1257
Standard reports
1258
Standard reports
BestAir
-
#3 4!
Report (page 2 of 55)
+%
)( %% $%# %') )' )% #%
#$%+
$!9:;$-
+(
7 / &
7 / . . 7 77 7/ / 7 / 7 / . 7 7 >
&6
*6
6
'
'6
$6
)
)6
% %
%6
# #
#6
6
7 / . .7 ./ 7 7 7 / = . = . = . 7/
$% >
#&% +
+( 7 / 7 / . . 7 77 7/ / 7 / 7 / . 7 7 >
&
&6
*6
6
'
'6
$6
)
)6
% %
%6
# #
#6
6
7 / . .7 ./ 7 7 7 / = . = . = . 7/
$% >
.=
7
.
.
.
)( %% $%# %') )' )% #%
01,2
0#' 03
0 0
,04
00 5!60!-$11781
1 0 &2%(2%'##&%&
- .,%''
BestAir
Report (page 55 of 55)
./,0
.#' .1
. .
,.2
.. 3!4.!-$//56/
& "'!'! "!"
( )*
1259
Standard reports
Standard reports Standard 8.11
Network Control Center option only. This report is similar to the Application
Performance report, but it contains statistics for all applications in the network.
Application statistics are consolidated across all sites. For each application, the
report gives an overview of contacts accepted, delayed, and abandoned. It can be
particularly useful in determining the efficiency of your network configuration.
ATTENTION
To run this report, you must select at least one network site.
For more information, see “Understanding the report descriptions” on page 787.
Views
This report uses the ApplicationStat view (see page 249.) For more information
about views, see “Access rights by view” on page 156.
Collection frequency
The following collection frequency types are available for this report:
interval
daily
weekly
monthly
Templates
This report uses the following templates:
inodapp1.rpt
dnodapp1.rpt
wnodapp1.rpt
mnodapp2.rpt
Selection criteria
Statistics
Summaries
The report provides totals for each site, and subtotals for each application.
Statistics are further broken down by day, week, or month, depending on the
reporting period selected. For the interval reporting period, statistics are further
broken down by interval.
BestAir
+ - !./ + * !./0) * %& #
'
,**) +) %& %& %& ( () )) %& ( () '
$
Report (page 1 of 18)
Galway
'()(*(
+
! ! " # $ ! !#$ ! # %$#&
1&
#! #! %&
-,
1&
%&
/
%
./,
0,0
1&
%&
/
%
/
1)2*
1&
# #" # "! "# %&
45-6
4+' 47
4 4
-48
44 9!:4!,%55/5
45 0 !6 6 " #
/ -!
1263
Standard reports
1264
Standard reports
BestAir
+ - !./ + * !./0) * %& #
'
,**) +) %& %& %& ( () )) %& ( () ' $
/
*
/
1&
%&
/
%
/
(/
)
1&
# $ # " $ " %&
/
(/
/
1&
#" # "! # " %&
0,7
1&
%&
/
%
45-6
4+' 47
4 4
-48
44 9!:4!,%55/5
45 0 !6 6 " #
/ - !
BestAir
+ - !./ + * !./0) * %& #
'
,**) +) %& %& %& ( () )) %& ( () ' $
Report (page 18 of 18)
* )) +%& *( () %&'
#
( () $
!" ! #"!$
31-4
3+' 35
3 3
-36
33 7!83!,%11/1
%& '' !
( )
1265
Standard reports
Standard reports Standard 8.11
In this chapter
Overview 1268
Sample Report Creation Wizard reports 1269
Section A: CS 1000/Meridian 1, CS 2x00/DMS, and SIP reports 1273
Section B: License Manager reports 1293
Section C: Contact Center Multimedia reports 1297
Section D: Network consolidated reports 1317
Section E: Functions, operators, and formulas 1323
Overview
Report Creation Wizard is a new reporting feature accessible through the main
Historical Reporting interface. Through a user-friendly interface, you create,
maintain, and modify customized ad hoc reports. You can import and schedule
the reports in Historical Reporting.
ATTENTION
You cannot import user created Crystal reports using Report
Creation Wizrd. You must use the Historical Reporting
Template Importing Wizard. For more information, see
“Importing a user-created Crystal Report” on page 87.
For details about using the Report Creation Wizard, see the Contact Center
Manager Supervisor's Guide.
This section describes the contents of the Report Creation Wizard sample
reports in this appendix. You can use this information to understand the content
of the sample reports and the choices made in Report Creation Wizard to
produce these reports.
This section covers the basic choices made in the Report Creation Wizard, but
does not detail the changes made on the Report Layout page. Modifications not
covered include:
Changing the position of fields
Suppressing section of the report
Adding static text fields
Selecting font size and style
Description
Brief description of the report
Report Type
Indicates the report type selected when the sample report was created. The
available report types are:
Simplified Report—The sample report is using one of the report
definitions packaged with the Report Creation Wizard.
Advanced Report—The sample report is using an ODBC Data Source
Name (DSN).
Data Source
If the report type is Simplified Report, this indicates the path to the Report
Definition file selected to create the sample report. The path shown is the path
that appears in the Report Creation Wizard page. The Report Definition files are
stored in: <Install Directory>\Apps\Reporting\Historical\rpt\RCW.
If the report type is Advanced Report, this indicates the ODBC Data Source
Name (DSN) selected to create the sample report. This name is a general Data
Source Name because the actual name depends on the DSNs configured.
Table Selection
Indicates the database table or view that provides the data for the report. (For
more information about the database views, see Chapter 4, “Contact Center
Manager Data dictionary” and Chapter 6, “Contact Center Multimedia Data
dictionary”.)
If the Report Type is Simplified Report, the Table Selection page is not
available to the user. The description in this case provides details about the
tables included in the Report Definition. If the Report Type is Advanced Report,
the tables listed must be selected on the Table Selection page.
Field Selection
This section of the sample report describes the selections made on the Field
Selection page. The details are shown in a table with the following columns.
Column Description
Column Heading The modified title for the text objects that appear in the Page
Heading section. When fields and formulas are selected, the
default title for the column heading is the same as the field or
formula name. This must be edited on the Report Layout
page.
View field/RCW Formula The fields and formulas selected for the report. To
differentiate between view fields and RCW formulas, view
fields are shown in italics.
Grouping
This section of the sample report describes the selections made on the Grouping
page. The order shown is the same order the fields are placed in the Group By
list. The groups you choose determine the summary statistics that can be
generate. For example, to obtain totals for each supervisor, you must group the
report by supervisor.
Column Description
Sort Order Sort order for the group by field. This can be ascending or
descending.
The section will be printed For Time, Date or DateTime fields only (for example,
Timestamp fields). Indicates how often the group is printed
(for example, for each hour, for each day, and so on).
Summaries
This section of the sample report describes the selections made on the
Summaries page. The details are shown in a table with the following columns.
Column Description
Summation Type The summation type for the selected field. For dynamic
formulas that perform group summation, the summation type
is not required. Therefore, it is blank.
Column Description
Preview
This section shows a graphic representation of the sample report, showing how it
looks when previewed in the Report Creation Wizard. The data included in this
preview is limited to a small number of records and is meant to assist in the
report creation.
In this section
Agent DN Performance.rpt 1274
Agent Performance.rpt 1281
CDN Statistics.rpt 1285
Skillset Performance.rpt 1289
Agent DN Performance.rpt
The Agent DN Performance.rpt sample report shows the amount of time that
agents spend on their personal or secondary directory numbers (DN). The report
records incoming and outgoing information, including the total number of DN
calls and the average amount of time spent on DN calls.
For more information, see “Understanding the report descriptions” on page 787.
Report type
This is a Simplified Report.
Data source
The following report definitions are available:
Report Definitions\CS1000 (M1)\Agent Performance\Agent Performance
Stats.rpt
Report Definitions\CS2x00 (DMS)\Agent Performance\Agent Performance
Stats.rpt
Report Definitions\SIP_CC\Agent Performance\Agent Performance
Stats.rpt
Table selection
This report uses the AgentPerformanceStat view (see page 220.) For more
information about views, see “Access rights by view” on page 156.
Field selection
@RCW_SupervisorNameID 300
@RCW_AgentNameID 300
Timestamp 100
Total @RCW_DNInCalls 50
Internal DNInIntCalls 50
Total @RCW_DNOutCalls 50
Internal DNOutIntCalls 50
External DNOutExtCalls 50
Average Ext. Talk Time @RCW_AverageDNOutExtCallsTalkTime 50
@RCW_SupervisorNameID 300
@RCW_AgentNameID 300
Timestamp 100
Time Time 100
DN In Calls @RCW_DNInCalls 50
Avg DN In Calls Talk Time @RCW_AverageDNInCallsTalkTime 50
Grouping
Summaries
!"
&'()*
&+ , -
.
-&)/01
/'2''2(//1''+// / / / / //+//+// / //+//+// / / //+//+// / //+//+//
&+ ,3#&)'4'
/'2''2(//1''+// / / / / //+//+// / //+//+// / / //+//+// / //+//+//
5555556
555555
1279
Report Creation Wizard
Report Creation Wizard Standard 8.11
"' ( )
*
)"$+,%
"' (!3"$-2-
4444445
444444
+ + + ++'++'++ + ++'++'++
!"#$! !%&''
(" )$*
Agent Performance.rpt
Description
The Agent Performance.rpt sample report shows summarized performance
information for a specific agent. The report tracks the agent's call handling
activities, drawing attention to activities to reward or weaknesses to address.
For more information, see “Understanding the report descriptions” on page 787.
Report type
This is a Simplified Report.
Data source
The following report definitions are available:
Report Definitions\CS1000 (M1)\Agent Performance\Agent Performance
Stats.rpt
Report Definitions\CS2x00 (DMS)\Agent Performance\Agent Performance
Stats.rpt
Report Definitions\SIP_CC\Agent Performance\Agent Performance
Stats.rpt
Table selection
This report uses the AgentPerformanceStat view (see page 220.) For more
information about views, see “Access rights by view” on page 156.
Field selection
@RCW_SupervisorNameID 300
@RCW_AgentNameID 300
Timestamp 100
%Work @RCW_%Work 50
%Available @RCW_%Available 50
Grouping
Summaries
!
!
" # #
$
2x00/DMS, and SIP report
()*+,
( - . /0
0(+123
1)8))8*113))-11 34 34 11-11-*5 11-11-14 11-))-33 1 11-11-11 1 11-11-11 11-,3-11 536** 7)63*
1)8))8*113)*-11 7+ 7+ 11-11-+* 11-11-1, 11-)3-,3 1 11-11-11 1 11-11-11 1)-11-11 2)6), 7*64)
1)8))8*113)+-11 7+ 7+ 11-11-+* 11-11-1, 11-)4-1* 1 11-11-11 1 11-11-11 1)-11-11 2)675 7+6*5
1)8))8*113),-11 +7 +7 11-11-+* 11-11-1, 11-)3-,2 1 11-11-11 1 11-11-11 1)-11-11 2)652 7+64,
*+2 *+2 11-11-+) 11-11-1, 11-32-+) 1 11-11-11 1 11-11-11 1+-,3-11 216++ 7*65,
'! *+2 *+2 11-11-+) 11-11-1, 11-32-+) 1 11-11-11 1 11-11-11 1+-,3-11 216++ 7*65,
( - .%(+)5)
1)8))8*113))-11 34 34 11-11-*2 11-11-14 11-))-11 1 11-11-11 1 11-11-11 11-,3-11 536** 7+6,5
1)8))8*113)*-11 7+ 7+ 11-11-++ 11-11-1, 11-),-+, 1 11-11-11 1 11-11-11 1)-11-11 21647 7,64,
1)8))8*113)+-11 7, 7, 11-11-++ 11-11-1, 11-),-,5 1 11-11-11 1 11-11-11 1)-11-11 2)675 736++
1)8))8*113),-11 +4 +4 11-11-++ 11-11-1, 11-),-+4 1 11-11-11 1 11-11-11 1)-11-11 2)65+ 7364)
*+2 *+2 11-11-+* 11-11-1, 11-3,-35 1 11-11-11 1 11-11-11 1+-,3-11 216)2 7,653
'! *+2 *+2 11-11-+* 11-11-1, 11-3,-35 1 11-11-11 1 11-11-11 1+-,3-11 216)2 7,653
999999:
999999
,75 ,75 11-11-+* 11-11-1, 1)-3,-*2 1 11-11-11 1 11-11-11 17-+1-11 216*4 7+653
CDN Statistics.rpt
Description
The CDN Statistics.rpt sample report details summarized call volume
information for the CDNs configured on the server. The report lists the total
number of calls offered to the CDN and the total number of calls answered. The
report also provides terminated and abandoned call information.
For more information, see “Understanding the report descriptions” on page 787.
Report type
This is a Simplified Report.
Data source
The following report definitions are available:
Report Definitions\CS1000 (M1)\Other\CDN Stats.rpt
Report Definitions\CS2x00 (DMS)\Other\CDN Stats.rpt
Report Definitions\SIP_CC\Other\CDN Stats.rpt
Table selection
This report uses the CDNStat view (see page 275.) For more information about
views, see “Access rights by view” on page 156.
Field selection
@RCW_CDNNameOrID 200
Timestamp 100
Grouping
Summaries
! -
//////0
/////
Skillset Performance.rpt
For more information, see “Understanding the report descriptions” on page 787.
Report type
This is a Simplified Report.
Data source
The following report definitions are available:
Report Definitions\CS1000 (M1)\Other\Skillset Stats.rpt
Report Definitions\CS2x00 (DMS)\ Other\Skillset Stats.rpt
Report Definitions\SIP_CC\ Other\Skillset Stats.rpt
Table selection
This report uses the SkillsetStat view (see page 325.) For more information
about views, see “Access rights by view” on page 156.
Field selection
@RCW_SkillsetNameID 300
@ RCW_ApplicationNameID 300
Timestamp 100
Grouping
Summaries
!
&
"'*+
% &
'())))
! "'*+
%'())),
! (42 ) ).)) ))+))+1, ))+))+)) ))+))+)( ))+))+)) ))+))+)) ))+))+)) )
&
&
"'*+
'())()
! "'*+
%'())),
! ,0) ) ).)) ))+)1+03 ))+))+)( ))+))+)3 ))+))+)) ))+))+)) ))+))+)) )
&
%%%%%%5
%%%%%%
In this section
License Usage Statistics.rpt 1294
The License Usage Statistics.rpt sample report provides license usage stats per
server. The report shows the licensed feature, the IP address of the server using
the feature and the maximum licenses used for the report interval.
For more information, see “Understanding the report descriptions” on page 787.
Report type
This is a Simplified Report.
Data source
You can find the report definition here: Report Definitions\Common
Definitions\License Manager\License Usage Stat.rpt
Table selection
This report uses the LicenseStat view (see page 298.) For more information
about views, see “Access rights by view” on page 156.
Field selection
Timestamp
Feature
Grouping
!"
#$
!"" !#$ %&
In this section
SampleContactsOutstandingDrilldown.rpt 1298
SampleContactsOutstandingSummary.rpt 1301
SampleCampaignAgentScriptData.rpt 1304
SampleCampaignCallByCallData.rpt 1307
SampleCampaignDispCodeData.rpt 1310
SampleCampaignSumm.rpt 1313
SampleContactsOutstandingDrilldown.rpt
For more information, see “Understanding the report descriptions” on page 787.
Report type
This is a Simplified Report.
Data source
You can find the report definition here: Report Definitions\MultiMedia
(CCMM)\Contacts Outstanding Drilldown.rpt.
Table selection
This report uses the ContactsOutstanding view.
Field selection
Skillset 300
Contact ID Contact No 50
Status Status 50
Grouping
Summaries
"
"
! ') * *++ %& $$
( ! ') * *++ %& $$
' ! ') * *++ %& $$
' ! " *++
') ! " *++
"
& # (
& # $)
SampleContactsOutstandingSummary.rpt
For more information, see “Understanding the report descriptions” on page 787.
Report type
This is a Simplified Report.
Data source
You can find the report definition here: Report Definitions\MultiMedia
(CCMM)\Contacts Outstanding Summary.rpt
Table selection
This report uses the ContactsOutstandingSumm view.
Field selection
ByDay 120
Grouping
Summaries
"
!"# $%%&
! #$$%
#
!"# '
!
&
!"#
!
%
$
!"#
!
"
SampleCampaignAgentScriptData.rpt
For more information, see “Understanding the report descriptions” on page 787.
Report type
This is a Simplified Report.
Data source
You can find the report definition here: Report Definitions\MultiMedia
(CCMM)\Outbound\Campaign Agent Script Data.rpt
Table selection
This report uses the CampaignAgentScriptResultsCallByCall view.
Field selection
Campaign 200
ContactID 60
For this report, the following additional fields were added to Group Header #2
(ContactID) from the Report Layout page.
CustomerID 60
PhoneNumber 80
FirstName 140
LastName 200
DispositionCode 140
DateCreated 120
Grouping
SampleCampaignCallByCallData.rpt
For more information, see “Understanding the report descriptions” on page 787.
Report type
This is a Simplified Report.
Data source
You can find the report definition here: Report Definitions\MultiMedia
(CCMM)\Outbound\Campaign Call by Call Data.rpt.
Table selection
This report uses the CampaignCallByCallDetails view.
Field selection
ContactID ContactID 60
FirstName FirstName 80
ActionID ActionID 60
CallProcessedTime CallProcessedTime 100
DialedDN DialedDN 60
Agent Agent 80
Grouping
#(!)" *( !" "" !#$$" #""" +% !""" %%& ' "" """
#(!)! , ** !" "" !#$#" #"" +% !""" %%& - $"" """
#(!) . *$" !" "" !#$)#" (""! +% !""" %%&
#(!)# *$$ !" "" !#$/# #""" +% !""" %%& - $"" """
#(!( 3 *#! !" "" !"$#) #"" +% !""" 4
4
#(!( 3 *! !" "" !"/#$ #"" +% !""" 4
4
#(!( 3 *) !" "" !!"! #"" +% !""" 4
4
#(!($ +5 *# !" "" !"#!# #""" +% !""" %%&
#(!(# ,6 *#$ !" "" !"#$* (""! +% !""" 74% 89
#(!( 7 : *## !" "" !""# #""" +% !""" +;
#(!( 7 : * !" "" !!""" #""" +% !""" %%& ' "" """
#(!() +5 *# !" "" !"# #"" +% !""" %%& - $"" """
#(!(( < 2 *#( !" "" !")$( #"" +% !""" %%& ' $"" """
#(!(/ +5
4 *#/ !" "" !"(! #""" +% !""" %%& ' !"" """
#(!(* + 6 *#* !" "" !"/! (""! +% !""" %%& ' "" """
#($( !!$# ( !" "" "*"*$$ #""" +% !""! %%& - $"" """
1309
Report Creation Wizard
Report Creation Wizard Standard 8.11
SampleCampaignDispCodeData.rpt
For more information, see “Understanding the report descriptions” on page 787.
Report type
This is an Advanced Report.
Data source
Select CCMM_<IP address>_DSN.
When selecting a DSN to use for creating this report, the <IP address> is the IP
address of a Contact Center Manager Server configured in Contact Center
Manager Administration.
Table selection
This report uses the DispCodeData view.
Field selection
CampaignName 200
DialedDN DialedDN 80
FirstName FirstName 80
LastName LastName 100
Agent Agent 80
Grouping
SampleCampaignSumm.rpt
For more information, see “Understanding the report descriptions” on page 787.
Report type
This is a Simplified Report.
Data source
You can find the report definition here: Report Definitions\MultiMedia
(CCMM)\Outbound\Campaign Summary Data.rpt.
Table selection
This report uses the CampaignSummary view.
Field selection
CampaignName 200
Count DispositionCodeCount 60
Grouping
Summaries
! "
! # $$ $$$
! # %$$ $$$ &
! # "$$ $$$
! ' "$$ $$$ (
In this section
Network Consolidated Skillset Performance 1318
Network Control Center option only. This report contains skillset performance
statistics for all sites in the network. For each site, the report lists the total, local,
and remote calls answered by agents for the skillset, the percentage of calls that
are local or remote, and the maximum delay a caller experienced.
For more information, see “Understanding the report descriptions” on page 787.
Report type
This is a Simplified Report.
Data source
You can find the report definition here: Report Definitions\Network
Consolidated (NCC)\Other\ Network Skillset Consolidated Statistics.rpt.
Table selection
This report uses the SkillsetConStat view.
Field selection
@RCW_SkillsetNameID 150
TerminatingSite 50
Timestamp 115
Answered CallsAnswered 50
Local @RCW_LocalCallsAnswered 50
Remote NetCallsAnswered 50
Grouping
Summaries
%
&#
!"!! !"!! !"!! $!!"!! !"!! !!#!!#!$
1321
Report Creation Wizard
Report Creation Wizard Standard 8.11
In this section
Report Creation Wizard functions 1324
Report Creation Wizard operators 1330
Report Creation Wizard formulas 1332
When you specify a function, the program performs the set of operations built
into the function without needing you to specify each operation separately. In
this way, a function is shorthand that makes it easier and less time consuming
for you to create reports.
Standard functions
Report Creation Wizard supports a set of standard functions, which are a subset
of functions supported by Crystal Reports 10. A subset of functions are listed in
Report Creation Wizard to help reduce the complexity involved in creating
formulas.
Because Report Creation Wizard is built on Crystal Reports 10, all functions
supported in Crystal Reports 10 are support in Report Creation Wizard. Users
familiar with Crystal Reports 10 can use these additional functions.
For details about the standard functions listed in Report Creation Wizard, see the
online help within the Report Creation Wizard application.
1 HH:MM:SS
2 HH:MM
3 MM:SS
4 HH Hrs
5 MM Mins
6 Secs
AccessRights.CreateDeleteAccess +
AccessRights.CreatedDeleteAgentAccess +
AccessRights.CreateDeleteAllAgentAccess + “.”
AccessRights.ReadAccess +
AccessRights.ReadAgentAccess +
AccessRights.ReadAllAgentAccess + “.”
AccessRights.WriteAccess +
AccessRights.WriteAgentAccess +
AccessRights.WriteAllAgentAccess
The Number field contains the value of the ALG field of the NBManagedObject
view.
String functions
Standard operators
Report Creation Wizard supports a set of standard operators, which are a subset
of operators supported by Crystal Reports 10. A subset of operators are listed in
Report Creation Wizard to help reduce the complexity involved in creating
formulas.
Because Report Creation Wizard is built on Crystal Reports 10, all operators
supported in Crystal Reports 10 are supported in Report Creation Wizard. This
lets users familiar with Crystal Reports 10 to use these additional operators.
For details about the standard operators listed in Report Creation Wizard, see the
online help within the Report Creation Wizard application.
For additional details see the online help with the Report Creation Wizard
application.
Report Creation Wizard provides a number of formulas that you can use in your
reports. This section lists and describes those formulas.
Dynamic formulas
Dynamic formulas are formulas that are automatically customized before they
are added to the report. Two types of dynamic formulas are provided with the
Report Creation Wizard—time format formulas and dynamic group formulas.
Generic formulas
The following generic formulas are available.
@begin_date_end_date_interval
Lists the value set for the @report_interval formula. If the collection period is
not entered, No Selection Criteria was passed message appears.
@printed_date_time
Lists the date and time that the report was generated.
@RCW_DataRange
Lists the value set for the @report_datarange formula as a string.
@report_datarange
Numeric value related to the data range selected in the Historical Reporting
application. The possible values are:
0 = Not applicable
1 = Interval
2 = Daily
4 = Weekly
8 = Monthly
@report_interval
Lists the collection period selected when running the report. This value is passed
from the Historical Reporting application when the report is run.
@report_language
Lists the language code set for the report. The default value is “en-us.” The
formula is used to pass the report language into other formulas requiring the
language code.
@report_tablenames
Lists the table names used to generate the report. This value is passed from the
Historical Reporting application when the report is run.
@report_title
Lists the title of the report, as defined on the General - Report Properties
property page. This value is passed from the Historical Reporting application
when the report is run.
@report_user
Lists the user ID of the user who printed the report. This value is passed from the
Historical Reporting application when the report is run.
@revenue_unit
The default value is 1. This value is passed from the Historical Reporting
application when the report is run.
@site_id_name
Lists the name of the site at which the report is being printed. To change the site
name, see the Contact Center Manager Supervisor’s Guide. This value is passed
from the Historical Reporting application when the report is run.
@source_site_id
Lists the name of the source site for a network consolidated report. This value is
passed from the Historical Reporting application when the report is run.
ActivityCodeStat formulas
The following ActivityCodeStat formulas are available.
@RCW_ActivityCodeNameID
Lists the Activity Code name and ID in the format ActivityCodeName -
ActivityCode. If the information is not available, No Information on Activity
Code message appears.
@RCW_ActivityCodeNameIDLabel
Lists the text Activity Name & ID: ActivityCodeName - ActivityCode. If the
information is not available, No Information on Activity Code message appears.
@RCW_ActivityTime
Lists the total time spent on this activity by an agent.
@RCW_AgentName
Lists the agent's full name in the format AgentGivenName AgentSurName. If
the information is not available, Agent Name Not Defined message appears.
@RCW_AgentNameID
Lists the agent's full name and login ID in the format AgentGivenName
AgentSurName - AgentLogin. If the information is not available, No Agent
Name and ID Available message appears.
@RCW_AgentNameIDLabel
Lists the text Agent Name & ID: AgentGivenName AgentSurname -
AgentLogin. If the agent information is not available, No Agent Name and ID
Available message appears.
@RCW_ApplicationLabel
Lists the text Application: Application.
@RCW_ApplicationNameID
Lists the application name and ID in the format Application - ApplicationID. If
the information is not available, No Information on Application message
appears.
@RCW_ApplicationNameIDLabel
Lists the text Application Name & ID: Application - ApplicationID. If the
information is not available, No Information on Application message appears.
@RCW_ApplicationNameOrID
Lists Application, or if this is not available, ApplicationID. If the information is
not available, No Information on Application message appears.
@RCW_ApplicationNameOrIDLabel
Lists the text Application Name: Application or, if this is not available,
Application Name: ApplicationID. If the information is not available, No
Information on Application message appears.
@RCW_AverageActivityTime
Lists the average time spent on this activity by an agent by dividing
ActivityTime by Occurrences.
@RCW_EstimatedRevenue
Calculates the estimated revenue by multiplying the value set for @revenue_unit
by Occurrences.
@RCW_TimestampGroupName
Lists the Timestamp value as a formatted string based on the @report_datarange
formula and the setting for the option The section will be printed. If the value set
for @report_datarange is Daily, Weekly, or Monthly, only the date is printed. If
the value set for @report_datarang is Interval, the value is modified based on the
setting for The section will be printed.
You can use this formula in the Timestamp group header or group footer only.
@RCW_TimestampGroupNameLabel
Lists a label indicating the group option selected followed by the Timestamp
value as a formatted string (for example, Daily: 25/10/2005). The label and date
shown are based on the @report_datarange formula and the setting for the
option The section will be printed.
If the value set for @report_datarange is Daily, Weekly, or Monthly, only the
label and date are printed. If the value set for @report_datarange is Interval, the
label and value are modified based on the setting for The section will be printed.
You can use this formula in the Timestamp group header or group footer only.
AgentByApplicationStat formulas
The following AgentByApplicationStat formulas are available.
@RCW_%CallsAnswered
Calculates the percentage of calls answered by dividing CallsAnswered by
CallsOffered, and multiplying by 100.
@RCW_AgentName
Lists the agent's full name in the format AgentGivenName AgentSurName. If
the information is not available, Agent Name Not Defined message appears.
@RCW_AgentNameID
Lists the agent's full name and login ID in the format AgentGivenName
AgentSurName - AgentLogin. If the information is not available, No Agent
Name and ID Available message appears.
@RCW_AgentNameIDLabel
Lists the text Agent Name & ID: AgentGivenName AgentSurname -
AgentLogin. If the agent information is not available, No Agent Name and ID
Available message appears.
@RCW_ApplicationLabel
Lists the text Application: Application.
@RCW_ApplicationNameID
Lists the application name and ID in the format Application - ApplicationID. If
the information is not available, No Information on Application message
appears.
@RCW_ApplicationNameIDLabel
Lists the text Application Name & ID: Application - ApplicationID. If the
information is not available, No Information on Application message appears.
@RCW_ApplicationNameOrID
Lists Application or, if this is not available, ApplicationID. If the information is
not available, No Information on Application message appears.
@RCW_ApplicationNameOrIDLabel
Lists the text Application Name: Application or, if this is not available,
Application ID: ApplicationID. If the information is not available, No
Information on Application message appears.
@RCW_AverageHoldTime
Lists the average time an agent spends on hold during Contact Center Manager
calls for this application by dividing HoldTime by the CallsAnswered.
@RCW_AveragePostCallProcessingTime
Lists the average time an agent spends performing post-call processing by
dividing PostCallProcessingTime by the CallsAnswered.
@RCW_AverageTalkTime
Lists the average time an agent spends handling contacts, excluding DN calls,
after the contact is answered or accepted by dividing TalkTime by
CallsAnswered. This statistic includes hold time.
@RCW_AverageWaitTime
Lists average time an agent spends in the idle state after releasing a Contact
Center Manager call for this application by dividing WaitTime by
CallsAnswered.
@RCW_ConsultTime
Lists the time an agent spends in consultation during Contact Center Manager
calls for this application. Consultation time occurs during a consult transfer if
the caller disconnects and the answering agent remains on the line.
@RCW_DNOutExtTalkTime
(Communication Server 1000/Meridian 1 PBX switch only) Lists the total time
spent on outgoing external DN calls.
@RCW_DNOutIntTalkTime
(Communication Server 1000/Meridian 1 PBX switch only) Lists the total time
spent on outgoing internal DN calls.
@RCW_DNOutTalkTime
(Communication Server 1000/Meridian 1 PBX switch only) Lists the total time
spent on outgoing DN calls by adding DNOutIntTalkTime +
DNOutExtTalkTime.
@RCW_HoldTime
Lists the total time an agent spends on hold during Contact Center Manager calls
for this application.
@RCW_PostCallProcessingTime
Lists the total time an agent spends performing post-call processing. Normally,
an agent uses this time to complete any work related to the call just released,
such as filling in forms or filing papers.
@RCW_RingTime
Lists the total time that contacts spend in the Alert (Ringing) state before they
are answered or accepted, returned to the queue by this agent, or abandoned.
@RCW_TalkTime
Lists the total time an agent spends handling contacts, excluding DN calls, after
the contact is answered or accepted. This statistic includes hold time.
@RCW_TimestampGroupName
Lists the Timestamp value as a formatted string based on the @report_datarange
formula and the setting for the option The section will be printed. If the value set
for @report_datarange is Daily, Weekly, or Monthly, only the date is printed. If
the value set for @report_datarang is Interval, the value is modified based on the
setting for The section will be printed.
You can use this formula in the Timestamp group header or group footer only.
@RCW_TimestampGroupNameLabel
Lists a label indicating the group option selected followed by the Timestamp
value as a formatted string (for example, Daily: 25/10/2005). The label and date
shown are based on the @report_datarange formula and the setting for the
option The section will be printed.
If the value set for @report_datarange is Daily, Weekly, or Monthly, only the
label and date are printed. If the value set for @report_datarange is Interval, the
label and value is modified based on the setting for The section will be printed.
You can use this formula in the Timestamp group header or group footer only.
@RCW_WaitTime
Lists the total time the agent has spent in the idle state after releasing a Contact
Center Manager call for this application.
AgentBySkillsetStat formulas
The following AgentBySkillsetStat formulas are available.
@RCW_%CallsAnswered
Calculates the percentage of calls answered by dividing CallsAnswered by
CallsOffered, and multiplying by 100.
@RCW_%ShortCallsAnswered
Calculates the percentage of short calls answered by dividing
ShortCallsAnswered by CallsAnswered, and multiplying by 100. Short calls are
calls that to a talk time less than the short call threshold assigned to the threshold
class for the skillset.
@RCW_AgentName
Lists the agent's full name in the format AgentGivenName AgentSurName. If
the information is not available, Agent Name Not Defined message appears.
@RCW_AgentNameID
Lists the agent's full name and login ID in the format AgentGivenName
AgentSurName - AgentLogin. If the information is not available, No Agent
Name and ID Available message appears.
@RCW_AgentNameIDLabel
Lists the text Agent Name & ID: AgentGivenName AgentSurname -
AgentLogin. If the agent information is not available, No Agent Name and ID
Available message appears.
@RCW_AgentSkillsetTime
Lists the amount of time that the agent spent on calls for this skillset by adding
TalkTime + PostCallProcessingTime.
@RCW_AverageHoldTime
Lists the average time an agent spends on hold during Contact Center Manager
calls for this application by dividing HoldTime by the CallsAnswered. This also
includes agent walkaway time.
@RCW_AveragePostCallProcessingTime
Lists the average time an agent spends performing post-call processing by
dividing PostCallProcessingTime by the CallsAnswered.
@RCW_AverageTalkTime
Lists the average time for local Contact Center Manager contacts, incoming
NSBR contacts, ACD calls, and NACD calls for this skillset, including hold
time, by dividing TalkTime by CallsAnswered.
@RCW_AverageWaitTime
Lists average time an agent spends in the idle state after releasing a Contact
Center Manager call for this skillset by dividing WaitTime by CallsAnswered.
@RCW_ConsultTime
Lists the time an agent spends in consultation during Contact Center Manager
calls for this skillset. Consultation time occurs during a consult transfer if the
caller disconnects and the answering agent remains on the line.
@RCW_DNOutExtTalkTime
(Communication Server 1000/Meridian 1 PBX switch only) Lists the total time
spent on outgoing external DN calls.
@RCW_DNOutIntTalkTime
(Communication Server 1000/Meridian 1 PBX switch only) Lists the total time
spent on outgoing internal DN calls.
@RCW_DNOutTalkTime
(Communication Server 1000/Meridian 1 PBX switch only) Lists the total time
spent on outgoing DN calls by adding DNOutIntTalkTime +
DNOutExtTalkTime.
@RCW_HoldTime
Lists the amount of time the agent spent on hold for this skillset.
@RCW_PostCallProcessingTime
The total time an agent spends performing post-call processing. Normally, an
agent uses this time to complete any work related to the call just released, such
as filling in forms or filing papers.
@RCW_RingTime
Lists the total time that Contact Center Manager contacts queued to this skillset
spent in Ringing state before they are answered or returned to queue by this
agent, or abandoned.
@RCW_SkillsetLabel
Lists the text Skillset: Skillset.
@RCW_SkillsetNameID
Lists the skillset name and ID in the format Skillset - SkillsetID. If the
information is not available, No Information on Skillset message appears.
@RCW_SkillsetNameIDLabel
Lists the text Skillset Name & ID: Skillset - SkillsetID. If the information is not
available, No Information on Skillset message appears.
@RCW_SkillsetNameOrID
Lists Skillset or, if this is not available, SkillsetID. If the information is not
available, No Information on Skillset message appears.
@RCW_SkillsetNameOrIDLabel
Lists the text Skillset Name: Skillset, or if this is not available Skillset ID:
SkillsetID. If the information is not available, No Information on Skillset
message appears.
@RCW_TalkTime
Lists the total time spent by the agent on local Contact Center Manager calls,
incoming NSBR calls, ACD calls, and NACD calls, including hold time, for this
skillset.
@RCW_TimestampGroupName
Lists the Timestamp value as a formatted string based on the @report_datarange
formula and the setting for the option The section will be printed. If the value set
for @report_datarange is Daily, Weekly, or Monthly, only the date is printed. If
the value set for @report_datarang is Interval, the value is modified based on the
setting for The section will be printed.
You can use this formula in the Timestamp group header or group footer only.
@RCW_TimestampGroupNameLabel
Lists a label indicating the group option selected followed by the Timestamp
value as a formatted string (for example, Daily: 25/10/2005). The label and date
shown are based on the @report_datarange formula and the setting for the
option The section will be printed.
If the value set for @report_datarange is Daily, Weekly, or Monthly, only the
label and date are printed. If the value set for @report_datarange is Interval, the
label and value are modified based on the setting for The section will be printed.
You can use this formula in the Timestamp group header or group footer only.
@RCW_TotalStaffedTime
Lists the total time an agent is logged on and assigned to this skillset.
@RCW_WaitTime
Lists the total time an agent spends in the idle state after releasing a Contact
Center Manager call for this skillset.
AgentPerformanceStat formulas
The following AgentPerformanceStat formulas are available.
@RCW_%ACDCallsAnswered
(Communication Server 1000/Meridian 1 PBX) Calculates the percentage of
ACD calls answered by dividing ACDCallsAnswered by CallsAnswered +
ACDCallsAnswered + NACDCallsAnswered, and multiplying by 100.
(Communication Server 2x00/DMS) Calculates the percentage of ACD calls
answered by dividing ACDCallsAnswered by CallsAnswered +
ACDCallsAnswered, and multiplying by 100.
@RCW_%Available
(Communication Server 1000/Meridian 1 PBX) Calculates the percentage of
time an agent is busy on calls routed to the Contact Center Manager or Idle
waiting for calls by dividing TalkTime + ACDCallsTalkTime +
NACDCallsTalkTime + WaitingTime by LoggedInTime, and multiplying by
100.
(Communication Server 2x00/DMS) Calculates the percentage of time an agent
is busy on calls routed to the Contact Center Manager or Idle waiting for calls by
dividing TalkTime + ACDCallsTalkTime + WaitingTime by LoggedInTime,
and multiplying by 100.
@RCW_%Busy
Calculates the percentage of time an agent is busy on calls routed to the Contact
Center Manager, in the Not Ready state or on a DN call by dividing
LoggedInTime - WaitingTime by LoggedInTime, and multiplying by 100.
@RCW_%CallsAnswered
Calculates the percentage of calls answered by dividing CallsAnswered by
CallsOffered, and multiplying by 100.
@RCW_%LocalCallsAnswered
Calculates the percentage of local calls answered by dividing CallsAnswered -
NetworkCallsAnswered by CallsAnswered, and multiplying by 100.
@RCW_%NACDCallsAnswered
(Communication Server 1000/Meridian 1 PBX only) Calculates the percentage
of NACD calls answered by dividing NACDCallsAnswered by CallsAnswered
+ ACDCallsAnswered + NACDCallsAnswered, and multiplying by 100.
@RCW_%NetworkCallsAnswered
Calculates the percentage of network calls answered by dividing
NetworkCallsAnswered by CallsAnswered, and multiplying by 100.
@RCW_%ShortCallsAnswered
(Communication Server 1000/Meridian 1 PBX) Calculates the percentage of
short calls answered by dividing ShortCallsAnswered by CallsAnswered +
ACDCallsAnswered + NACDCallsAnswered, and multiplying by 100. Short
calls are calls that have a talk time less than the short call threshold assigned to
the threshold class for the skillset in which the call is answered.
(Communication Server 2x00/DMS) Calculates the percentage of short calls
answered by dividing ShortCallsAnswered by CallsAnswered +
ACDCallsAnswered, and multiplying by 100. Short calls are calls that have a
talk time less than the short call threshold assigned to the threshold class for the
skillset in which the call is answered.
@RCW_%Work
(Communication Server 1000/Meridian 1 PBX) Calculates the percentage of
logged on time an agent is either busy on calls routed to the Contact Center
Manager or in Not Ready state by dividing TalkTime + ACDCallsTalkTime +
NACDCallsTalkTime + NotReadyTime by LoggedInTime, and multiplying by
100.
@RCW_ACDCallsConferenced
Calculates the number of ACD calls conferenced bay adding
ACDCallsConfToCDN + ACDCallsConfToDN + ACDCallsConfToIncalls +
ACDCallsConfToOther.
@RCW_ACDCallsTalkTime
(Communication Server 1000/Meridian 1 PBX switch) Lists the total time spent
on ACD calls, including hold time.
(Communication Server 2x00/DMS switch) Lists the total time spent on ACD
and NACD calls, including hold time.
@RCW_ACDCallsTransferred
Calculates the number of ACD calls transferred by adding
ACDCallsTransferredToCDN + ACDCallsTransferredToDN +
ACDCallsTransferredToIncalls + ACDCallsTransferredToOther.
@RCW_ACDNACDCallsAnswered
(Communication Server 1000/Meridian 1 PBX switch only) Calculates the total
number of ACD and NACD calls answered by adding ACDCallsAnswered +
NACDCallsAnswered.
@RCW_ACDNACDCallsTalkTime
(Communication Server 1000/Meridian 1 PBX switch only) Lists the total talk
time for both ACD and NACD calls by adding ACDCallsTalkTime +
NACDCallsTalkTime.
@RCW_AgentName
Lists the agent's full name in the format AgentGivenName AgentSurName. If
the information is not available, Agent Name Not Defined message appears.
@RCW_AgentNameID
Lists the agent's full name and login ID in the format AgentGivenName
AgentSurName - AgentLogin. If the information is not available, No Agent
Name and ID Available message appears.
@RCW_AgentNameIDLabel
Lists the text Agent Name & ID: AgentGivenName AgentSurname -
AgentLogin. If the agent information is not available, No Agent Name and ID
Available message appears.
@RCW_AverageACDCallsTalkTime
Lists the average time spent on ACD calls by dividing ACDCallsTalkTime by
ACDCallsAnswered.
@RCW_AverageACDNACDCallsTalkTime
(Communication Server 1000/Meridian 1 PBX switch only) Lists the average
time spent on ACD and NACD calls by dividing ACDCallsTalkTime +
NACDCallsTalkTime by ACDCallsAnswered + NACDCallsAnswered.
@RCW_AverageBusyOnDNTime
(Communication Server 1000/Meridian 1 PBX switch only) Lists the average
time the Incalls key of an agent is busy because the agent pressed the personal
DN key or is busy on a DN call by dividing BusyOnDNTime by DNInExtCalls
+ DNInIntCalls + DNOutExtCalls + DNOutIntCalls.
@RCW_AverageCallsAnsweredPerHour
Lists the average number of contacts answered per hour by dividing
CallsAnswered + CDCallsAnswered + NACDCallsAnswered by
(LoggedInTime/3600).
@RCW_AverageDNCallsHoldTime
(Communication Server 1000/Meridian 1 PBX switch) Lists the average time
DN calls are on hold by dividing DNInExtCallsHoldTime +
DNInIntCallsHoldTime + DNOutExtCallsHoldTime +
DNOutIntCallsHoldTime by DNInExtCalls + DNInIntCalls + DNOutExtCalls +
DNOutIntCalls.
(Communication Server 2x00/DMS switch) Lists the average time DN calls are
on hold by dividing DNInExtCallsHoldTime + DNInIntCallsHoldTime +
DNOutExtCallsHoldTime + DNOutIntCallsHoldTime by DNInCalls +
DNOutCalls.
@RCW_AverageDNCallsTalkTime
(Communication Server 1000/Meridian 1 PBX switch) Lists the average time
spent on DN calls, including hold time, by dividing DNInExtCallsTalkTime +
DNInIntCallsTalkTime + DNOutExtCallsTalkTime + DNOutIntCallsTalkTime
by DNInExtCalls + DNInIntCalls + DNOutExtCalls + DNOutIntCalls.
(Communication Server 2x00/DMS switch) Lists the average time spent on DN
calls, including hold time, by dividing DNInCallsTalkTime +
DNOutCallsTalkTime by DNInCalls + DNOutCalls.
@RCW_AverageDNInCallsHoldTime
(Communication Server 1000/Meridian 1 PBX switch) Lists the average time
incoming DN calls are on hold by dividing DNInExtCallsHoldTime +
DNInIntCallsHoldTime by DNInExtCalls + DNInIntCalls.
@RCW_AverageDNInCallsTalkTime
(Communication Server 1000/Meridian 1 PBX switch) Lists the average time
spent on incoming DN calls, including hold time, by dividing
DNInExtCallsTalkTime + DNInIntCallsTalkTime by DNInExtCalls +
DNInIntCalls.
(Communication Server 2x00/DMS switch) Lists the average time spent on
incoming DN calls, including hold time, by dividing DNInCallsTalkTime by
DNInCalls.
@RCW_AverageDNInExtCallsHoldTime
(Communication Server 1000/Meridian 1 PBX switch only) Lists the average
time incoming external DN calls are on hold by dividing
DNInExtCallsHoldTime by DNInExtCalls.
@RCW_AverageDNInExtCallsTalkTime
(Communication Server 1000/Meridian 1 PBX switch only) Lists the average
time spent on incoming external DN calls, including hold time, by dividing
DNInExtCallsTalkTime by DNInExtCalls.
@RCW_AverageDNInIntCallsHoldTime
(Communication Server 1000/Meridian 1 PBX switch only) Lists the average
time incoming internal DN calls are on hold by dividing DNInIntCallsHoldTime
by DNInIntCalls.
@RCW_AverageDNInIntCallsTalkTime
(Communication Server 1000/Meridian 1 PBX switch only) Lists the average
time spent on incoming internal DN calls, including hold time, by dividing
DNInIntCallsTalkTime by DNInIntCalls.
@RCW_AverageDNOutCallsHoldTime
(Communication Server 1000/Meridian 1 PBX switch) Lists the average time
outgoing DN calls are on hold by dividing DNOutExtCallsHoldTime +
DNOutIntCallsHoldTime by DNOutExtCalls + DNOutIntCalls.
(Communication Server 2x00/DMS switch) Lists the average time outgoing DN
calls are on hold by dividing DNOutExtCallsHoldTime +
DNOutIntCallsHoldTime by DNOutCalls.
@RCW_AverageDNOutCallsTalkTime
(Communication Server 1000/Meridian 1 PBX switch) Lists the average time
spent on outgoing DN calls, including hold time, by dividing
DNOutExtCallsTalkTime + DNOutIntCallsTalkTime by DNOutExtCalls +
DNOutIntCalls.
(Communication Server 2x00/DMS switch) Lists the average time spent on
outgoing DN calls, including hold time, by dividing DNOutCallsTalkTime by
DNOutCalls.
@RCW_AverageDNOutExtCallsHoldTime
(Communication Server 1000/Meridian 1 PBX switch only) Lists the average
time outgoing external DN calls are on hold by dividing
DNOutExtCallsHoldTime by DNOutExtCalls.
@RCW_AverageDNOutExtCallsTalkTime
(Communication Server 1000/Meridian 1 PBX switch only) Lists the average
time spent on outgoing external DN calls, including hold time, by dividing
DNOutExtCallsTalkTime by DNOutExtCalls.
@RCW_AverageDNOutIntCallsHoldTime
(Communication Server 1000/Meridian 1 PBX switch only) Lists the average
time outgoing internal DN calls are on hold by dividing
DNOutIntCallsHoldTime by DNOutIntCalls.
@RCW_AverageDNOutIntCallsTalkTime
(Communication Server 1000/Meridian 1 PBX switch only) Lists the average
time spent on outgoing internal DN calls, including hold time, by dividing
DNOutIntCallsTalkTime by DNOutIntCalls.
@RCW_AverageHoldTime
Lists the average time this agent put local and incoming contacts on hold,
excluding DN calls, ACD calls and NACD calls by dividing HoldTime by the
CallsAnswered.
@RCW_AverageLocalCallsTalkTime
Lists the average time that the agent spent handling local contacts, including
hold time, by dividing TalkTime - NetworkCallsTalkTime by CallsAnswered -
NetworkCallsAnswered.
@RCW_AverageNACDCallsTalkTime
(Communication Server 1000/Meridian 1 PBX switch only) Lists the average
time spent on NACD calls, including hold time, by dividing
NACDCallsTalkTime by NACDCallsAnswered.
@RCW_AverageNetworkCallsTalkTime
Lists the average time that the agent spent handling incoming NSBR contacts,
including hold time, by dividing NetworkCallsTalkTime by
NetworkCallsAnswered.
@RCW_AverageNotReadyTime
(Communication Server 1000/Meridian 1 PBX switch) Lists the average Not
Ready time by dividing NotReadyTime by CallsAnswered +
ACDCallsAnswered + NACDCallsAnswered.
(Communication Server 2x00/DMS switch) Lists the average Not Ready time
by dividing NotReadyTime by CallsAnswered + ACDCallsAnswered.
@RCW_AverageNotReadyTimePerHour
Lists the average Not Ready time per hour by dividing NotReadyTime by
(LoggedInTime/3600).
@RCW_AverageTalkTime
Lists the average time spent by the agent handling all contacts except DN calls,
ACD calls and NACD calls, including hold time, by dividing TalkTime by
CallsAnswered.
@RCW_AverageTalkTimePerHour
(Communication Server 1000/Meridian 1 PBX switch) Lists the average time
spent per hour by the agent on calls, including hold time, by dividing TalkTime
+ ACDTalkTime + NACDTalkTime by (LoggedInTime/3600).
(Communication Server 2x00/DMS switch) Lists the average time spent per
hour by the agent on calls, including hold time, by dividing TalkTime +
ACDTalkTime by (LoggedInTime/3600).
@RCW_AverageTotalTalkTime
(Communication Server 1000/Meridian 1 PBX switch) Lists the average time
spent by the agent on calls, including hold time, by dividing TalkTime +
ACDTalkTime + NACDTalkTime by CallsAnswered + ACDCallsAnswered +
NACDCallsAnswered.
(Communication Server 2x00/DMS switch) Lists the average time spent by the
agent on calls, including hold time, by dividing TalkTime + ACDTalkTime by
CallsAnswered + ACDCallsAnswered.
@RCW_AverageWaitingTime
Lists average time an agent spends waiting for contacts by dividing
WaitingTime by CallsAnswered + ACDCallsAnswered +
NACDCallsAnswered.
@RCW_BreakTime
(Communication Server 1000/Meridian 1 PBX switch only) Lists the total time
an agent is in the Break state for all skillsets. You can configure an agent’s call
presentation class to place the agent in Break state after each call.
@RCW_BusyMiscTime
(Communication Server 1000/Meridian 1 PBX switch only) Lists the total time
the Incalls key of an agent is busy because of events not related to DN calls (for
example, programming the Call Forward key or ACD call ringing).
@RCW_BusyOnDNTime
(Communication Server 1000/Meridian 1 PBX switch only) Lists the total time
the Incalls key of an agent is busy because the agent pressed the personal DN
key or is busy on a DN call. This statistic does not include DN calls originated as
part of a Contact Center Outbound contact.
@RCW_CallsConferenced
Calculates the total number of calls conferenced, by adding
ACDCallsConfToCDN + ACDCallsConfToDN + ACDCallsConfToIncalls +
ACDCallsConfToOther + CDNCallsConfToCDN + CDNCallsConfToDN +
CDNCallsConfToIncalls + CDNCallsConfToOther + DNCallsConfToCDN +
DNCallsConfToDN + DNCallsConfToACDDN + DNCallsConfToOther.
@RCW_CallsConferencedToACD
Calculates the number of calls conferenced to an ACD-DN by adding
ACDCallsConfToIncalls + CDNCallsConfToIncalls +
DNCallsConfToACDDN.
@RCW_CallsConferencedToCDN
Calculates the number of calls conferenced to a CDN acquired by Contact
Center Manager by adding ACDCallsConfToCDN + CDNCallsConfToCDN +
DNCallsConfToCDN.
@RCW_CallsConferencedToDN
Calculates the number of calls conferenced to a DN by adding
ACDCallsConfToDN + CDNCallsConfToDN + DNCallsConfToDN.
@RCW_CallsConferencedToOther
Calculates the number of calls conferenced to resources external to Contact
Center Manager system by adding ACDCallsConfToOther +
CDNCallsConfToOther + DNCallsConfToOther.
@RCW_CallsTransferred
Calculates the total number of calls transferred, by adding
ACDCallsTransferredToCDN + ACDCallsTransferredToDN +
ACDCallsTransferredToIncalls + ACDCallsTransferredToOther +
CDNCallsTransferredToCDN + CDNCallsTransferredToDN +
CDNCallsTransferredToIncalls + CDNCallsTransferredToOther +
DNCallsTransferredToCDN + DNCallsTransferredToDN +
DNCallsTransferredToACDDN + DNCallsTransferredToOther.
@RCW_CallsTransferredToACD
Calculates the number of calls transferred to an ACD-DN by adding
ACDCallsTransferredToIncalls + CDNCallsTransferredToIncalls +
DNCallsTransferredToACDDN.
@RCW_CallsTransferredToCDN
Calculates the number of calls transferred to a CDN acquired by Contact Center
Manager ACDCallsTransferredToCDN + CDNCallsTransferredToCDN +
DNCallsTransferredToCDN.
@RCW_CallsTransferredToDN
Calculates the number of calls transferred to a DN by adding
ACDCallsTransferredToDN + CDNCallsTransferredToDN +
DNCallsTransferredToDN.
@RCW_CallsTransferredToOther
Calculates the number of calls transferred to resources external to the Contact
Center Manager system by adding ACDCallsTransferredToOther +
CDNCallsTransferredToOther + DNCallsTransferredToOther.
@RCW_CDNCallsConferenced
Calculates the number of CDN calls conferenced by adding
CDNCallsConfToCDN + CDNCallsConfToDN + CDNCallsConfToIncalls +
CDNCallsConfToOther.
@RCW_CDNCallsTransferred
Calculates the number of CDN calls transferred by adding
CDNCallsTransferredToCDN + CDNCallsTransferredToDN +
CDNCallsTransferredToIncalls + CDNCallsTransferredToOther.
@RCW_ConsultationTime
Lists the total time an agent spends in consultation with another agent during a
call transfer or conference after the caller drops off the call.
@RCW_DNCalls
(Communication Server 1000/Meridian 1 PBX switch) Calculates the number of
DN calls handled by an agent, by adding DNInExtCalls + DNInIntCalls +
DNOutExtCalls + DNOutIntCalls.
(Communication Server 2x00/DMS switch) Calculates the number of DN calls
handled by an agent, by adding DNInCalls + DNOutCalls.
@RCW_DNCallsConferenced
Calculates the number of DN calls conferenced by adding
DNCallsConfToACDDN + DNCallsConfToCDN + DNCallsConfToDN +
DNCallsConfToOther.
@RCW_DNCallsHoldTime
Lists the total time DN calls are on hold by adding DNInExtCallsHoldTime +
DNInIntCallsHoldTime + DNOutExtCallsHoldTime +
DNOutIntCallsHoldTime.
@RCW_DNCallsTalkTime
(Communication Server 1000/Meridian 1 PBX switch) Lists the total time spent
handling DN calls by adding DNInExtCallsTalkTime + DNInIntCallsTalkTime
+ DNOutExtCallsTalkTime + DNOutIntCallsTalkTime.
(Communication Server 2x00/DMS switch) Lists the total time spent handling
DN calls by adding DNInCallsTalkTime + DNOutCallsTalkTime.
@RCW_DNCallsTransferred
Calculates the number of DN calls transferred by adding
DNCallsTransferredToACDDN + DNCallsTransferredToCDN +
DNCallsTransferredToDN + DNCallsTransferredToOther.
@RCW_DNInCalls
(Communication Server 1000/Meridian 1 PBX switch) Calculates the number of
incoming DN calls by adding DNInExtCalls + DNInIntCalls.
@RCW_DNInCallsHoldTime
Lists the total time incoming DN calls are on hold by adding
DNInExtCallsHoldTime + DNInIntCallsHoldTime.
@RCW_DNInCallsTalkTime
(Communication Server 1000/Meridian 1 PBX switch) Lists the total time spent
on incoming DN calls, including hold time, by adding DNInExtCallsTalkTime +
DNInIntCallsTalkTime.
(Communication Server 2x00/DMS switch) Lists the total time spent on
incoming DN calls, including hold time.
@RCW_DNInExtCallsHoldTime
Lists the total time incoming external DN calls are on hold.
@RCW_DNInExtCallsTalkTime
(Communication Server 1000/Meridian 1 PBX switch only) Lists the total time
spent on incoming external DN calls, including hold time.
@RCW_DNInIntCallsHoldTime
Lists the total time incoming internal DN calls are on hold.
@RCW_DNInIntCallsTalkTime
(Communication Server 1000/Meridian 1 PBX switch only) Lists the total time
spent on incoming internal DN calls, including hold time.
@RCW_DNOutCalls
(Communication Server 1000/Meridian 1 PBX) Calculates the number of
outgoing DN calls by adding DNOutExtCalls + DNOutIntCalls.
(Communication Server 2x00/DMS) Calculates the number of outgoing DN
calls as DNOutCalls.
@RCW_DNOutCallsHoldTime
Lists the total time outgoing DN calls are on hold by adding
DNOutExtCallsHoldTime + DNOutIntCallsHoldTime.
@RCW_DNOutCallsTalkTime
(Communication Server 1000/Meridian 1 PBX switch only) Lists the total time
spent on outgoing DN calls, including hold time, by adding
DNOutExtCallsTalkTime + DNOutIntCallsTalkTime.
(Communication Server 2x00/DMS) Lists the total time spent on outgoing DN
calls, including hold time.
@RCW_DNOutExtCallsHoldTime
Lists the total time outgoing external DN calls are on hold.
@RCW_DNOutExtCallsTalkTime
(Communication Server 1000/Meridian 1 PBX switch only) Lists the total time
spent on outgoing external DN calls, including hold time.
@RCW_DNOutIntCallsHoldTime
Lists the total time outgoing internal DN calls are on hold.
@RCW_DNOutIntCallsTalkTime
(Communication Server 1000/Meridian 1 PBX switch only) Lists the total time
spent on outgoing internal DN calls, including hold time.
@RCW_HoldTime
Lists the amount of time this agent put local and incoming contacts on hold,
excluding DN calls, ACD calls and NACD calls.
@RCW_LocalCallsAnswered
Calculates the number of local contacts answered by subtracting
NetworkCallsAnswered from CallsAnswered.
@RCW_LocalCallsTalkTime
Lists the total time that the agent spent handling local contacts, including hold
time, by subtracting NetworkCallsTalkTime from TalkTime.
@RCW_LoggedInTime
Lists the total time an agent is in the Login state.
@RCW_NACDCallsTalkTime
(Communication Server 1000/Meridian 1 PBX switch only) Lists total time
spent on NACD calls by an agent, including hold time.
@RCW_NetworkCallsTalkTime
Lists the total time that the agent spent handling incoming NSBR contacts,
including hold time.
@RCW_NotReadyTime
Lists total time an agent spends in the Not Ready state. Not Ready time includes
post-call processing time and Not Ready time with reason codes.
@RCW_ReservedTime
Lists the total time the agent is in Reserved state.
@RCW_RingTime
Lists the total time an agent spends in the Ringing state before answering a
Contact Center Manager call.
@RCW_SupervisorName
Lists the supervisor's full name in the format SupervisorGivenName
SupervisorSurName. If the information is not available, Supervisor Name Not
Defined message appears.
@RCW_SupervisorNameID
Lists the supervisor's full name and login ID in the format
SupervisorGivenName SupervisorSurName - SupervisorLogin. If the
information is not available, No Supervisor Name or ID Available message
appears.
@RCW_SupervisorNameIDLabel
Lists the text Supervisor Name & ID: SupervisorGivenName
SupervisorSurname - SupervisorLogin. If the information is not available,
Supervisor Name & ID Not Found message appears.
@RCW_TalkTime
Lists the total time spent by the agent handling all contacts except DN calls,
ACD calls, and NACD calls, including hold time.
@RCW_TimestampGroupName
Lists the Timestamp value as a formatted string based on the @report_datarange
formula and the setting for the option The section will be printed. If the value set
for @report_datarange is Daily, Weekly, or Monthly, only the date is printed. If
the value set for @report_datarang is Interval, the value is modified based on the
setting for The section will be printed.
You can use this formula in the Timestamp group header or group footer only.
@RCW_TimestampGroupNameLabel
Lists a label indicating the group option selected followed by the Timestamp
value as a formatted string (for example, Daily: 25/10/2005). The label and date
shown are based on the @report_datarange formula and the setting for the
option The section will be printed.
If the value set for @report_datarange is Daily, Weekly, or Monthly, only the
label and date are printed. If the value set for @report_datarange is Interval, the
label and value are modified based on the setting for The section will be printed.
You can use this formula in the Timestamp group header or group footer only.
@RCW_TotalCallsAnswered
(Communication Server 1000/Meridian 1 PBX switch) Calculates the total
number of calls answered by adding CallsAnswered + ACDCallsAnswered +
NACDCallsAnswered.
(Communication Server 2x00/DMS switch) Calculates the total number calls
answered by adding CallsAnswered + ACDCallsAnswered.
@RCW_TotalTalkTime
(Communication Server 1000/Meridian 1 PBX switch) Lists the total time spent
by the agent handling all contacts, including hold time by adding TalkTime +
ACDCallsTalkTime + NACDCallsTalkTime.
(Communication Server 2x00/DMS switch) Lists the total time spent by the
agent handling all contacts, including hold time by adding TalkTime +
ACDCallsTalkTime.
@RCW_VariableWrapTime
(Communication Server 2x00/DMS switch only) Lists the total time an agent is
in the Variable Wrap state for all skillsets.
@RCW_WaitingTime
Lists the total time an agent spends waiting for contacts.
@RCW_WalkawayTime
Lists the total time an agent is in the Walkaway state.
ApplicationStat formulas
The following ApplicationStat formulas are available.
@RCW_%CallsAbandoned
Calculates the percentage of calls abandoned by dividing CallsAbandoned by
CallsOffered, and multiplying by 100.
@RCW_%CallsAnswered
Calculates the percentage of calls answered by dividing CallsAnswered by
CallsOffered, and multiplying by 100.
@RCW_%CallsAnsweredAfterThreshold
Calculates the percentage of calls answered that are answered after a wait
greater than or equal to the service level threshold for the threshold class to
which the application belongs by dividing CallsAnsweredAftThreshold by
CallsAnswered, and multiplying by 100.
@RCW_%CallsAnsweredBeforeThreshold
Calculates the percentage of calls answered that are answered before a wait
greater than or equal to the service level threshold for the threshold class to
which the application belongs by dividing CallsAnswered -
CallsAnsweredAftThreshold by CallsAnswered, and multiplying by 100.
@RCW_%CallsGivenDefault
Calculates the percentage of calls given default treatment by dividing
CallsGivenDefault by CallsOffered, and multiplying by 100.
@RCW_%CallsGivenForceBusy
Calculates the percentage of calls given Force Busy treatment by dividing
CallsGivenForceBusy by CallsOffered, and multiplying by 100.
@RCW_%CallsGivenForceDisconnect
Calculates the percentage of calls given Force Disconnect treatment by dividing
CallsGivenForceDisconnect by CallsOffered, and multiplying by 100.
@RCW_%CallsGivenForceOverflow
Calculates the percentage of calls given Force Overflow treatment by dividing
CallsGivenForceOverflow by CallsOffered, and multiplying by 100.
@RCW_%CallsGivenHostLookup
Calculates the percentage of calls given Host Lookup treatment by dividing
CallsGivenHostLookup by CallsOffered, and multiplying by 100.
@RCW_%CallsGivenRouteTo
Calculates the percentage of calls given Route To treatment by dividing
CallsGivenRouteTo by CallsOffered, and multiplying by 100.
@RCW_%ServiceLevel
Calculates the percentage of calls that are serviced within the service level
threshold for the application by dividing (CallsAnswered + CallsAbandoned) -
(CallsAnsweredAftThreshold + CallsAbandonedAftThreshold) by
(CallsAnswered + CallsAbandoned), and multiplying by 100.
@RCW_ApplicationCallsAbandoned
Calculates the actual number of calls that entered the application and are hung
up before they are answered by subtracting IVRAbandoned from
CallsAbandoned.
@RCW_ApplicationLabel
Lists the text Application: Application.
@RCW_ApplicationNameID
Lists the application name and ID in the format Application - ApplicationID. If
the information is not available, No Information on Application message
appears.
@RCW_ApplicationNameIDLabel
Lists the text Application Name & ID: Application - ApplicationID. If the
information is not available, No Information on Application message appears.
@RCW_ApplicationNameOrID
Lists Application or, if this is not available, ApplicationID. If the information is
not available, No Information on Application message appears.
@RCW_ApplicationNameOrIDLabel
Lists the text Application Name: Application or, if this is not available,
Application ID: ApplicationID. If the information is not available, No
Information on Application message appears.
@RCW_AverageCallsAbandonedDelay
Lists the average wait time experienced by calls that are abandoned by dividing
CallsAbandonedDelay by the CallsAbandoned.
@RCW_AverageCallsAnsweredDelay
Lists the average wait time experienced by calls that are answered by dividing
CallsAnsweredDelay by the CallsAnswered.
@RCW_AverageNetOutCallsAbandonedDelay
Lists the average time delay experienced by outgoing NSBR calls sent by this
application and abandoned at the destination sites, by dividing
NetOutCallsAbandonedDelay by NetOutCallsAbandoned.
@RCW_AverageNetOutCallsAnsweredDelay
Lists the average time delay experienced by outgoing NSBR calls routed by this
application and answered at the destination sites, by dividing
NetOutCallsAnsweredDelay by NetOutCallsAnswered.
@RCW_AveragePostCallProcessingTime
Displays the average time agents spent performing post-call processing by
dividing PostCallProcessingTime by the CallsAnswered.
@RCW_AverageTalkTime
Displays the average time agents spent handling contacts (excluding DN calls)
in this interval, that were handled by this application by dividing TalkTime by
CallsAnswered. This statistic includes hold time.
@RCW_AverageTimeBeforeDefault
Lists the average time spent in the system by local Contact Center Manager
contacts and incoming NSBR contacts that received default treatment for this
application, by dividing TimeBeforeDefault by CallsGivenDefault.
@RCW_AverageTimeBeforeForceBusy
Lists the average time spent in the system by local Contact Center Manager calls
and incoming NSBR calls that received Force Busy treatment for this
application, by dividing TimeBeforeForceBusy by CallsGivenForceBusy.
@RCW_AverageTimeBeforeForceDisconnect
Lists the average time spent in the system by local Contact Center Manager calls
and incoming NSBR calls that received Force Disconnect treatment for this
application, by dividing TimeBeforeForceDisconnect by
CallsGivenForceDisconnect.
@RCW_AverageTimeBeforeForceOverflow
Lists the average time spent in the system by local Contact Center Manager calls
and incoming NSBR calls that received Force Overflow treatment for this
application, by dividing TimeBeforeForceOverflow by
CallsGivenForceOverflow.
@RCW_AverageTimeBeforeRouteTo
Lists the average time spent in the system by local Contact Center Manager calls
and incoming NSBR calls that received Route Call treatment, by dividing
TimeBeforeRouteTo by CallsGivenRouteTo.
@RCW_AverageWaitTime
Displays the average time agents spend waiting for a contact after releasing a
voice call or closing a multimedia contact handled by this application by
dividing WaitTime by CallsAnswered.
@RCW_CallsAbandonedDelay
Lists the wait time experienced by all Contact Center Manager calls abandoned
by callers.
@RCW_CallsAnsweredBeforeThreshold
Calculates the number of calls answered before a wait greater than or equal to
the service level threshold for the threshold class to which the application
belongs by subtracting CallsAnsweredAftThreshold from CallsAnswered.
@RCW_CallsAnsweredDelay
Lists the wait time experienced by all Contact Center Manager contacts
answered or accepted for this application.
@RCW_CallsAnsweredDelayAtSkillset
Lists the total wait time experienced in the skillset queue by all Contact Center
Manager contacts that are answered for this application.
@RCW_DNOutCallsTalkTime
(Communication Server 1000/Meridian 1 PBX switch only) Displays the total
time spent on outgoing DN calls, including hold time, for this application by
adding DNOutExtCallsTalkTime + DNOutIntCallsTalkTime.
@RCW_DNOutExtCallsTalkTime
(Communication Server 1000/Meridian 1 PBX switch only) Displays the total
time spent by agents on outgoing external DN calls, including hold time, for this
application.
@RCW_DNOutIntCallsTalkTime
(Communication Server 1000/Meridian 1 PBX switch only) Displays the total
time spent by agents on outgoing internal DN calls, including hold time, for this
application.
@RCW_MaxCallsAbandonedDelay
Lists the wait time experienced by the Contact Center Manager call that waited
the longest before it is abandoned.
@RCW_MaxCallsAnsDelay
Lists the wait time experienced by the Contact Center Manager call that waited
the longest before it is answered.
@RCW_MaxCallsAnsDelayAtSkillset
Lists the wait time experienced by the Contact Center Manager contact that
waited the longest in the skillset queue before it is answered.
@RCW_MaxNetOutCallsAbandonedDelay
Lists the wait time experienced by the outgoing NSBR Contact Center Manager
contact routed by this application that waited the longest before it is abandoned
at the destination site.
@RCW_MaxNetOutCallsAnsweredDelay
Lists the wait time experienced by the outgoing NSBR contact routed by this
application that waited the longest before it is answered or terminated at the
destination site.
@RCW_NetOutCallsAbandonedDelay
Lists the total time delay experienced by outgoing NSBR calls sent by this
application and abandoned at the destination sites.
@RCW_NetOutCallsAnsweredDelay
Lists the total time delay experienced by outgoing NSBR calls routed by this
application and answered at the destination sites.
@RCW_PostCallProcessingTime
Displays the total time agents spent performing post-call processing. Normally,
an agent uses this time to complete any work related to the call just released,
such as filling in forms or filing papers.
@RCW_TalkTime
Displays the total time agents spent handling contacts (excluding DN calls) in
this interval, that were handled by this application. This statistic includes hold
time.
@RCW_TimeBeforeDefault
Lists the total time spent in the system by local Contact Center Manager contacts
and incoming NSBR contacts that received default treatment for this application.
@RCW_TimeBeforeForceBusy
Lists the total time spent in the system by local Contact Center Manager calls
and incoming NSBR calls that received Force Busy treatment for this
application.
@RCW_TimeBeforeForceDisconnect
Lists the total time spent in the system by local Contact Center Manager calls
and incoming NSBR calls that received Force Disconnect treatment for this
application.
@RCW_TimeBeforeForceOverflow
Lists the total time spent in the system by local Contact Center Manager calls
and incoming NSBR calls that received Force Overflow treatment for this
application.
@RCW_TimeBeforeInterflow
Lists total amount of time that local Contact Center Manager contacts and
outgoing NSBR contacts spent in the Master_Script application before they are
passed to a primary application. For the Master_Script application, this is the
total time spent in the Master_Script by all contacts. For primary applications,
this is the total time spent in the Master_Script application by all contacts
answered for the primary application.
@RCW_TimeBeforeIVRTransferred
Lists the total time spent in the system by local Contact Center Manager calls
and incoming NSBR calls transferred to an IVR session for this application.
@RCW_TimeBeforeNACDOut
(Communication Server 1000/Meridian 1 PBX switch only) Lists the total time
spent in the system by local Contact Center Manager calls networked out
through the NACD queue and answered at remote nodes. NACD calls are sent to
other switches without using the Contact Center Manager NSBR feature.
@RCW_TimeBeforeNetOut
Lists the total time spent in the system by outgoing NSBR contacts that are
networked out by this application.
@RCW_TimeBeforeReachNonISDN
Lists the total time spent in the system by outgoing NSBR Contact Center
Manager calls before they reached a non-ISDN trunk.
@RCW_TimeBeforeRouteTo
Lists the total time spent in the system by local Contact Center Manager calls
and incoming NSBR calls that received Route Call treatment.
@RCW_TimestampGroupName
Lists the Timestamp value as a formatted string based on the @report_datarange
formula and the setting for the option The section will be printed. If the value set
for @report_datarange is Daily, Weekly, or Monthly, only the date is printed. If
the value set for @report_datarang is Interval, the value is modifed based on the
setting for The section will be printed.
You can use this formula in the Timestamp group header or group footer only.
@RCW_TimestampGroupNameLabel
Lists a label indicating the group option selected followed by the Timestamp
value as a formatted string (for example, Daily: 25/10/2005). The label and date
shown are based on the @report_datarange formula and the setting for the
option The section will be printed.
If the value set for @report_datarange is Daily, Weekly, or Monthly, only the
label and date are printed. If the value set for @report_datarange is Interval, the
label and value are modified based on the setting for The section will be printed.
You can use this formula in the Timestamp group header or group footer only.
@RCW_WaitTime
Displays the total time agents spend waiting for a contact after releasing a voice
call or closing a multimedia contact handled by this application.
CDNStat formulas
The following CDNStat formulas are available.
@RCW_%CallsAbandoned
Calculates the percentage of calls abandoned by dividing CallsAbandoned by
CallsOffered, and multiplying by 100.
@RCW_%CallsAnswered
Calculates the percentage of calls answered by dividing CallsAnswered by
CallsOffered, and multiplying by 100.
@RCW_%CallsTerminated
Calculates the percentage of calls abandoned by dividing CallsTerminated by
CallsOffered, and multiplying by 100.
@RCW_CDNNameID
Lists the CDN name and ID in the format CDNName - CDN. If the information
is not available, No Information on CDN message appears.
@RCW_CDNNameIDLabel
Lists the text CDN Name & ID: CDNName - CDN. If the information is not
available, There is no CDN Name or ID message appears.
@RCW_CDNNameOrID
Lists CDNName or, if this is not available, CDN. If the information is not
available, No Information on CDN message appears.
@RCW_CDNNameOrIDLabel
Lists the text CDN Name: CDNName or, if this is not available, CDN ID: CDN.
If the information is not available, No Information on CDN message appears.
@RCW_TimestampGroupName
Lists the Timestamp value as a formatted string based on the @report_datarange
formula and the setting for the option The section will be printed. If the value set
for @report_datarange is Daily, Weekly, or Monthly, only the date is printed. If
the value set for @report_datarang is Interval, the value is modifed based on the
setting for The section will be printed.
You can use this formula in the Timestamp group header or group footer only.
@RCW_TimestampGroupNameLabel
Lists a label indicating the group option selected followed by the Timestamp
value as a formatted string (for example, Daily: 25/10/2005). The label and date
shown are based on the @report_datarange formula and the setting for the
option The section will be printed.
If the value set for @report_datarange is Daily, Weekly, or Monthly, only the
label and date are printed. If the value set for @report_datarange is Interval, the
label and value are modified based on the setting for The section will be printed.
You can use this formula in the Timestamp group header or group footer only.
DNISStat formulas
The following DNISStat formulas are available.
@RCW_%CallsAbandoned
Calculates the percentage of calls abandoned by dividing CallsAbandoned by
CallsOffered, and multiplying by 100.
@RCW_%CallsAbandonedAfterThreshold
Calculates the percentage of calls abandoned that are abandoned after a wait
greater than or equal to the service level threshold for the DNIS number by
dividing CallsAbandonedAftThreshold by CallsAbandoned, and multiplying by
100.
@RCW_%CallsAbandonedBeforeThreshold
Calculates the percentage of calls abandoned that are abandoned before a wait
greater than or equal to the service level threshold for the DNIS number by
dividing CallsAbandoned - CallsAbandonedAftThreshold by CallsAbandoned,
and multiplying by 100.
@RCW_%CallsAnswered
Calculates the percentage of calls answered by dividing CallsAnswered by
CallsOffered, and multiplying by 100.
@RCW_%CallsAnsweredAfterThreshold
Calculates the percentage of calls answered that are answered after a wait
greater than or equal to the service level threshold for the DNIS number by
dividing CallsAnsweredAftThreshold by CallsAnswered, and multiplying by
100.
@RCW_%CallsAnsweredBeforeThreshold
Calculates the percentage of calls answered that are answered before a wait
greater than or equal to the service level threshold for the DNIS number by
dividing CallsAnswered - CallsAnsweredAftThreshold by CallsAnswered, and
multiplying by 100.
@RCW_%CallsGivenDefault
Calculates the percentage of calls given default treatment by dividing
CallsGivenDefault by CallsOffered, and multiplying by 100.
@RCW_%CallsGivenForceBusy
Calculates the percentage of calls given Force Busy treatment by dividing
CallsGivenForceBusy by CallsOffered, and multiplying by 100.
@RCW_%CallsGivenForceDisconnect
Calculates the percentage of calls given Force Disconnect treatment by dividing
CallsGivenForceDisconnect by CallsOffered, and multiplying by 100.
@RCW_%CallsGivenForceOverflow
Calculates the percentage of calls given Force Overflow treatment by dividing
CallsGivenForceOverflow by CallsOffered, and multiplying by 100.
@RCW_%CallsGivenRouteTo
Calculates the percentage of calls given Route To treatment by dividing
CallsGivenRouteTo by CallsOffered, and multiplying by 100.
@RCW_%CallsNetworkedOut
Calculates the percentage of calls that are routed to a remote site and answered
or abandoned by dividing CallsNetworkedOut by CallsOffered, and multiplying
by 100.
@RCW_%ServiceLevel
Calculates the percentage of calls that are serviced within the service level
threshold for the application by dividing (CallsAnswered + CallsAbandoned) -
(CallsAnsweredAftThreshold + CallsAbandonedAftThreshold) by
(CallsAnswered + CallsAbandoned), and multiplying by 100.
@RCW_AverageAbandonedDelay
Calculates the average wait time experienced by all local Contact Center
Manager calls and incoming NSBR calls abandoned for a DNIS number, by
dividing CallsAbandonedDelay by CallsAbandoned.
@RCW_AverageAnsweredDelay
Calculates the average wait time experienced by all local Contact Center
Manager calls and incoming NSBR calls answered for a DNIS number, by
dividing CallsAnsweredDelay by CallsAnswered.
@RCW_AverageTalkTime
Lists the average time spent by all agents on local Contact Center Manager calls
and incoming NSBR calls for a DNIS number, including hold time, by dividing
TalkTime by CallsAnswered.
@RCW_CallsAbandonedBeforeThreshold
Calculates the number of calls answered that are answered before a wait greater
than or equal to the service level threshold for the DNIS number, by subtracting
CallsAbandonedAftThreshold from CallsAbandoned.
@RCW_CallsAbandonedDelay
Lists the total wait experienced by calls that are abandoned.
@RCW_CallsAnsweredBeforeThreshold
Calculates the number of calls answered before a wait greater than or equal to
the service level threshold for the DNIS number by subtracting
CallsAnsweredAftThreshold from CallsAnswered.
@RCW_CallsAnsweredDelay
Lists the wait time experienced by all local Contact Center Manager calls and
incoming NSBR calls answered for a DNIS number.
@RCW_DNISNameID
Lists the DNIS name and ID in the format DNISName - DNIS. If the
information is not available, No Information on DNIS message appears.
@RCW_DNISNameIDLabel
Lists the text DNIS Name & ID: DNISName - DNIS. If the information is not
available, No DNIS Information available message appears.
@RCW_DNISNameOrID
Lists DNISName or, if this is not available, DNIS. If the information is not
available, No Information on DNIS message appears.
@RCW_DNISNameOrIDLabel
Lists the text DNIS Name: DNISName or, if this is not available, DNIS ID:
DNIS. If the information is not available, No Information on DNIS message
appears.
@RCW_MaxAbandonDelay
Lists the wait time experienced by the local Contact Center Manager calls or
incoming NSBR call that waited the longest before it is abandoned.
@RCW_MaxAnsweredDelay
Lists the wait time experienced by the local Contact Center Manager calls or
incoming NSBR call that waited the longest before it is answered.
@RCW_TalkTime
Lists the total time spent by all agents on local Contact Center Manager calls and
incoming NSBR calls for a DNIS number, including hold time.
@RCW_TimestampGroupName
Lists the Timestamp value as a formatted string based on the @report_datarange
formula and the setting for the option The section will be printed. If the value set
for @report_datarange is Daily, Weekly, or Monthly, only the date is printed. If
the value set for @report_datarang is Interval, the value is modifed based on the
setting for The section will be printed.
You can use this formula in the Timestamp group header or group footer only.
@RCW_TimestampGroupNameLabel
Lists a label indicating the group option selected followed by the Timestamp
value as a formatted string (for example, Daily: 25/10/2005). The label and date
shown are based on the @report_datarange formula and the setting for the
option The section will be printed.
If the value set for @report_datarange is Daily, Weekly, or Monthly, only the
label and date are printed. If the value set for @report_datarange is Interval, the
label and value are modified based on the setting for The section will be printed.
You can use this formula in the Timestamp group header or group footer only.
IVRPortStat formulas
The following IVRPortStat formulas are available.
@RCW_AverageNotReadyTime
Lists the average time spent by the IVR port in the Not Ready state by dividing
NotReadyTime by CallsAnswered.
@RCW_AverageTalkTime
Lists the average time the IVR port is in use by dividing TalkTime by
CallsAnswered.
@RCW_AverageWaitingTime
Lists average time the IVR port is idle by dividing WaitingTime by
CallsAnswered.
@RCW_IVRPortNameID
Lists the IVR Port name and ID in the format IVRPortName - IVRPortID. If the
information is not available, No Information on IVRPort message appears.
@RCW_IVRPortNameIDLabel
Lists the text Port Name & ID: IVRPortName - IVRPortID. If the information is
not available, IVR Port Name & ID not available message appears.
@RCW_IVRQueueNameID
Lists the IVR Queue name and ID in the format IVRQueueName -
IVRQueueID. If the information is not available, No Information on IVRQueue
message appears.
@RCW_IVRQueueNameIDLabel
Lists the text Queue Name & ID: IVRQueueName - IVRQueueID. If the
information is not available, IVR Queue Name & ID not available message
appears.
@RCW_LoggedInTime
Lists the total time that the IVR port is logged on.
@RCW_NotReadyTime
Lists the total time spent by the IVR port in the Not Ready state.
@RCW_TalkTime
Lists the total time the IVR port is in use.
@RCW_TimestampGroupName
Lists the Timestamp value as a formatted string based on the @report_datarange
formula and the setting for the option The section will be printed. If the value set
for @report_datarange is Daily, Weekly, or Monthly, only the date is printed. If
the value set for @report_datarang is Interval, the value is modifed based on the
setting for The section will be printed.
You can use this formula in the Timestamp group header or group footer only.
@RCW_TimestampGroupNameLabel
Lists a label indicating the group option selected followed by the Timestamp
value as a formatted string (for example, Daily: 25/10/2005). The label and date
shown are based on the @report_datarange formula and the setting for the
option The section will be printed.
If the value set for @report_datarange is Daily, Weekly, or Monthly, only the
label and date are printed. If the value set for @report_datarange is Interval, the
label and value are modified based on the setting for The section will be printed.
You can use this formula in the Timestamp group header or group footer only.
@RCW_WaitTime
Lists the total time the IVR port is idle.
IVRStat formulas
The following IVRStat formulas are available.
@RCW_%CallsAnswered
Calculates the percentage of calls answered by dividing CallsAnswered by
CallsOffered, and multiplying by 100.
@RCW_%CallsAnsweredAfterThreshold
Calculates the percentage of calls answered that are answered after a wait
greater than or equal to the service level threshold for the threshold class to
which the IVR ACD-DN belongs by dividing CallsAnsweredAftThreshold by
CallsAnswered, and multiplying by 100.
@RCW_%CallsAnsweredBeforeThreshold
Calculates the percentage of calls answered that are answered before a wait
greater than or equal to the service level threshold for the threshold class to
which the IVR ACD-DN belongs by dividing CallsAnswered -
CallsAnsweredAftThreshold by CallsAnswered, and multiplying by 100.
@RCW_AverageCallsAnsweredDelay
Lists the average wait time experienced by all the calls answered by dividing
CallsAnsweredDelay by CallsAnswered.
@RCW_AverageCallsNotTreatedDelay
Lists the average wait time experienced by all the calls abandoned or pulled
back from an IVR queue by dividing CallsNotTreatedDelay by CallsNotTreated.
@RCW_CallsAnsweredBeforeThreshold
Calculates the number of calls answered before a wait greater than or equal to
the service level threshold for the threshold class to which the IVR ACD-DN
belongs by subtracting CallsAnsweredAftThreshold from CallsAnswered.
@RCW_CallsAnsweredDelay
Lists the total wait time experienced by all the calls answered.
@RCW_CallsNotTreatedDelay
Lists the total wait time experienced by all the calls abandoned or pulled back
from an IVR queue.
@RCW_IVRQueueNameID
Lists the IVR Queue name and ID in the format IVRQueueName -
IVRQueueID. If the information is not available, No Information on IVRQueue
message appears.
@RCW_IVRQueueNameIDLabel
Lists the text Queue Name & ID: IVRQueueName - IVRQueueID. If the
information is not available, No Queue Information available message appears.
@RCW_TimestampGroupName
Lists the Timestamp value as a formatted string based on the @report_datarange
formula and the setting for the option The section will be printed. If the value set
for @report_datarange is Daily, Weekly, or Monthly, only the date is printed. If
the value set for @report_datarang is Interval, the value is modifed based on the
setting for The section will be printed.
You can use this formula in the Timestamp group header or group footer only.
@RCW_TimestampGroupNameLabel
Lists a label indicating the group option selected followed by the Timestamp
value as a formatted string (for example, Daily: 25/10/2005). The label and date
shown are based on the @report_datarange formula and the setting for the
option The section will be printed.
If the value set for @report_datarange is Daily, Weekly, or Monthly, only the
label and date are printed. If the value set for @report_datarange is Interval, the
label and value are modified based on the setting for The section will be printed.
You can use this formula in the Timestamp group header or group footer only.
LicenseStat formulas
The following LicenseStat formulas are available.
@RCW_TimestampGroupName
Lists the Timestamp value as a formatted string based on the @report_datarange
formula and the setting for the option The section will be printed. If the value set
for @report_datarange is Daily, Weekly, or Monthly, only the date is printed. If
the value set for @report_datarang is Interval, the value is modifed based on the
setting for The section will be printed.
You can use this formula in the Timestamp group header or group footer only.
@RCW_TimestampGroupNameLabel
Lists a label indicating the group option selected followed by the Timestamp
value as a formatted string (for example, Daily: 25/10/2005). The label and date
shown are based on the @report_datarange formula and the setting for the
option The section will be printed.
If the value set for @report_datarange is Daily, Weekly, or Monthly, only the
label and date are printed. If the value set for @report_datarange is Interval, the
label and value are modified based on the setting for The section will be printed.
You can use this formula in the Timestamp group header or group footer only.
NetworkInCallStat formulas
The following NetworkInCallStat formulas are available.
@RCW_%CallsAbandoned
Calculates the percentage of calls abandoned by dividing CallsAbandoned by
CallsOffered, and multiplying by 100.
@RCW_%CallsAbandonedAfterThreshold
Calculates the percentage of calls abandoned that are abandoned after a wait
greater than or equal to the service level threshold for the application by dividing
CallsAbandonedAftThreshold by CallsAbandoned, and multiplying by 100.
@RCW_%CallsAbandonedBeforeThreshold
Calculates the percentage of calls abandoned that are abandoned before a wait
greater than or equal to the service level threshold for the application by dividing
CallsAbandoned - CallsAbandonedAftThreshold by CallsAbandoned, and
multiplying by 100.
@RCW_%CallsAnswered
Calculates the percentage of calls answered by dividing CallsAnswered by
CallsOffered, and multiplying by 100.
@RCW_%CallsAnsweredAfterThreshold
Calculates the percentage of calls answered that are answered after a wait
greater than or equal to the service level threshold for the application by dividing
CallsAnsweredAftThreshold by CallsAnswered, and multiplying by 100.
@RCW_%CallsAnsweredBeforeThreshold
Calculates the percentage of calls answered that are answered before a wait
greater than or equal to the service level threshold for the application by dividing
CallsAnswered - CallsAnsweredAftThreshold by CallsAnswered, and
multiplying by 100.
@RCW_AverageCallsAbandonedDelay
Lists the average wait time experienced by all incoming NSBR calls abandoned
at the local site, by dividing CallsAbandonedDelay by CallsAbandoned.
@RCW_AverageCallsAbandonedDelayAtDest
Lists the average wait time experienced at the local site by all incoming NSBR
calls abandoned at the local site, by dividing CallsAbandonedDelayAtDest by
CallsAbandoned.
@RCW_AverageCallsAnsweredDelay
Lists the average wait time experienced by all incoming NSBR calls answered at
the local site, by dividing CallsAnsweredDelay by CallsAnswered.
@RCW_AverageCallsAnsweredDelayAtDest
Lists the average wait time experienced at the local site by all incoming NSBR
calls answered at the local site, by dividing CallsAnsweredDelayAtDest by
CallsAnswered.
@RCW_CallsAbandonedBeforeThreshold
Calculates the number of calls answered that are answered before a wait greater
than or equal to the service level threshold for the application, by subtracting
CallsAbandonedAftThreshold from CallsAbandoned.
@RCW_CallsAbandonedDelay
Lists the total wait time experienced by all incoming NSBR calls abandoned at
the local site.
@RCW_CallsAbandonedDelayAtDest
Lists the total wait time experienced at the local site by all incoming NSBR calls
abandoned at the local site.
@RCW_CallsAnsweredBeforeThreshold
Calculates the number of calls answered before a wait greater than or equal to
the service level threshold for the application by subtracting
CallsAnsweredAftThreshold from CallsAnswered.
@RCW_CallsAnsweredDelay
Lists the total wait time experienced by all incoming NSBR calls answered at
the local site.
@RCW_CallsAnsweredDelayAtDest
Lists the total wait time experienced at the local site by all incoming NSBR calls
answered at the local site.
@RCW_DstSiteNameOrID
Lists DstSite or, if this is not available, DstSiteID. If the information is not
available, No Information on Destination Site message appears.
@RCW_MaxAbandonedDelay
Lists the wait time experienced by the incoming NSBR call that waited the
longest before it is abandoned at the local site.
@RCW_MaxAbandonedDelayAtDest
Lists the wait time experienced by the call that waited the longest at the local site
before it is abandoned.
@RCW_MaxAnsweredDelay
Lists the total wait time experienced by all calls answered at the local site.
@RCW_MaxAnsweredDelayAtDest
Lists the wait time experienced by the call that waited the longest at the local site
before it is answered.
@RCW_SrcSiteNameOrID
Lists SrcSite or, if this is not available, SrcSiteID. If the information is not
available, No Information on Source Site message appears.
@RCW_TimestampGroupName
Lists the Timestamp value as a formatted string based on the @report_datarange
formula and the setting for the option The section will be printed. If the value set
for @report_datarange is Daily, Weekly, or Monthly, only the date is printed. If
the value set for @report_datarang is Interval, the value is modifed based on the
setting for The section will be printed.
You can use this formula in the Timestamp group header or group footer only.
@RCW_TimestampGroupNameLabel
Lists a label indicating the group option selected followed by the Timestamp
value as a formatted string (for example, Daily: 25/10/2005). The label and date
shown are based on the @report_datarange formula and the setting for the
option The section will be printed.
If the value set for @report_datarange is Daily, Weekly, or Monthly, only the
label and date are printed. If the value set for @report_datarange is Interval, the
label and value are modified based on the setting for The section will be printed.
You can use this formula in the Timestamp group header or group footer only.
NetworkOutStat formulas
The following NetworkOutStat formulas are available.
@RCW_%CallsAbandoned
Calculates the percentage of calls abandoned by dividing CallsAbandoned by
CallsOffered, and multiplying by 100.
@RCW_%CallsAnswered
Calculates the percentage of calls answered by dividing CallsAnswered by
CallsOffered, and multiplying by 100.
@RCW_AverageCallAbandonedDelayAtDest
Lists the average wait time experienced at the destination site by all calls from
the local site that are abandoned at the destination site, by dividing
CallAbandonedDelayAtDest by CallsAbandoned.
@RCW_AverageCallAnsweredDelayAtDest
Lists the average wait time experienced at the destination site by all calls from
the local site that are answered by an agent, answered by IVR, or terminated at
the destination site, by dividing CallAnsweredDelayAtDestination by
CallsAnswered.
@RCW_AverageTotalCallAbandonedDelay
Lists the average wait time experienced by all calls from the local site that are
abandoned at the destination site, by dividing TotalCallAbandonedDelay by
CallsAbandoned.
@RCW_AverageTotalCallAnsweredDelay
Lists the average wait time experienced by all calls from the local site that are
answered by an agent, answered by IVR, or terminated at the destination site, by
dividing TotalCallAnsweredDelay by CallsAnswered.
@RCW_CallAbandonedDelayAtDest
Lists the total wait time experienced at the destination site by all calls from the
local site that are abandoned at the destination site.
@RCW_CallAnsweredDelayAtDest
Lists the total wait time experienced at the destination site by all calls from the
local site that are answered by an agent, answered by IVR, or terminated at the
destination site.
@RCW_DstSiteNameOrID
Lists DstSite or, if this is not available, DstSiteID. If the information is not
available, No Information on Destination Site message appears.
@RCW_MaxCallAbandonedDelay
Lists the wait time experienced by the call originating at the local site that
waited the longest before it is abandoned at the destination site.
@RCW_MaxCallAbandonedDelayAtDest
Lists the wait time experienced by the call originating at the local site that
waited the longest at the destination site before it is abandoned.
@RCW_MaxCallAnsweredDelay
Lists the wait time experienced by the call originating at the local site that
waited the longest before it is answered by an agent, answered by IVR, or
terminated at the destination site.
@RCW_MaxCallAnsweredDelayAtDest
Lists the wait time experienced by the call originating at the local site that
waited the longest at the destination site before it is answered by an agent,
answered by IVR, or terminated.
@RCW_SrcSiteNameOrID
Lists SrcSite or, if this is not available, SrcSiteID. If the information is not
available, No Information on Source Site message appears.
@RCW_TimestampGroupName
Lists the Timestamp value as a formatted string based on the @report_datarange
formula and the setting for the option The section will be printed. If the value set
for @report_datarange is Daily, Weekly, or Monthly, only the date is printed. If
the value set for @report_datarang is Interval, the value is modifed based on the
setting for The section will be printed.
You can use this formula in the Timestamp group header or group footer only.
@RCW_TimestampGroupNameLabel
Lists a label indicating the group option selected followed by the Timestamp
value as a formatted string (for example, Daily: 25/10/2005). The label and date
shown are based on the @report_datarange formula and the setting for the
option The section will be printed.
If the value set for @report_datarange is Daily, Weekly, or Monthly, only the
label and date are printed. If the value set for @report_datarange is Interval, the
label and value are modified based on the setting for The section will be printed.
You can use this formula in the Timestamp group header or group footer only.
@RCW_TotalCallAbandonedDelay
Lists the total wait time experienced by all calls from the local site that are
abandoned at the destination site.
@RCW_TotalCallAnsweredDelay
Lists the total wait time experienced by all calls from the local site that are
answered by an agent, answered by IVR, or terminated at the destination site.
RANMusicRouteStat formulas
The following RANMusicRouteStat formulas are available.
@RCW_RouteAccessTime
Lists the total time a music or RAN route is in use.
@RCW_RouteNameID
Lists the Route name and ID in the format RouteName - RouteID. If the
information is not available, No Information on Route message appears.
@RCW_RouteNameIDLabel
Lists the text Route Name & ID: RouteName - RouteID. If the information is not
available, Route Name and ID not available message appears.
@RCW_TimestampGroupName
Lists the Timestamp value as a formatted string based on the @report_datarange
formula and the setting for the option The section will be printed. If the value set
for @report_datarange is Daily, Weekly, or Monthly, only the date is printed. If
the value set for @report_datarang is Interval, the value is modifed based on the
setting for The section will be printed.
You can use this formula in the Timestamp group header or group footer only.
@RCW_TimestampGroupNameLabel
Lists a label indicating the group option selected followed by the Timestamp
value as a formatted string (for example, Daily: 25/10/2005). The label and date
shown are based on the @report_datarange formula and the setting for the
option The section will be printed.
If the value set for @report_datarange is Daily, Weekly, or Monthly, only the
label and date are printed. If the value set for @report_datarange is Interval, the
label and value are modified based on the setting for The section will be printed.
You can use this formula in the Timestamp group header or group footer only.
RouteStat formulas
The following RouteStat formulas are available.
@RCW_AllTrunksBusyTime
Lists the total time all trunks in this route are busy.
@RCW_AverageAllTrunksBusyTime
Lists the total time all trunks in this route are busy by dividing
AllTrunksBusyTime by AllTrunksBusy.
@RCW_RouteNameID
Lists the Route name and ID in the format RouteName - RouteID. If the
information is not available, No Information on Route message appears.
@RCW_RouteNameIDLabel
Lists the text Route Name & ID: RouteName - RouteID. If the information is not
available, No Route Name and ID Available message appears.
@RCW_TimestampGroupName
Lists the Timestamp value as a formatted string based on the @report_datarange
formula and the setting for the option The section will be printed. If the value set
for @report_datarange is Daily, Weekly, or Monthly, only the date is printed. If
the value set for @report_datarang is Interval, the value is modifed based on the
setting for The section will be printed.
You can use this formula in the Timestamp group header or group footer only.
@RCW_TimestampGroupNameLabel
Lists a label indicating the group option selected followed by the Timestamp
value as a formatted string (for example, Daily: 25/10/2005). The label and date
shown are based on the @report_datarange formula and the setting for the
option The section will be printed.
If the value set for @report_datarange is Daily, Weekly, or Monthly, only the
label and date are printed. If the value set for @report_datarange is Interval, the
label and value are modified based on the setting for The section will be printed.
You can use this formula in the Timestamp group header or group footer only.
SkillsetStat formulas
The following SkillsetStat formulas are available.
@RCW_%CallsAnswered
Calculates the percentage of calls answered by dividing CallsAnswered by
CallsOffered, and multiplying by 100.
@RCW_%CallsAnsweredAfterThreshold
Calculates the percentage of calls answered that are answered after a wait
greater than or equal to the service level threshold for the threshold class to
which the skillset belongs by dividing CallsAnsweredAftThreshold by
CallsAnswered, and multiplying by 100.
@RCW_%CallsAnsweredBeforeThreshold
Calculates the percentage of calls answered that are answered before a wait
greater than or equal to the service level threshold for the threshold class to
which the skillset belongs by dividing CallsAnswered -
CallsAnsweredAftThreshold by CallsAnswered, and multiplying by 100.
@RCW_%LocalCallsAnswered
Calculates the percentage of local calls answered for this skillset by dividing
CallsAnswered - NetCallsAnswered by CallsAnswered, and multiplying by 100.
@RCW_%NetCallsAnswered
Calculates the percentage of incoming network calls answered for this skillset
by dividing NetCallsAnswered by CallsAnswered, and multiplying by 100.
@RCW_ActiveTime
Lists the amount of time a skillset is in service. A skillset is in service when it is
not in Out of Service mode and at least one agent is logged on.
@RCW_AllAgentBusyTime
Lists the total time that all agents assigned this skillset are busy with calls or no
agents are logged on.
@RCW_ApplicationNameID
Lists the application name and ID in the format Application - ApplicationID. If
the information is not available, No Information on Application message
appears.
@RCW_ApplicationNameIDLabel
Lists the text Application Name & ID: Application - ApplicationID. If the
information is not available, No Information on Application message appears.
@RCW_ApplicationNameOrID
Lists Application, or if this is not available, ApplicationID. If the information is
not available, No Information on Application message appears.
@RCW_ApplicationNameOrIDLabel
Lists the text Application Name: Application or, if this is not available,
Application ID: ApplicationID. If the information is not available, No
Information on Application message appears.
@RCW_AverageCallsAnsweredDelay
Calculates the average wait time experienced by all local Contact Center
Manager calls and incoming NSBR calls answered for this skillset, by dividing
CallsAnsweredDelay by CallsAnswered.
@RCW_AverageNumberOfAgents
Calculates the average number of logged on agents belonging to this skillset, by
dividing TotalStaffedTime by ActiveTime.
@RCW_AveragePostCallProcessingTime
Displays the average time agents spent performing post-call processing by
dividing PostCallProcessingTime by the CallsAnswered.
@RCW_AverageSkillsetAbandonedDelay
Lists the average wait time experienced by Contact Center Manager calls that
are abandoned for this skillset, by dividing SkillsetAbandonedDelay by
SkillsetAbandoned.
@RCW_AverageTalkTime
Displays the average time agents spent handling contacts (excluding DN calls)
in this interval, that were handled by this skillset by dividing TalkTime by
CallsAnswered. This statistic includes hold time.
@RCW_AverageWaitTime
Displays the average time agents spend waiting for a contact after releasing a
voice call or closing a multimedia contact handled by this skillset by dividing
WaitTime by CallsAnswered.
@RCW_CallsAnsweredBeforeThreshold
Calculates the number of calls answered before a wait greater than or equal to
the service level threshold for the threshold class to which the skillset belongs by
subtracting CallsAnsweredAftThreshold from CallsAnswered.
@RCW_CallsAnsweredDelay
Lists the wait time experienced by all local Contact Center Manager calls and
incoming NSBR calls answered for this skillset.
@RCW_DNOutCallsTalkTime
(Communication Server 1000/Meridian 1 PBX switch only) Displays the total
time spent on outgoing DN calls, including hold time, for this skillset by adding
DNOutExtCallsTalkTime + DNOutIntCallsTalkTime.
@RCW_DNOutExtCallsTalkTime
(Communication Server 1000/Meridian 1 PBX switch only) Displays the total
time spent by agents on outgoing external DN calls, including hold time, for this
skillset.
@RCW_DNOutIntCallsTalkTime
(Communication Server 1000/Meridian 1 PBX switch only) Displays the total
time spent by agents on outgoing internal DN calls, including hold time, for this
skillset.
@RCW_LocalCallsAnswered
Calculates the number of local contacts answered by subtracting
NetCallsAnswered from CallsAnswered.
@RCW_MaxAnsweredDelay
Lists the wait time experienced by the local Contact Center Manager calls or
incoming NSBR call that waited the longest before it is answered.
@RCW_MaxSkillsetAbandonedDelay
Lists the wait time experienced by the local Contact Center Manager call or
incoming NSBR call queued to this skillset that waited the longest before it is
abandoned.
@RCW_PostCallProcessingTime
Displays the total time agents spent performing post-call processing. Normally,
an agent uses this time to complete any work related to the call just released,
such as filling in forms or filing papers.
@RCW_SiteNameOrID
Lists Site or, if this is not available, SiteID. If the information is not available,
No Information on Site message appears.
@RCW_SkillsetAbandonedBeforeThreshold
Calculates the number of Contact Center Manager calls abandoned for this
skillset before a wait greater than or equal to the service level threshold for the
threshold class to which the skillset belongs, by subtracting
SkillsetAbandonedAftThreshold from SkillsetAbandoned.
@RCW_SkillsetAbandonedDelay
Lists the total wait time experienced by Contact Center Manager calls that are
abandoned for this skillset.
@RCW_SkillsetNameID
Lists the skillset name and ID in the format Skillset - SkillsetID. If the
information is not available, No Information on Skillset message appears.
@RCW_SkillsetNameIDLabel
Lists the text Skillset Name & ID: Skillset - SkillsetID. If the information is not
available, No Information on Skillset message appears.
@RCW_SkillsetNameOrID
Lists Skillset or, if this is not available, SkillsetID. If the information is not
available, No Information on Skillset message appears.
@RCW_SkillsetNameOrIDLabel
Lists the text Skillset Name: Skillset or, if this is not available, Skillset ID:
SkillsetID. If the information is not available, No Information on Skillset
message appears.
@RCW_TalkTime
Displays the total time agents spent handling contacts (excluding DN calls) in
this interval, that were handled by this skillset. This statistic includes hold time.
@RCW_TimestampGroupName
Lists the Timestamp value as a formatted string based on the @report_datarange
formula and the setting for the option The section will be printed. If the value set
for @report_datarange is Daily, Weekly, or Monthly, only the date is printed. If
the value set for @report_datarang is Interval, the value is modifed based on the
setting for The section will be printed.
You can use this formula in the Timestamp group header or group footer only.
@RCW_TimestampGroupNameLabel
Lists a label indicating the group option selected followed by the Timestamp
value as a formatted string (for example, Daily: 25/10/2005). The label and date
shown are based on the @report_datarange formula and the setting for the
option The section will be printed.
If the value set for @report_datarange is Daily, Weekly, or Monthly, only the
label and date are printed. If the value set for @report_datarange is Interval, the
label and value are modified based on the setting for The section will be printed.
You can use this formula in the Timestamp group header or group footer only.
@RCW_TotalStaffedTime
Lists the amount of logon time for all agents belonging to this skillset.
@RCW_WaitTime
Displays the total time agents spend waiting for a contact after releasing a voice
call or closing a multimedia contact handled by this skillset.
TrunkStat formulas
The following TrunkStat formulas are available:
@RCW_%CallsAbandoned
Calculates the percentage of calls abandoned by dividing CallsAbandoned by
CallsOffered, and multiplying by 100.
@RCW_%CallsAnswered
Calculates the percentage of calls answered by dividing CallsAnswered by
CallsOffered, and multiplying by 100.
@RCW_%Usage
Calculates the percentage of time that the trunk is occupied during the selected
interval by dividing OccupancyTime by the time the trunk is available, and
multiplying by 100. The time the trunk is available is determined based on the
value set for the @report_datarange formula.
@RCW_AverageCallsAbandonedDelay
Lists the average wait time experienced by calls that are abandoned by dividing
CallsAbandonedDelay by the CallsAbandoned.
@RCW_AverageCallsAnsweredDelay
Lists the average wait time experienced by calls that are answered by dividing
CallsAnsweredDelay by the CallsAnswered.
@RCW_CallsAbandonedDelay
Lists the total wait time experienced by calls that are abandoned.
@RCW_CallsAnsweredDelay
Lists the total wait time experienced by calls that are answered.
@RCW_OccupancyTime
Lists the amount of time that the trunk is occupied.
@RCW_TimestampGroupName
Lists the Timestamp value as a formatted string based on the @report_datarange
formula and the setting for the option The section will be printed. If the value set
for @report_datarange is Daily, Weekly, or Monthly, only the date is printed. If
the value set for @report_datarang is Interval, the value is modifed based on the
setting for The section will be printed.
You can use this formula in the Timestamp group header or group footer only.
@RCW_TimestampGroupNameLabel
Lists a label indicating the group option selected followed by the Timestamp
value as a formatted string (for example, Daily: 25/10/2005). The label and date
shown are based on the @report_datarange formula and the setting for the
option The section will be printed.
If the value set for @report_datarange is Daily, Weekly, or Monthly, only the
label and date are printed. If the value set for @report_datarange is Interval, the
label and value are modified based on the setting for The section will be printed.
You can use this formula in the Timestamp group header or group footer only.
@RCW_TrunkIDRouteLabel
Lists a string identifying the specific trunk by combining Trunk ID: + TrunkID +
Route Name: + Route + Route ID: RouteID. If the Route or RouteID fields are
blank they are not displayed.
Pegging examples
In this appendix
Pegging of local calls 1392
Pegging of network calls 1395
Pegging of activity codes 1399
Pegging of Not Ready reason codes 1403
Pegging of agent state timers 1406
Pegging of ACD-DNs 1408
Pegging of DNIS calls 1410
Pegging of calls returned to queue 1411
Pegging when a skillset is out of service 1412
Pegging for calls networked out by NACD 1414
Pegging blind transfers 1416
Pegging when the caller leaves a message 1419
Pegging of calls answered by a backup skillset 1420
Scenario
Call arrives 09:00:00
In this scenario, the agent’s call presentation class is configured for a break
(variable wrap) of 30 seconds after each call.
Pegging
Field Pegging
CallsOffered 1
CallsAnswered 1
CDNCallsConferencedToDN 1
ConsultationTime 3
(Communication Server 1000/
Meridian 1 PBX switch)
TalkTime 23
BreakTime/VariableWrapTime 30
Field Pegging
CallsOffered 1
CallsGivenIVR 1
Field Pegging
CallsOffered 1
CallsAnswered 1
Field Pegging
CallsAnsweredDelay 15 seconds
Time from when the Master handed
off to the primary and is answered.
AnsDelay16 1
CallsAnsweredDelayAtSkillset 12 seconds
CallsConferencedOut 1
TimeBeforeInterflow 2 seconds
CDNStat view
Field Pegging
CallsAnswered 1
Field Pegging
Application Booking_Script
CallsOffered 1
CallsAnswered 1
CallsAnsweredDelay 12 seconds
BreakTime/VariableWrapTime 30 seconds
This section provides a typical example of how network calls peg (at the source
site and at the destination site).
Scenario
Call arrives at Toronto 09:00:00
Field Pegging
CallsOffered 1
Field Pegging
CallsOffered 1
NetOutCalls 1
NetOutCallsAnswered 1
NetOutCallsAnsweredDelay 15 seconds
AnsDelay16 1
CallsAnsweredDelayAtSkillset 13 seconds
NetworkOutCallStat view
Field Pegging
Calls Offered 1
Calls Answered 1
Field Pegging
CallsAnsweredDelay 7 seconds
AnsDelay8 1
CallsAnsweredDelayAtSkillset 13 seconds
NetworkInCallStat view
Field Pegging
Field Pegging
Calls Offered 1
Calls Answered 1
Field Pegging
CallsAnswered 1
TalkTime 20
3456 1 1 minutes
5678 1 3 minutes
1234 1 9 minutes
09:30:00 1234 0 3 minutes
The system default activity code is used because the agent did not enter an
activity code during the first interval.
1234 1 3 minutes
123 1 10 minutes
Not Ready reason code statistics peg as follows, in the ActivityCodeStat view:
3456 1 4 minutes
Not Ready reason code statistics peg as follows, in the ActivityCodeStat view:
1234 1 1 minutes
3456 1 6 minutes
5678 1 1 minutes
Not Ready reason code statistics peg as follows, in the ActivityCodeStat view:
Not Ready reason code statistics peg as follows, in the ActivityCodeStat view.
Example 2: Agent goes Not Ready, and does not enter Not Reason
code.
For this example, the following events occur (NR timeout configured at 20
seconds).
Not Ready reason code statistics peg as follows, in the ActivityCodeStat view.
Scenario
All agent state timers are maintained independently. For example, the following
events occur.
9:00:20 The agent places the DN call on hold and answers a Contact
Center Manager call.
9:01:20 The agent releases the Contact Center Manager call and resumes
the DN call.
LoggedInTime 90 seconds
WaitingTime 10 seconds
TalkTime 60 seconds
The total activity time for the agent, as calculated in the following example,
exceeds the agent logon time of 90 seconds.
Pegging of ACD-DNs
By default, statistics for ACD-DNs peg against the Default ACD skillset, and
statistics for NACD-DNs peg against the Default NACD skillset. However, you
can map an ACD-DN, using Contact Center Manager Administration. If you
map an ACD-DN, statistics for that ACD-DN peg against that skillset.
Scenario
For this example, an agent who is assigned to the Eng_Service_Sk answers an
ACD and NACD call as follows.
Default ACD 1 0 0 0 0
ACD_DN_ 1 0 0 0 0
Application
Default NACD 1 0 0 0 0
NACD_DN_ 1 0 0 0 0
Application
Eng_Service_Sk 0 5 15 15 1
Totals 2 5 15 15 1
The calls peg against the Default ACD and Default NACD skillsets.
Eng_Service_Sk 2 5 15 15 1
ACD_DN_ 1 0 0 0 0
Application
NACD_DN_ 1 0 0 0 0
Application
Totals 2 5 15 15 1
Scenario
Consider a scenario where the following events occur:
1. A call arrives on DNIS 3111.
2. The Contact Center Manager script routes the call to the voice processing
system.
3. The voice processing system transfers the call to another CDN acquired by
Contact Center Manager Server.
4. The Contact Center Manager script queues the call to a skillset.
5. An agent answers the call.
Statistic Value
CallsOffered 2
CallsAnswered 1
CallsRouted 1
The CallsOffered statistic pegs twice because the DNIS call is offered to Contact
Center Manager two times.
Scenario
1. A call comes into CDN controlled by Contact Center Manager.
2. Contact Center Manager executes a script, which checks whether the
skillset is staffed.
3. The skillset is staffed, so the script queues the call.
4. When an agent becomes available, the call is offered and presented to
Agent 1 (no call forcing).
5. The call rings three times on the agent phoneset, but the agent does not
answer.
6. After 18 seconds (the return to queue timeout as defined in the call
presentation class), the call is returned to the queue.
7. Agent 2 is available and is presented with the call.
8. The call rings for 6 seconds and the agent answers.
Returned to Queue
Agent Presented due to Timeout Answered
Agent 1 1 1 0
Agent 2 1 0 1
Scenario
1. A call arrives at a CDN controlled by Contact Center Manager.
2. The script checks the status of the skillset. The skillset is in night service
mode.
3. The call is routed to a voice mailbox on a third-party voice processing
system.
Pegging
The call statistics peg as follows.
ApplicationStat view 1 1 0
CDNStat view 1 0 1
Scenario
11:01:05 An agent, realizing that the skillset is not staffed, quickly logs on.
The script checks the call condition and determines that it is
released, but the skillset is now staffed. Contact Center Manager
requeues the call to the skillset.
Pegging
The call statistics peg as follows.
Scenario
The following events occur.
11:30:01 The Master script queues the call to the Information_Sk skillset.
11:30:10 The script queues the call to an NACD queue. The switch requests
an agent from the remote switch.
The remote switch responds with the information that all agents
are busy. The call receives RAN treatment.
11:30:17 The local switch routes the call to the remote switch.
CDNStat view
3010 1 1
ApplicationStat view
Master_Script 1 1 1 1
Network_Application
ApplicationStat view
NACD_DN_Application 1 1
AgentPerformanceStat view
11:32:02 The Sales agent determines that the call should be transferred to
the Service group, presses the Transfer button, and dials the
Service CDN (3760). The call enters the Master script, and the
Sales agent hears Ringback for 2 seconds.
11:32:06 The Sales agent finishes the transfer. The Master script restarts for
the call, determines that the call is for the Service CDN, and
executes the Service Application (Service_App). The call receives
Ringback treatment.
3759 1 1
3760 1 1
Master 2 0 0 seconds
Sales_App 1 1 2 seconds
Service_App 1 1 20 seconds
Sales_Skillset 1 1 0 seconds
Service_Skillset 1 1 18 seconds
11:30:02 The call is queued to the Sales skillset (Sales_Skillset) and a Sales
agent answers immediately.
11:32:02 The Sales agent determines that the call should be transferred to
the Service group, presses the Transfer button, and dials the
Service CDN (3760). The call enters the Master script, and the
Sales agent hears Ringback for 6 seconds.
11:32:08 The Master script hands off control to the Service application
(Service_App). The Service application (Service_App) queues the
call to the Service Skillset (Service_Skillset).
11:32:23 The call is presented to a Service agent. The Sales agent releases
the call after talking to Service agent for 3 seconds.
11:32:26 The original caller and the Service agent are connected.
3759 1 1
3760 1 1
Master 2 0 0
Sales_App 1 1 2 seconds
Service_App 1 1 20 seconds
Sales_Skillset 1 1 0 seconds
Service_Skillset 1 1 18 seconds
Scenario
The following events occur.
11:44:12 The script executes a Give IVR command, which gives the caller
the option to leave a voice message. The caller chooses to leave a
message and disconnects.
Pegging
CDNStat 1 1
ApplicationStat 1 1
Scenario
The following events occur.
11:13:04 The Sales application queues the call to the Sales_Sk skillset.
Pegging
ApplicationStat view
Master_Script 1 0 0 seconds
Sales_Application 1 1 14 seconds
CDNStat view
3759 1 0
SkillsetStat view
Sales_Sk 1 0
Backup_Sk 1 1
In this appendix
Pegging agent state 1424
The following table shows how agent state pegs in reports for several different
Incalls and DN key statuses. The table does not distinguish between internal and
external DN calls, which peg separately for the Communication Server 1000/
Meridian 1 PBX switch.
If the agent key status is Agent time pegs against the following states:
Walkaway time
Not ready time
Waiting time
Talk Time
Hold time
Ring time
DN key
Incalls key (see Note 1)
Idle Incoming DN • • •
(see Note 2) call on hold
Idle Outgoing DN • •
call active
Idle Outgoing DN • • •
(see Note 2) call on hold
Idle Incoming DN •
call ringing
If the agent key status is Agent time pegs against the following states:
Walkaway time
Not ready time
Waiting time
Talk Time
Hold time
Ring time
DN key
Incalls key (see Note 1)
If the agent key status is Agent time pegs against the following states:
Walkaway time
Not ready time
Waiting time
Talk Time
Hold time
Ring time
DN key
Incalls key (see Note 1)
If the agent key status is Agent time pegs against the following states:
Walkaway time
Not ready time
Waiting time
Talk Time
Hold time
Ring time
DN key
Incalls key (see Note 1)
Note 1: Not Active for the DN key status means that no DN calls are present.
Note 3:
Busy on Misc. time for Communication Server 1000/Meridian 1 PBX only.
Outgoing DN calls talk time for Communication Server 2x00/DMS only.
Note 4: This does not peg if the active skillset contact is an outbound campaign
contact.
A accelerator key
A key on a phoneset that an agent can use to place a call quickly. When an agent
presses an accelerator key, the system places the call to the configured number
associated with the key. For example, if an agent presses the Emergency key, the
system places a call to the agent’s supervisor.
ACCESS
An internal protocol used by Contact Center Manager Server to directly control
some of the voice services available on the CallPilot or Meridian Mail platform.
access class
A collection of access levels that defines the actions a member of the access
class can perform within the system. For example, a member of the
Administrator access class might be given a collection of Read/Write access
levels.
access level
A level of access or permission given to a particular user for a particular
application or function. For example, a user might be given View Only access to
historical reports.
ACCESS link
A communication channel between Contact Center Manager Server and
CallPilot or Meridian Mail.
ACD call
See automatic call distribution call.
ACD-DN
See automatic call distribution directory number.
ACD group
See automatic call distribution group.
ACD subgroup
See automatic call distribution subgroup.
acquired resource
A resource configured on the switch under the control of Contact Center
Manager Server. Resources must be configured with matching values on both
the switch and Contact Center Manager Server.
activated script
A script that is processing calls or is ready to process calls. Before you can
activate a script, you must first validate it.
active server
In a system with a Replication Server, the server providing call processing and
administration services.
activity code
A number that agents enter on their phoneset during a call. Activity codes
provide a way of tracking the time agents spend on various types of incoming
calls. They are also known as Line of Business (LOB) codes. For example, the
activity code 720 might be used to track sales calls. Agents can then enter 720
on their agent desktop applications during sales calls, and this information can
be generated in an Activity Code report.
adapter
Hardware required to support a particular device. For example, network adapters
provide a port for the network wire. Adapters can be expansion boards or part of
the computer’s main circuitry.
administrator
A user who sets up and maintains Contact Center Manager and Contact Center
Multimedia.
agent
A user who handles inbound and outbound voice calls, e-mail messages, and
Web communications.
agent logon ID
A unique identification number assigned to a particular agent. The agent uses
this number when logging on. The agent ID is not associated with any particular
phoneset.
agent-to-skillset assignment
A matrix that, when you run it, sets the priority of one or more agents for a
skillset. Agent to skillset assignments can be scheduled.
agent-to-supervisor assignment
A matrix that, when you run it, assigns one or more agents to specific
supervisors. Agent to supervisor assignments can be scheduled.
AIP
Advanced I/O Processor
alias
See e-mail alias.
AML
See Application Module Link.
ANI
See automatic Number Identification.
API
See application program interface.
application
1. A logical entity that represents a Contact Center Manager script for reporting
purposes. The Master script and each primary script have an associated
application. The application has the same name as the script it represents. 2. A
program that runs on a computer.
application server
The server on which the Contact Center Manager Administration software is
installed. This server acts as the middle layer that communicates with Contact
Center Manager Server and makes information available to the client PCs.
associated supervisor
A supervisor who is available for an agent if the agent’s reporting supervisor is
unavailable. See also reporting supervisor.
auto-response
A message sent to a customer with no agent interaction. An auto-response can
be an intelligent response, such as a sales promotion flyer, or an
acknowledgement, such as, “We received your e-mail and will respond to you
within three days.”
B basic call
A simple unfeatured call between two 2500 phonesets, on the same switch,
using a four-digit dialing plan.
BBUA
Back-to-Back User Agent
C call age
The amount of time a call waits in the system before being answered by an
agent.
call destination
The site to which an outgoing network call is sent. See also call source.
call intrinsic
A script element that stores call-related information assigned when a call enters
Contact Center Manager Server. See also intrinsic, skillset intrinsic, time
intrinsic, traffic intrinsic.
call priority
The priority given to a request for a skillset agent in a QUEUE TO SKILLSET
or QUEUE TO NETWORK SKILLSET script element. This priority is used
only in queuing a pending request in the pending request queue corresponding to
the required skillsets. This allows pending requests with greater priority in a
skillset to be presented to agents before calls of lesser priority. Call priority has a
range or 1 to 6, with 1 having the greatest priority. Six priorities are used to fully
support the many queuing variations provided by existing NACD functionality.
Call priority is maintained at target nodes for network call requests.
call source
The site from which an incoming network call originates. See also call
destination.
call treatment
A script element that enables you to provide handling to a call while it is waiting
to be answered by a contact center agent. For example, a caller can hear a
recorded announcement or music while waiting for an agent.
call variable
A script variable that applies to a specific call. A call variable follows the call
through the system and is passed from one script to another with the call. See
also global variable, script variable.
CallPilot
A multimedia messaging system you can use to manage many types of
information, including voice messages, fax messages, e-mail messages,
telephone calls (including conferencing), calendars, and directories.
campaign
See outbound campaign.
CAT
Channel Allocation Table
CCR
customer controlled routing
CDN
See controlled directory number.
CLAN
See Customer Local Area Network.
CLAN subnet
See enterprise IP network.
CLID
See Calling Line Identification.
client
The part of Contact Center Manager Server that runs on a personal computer or
workstation and relies on the server to perform some operations. Two types of
client are available: Server Utility and Contact Center Manager Administration.
See also server.
closed reasons
An item configured in Contact Center Multimedia to indicate the result of a
completed e-mail contact. Agents choose a closed reason, and this information
can be generated in a report.
command
A building block used with expressions, variables, and intrinsics to create
scripts. Commands perform distinct functions, such as routing a call to a specific
destination, playing music to a caller, or disconnecting a caller.
CPH
calls per hour
CPU
See central processing unit.
CRM
See Customer Relationship Manager.
CRQS
See Call Request Queue Size.
CSL
Command and Status Link
CTD
See Conditionally Toll Denied.
CTI
See Computer Telephony Integration.
customer administrator
A user who maintains Contact Center Manager.
database views
A logical representation of the database used to organize information in the
database for your use. Event statistics are accessible through database views.
DBMS
Database Management System
deacquire
To release an acquired switch resource from the control of the contact center.
deactivated script
A script that does not process any new calls. If a script is in use when it is
deactivated, calls continue to be processed by the script until they are completed.
default skillset
The skillset to which calls are queued if they are not queued to a skillset or a
specific agent by the end of a script.
denial of service
An incident in which a user or organization is unable to gain access to a resource
that they can normally access.
DEP
See Data Execution Prevention.
Designer Patch
An emergency fix packaged to address specific individual Contact Center
software problems. Designer Patches are viewable from a patch viewer
application. Designer Patches are included in the next scheduled Service Update
or Service Update Supplementary. See also Service Update and Service Update
Supplementary.
desktop user
A configured user who can log on to the Contact Center Manager Server from a
client PC.
destination site
The site to which an outgoing network call is sent. See also source site.
DHCP
See dynamic host configuration protocol.
Dial-Up Networking
See Remote Access Services.
DID
Direct Inward Dial
directory number
The number that identifies a phoneset on a switch. The directory number (DN)
can be a local extension (local DN), a public network telephone number, or an
automatic call distribution directory number (ACD-DN).
display threshold
A threshold used in real-time displays to highlight a value below or above the
normal range.
disposition code
An item configured in Contact Center Multimedia to indicate the result of a
completed outbound contact. Agents choose a disposition code, and this
information can be generated in a report.
DMS
Digital Multiplex Switch
DN
See directory number.
DN call
See directory number call.
DNIS
See Dialed Number Identification Service.
DoS
See denial of service.
DP
See Designer Patch.
DSC
Distant Steering Code
DTMF
Dual Tone Multi Frequency
DVMRP
See Distance Vector Multicast Routing Protocol.
E EBC
See equivalent basic calls.
EIU
Ethernet Interface Unit
ELAN Subnet
See embedded local area network.
e-mail alias
An e-mail address that forwards all e-mail messages it receives to another e-mail
account. For example, the mailbox [email protected] can have the
aliases [email protected] and [email protected]. E-mail
addressed to either of these aliases is forwarded to the [email protected]
mailbox. To route e-mail differently depending on the alias to which it is
addressed, create a recipient mailbox as an alias in the Contact Center
Multimedia Administrator application and then create routing rules based on the
alias.
e-mail rule
Determine how an e-mail contact is routed based on information about the
e-mail message (inputs) and configurations in your contact center (outputs).
Emergency key
A key on an agent’s phoneset that, when pressed by an agent, automatically calls
their supervisor to notify the supervisor of a problem with a caller.
enterprise IP network
Your entire IP network including the ELAN subnet and the Nortel server subnet.
event
1. An occurrence or action on Contact Center Manager, such as the sending or
receiving of a message, the opening or closing of an application, or the reporting
of an error. Some events are for information only, while others can indicate a
problem. Events are categorized by severity: information, minor, major, and
critical. 2. An action generated by a script command, such as queuing a call to a
skillset or playing music.
expression
1. A building block used in scripts to test for conditions, perform calculations, or
compare values within scripts. See also logical expression and mathematical
expression. 2. A category of disk drives that employs two or more drives in
combination for fault tolerance and performance. See also relational expression.
F FCTH
See Flow Control Threshold.
filter timer
The length of time after the system unsuccessfully attempts to route calls to a
destination site before that site is filtered out of a routing table.
firewall
A set of programs that protects the resources of a private network from external
users.
first-level threshold
The value that represents the lowest value of the normal range for a statistic in a
threshold class. The system tracks how often the value for the statistic falls
below this value.
G global settings
Settings that apply to all skillsets or IVR ACD-DNs configured on your system.
global variable
A variable that contains values that can be used by any script on the system. You
can only change the value of a global variable in the Script Variable Properties
sheet. You cannot change it in a script. See also call variable, variable.
GOS
See grade of service.
grade of service
The probability that calls are delayed by more than a certain number of seconds
while waiting for a port.
H HDX
See Host Data Exchange.
HTTP
See Hypertext Transfer Protocol.
I ICM
See Intelligent Call Manager.
IGMP
See Internet Group Management Protocol.
Incalls key
The key on an agent phoneset to which incoming ACD and Contact Center
Manager calls are presented.
intrinsic
A word or phrase used in a script to gain access to system information about
skillsets, agents, time, and call traffic that can then be used in formulas and
decision-making statements. See also call intrinsic, skillset intrinsic, time
intrinsic, traffic intrinsic.
IP address
See Internet Protocol address.
IPML
See Integration Package for Meridian Link.
ISDN
See Integrated Services Digital Network.
IVR
See Interactive Voice Response.
IVR ACD-DN
See Interactive Voice Response ACD-DN.
IVR event
See Interactive Voice Response event.
IVR port
See voice port.
L LAN
See local area network.
LOB code
See activity code.
local call
A call that originates at the local site. See also network call.
local skillset
A skillset that can be used at the local site only. See also network skillset,
skillset.
logical expression
1. A symbol used in scripts to test for different conditions. Logical expressions
are AND, OR, and NOT. See also expression, mathematical expression. 2. A
category of disk drives that employs two or more drives in combination for fault
tolerance and performance. See also relational expression.
M M1
Meridian 1 switch
M1 IE
Meridian 1 Internet Enabled switch
mailbox
See recipient mailbox.
Master script
The first script executed when a call arrives at the Contact Center. A default
Master script is provided with Contact Center Manager, but it can be customized
by an authorized user. It cannot be deactivated or deleted. See also network
script, primary script, script, secondary script.
mathematical expression
1. An expression used in scripts to add, subtract, multiply, and divide values.
Mathematical expressions are addition (+), subtraction (-), division (/), and
multiplication (*). See also expression and logical expression. 2. A category of
disk drives that employs two or more drives in combination for fault tolerance
and performance. See also relational expression.
Meridian Mail
A Nortel product that provides voice messaging and other voice and fax
services.
Meridian MAX
A Nortel product that provides call processing based on ACD routing.
MHT
See mean holding time.
MIB
See Management Information Base.
MLS
See Meridian Link Services.
MM
See Meridian Mail.
MOSPF
See Multicasting Extensions to Open Shortest Path First.
MTBC
See mean time between calls.
Multimedia database
A Caché database used to store customer information and contact details for
outbound, e-mail, and Web communication contacts.
MSL-100
Meridian Stored Logic 100 switch
music route
A resource installed on the switch that provides music to callers while they wait
for an agent.
N NACD call
A call that arrives at the server from a network ACD-DN.
NAT
See Network Address Translation.
NCC
See Network Control Center.
NCRTD
See Network Consolidated Real-Time Display.
network call
A call that originates at another site in the network. See also local call.
network script
The script executed to handle error conditions for Contact Center Manager
Server calls forwarded from one site to another for customers using NSBR. The
network script is a system-defined script provided with Contact Center Manager,
but it can be customized by an authorized user. It cannot be deactivated or
deleted. See also Master script, primary script, script, secondary script.
network skillset
A skillset common to every site on the network. Network skillsets must be
created at the Network Control Center (NCC).
night mode
A skillset state in which the server does not queue incoming calls to the skillset,
and in which all queued calls are given night treatment. A skillset goes into night
mode automatically when the last agent logs off, or the administrator can put it
into night mode manually. See also out-of-service mode, transition mode.
NPA
See Number Plan Area.
NSBR
See Network Skill-Based Routing.
ODBC
See Open Database Connectivity.
OEM
Original equipment manufacturer
Office hours
Hours configured in the contact center where e-mail messages can be routed
using one method when the contact center is open, and another method when the
contact center is closed.
OLE
See object linking and embedding.
OSPF
See Open Shortest Path First.
OTM
See Optivity Telephony Manager.
outbound campaign
A group of outgoing calls from the contact center for a specific purpose, for
example, customer satisfaction surveys.
outbound contact
An outgoing voice call intelligently routed to an agent according to a skillset
within a defined time interval. The call can be dialed by the agent or the switch.
out-of-service mode
A skillset state in which the skillset does not take calls. A skillset is out of
service if no agents are logged on or if the supervisor puts the skillset into out-
of-service mode manually. See also night mode, transition mode.
out-of-service skillset
A skillset not taking any new calls. While a skillset is out of service, incoming
calls cannot be queued to the skillset. See also local skillset, network skillset,
skillset.
P patch
See Designer Patch.
PBX
See private branch exchange.
pegging
The action of incrementing statistical counters to track and report on system
events.
pegging threshold
A threshold used to define a cut-off value for statistics, such as short call and
service level. Pegging thresholds are used in reports.
PEP
Performance Enhancement Package. Now known as Designer Patch. See
Designer Patch.
phoneset
The physical device, connected to the switch, to which calls are presented. Each
agent and supervisor must have a phoneset.
phoneset display
The display area on an agent’s phoneset where information about incoming calls
can be communicated.
PIM
See Protocol Independent Multicast.
Position ID
A unique identifier for a phoneset, used by the switch to route calls to the
phoneset. Referred to as Telephony/Port Address in Contact Center Manager
Server.
primary ACD-DN
A directory number that callers can dial to reach an ACD group.
primary script
A script executed or referenced by the Master script. A primary script can route
calls to skillsets, or it can transfer routing control to a secondary script. See also
Master script, network script, script, secondary script.
priorities
Two sets of priorities affect queuing and call presentation: agent priority per
skillset and call priority. For both sets of priorities, the lower in value of the
number indicates a greater priority in presentation. All idle agent queues and all
pending request queues always queue by priority as its top precedence. All other
queuing options, such as age of call and agent idle time, take a lower precedence
than priority. See also call priority and agent priority per skillset.
PSTN
See public switched telephone network.
R RAID
See Redundant Array of Intelligent/Inexpensive Disks.
RAN
recorded announcement
RAN route
See recorded announcement route.
RAS
See Remote Access Services.
recipient mailbox
A container on the e-mail server that hold e-mail messages. Standard mailboxes
are monitored by the Contact Center E-mail Manager, which routes the e-mail to
an agent or group of agents (skillset) based on an analytical search of the sender
address, the recipient address, the subject and body of an e-mail message for
predetermined keywords, or a combination of these. The e-mail server must be
compliant with Post Office Protocol 3 (POP3) and Standard Mail Transfer
Protocol (SMTP).
redundant server
A warm standby server, used for shadowing the Multimedia database on the
Multimedia server and providing a quick recovery if the primary server fails.
relational expression
An expression used in scripts to test for different conditions. Relational
expressions are less than (<), greater than (>), less than or equal to (< =), greater
than or equal to (> =), and not equal to (< >). See also expression, logical
expression, mathematical expression.
Replication Server
A server that backs up the active Contact Center Manager Server to the standby
Contact Center Manager Server in real time.
reporting supervisor
The supervisor who has primary responsibility for an agent. When an agent
presses the Emergency key on the phoneset, the emergency call is presented to
the agent’s reporting supervisor. See also associated supervisor.
route
A group of trunks. Each trunk carries either incoming or outgoing calls to the
switch. See also music route, RAN route.
router
A device that connects two LANs. Routers can also filter messages and forward
them to different places based on various criteria.
routing table
A table that defines how calls are routed to the sites on the network. See also
round robin routing table, sequential routing table.
RSM
See Real-time Statistics Multicast.
RSVP
See Resource Reservation Protocol.
rule
See e-mail rule.
S sample script
A script installed with the Contact Center Manager Server client. Sample scripts
are stored as text files in a special folder on the client. The contents of these
scripts can be imported or copied into user scripts to create scripts for typical
contact center scenarios.
SCM
See Service Control Manager.
script
A set of instructions that relates to a particular type of call, caller, or set of
conditions, such as time of day or day of week. See also Master script, network
script, primary script, secondary script.
script variable
See variable.
second-level threshold
The value used in display thresholds that represents the highest value of the
normal range for a given statistic. The system tracks how often the value for the
statistic falls outside this value.
secondary script
Any script (other than a Master, network, or primary script) referenced from a
primary script or any other secondary script. Statistics are not pegged for actions
occurring during a secondary script. See also Master script, network script,
primary script, script.
server
A computer or device on a network that manages network resources. Examples
of servers include file servers, print servers, network servers, and database
servers. Contact Center Manager Server is used to configure the operations of
the contact center. See also client.
server subnet
The subnet to which the Nortel servers, such as Contact Center Manger Server,
Network Control Center, Contact Center Manager Administration, Contact
Center Multimedia, and CallPilot are connected.
service
A process that adheres to a Windows NT structure and requirements. A service
provides system functionality.
service level
The percentage of incoming calls answered within a configured number of
seconds.
Service Update
A Contact Center supplementary software application that enhances the
functionality of previously released software by improving performance, adding
functionality, or correcting a problem discovered since the original release. All
previous Service Updates (SUs) for the release are included in the latest Service
Update. For example, SU02 contains the contents of SU01 as well as the fixes
delivered in SU02. SU03 contains SU01, SU02, and the fixes delivered in SU03.
See also Service Update Supplementary and Designer Patch.
SIP
See Session Initiation Protocol.
SIP Terminal
The SIP Address of the TR87 controlled terminal dedicated to this agent. This is
the phone number that the agent controls, combined with the domain of the
agent in the SIP URI.
SIP URI
The SIP Address for the agent as configured on the target SIP server. The SIP
Address uniquely identifies the agent on the SIP network.
site
1. A system using Contact Center Manager Server that can be accessed using
Server Utility. 2. A system using Contact Center Manager Server and
participating in Network Skill-Based Routing.
skillset
A group of capabilities or knowledge required to answer a specific type of call.
See also local skillset, network skillset.
skillset intrinsic
A script element that inserts information about a skillset in a script. Skillset
intrinsics return values such as skillsets, integers, and agent IDs. These values
are then used in queuing commands. See also call intrinsic, intrinsic, time
intrinsic, and traffic intrinsic.
SL-100
Stored Logic 100 switch
SNMP
See Simple Network Management Protocol.
source site
The site from which an incoming network call originates. See also destination
site.
standby
In skillset assignments, a property that grants an agent membership in a skillset,
but makes the agent inactive for that skillset.
standby server
A server that contains an up-to-date version of the database, for use when the
active server becomes unavailable.
SU
See Service Update.
supervisor
A user who manages a group of agents. See also associated supervisor and
reporting supervisor.
supplementary ACD-DN
A DN associated with a primary DN. Any calls to the supplementary DN are
automatically routed to the primary DN. A supplementary DN can be a toll-free
(1-800) number.
SUS
See Service Update Supplementary.
switch
See telephony switch.
switch resource
A device configured on the switch. For example, a CDN is configured on the
switch and then used as a resource with Contact Center Manager Server. See
also acquired resource.
system-defined scripts
The Master_Script and the Network_Script (if NSBR is enabled). Users can
customize or deactivate these scripts, but they cannot delete them. These scripts
are the first scripts executed for every local or network call arriving at the
contact center.
T TAPI
See Telephony Application Program Interface.
target site
See destination site.
TCP/IP
See Transmission Control Protocol/Internet Protocol.
TDM
See Time-Division Multiplex.
telephony
The science of translating sound into electrical signals, transmitting them, and
then converting them back to sound. The term is used frequently to refer to
computer hardware and software that perform functions traditionally performed
by telephone equipment.
telephony switch
The hardware that processes calls and routes them to their destination.
threshold
A value for a statistic at which system handling of the statistic changes.
threshold class
A set of options that specifies how statistics are treated in reports and real-time
displays. See also display threshold, pegging threshold.
Time-Division Multiplex
A method of transmission in which a signal is separated into multiple segments
at the transmission source, and then reassembled at the receiving end.
time intrinsic
A script element that stores information about system time, including time of
day, day of week, and week of year. See also call intrinsic, intrinsic, skillset
intrinsic, traffic intrinsic.
Token Ring
A PC network protocol developed by IBM. A Token Ring network is a type of
computer network in which all the computers are arranged schematically in a
circle.
traffic intrinsic
An intrinsic that inserts information about system-level traffic in a script. See
also call intrinsic, intrinsic, skillset intrinsic, time intrinsic.
transition mode
A skillset state in which the server presents already queued calls to a skillset.
New calls queued to the skillset are given out-of-service treatment. See also
night mode, out-of-service mode.
treatment
See call treatment.
trunk
A communications link between a PBX and the public central office, or between
PBXs. Various trunk types provide services such as Direct Inward Dialing (DID
trunks), ISDN, and Central Office connectivity.
U user-created script
A script created by an authorized user on the Contact Center Manager system.
Primary and secondary scripts are user created scripts.
user-defined script
A script modified by an authorized user on the Contact Center Manager system.
utility
A program that performs a specific task, usually related to managing system
resources. Operating systems contain a number of utilities for managing disk
drives, printers, and other devices.
V validation
The process of checking a script to ensure that all the syntax and semantics are
correct. A script must be validated before it can be activated.
variable
A placeholder for values calculated within a script, such as CLID. Variables are
defined in the Script Variable Properties sheet and can be used in multiple
scripts to determine treatment and routing of calls entering Contact Center
Manager Server. See also call variable, global variable.
Voice over IP
Voice traffic transmitted in digital format using the IP protocol.
voice port
A connection from a telephony port on the switch to a port on the IVR system.
VPN
See Virtual Private Network.
VXML
See Voice Extensible Markup Language.
W WAN
See wide area network.
Web-on-hold
A set of URLs that a customer sees after requesting a text chat session, and
before the agent connects to the Web Communications contact.
workload scenarios
Sets of configuration values defined for typical patterns of system operations.
Five typical workload scenarios (entry, small, medium, large, and upper end) are
used in the Capacity Assessment Tool for capacity analysis for Contact Center
Manager.
Index
@RCW_ActiveTime, 1384
Symbols @RCW_ActivityCodeNameID, 1334
@begin_date_end_date_interval, 1332 @RCW_ActivityCodeNameIDLabel, 1334
@printed_date_time, 1332 @RCW_ActivityTime, 1334
@RCW_%ACDCallsAnswered, 1343 @RCW_AgentName, 1334, 1336, 1340, 1345
@RCW_%Available, 1343 @RCW_AgentNameID, 1334, 1336, 1340, 1346
@RCW_%Busy, 1343 @RCW_AgentNameIDLabel, 1334, 1336, 1340,
@RCW_%CallsAbandoned, 1358, 1366, 1367, 1346
1375, 1378, 1388 @RCW_AgentSkillsetTime, 1340
@RCW_%CallsAbandonedAfterThreshold, @RCW_AllAgentBusyTime, 1384
1367, 1375 @RCW_AllTrunksBusyTime, 1382
@RCW_%CallsAbandonedBeforeThreshold, @RCW_ApplicationCallsAbandoned, 1359
1367, 1376 @RCW_ApplicationLabel, 1335, 1336, 1359
@RCW_%CallsAnswered, 1336, 1339, 1344, @RCW_ApplicationNameID, 1335, 1337, 1359,
1358, 1366, 1367, 1373, 1376, 1379, 1388 1384
@RCW_%CallsAnsweredAfterThreshold, @RCW_ApplicationNameIDLabel, 1335, 1337,
1358, 1368, 1373, 1376, 1383 1359, 1384
@RCW_%CallsAnsweredBeforeThreshold, @RCW_ApplicationNameOrID, 1335, 1337,
1358, 1368, 1373, 1376, 1383 1360, 1384
@RCW_%CallsGivenDefault, 1358, 1368 @RCW_ApplicationNameOrIDLabel, 1335,
@RCW_%CallsGivenForceBusy, 1358, 1368 1337, 1360, 1384
@RCW_%CallsGivenForceDisconnect, 1359, @RCW_AverageAbandonedDelay, 1369
1368 @RCW_AverageACDCallsTalkTime, 1346
@RCW_%CallsGivenForceOverflow, 1359, @RCW_AverageACDNACDCallsTalkTime,
1368 1346
@RCW_%CallsGivenHostLookup, 1359 @RCW_AverageActivityTime, 1335
@RCW_%CallsGivenRouteTo, 1359, 1368 @RCW_AverageAllTrunksBusyTime, 1382
@RCW_%CallsNetworkedOut, 1368 @RCW_AverageAnsweredDelay, 1369
@RCW_%CallsTerminated, 1366 @RCW_AverageBusyOnDNTime, 1346
@RCW_%LocalCallsAnswered, 1344, 1383 @RCW_AverageCallAbandonedDelayAtDest,
@RCW_%NACDCallsAnswered, 1344 1379
@RCW_%NetCallsAnswered, 1383 @RCW_AverageCallAnsweredDelayAtDest,
@RCW_%NetworkCallsAnswered, 1344 1379
@RCW_%ServiceLevel, 1359, 1369 @RCW_AverageCallsAbandonedDelay, 1360,
@RCW_%ShortCallsAnswered, 1339, 1344 1376, 1388
@RCW_%Usage, 1388 @RCW_AverageCallsAbandonedDelayAtDest,
@RCW_%Work, 1344 1376
@RCW_ACDCallsConferenced, 1345 @RCW_AverageCallsAnsweredDelay, 1360,
@RCW_ACDCallsTalkTime, 1345 1373, 1376, 1384, 1388
@RCW_ACDCallsTransferred, 1345 @RCW_AverageCallsAnsweredDelayAtDest,
@RCW_ACDNACDCallsAnswered, 1345 1376
@RCW_ACDNACDCallsTalkTime, 1345 @RCW_AverageCallsAnsweredPerHour, 1346
Crosstab - Application Performance report, 1112 Network Consolidated Outgoing Calls report,
Crosstab - CDN Statistics report, 1115–1117 1219, 1223, 1231
Crosstab - DNIS Statistics report, 1119–1122 Network Incoming Calls report, 1212
Crosstab - Network Incoming Calls report, Data Set Name, 23
1045–1048 data, types of, 25
Crosstab - Network Outgoing Calls report, 1048– database, 23–27, 601
1051 database aliases, 66
Crosstab - Route Performance report, 1122–1129 creating, 66
Crosstab - Skillset Performance report, 1125– database field conversion functions, 1325
1128 database size, 323
Crosstab - Trunk Performance report, 1129–1132 database variables, 601
Crystal Reports, 787, 1324, 1330 Database View Definitions report, 49–50, 954–
cumulation of statistics, 170, 346, 520, 588 957
custom reports database views, 24, 596, 746
to support Record format, 96 DateCreated, 617, 635, 640
Customer, 612, 647 DateTimeStamp, 625
CustomerID, 648 daylight savings time, changing to or from, 589
CustomerId, 625 DaysofAgentLogin field, 408
Customers, 660 DaysOfCallByCall field, 408
CustomFields, 607, 634, 647, 656 DaysOfDaily field, 409
customized formulas, adding in Crystal Reports, DaysOfInterval field, 409
94 DaysofIVRPortLogin field, 409
customized reports DaysOfSkillsetState field, 409
skills needed to create, 29 DBName field, 323
See also expert reports DBSize field, 323
dCDNStat view, 275–279, 546–550
dDNISStat view, 280–287, 551–558
D Debugs, 664
Default, 612
dActivityCodeStat, 188–196 Default ACD skillset, 1408
dAgentByApplicationStat view, 197–207 default activity code
dAgentBySkillsetStat view, 208–219 skillset, 188
dAgentPerformanceStat view, 220–248 system, 188
daily view, 787 Default NACD skillset, 1408
daily views, 168, 519 default treatment, 258, 270, 282, 529, 541, 553
DailyEndTime, 635 defining
DailyStartTime, 635 See also adding, creating
dApplicationConStat view, 522–?? defining connection to the Contact Center
dApplicationStat view, 249–274 Manager Server, 41
data extraction period defining connection to the Contact Center
Network Call By Call Statistics report, 1196 Multimedia server, 52
Network Consolidated Application Definition field, 402
Performance report, 1200 delays, abandoned call
Network Consolidated DNIS Statistics report, application consolidated statistics, 524, 526
1206 application statistics, 252, 254, 264, 535
DNIS statistics, 281, 285, 552, 556
F G
Fast Transfer key, 221 Give Busy script command, 258, 282, 530, 553
FaxNumber, 615 Give Controlled Broadcast Announcement
Field field script command, 257, 529
ApplicationThresholdTemplate view, 392 Give IVR script command, 259, 531
NetworkThresholdTemplate view, 432 Give Music script command, 260, 531
RouteThresholdTemplate view, 449 Give Overflow script command, 259, 283, 530,
SkillsetThresholdTemplate view, 415, 475 554
SummaryThresholdTemplate view, 477 Give RAN script command, 260, 532
field types, 146–147, 512–513 GivenName field
FieldID field AccessRights view, 378
RouteThresholdTemplate view, 449 Agent view, 383
SkillsetThresholdTemplate view, 415, 475 Script view, 457
SummaryThresholdTemplate view, 477 Supervisor view, 479
UserThresholdTemplate view, 495 Grouping field, 460
FieldName, 642 GroupName field, 378
FieldName field, 434
FileContents, 622, 629
filter sets, 99
FilterStatus field, 430
H
FirstDayOfWeek field, 409 HeteroNetworking field, 464
FirstEventTimeStamp field, 353, 371 Historical and Real Time Statistics Properties
FirstName, 615 report, 964–974
FlowControlStatus field, 430 historical reports, 784
force busy treatment historical statistics, 25, 165–344, 517–??
ApplicationStat views, 258, 270, 530, 541 collection properties, 404–410
DNISStat views, 282, 553 storage duration for, 26
force disconnect treatment See also event statistics
ApplicationStat views, 259, 270, 530, 542 historical statistics collection report, 964–974
DNISStat views, 283, 554 HistoricalStatCollection view, 404–407
force overflow treatment HistoricalStatDuration view, 408–409
ApplicationStat views, 259, 270, 530, 542 HistoricalStatStorage view, 410
DNISStat views, 283, 554 HistoryFlag, 608
foreign keys, 765 HoldTime field, 240
Format field, 402, 438 HolidayHours, 672
Formula Properties report, 961–963 hook-flash transfer, 125
Formula view, 402–403 host lookup treatment, 259, 531
FormulaID field, 402, 438
formulas
properties, 402–403 I
reports, 961–963
FreeSpace field, 323 iActivityCodeStat, 188–196
FreeText, 618 iAgentByApplicationStat view, 197–207
FullAddress, 613 iAgentBySkillsetStat view, 208–219
iAgentPerformanceStat view, 220–248
iApplicationConStat view, 522–??
W
wActivityCodeStat, 188–196
wAgentByApplicationStat view, 197–207
wAgentBySkillsetStat view, 208–219
wAgentPerformanceStat view, 220–248
WaitingTime field, 246, 291
WalkawayTime field, 247
wApplicationConStat view, 522–??
wApplicationStat view, 249–274
wCDNStat view, 275–279, 546–550
wDNISStat view, 280–287, 551–558
WebCommsMessages, 739
WebCommsSessions, 741
weekly view, 787
weekly views, 169, 520
WeeksOfWeekly field, 409
when caller leaves a message, 1419
Width field, 434
wIVRPortStat view, 288–292
wIVRStat view, 293–297
wNetworkInCallStat view, 300–307, ??–565
wNetworkOutStat view, 308–315, 566–??
wRANMusicRouteStat view, 316–318
WriteAccess field, 379
WriteAgentAccess field, 380
WriteAllAgentAccess field, 380
wRouteStat view, 319–322
wSkillsetStat view, 325–339, 573–586
Occupation: Phone:
Information is subject to change without notice. Nortel Networks reserves the right to make changes
in design or components as progress in engineering and manufacturing may warrant.
The process of transmitting data and call messaging between the Meridian 1 and Contact Center
Manager is proprietary to Nortel Networks. Any other use of the data and the transmission process
is a violation of the user license unless specifically authorized in writing by Nortel Networks prior to
such use. Violations of the license by alternative usage of any portion of this process or the related
hardware constitutes grounds for an immediate termination of the license and Nortel Networks
reserves the right to seek all allowable remedies for such breach.