While reasonable efforts were made to ensure that the information in this
document was complete and accurate at the time of printing, Avaya Inc. can
assume no liability for any errors. Changes and corrections to the information
in this document might be incorporated in future releases.
Documentation disclaimer
Avaya Inc. is not responsible for any modifications, additions, or deletions to
the original published version of this documentation unless such modifications,
additions, or deletions were performed by Avaya. Customer and/or End User
agree to indemnify and hold harmless Avaya, Avaya's agents, servants and
employees against all claims, lawsuits, demands and judgments arising out of,
or in connection with, subsequent modifications, additions or deletions to this
documentation to the extent made by the Customer or End User.
Link disclaimer
Avaya Inc. is not responsible for the contents or reliability of any linked Web
sites referenced elsewhere within this documentation, and Avaya does not
necessarily endorse the products, services, or information described or offered
within them. We cannot guarantee that these links will work all the time and we
have no control over the availability of the linked pages.
Warr ant y
Avaya Inc. provides a limited warranty on this product. Refer to your sales
agreement to establish the terms of the limited warranty. In addition, Avaya’s
standard warranty language, as well as information regarding support for this
product, while under warranty, is available through the Avaya Support Web
site:
http://www.avaya.com/support
License
USE OR INSTALLATION OF THE PRODUCT INDICATES THE END USER'S
ACCEPTANCE OF THE TERMS SET FORTH HEREIN AND THE GENERAL
LI CE N SE TE RMS AVAI LAB LE ON THE AVAYA W EB SIT E
http://support.avaya.com/LicenseInfo/
YOU DO NOT WISH TO BE BOUND BY THESE TERMS, YOU MUST
RETURN THE PRODUCT(S) TO THE POINT OF PURCHASE WITHIN TEN
(10) DAYS OF DELIVERY FOR A REFUND OR CREDIT.
Avaya grants End User a license within the scope of the license types
described below. The applicable number of licenses and units of capacity for
which the license is granted will be one (1), unless a different number of
licenses or units of capacity is specified in the Documentation or other
materials available to End User. "Designated Processor" means a single
stand-alone computing device. "Server" means a Designated Processor that
hosts a software application to be accessed by multiple users. "Software"
means the computer programs in object code, originally licensed by Avaya and
ultimately utilized by End User, whether as stand-alone Products or
pre-installed on Hardware. "Hardware" means the standard hardware
Products, originally sold by Avaya and ultimately utilized by End User.
License type(s)
Designated System(s) License (DS). End User may install and use each
copy of the Software on only one Designated Processor, unless a different
number of Designated Processors is indicated in the Documentation or other
materials available to End User. Avaya may require the Designated
Processor(s) to be identified by type, serial number, feature key, location or
other specific designation, or to be provided by End User to Avaya through
electronic means established by Avaya specifically for this purpose.
Concurrent User License (CU). End User may install and use the Software on
multiple Designated Processors or one or more Servers, so long as only the
licensed number of Units are accessing and using the Software at any given
time. A "Unit" means the unit on which Avaya, at its sole discretion, bases the
pricing of its licenses and can be, without limitation, an agent, port or user, an
e-mail or voice mail account in the name of a person or corporate function
(e.g., webmaster or helpdesk), or a directory entry in the administrative
database utilized by the Product that permits one user to interface with the
Software. Units may be linked to a specific, identified Server.
Copyright
Except where expressly stated otherwise, the Product is protected by copyright
and other laws respecting proprietary rights. Unauthorized reproduction,
transfer, and or use can be a criminal, as well as a civil, offense under the
applicable law.
Third-party components
Certain software programs or portions thereof included in the Product may
contain software distributed under third party agreements ("Third Party
Components"), which may contain terms that expand or limit rights to use
certain portions of the Product ("Third Party Terms"). Information identifying
Third Party Components and the Third Party Terms that apply to them is
available on the Avaya Support Web site:
http://support.avaya.com/ThirdPartyLicense/
("GENERAL LICENSE TERMS"). IF
Preventing toll fraud
"Toll fraud" is the unauthorized use of your telecommunications system by an
unauthorized party (for example, a person who is not a corporate employee,
agent, subcontractor, or is not working on your company's behalf). Be aware
that there can be a risk of toll fraud associated with your system and that, if toll
fraud occurs, it can result in substantial additional charges for your
telecommunications services.
Avaya fraud intervention
If you suspect that you are being victimized by toll fraud and you need technical
assistance or support, call Technical Service Center Toll Fraud Intervention
Hotline at +1-800-643-2353 for the United States and Canada. For additional
support telephone numbers, see the Avaya Support Web site:
http://www.avaya.com/support
Trademarks
Avaya and the Avaya logo are either registered trademarks or trademarks of
Avaya Inc. in the United States of America and/or other jurisdictions.
MultiVantage is a trademark of Avaya Inc.
All other trademarks are the property of their respective owners.
Downloading documents
For the most current versions of documentation, see the Avaya Support Web
site:
http://www.avaya.com/support
Avaya support
Avaya provides a telephone number for you to use to report problems or to ask
questions about your product. The support telephone number
is 1-800-242-2121 in the United States. For additional support telephone
numbers, see the Avaya Support Web site:
Avaya Call Management System (CMS) is an application for businesses and organizations that
use Avaya communication servers to process large volumes of telephone calls using the
Automatic Call Distribution (ACD) feature. Avaya CMS supports solutions for routing and agent
selection, multi-site contact centers, remote agents, reporting, interfaces to other systems,
workforce management, desktop applications, system recovery, and quality monitoring.
Avaya CMS is part of the Operational Effectiveness solution of the Avaya Customer Interaction
Suite.
This section includes the following topics:
●Purpose on page 19
●Intended users on page 19
●Overview on page 20
●Conventions and terminology on page 21
●Reasons for reissue on page 22
●Availability on page 22
●Related documentation on page 23
●Support on page 26
Purpose
The purpose of this document is to provide instructions on administering a contact center
through Avaya CMS Supervisor.
This information product specifically addresses the functionality of CMS.
Intended users
This document is written for:
●Avaya Call Management System (CMS) administrators who have access to all parts of
CMS
AdministrationJuly 200719
Preface
●Split/Skill supervisors with limited access to CMS
Overview
This document includes the following topics:
●Chapter 1: Introduction on page 27
This chapter provides an overview of this document, password information, and
cross-references for Avaya CMS Supervisor usage
●Chapter 2: Configuring Avaya CMS Supervisor on page 37
This chapter describes the Supervisor configuration options
●Chapter 3: Using the Dictionary to name contact center entities on page 49
This chapter describes how to create synonyms in the Dictionary
●Chapter 4: Using reports on page 179
This chapter describes the basic use of the Reports subsystem
●Chapter 5: Scripting CMS operations on page 187
This chapter describes how to script common actions
●Chapter 6: Administering contact center agents on page 201
This chapter describes how to change agent splits/skills, create agent templates, move
extensions between splits, and use agent trace
●Chapter 7: Administering the contact center configuration on page 227
This chapter describes how to add or delete call work codes and split/skill call profiles,
change VDN skill preferences, view trunk group assignments, change VDN call profiles,
and other contact center activities
●Chapter 8: Administering exceptions on page 283
This chapter describes how to define exceptions and run exception reports for agents,
split/skills, trunk groups, VDNs, and vectors
●Chapter 9: Administering user permissions on page 355
This chapter describes how to create users and define, change, or modify associated CMS
permissions
●Chapter 10: Configuring CMS system settings on page 429
This chapter describes how to change the state of CMS, allocate storage space, specify
storage intervals, and other system setup activities
20AdministrationJuly 2007
●Chapter 11: Maintaining CMS on page 487
This chapter describes backups, restores, backup strategies, maintenance reports,
backup volumes, and labeling
●Chapter 12: Using Solaris on page 571
This chapter describes the Sun Microsystems, Inc. Solaris operating system and how to
use it with CMS
●Chapter 13: Using timetables and shortcuts on page 579
This chapter describes how to use timetables and shortcuts to streamline activities
Conventions and terminology
If you see any of the following safety labels in this document, take careful note of the information
presented.
Conventions and terminology
!
CAUTION:
CAUTION:Caution statements call attention to situations that can result in harm to software,
loss of data, or an interruption in service.
!
!
WARNING:
WARNING:Warning statements call attention to situations that can result in harm to hardware
or equipment.
!
!
DANGER
DANGER:Danger statements call attention to situations that can result in harm to personnel.
!
!
SECURITY ALERT:
SECURITY ALERT:Security alert statements call attention to situations that can increase the potential
:
for unauthorized use of a telecommunications system.
Note:
Note:In some instances, your communication server and its associated software may
be referred to as "switch". Unless otherwise noted, the term, Communication Manager, includes earlier Avaya communication servers, such as MultiVantage
and DEFINITY®.
AdministrationJuly 2007
21
Preface
Reasons for reissue
This is the first issue of this document.
Availability
Copies of this document are available from one or both of the following sources:
Note:
Note:Although there is no charge to download documents through the Avaya Web site,
documents ordered from the Avaya Publications Center must be purchased.
●The Avaya online support Web site, http://www.avayadocs.com
●The Avaya Publications Center, which you can contact by:
Voice:
+1-207-866-6701
+1-800-457-1764 (Toll-free, U.S. and Canada only)
Fax:
+1-207-626-7269
+1-800-457-1764 (Toll-free, U.S. and Canada only)
Mail:
GlobalWare Solutions
200 Ward Hill Avenue
Haverhill, MA 01835 USA
Attention: Avaya Account Manager
E-mail:
totalware@gwsmail.com
22AdministrationJuly 2007
Related documentation
You might find the following Avaya CMS documentation useful. This section includes the
following topics:
●Change description on page 23
●Administration documents on page 23
●Software documents on page 24
●Hardware documents on page 24
●Call Center documents on page 24
●Avaya CMS upgrade documents on page 25
●Documentation Web sites on page 26
Change description
Related documentation
For information about recent changes made in Avaya CMS, see:
●Avaya Call Management System Release 14 Change Description, 07-601579
Administration documents
For more information about Avaya CMS administration, see:
●Avaya Call Management System Release 14 Administration, 07-601585
●Avaya Call Management System (CMS) Release 14 Database Items and Calculations,
07-601591
●Avaya Call Management System Supervisor Release 14 Reports, 07-601590
●Avaya Call Management System (CMS) Supervisor Release 14 Installation and Getting
Started, 07-601587
●Avaya Call Management System High Availability User Guide, 07-300066
●Avaya Call Management System High Availability Connectivity, Upgrade and
Administration, 07-600957
AdministrationJuly 2007
23
Preface
Software documents
For more information about Avaya CMS software, see:
●Avaya Call Management System Release 14 Software Installation, Maintenance, and
Troubleshooting Guide, 07-601578
●Avaya CMS Open Database Connectivity Version 5.2, 07-601580
●Avaya Call Management System Release 14 LAN Backup User Guide, 07-601589
●Avaya Call Management System Release 14 External Call History Interface, 07-601586
●Avaya CMS Custom Reports, 585-215-822
●Avaya CMS Forecast User Guide, 585-215-825
●Avaya Call Management System (CMS) Supervisor Release 14 Report Designer,
07-601588
●Avaya Business Advocate Reports, 07-601618
Hardware documents
For more information about Avaya CMS hardware, see:
●Avaya Call Management System Sun Netra 210 Computer Hardware Installation,
Maintenance, and Troubleshooting, 07-600963
●Avaya Call Management System Sun Fire V880/V890 Computer Hardware Installation,
Maintenance, and Troubleshooting, 07-600965
●Avaya Call Management System Sun Blade 100/150 Workstation Hardware Installation,
Maintenance, and Troubleshooting, 07-600964
●Avaya Call Management System Terminals, Printers, and Modems, 585-215-874
Call Center documents
For more information about Avaya Call Center documents, see:
●Avaya Call Management System Switch Connections, Administration, and
Troubleshooting, 07-601582
24AdministrationJuly 2007
Avaya CMS upgrade documents
There are several upgrade paths supported with Avaya CMS. There is a document designed to
support each upgrade.
This section includes the following topics:
●Base load upgrades on page 25
●Platform upgrades and data migration on page 25
●Avaya Call Management System Upgrade Express (CUE) on page 25
Base load upgrades
Use a base load upgrade when upgrading CMS to the latest load of the same version (for
example, r14ak.g to r14al.k). A specific set of instructions is included with the upgrade. The
Avaya Call Management System Release 14 Base Load Upgrade document is shipped to the
customer site with the CMS software CD-ROM as part of a Product Correction Notice (PCN).
Related documentation
Platform upgrades and data migration
Use a platform upgrade when upgrading to a new hardware platform (for example, upgrading
from a SPARCserver 5 to a Sun Netra 210). The new hardware platform is shipped from the
Avaya factory with the latest CMS load. Therefore, as part of the upgrade you will have the
latest CMS load (for example, R3V11 to R14).
For more information about platform upgrades and data migration, see:
●Avaya Call Management System Release 14 Platform Upgrade and Data Migration,
07-601581
Avaya Call Management System Upgrade Express (CUE)
Use CUE when CMS is being upgraded from an earlier version (for example, R3V11) to the
latest version (for example, R14).
A specific set of upgrade instructions is included with the upgrade. The Avaya Call Management System Release 14 CMS Upgrade Express (CUE) for Sun Computers document is included on
the CUE software CD-ROM that is shipped to the customer site with the CUE kit.
For information about customer requirements for CUE upgrades, see:
For Avaya product documentation, go to http://www.avayadocs.com. Additional information
about new software or hardware updates will be contained in future issues of this book. New
issues of this book will be placed on the Web site when available.
Use the following Web sites to view related support documentation:
●Information about Avaya products and service
●Sun hardware documentation
Support
Contacting Avaya technical support
Avaya provides support telephone numbers for you to report problems or ask questions about
your product.
For United States support:
1- 800- 242-2121
For international support:
See the 1-800 Support Directory
http://www.avaya.com
http://docs.sun.com
listings on the Avaya Web site.
Escalating a technical support issue
Avaya Global Services Escalation Management provides the means to escalate urgent service
issues. For more information, see the Escalation Management
listings on the Avaya Web site.
26AdministrationJuly 2007
Chapter 1:Introduction
This section provides introductory information on Avaya CMS Supervisor and complementary
products. Basic information regarding the interfaces and usage of Supervisor can be found in
the Avaya CMS Supervisor Installation and Getting Started document.
This section contains the following topics:
●What is Avaya CMS? on page 27
●How Avaya CMS stores ACD data on page 27
●ACD Administration on page 33
What is Avaya CMS?
Avaya CMS is a software product for businesses and organizations that have an Avaya
Communication Manager system and receive a large volume of telephone calls that are
processed through the Automatic Call Distribution (ACD) feature. Avaya CMS collects call-traffic
data, formats management reports, and provides an administrative interface to the ACD feature
on the Communication Manager system.
A CMS administrator accesses the CMS database, generates reports, administers ACD
parameters, and monitors call activities to determine the most efficient service for the calling
customers.
Operating system
Avaya CMS resides on the Sun Microsystems, Inc. Solaris operating system and uses several
Solaris system utilities to communicate with terminals and printers, to log errors, and to execute
processes. CMS utilizes the Informix Software, Inc. INFORMIX database management system,
which provides an interface to the CMS historical database.
How Avaya CMS stores ACD data
There are two ways to describe how Avaya Call Management System (CMS) stores ACD data:
●Logically - How the CMS system organizes data for processing
AdministrationJuly 200727
Chapter 1: Introduction
●Physically - How the CMS system mechanically stores the data on the disk drive
This section includes the following topics:
●How Avaya CMS logically stores ACD data on page 28
●How Avaya CMS physically stores ACD data on page 31
How Avaya CMS logically stores ACD data
The logical storage of the ACD data has more impact on the CMS user than does the physical
storage. The logical data storage controls how a CMS user is able to access and manipulate
ACD data. CMS stores all of the ACD data received from the communication server in the
real-time and historical databases.
Real-time databases
Real-time databases include tables for the current intrahour interval data and the previous
intrahour interval data. The storage interval can be 15, 30, or 60 minutes.
Historical databases
Historical databases include tables for the intrahour, daily, weekly, and monthly data. The
following table shows all of the historical database tables and the maximum amount of time data
can be stored in a particular table:
Historical database tablesMaximum time for data storage
Intrahour historical data62 days
Daily historical data5 years (1825 days)
Weekly historical data10 years (520 weeks)
Monthly historical data10 years (120 months)
Note:
Note:You can use historical data to predict future call traffic and future agent and trunk
requirements. For more information see Avaya CMS Forecast User Guide.
Data summarizing
When CMS collects data from the ACD, the data is stored in the real-time database for the
current interval. At the end of the current interval, the following events occur:
28AdministrationJuly 2007
How Avaya CMS stores ACD data
●The data that was in current interval database table is archived to the previous interval
database table.
●The data that was in previous interval database table is archived in the historical database
as intrahour historical data.
The data remains in the historical database as intrahour historical data for a maximum of 62
days. At your designated data summarizing time, the intrahour historical data is summarized
into daily historical data.
The daily historical data is summarized on a weekly and monthly basis. At the end of your
designated week, the daily historical data is summarized into weekly historical data. On the first
day of a new month, the daily historical data is summarized into monthly historical data for the
previous month.
For more information, see CMS data storage
CMS data storage
The following figure illustrates how CMS stores data.
on page 29.
AdministrationJuly 2007
29
Chapter 1: Introduction
Agent
(cagent)
Agent
(pagent)
The previous
interval data is
archived at the
end of the interval
to the intrahour
historical data
Split
(csplit)
Split
(psplit)
Agent
(hagent)
ACD#
Data
Real-time database
Current interval data
Trunk
(ctrunk)
Trunk
group
(ctkgrp)
Previous interval data
Trunk
(ptrunk)
Trunk
group
(ptkgrp)
Historical database
Intrahour historical data
Split
(hsplit)
Trunk
(htrunk)
Vector
(cvector)
Vector
(pvector)
Trunk
group
(htkgrp)
CMS processorCommunication Server
VDN
(cvdn)
VDN
(pvdn)
Vector
(hvector)
Call
work
codes
(ccwc)
Call
work
codes
(pcwc)
VDN
(hvdn)
The current
interval data is
archived at the
end of the interval
to the previous
interval data
Call
work
codes
(hcwc)
Intrahour data is
summarized into
daily data.
Daily data is
summarized into
weekly data and
monthly data
Weekly data is
summarized at
the end of your
designated week.
Monthly data is
summarized on
the first day of
the month for the
previous month.
Agent
(dagent)
Agent
(wagent)
Agent
(magent)
Split
(dsplit)
Split
(wsplit)
Split
(msplit)
Daily historical data
Trunk
(dtrunk)
Trunk
group
(dtkgrp)
Vector
(dvector)
Weekly historical data
Trunk
(wtrunk)
Trunk
group
(wtkgrp)
Vector
(wvector)
Monthly historical data
Trunk
(mtrunk)
Trunk
group
(mtkgrp)
Vector
(mvector)
VDN
(dvdn)
VDN
(wvdn)
VDN
(mvdn)
Call
work
codes
(dcwc)
Call
work
codes
(wcwc)
Call
work
codes
(mcwc)
30AdministrationJuly 2007
Loading...
+ 604 hidden pages
You need points to download manuals.
1 point = 1 manual.
You can buy points or you can get point for every manual you upload.