Avaya Contact Center Select Solution Description 01.01 June 2014

Avaya Contact Center Select Solution
Description
Release 6.4
Issue 01.01
June 2014
2014 Avaya Inc. applicable number of licenses and units of capacity for which the
license is granted will be one (1), unless a different number of
All Rights Reserved. licenses or units of capacity is specified in the documentation or other
Notice materials available to you. Software means Avayas computer
programs in object code, provided by Avaya or an Avaya Channel
While reasonable efforts have been made to ensure that the Partner, whether as stand-alone products, pre-installed , or remotely
information in this document is complete and accurate at the time of accessed on hardware products, and any upgrades, updates, bug
printing, Avaya assumes no liability for any errors. Avaya reserves fixes, or modified versions thereto. Designated Processor means a
the right to make changes and corrections to the information in this single stand-alone computing device. Server means a Designated
document without the obligation to notify any person or organization Processor that hosts a software application to be accessed by
of such changes. multiple users. Instance means a single copy of the Software
Documentation disclaimer executing at a particular time: (i) on one physical machine; or (ii) on
one deployed software virtual machine (VM) or similar deployment.
Documentation means information published by Avaya in varying
mediums which may include product information, operating License type(s)
instructions and performance specifications that Avaya may generally Concurrent User License (CU). End User may install and use the
make available to users of its products and Hosted Services. Software on multiple Designated Processors or one or more Servers,
Documentation does not include marketing materials. Avaya shall not so long as only the licensed number of Units are accessing and using
be responsible for any modifications, additions, or deletions to the the Software at any given time. A Unit means the unit on which
original published version of documentation unless such Avaya, at its sole discretion, bases the pricing of its licenses and can
modifications, additions, or deletions were performed by Avaya. End be, without limitation, an agent, port or user, an e-mail or voice mail
User agrees to indemnify and hold harmless Avaya, Avaya's agents, account in the name of a person or corporate function (e.g.,
servants and employees against all claims, lawsuits, demands and webmaster or helpdesk), or a directory entry in the administrative
judgments arising out of, or in connection with, subsequent database utilized by the Software that permits one user to interface
modifications, additions or deletions to this documentation, to the with the Software. Units may be linked to a specific, identified Server.
extent made by End User.
Heritage Nortel Software
Link disclaimer
Heritage Nortel Software means the software that was acquired by
Avaya is not responsible for the contents or reliability of any linked Avaya as part of its purchase of the Nortel Enterprise Solutions
websites referenced within this site or documentation provided by Business in December 2009. The Heritage Nortel Software currently
Avaya. Avaya is not responsible for the accuracy of any information, available for license from Avaya is the software contained within the
statement or content provided on these sites and does not list of Heritage Nortel Products located at http://support.avaya.com/
necessarily endorse the products, services, or information described LicenseInfo/ under the link Heritage Nortel Products, or such
or offered within them. Avaya does not guarantee that these links will successor site as designated by Avaya. For Heritage Nortel
work all the time and has no control over the availability of the linked Software, Avaya grants Customer a license to use Heritage Nortel
pages. Software provided hereunder solely to the extent of the authorized
Warranty activation or authorized usage level, solely for the purpose specified
in the Documentation, and solely as embedded in, for execution on,
Avaya provides a limited warranty on Avaya hardware and software. or (in the event the applicable Documentation permits installation on
Refer to your sales agreement to establish the terms of the limited non-Avaya equipment) for communication with Avaya equipment.
warranty. In addition, Avayas standard warranty language, as well as Charges for Heritage Nortel Software may be based on extent of
information regarding support for this product while under warranty is activation or use authorized as specified in an order or invoice.
available to Avaya customers and other parties through the Avaya
Support website: http://support.avaya.com or such successor site as Copyright
designated by Avaya. Please note that if you acquired the product(s) Except where expressly stated otherwise, no use should be made of
from an authorized Avaya Channel Partner outside of the United materials on this site, the Documentation, Software, Hosted Service,
States and Canada, the warranty is provided to you by said Avaya or hardware provided by Avaya. All content on this site, the
Channel Partner and not by Avaya. documentation, Hosted Service, and the Product provided by Avaya
Licenses including the selection, arrangement and design of the content is
owned either by Avaya or its licensors and is protected by copyright
THE SOFTWARE LICENSE TERMS AVAILABLE ON THE AVAYA and other intellectual property laws including the sui generis rights
WEBSITE, HTTP://SUPPORT.AVAYA.COM/LICENSEINFO OR relating to the protection of databases. You may not modify, copy,
SUCH SUCCESSOR SITE AS DESIGNATED BY AVAYA, ARE reproduce, republish, upload, post, transmit or distribute in any way
APPLICABLE TO ANYONE WHO DOWNLOADS, USES AND/OR any content, in whole or in part, including any code and software
INSTALLS AVAYA SOFTWARE, PURCHASED FROM AVAYA INC., unless expressly authorized by Avaya. Unauthorized reproduction,
ANY AVAYA AFFILIATE, OR AN AVAYA CHANNEL PARTNER (AS transmission, dissemination, storage, and or use without the express
APPLICABLE) UNDER A COMMERCIAL AGREEMENT WITH written consent of Avaya can be a criminal, as well as a civil offense
AVAYA OR AN AVAYA CHANNEL PARTNER. UNLESS under the applicable law.
OTHERWISE AGREED TO BY AVAYA IN WRITING, AVAYA DOES
NOT EXTEND THIS LICENSE IF THE SOFTWARE WAS Third Party Components
OBTAINED FROM ANYONE OTHER THAN AVAYA, AN AVAYA Third Party Components mean certain software programs or
AFFILIATE OR AN AVAYA CHANNEL PARTNER; AVAYA portions thereof included in the Software or Hosted Service may
RESERVES THE RIGHT TO TAKE LEGAL ACTION AGAINST YOU contain software (including open source software) distributed under
AND ANYONE ELSE USING OR SELLING THE SOFTWARE third party agreements (Third Party Components), which contain
WITHOUT A LICENSE. BY INSTALLING, DOWNLOADING OR terms regarding the rights to use certain portions of the Software
USING THE SOFTWARE, OR AUTHORIZING OTHERS TO DO SO, (Third Party Terms). As required, information regarding distributed
YOU, ON BEHALF OF YOURSELF AND THE ENTITY FOR WHOM Linux OS source code (for those Products that have distributed Linux
YOU ARE INSTALLING, DOWNLOADING OR USING THE OS source code) and identifying the copyright holders of the Third
SOFTWARE (HEREINAFTER REFERRED TO Party Components and the Third Party Terms that apply is available
INTERCHANGEABLY AS YOU AND END USER), AGREE TO in the Documentation or on Avayas website at: http://
THESE TERMS AND CONDITIONS AND CREATE A BINDING support.avaya.com/Copyright or such successor site as designated
CONTRACT BETWEEN YOU AND AVAYA INC. OR THE by Avaya. You agree to the Third Party Terms for any such Third
APPLICABLE AVAYA AFFILIATE (AVAYA). Party Components
Avaya grants you a license within the scope of the license types Preventing Toll Fraud
described below, with the exception of Heritage Nortel Software, for
which the scope of the license is detailed below. Where the order Toll Fraud is the unauthorized use of your telecommunications
documentation does not expressly identify a license type, the system by an unauthorized party (for example, a person who is not a
applicable license will be a Designated System License. The 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 Toll 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 website: http://support.avaya.com or such
successor site as designated by Avaya. Suspected security
vulnerabilities with Avaya products should be reported to Avaya by
sending mail to: securityalerts@avaya.com.
Downloading Documentation
For the most current versions of Documentation, see the Avaya
Support website: http://support.avaya.com, or such successor site as
designated by Avaya.
Contact Avaya Support
See the Avaya Support website: http://support.avaya.com for Product
or Hosted Service notices and articles, or to report a problem with
your Avaya Product or Hosted Service. For a list of support telephone
numbers and contact addresses, go to the Avaya Support website:
http://support.avaya.com (or such successor site as designated by
Avaya), scroll to the bottom of the page, and select Contact Avaya
Support.
Trademarks
Avaya, the Avaya logo, Avaya one-X Portal, Avaya Aura
Communication Manager, Avaya Aura Experience Portal, Avaya
Aura Orchestration Designer, Avaya Aura Session Manager, Avaya
Aura System Manager, and Application Enablement Services are
either registered trademarks or trademarks of Avaya Inc. in the
United States of America and/or other jurisdictions.
All non-Avaya trademarks are the property of their respective owners.
Linux is the registered trademark of Linus Torvalds in the U.S. and
other countries.
Contents
Chapter 1: Introduction............................................................................................................ 7
Related resources................................................................................................................... 7
Documentation..................................................................................................................7
Viewing Avaya Mentor videos.............................................................................................8
Support.................................................................................................................................. 9
Chapter 2: Solution overview................................................................................................ 10
Licensing.............................................................................................................................. 12
User Data Synchronization ....................................................................................................14
Topology.............................................................................................................................. 14
IP Office supported versions...................................................................................................18
Overview of solution configuration.......................................................................................... 19
Simple voice call flow example............................................................................................... 20
Sample Orchestration Designer voice flow applications............................................................ 22
Multimedia contacts processing..............................................................................................25
Simple email message flow ................................................................................................... 26
Call Recording...................................................................................................................... 27
Limitations............................................................................................................................ 28
Avaya Security Advisories......................................................................................................29
Upgrades and migrations....................................................................................................... 30
Chapter 3: Avaya Contact Center Select DVD......................................................................31
Platform Vendor Independence server specification................................................................. 33
Entry-level server specification......................................................................................... 33
Mid-range server specification.......................................................................................... 34
High-end server specifications..........................................................................................35
Server performance and BIOS settings............................................................................. 38
Avaya Contact Center Select DVD software specification......................................................... 41
Server naming requirements............................................................................................ 42
Microsoft security hotfixes................................................................................................ 42
Operating system updates............................................................................................... 43
Third-party software requirements.................................................................................... 44
Guidelines for the use of antivirus software........................................................................45
Avaya Contact Center Select DVD licensing............................................................................ 47
High-end 8core server specification................................................................................ 48
Chapter 4: Avaya Contact Center Select software appliance.............................................49
Avaya Contact Center Select OVA..........................................................................................51
4 Avaya Contact Center Select Solution Description June 2014

Comments? infodev@avaya.com
Contents

Avaya Media Server OVA...................................................................................................... 57
WebLM OVA.........................................................................................................................59
VMware host server specification............................................................................................59
High-end 8core server specification................................................................................ 60
High-end 10core server specification...............................................................................61
Virtualization considerations...................................................................................................62
VMware features............................................................................................................. 62
VMware vSphere Host considerations...............................................................................63
Server performance and BIOS settings............................................................................. 65
VMware networking best practices....................................................................................68
Avaya Contact Center Select VMware snapshot considerations.......................................... 68
Avaya Media Server VMware snapshot considerations.......................................................69
Guidance for storage requirements................................................................................... 70
Performance monitoring and management........................................................................ 70
Troubleshooting VMware................................................................................................. 71
Software Appliance Licensing.................................................................................................72
Chapter 5: Avaya Contact Center Select hardware appliance............................................74
Hardware Appliance server specification................................................................................. 75
Avaya Contact Center Select hardware appliance software specifications..................................77
Hardware Appliance Licensing............................................................................................... 83
Chapter 6: Solution capacity limits and supported features.............................................. 85
Avaya Contact Center Select maximum capacity limits............................................................. 85
Avaya Contact Center Select maximum configuration limits...................................................... 88
Avaya Contact Center Select supported features..................................................................... 88
Supported Telephony Features.............................................................................................. 94
Supported Telephony Devices..............................................................................................102
Remote access support ...................................................................................................... 104
Communication Control Toolkit supported functionality........................................................... 104
Chapter 7: Administration client computer requirements ............................................... 109
Administrator computer hardware requirements..................................................................... 109
Client operating system requirements................................................................................... 110
Third-party software requirements........................................................................................ 111
Chapter 8: Agent Desktop computer requirements ..........................................................112
Agent Desktop localized languages...................................................................................... 112
Agent Desktop computer hardware requirements...................................................................113
Client operating system requirements................................................................................... 113
Agent Desktop client network infrastructure requirements.......................................................114
June 2014 Avaya Contact Center Select Solution Description 5

Contents
Agent Desktop network ports................................................................................................121

Chapter 9: Avaya Contact Center Select port matrix........................................................ 122
Contact Center Manager Server port requirements................................................................ 122
Contact Center Manager Administration port requirements..................................................... 123
Communication Control Toolkit port requirements.................................................................. 125
Contact Center Multimedia port requirements........................................................................ 125
Avaya Media Server port requirements................................................................................. 127

Chapter 1: Introduction
This document provides a technical description of Avaya Contact Center Select Release 6.4. It
describes the product features, specifications, licensing, and interoperability with other supported
products.
This document is intended for personnel who want to understand how this solution meets customer
requirements.
Related resources
The following are some additional Avaya Contact Center Select related resources.
Documentation
The following table lists some of the documents related to Avaya Contact Center Select. Download
the documents from the Avaya Support website at http://support.avaya.com.
Category Title Description Audience

Overview Avaya Contact Center This document provides a This document is
Select Solution Description technical description of Avaya intended for
Contact Center Select. It personnel who
describes the product features, determine the best
specifications, licensing, and design to meet the
interoperability with other business needs of a
supported products. customer.
Deployment Deploying Avaya Contact This document contains This document is
Center Select DVD information about Avaya intended for
Contact Center Select DVD personnel who
installation, initial deploy, commission,
configuration, and verification. and test the Avaya
This document contains Contact Center Select
information about maintaining DVD.
and troubleshooting the Avaya
Contact Center Select server.

Introduction
Category Title Description Audience

Center Select Software information about Avaya intended for
Appliance Contact Center Select personnel who
Software Appliance (VMware deploy, commission,
OVA) preparation, deployment, and test the Avaya
initial configuration, and Contact Center Select
verification. This document software appliance.
contains information about
maintaining and
troubleshooting the software
appliance.
Center Select Hardware information about Avaya intended for
Appliance Contact Center Select personnel who
Hardware Appliance (physical deploy, commission,
server) installation, initial and test the Avaya
configuration, and verification. Contact Center Select
This document contains hardware appliance.
information about maintaining
and troubleshooting the
hardware appliance.
Administration Administering Avaya This document contains This document is
Contact Center Select information and procedures to intended for
configure the users, skillsets, personnel who
and contact center perform the day-to-
configuration data. This day administration of
document contains information Avaya Contact Center
about creating Avaya Contact Select.
Center Select real-time
displays and historical reports.
Administration Avaya Contact Center This document contains This document is
Select Advanced information about managing intended for
Administration Avaya Contact Center Select personnel who
licensing and multimedia manage Avaya
configuration. Contact Center
Select.
User guide Avaya Contact Center This document contains This document is
Select Agent Desktop Guide information about using Agent intended for Avaya
Desktop. Contact Center Select
Agents and Agent
Supervisors.
Viewing Avaya Mentor videos

Avaya Mentor videos provide technical content on how to install, configure, and troubleshoot Avaya
products.

Support
About this task

Videos are available on the Avaya Support website, listed under the video document type, and on
the Avaya-run channel on YouTube.
Procedure
To find videos on the Avaya Support site, go to http://support.avaya.com and perform one of
the following actions:
In Search, type Avaya Mentor Videos to see a list of the available videos.
In Search, type the product name. On the Search Results page, select Video in the
Content Type column on the left.
To find the Avaya Mentor videos on YouTube, go to http://www.youtube.com/AvayaMentor and
perform one of the following actions:
Enter a key word or key words in the Search Channel to search for a specific product or
topic.
Scroll down Playlists, and click the name of a topic to see the available list of videos posted
on the site.
Note:
Videos are not available for all products.
Support
Visit the Avaya Support website at http://support.avaya.com for the most up-to-date documentation,
product notices, and knowledge articles. You can also search for release notes, downloads, and
resolutions to issues. Use the online service request system to create a service request. Chat with
live agents to get answers to questions, or request an agent to connect you to a support team if an
issue requires additional expertise.

Chapter 2: Solution overview
Avaya Contact Center Select is a context-sensitive, collaborative, voice and multimedia customer
experience solution that allows small to midsize enterprises to anticipate, accelerate, and enhance
customer interactions. Avaya Contact Center Select uses the Avaya IP Office telephone system to
provide a real-time telephony platform. Avaya IP Office is a flexible and scalable phone system
designed specifically for small and midsize enterprises. IP Office supports a wide range of phones
and devices for use in contact centers.
Avaya Contact Center Select uses SIP and CTI interfaces to communicate with the IP Office
platform. This integration gives Avaya Contact Center Select access to and control of a wide range
of IP Office phones and features. Customers integrating Avaya Contact Center Select with the IP
Office platform gain skill-based routing, call treatments, reporting, unified agent management, and
the graphical Orchestration Designer utility. Agent Desktop supports specified IP Office phones and
also supports multimedia contact types.
The following diagram shows a typical contact center solution using voice and multimedia enabled
Avaya Contact Center Select and the Avaya IP Office voice phone system.
Avaya Contact Center Select provides a feature rich voice and multimedia solution with integrated
routing and reporting for the small to midsize enterprises. Avaya Contact Center Select provides
unified contact center and phone system management for agents and supervisors. Voice-enabled
agents and supervisors created in Avaya Contact Center Select are automatically added to the IP

Office platform. Avaya Contact Center Select synchronizes user (agent and supervisor) information
between Avaya Contact Center Select and the IP Office platform.
Avaya Contact Center Select is offered in the following deployment types:
Avaya Contact Center Select DVD; The Avaya Contact Center Select DVD contains the
application software. The Avaya Contact Center Select DVD deployment option supports
Platform Vendor Independence (PVI). The customer supplies the Microsoft Windows 2008
operating system license and server hardware that meets one of the Avaya Contact Center
Select PVI server specifications.
Avaya Contact Center Select software appliance; The Avaya Contact Center Select
software appliance is a set of VMware Open Virtual Appliance (OVA) virtualized servers; an
Avaya Contact Center Select OVA, an Avaya Media Server OVA, and a WebLM OVA. The
customer supplies the VMware resources and operating system licenses for the VMware
guests.
Avaya Contact Center Select hardware appliance; The Avaya Contact Center Select
hardware appliance is a physical server with the application software already loaded and
partially preconfigured. Avaya supplies the server hardware and a license the for the Microsoft
Windows 2008 operating system.
Avaya Contact Center Select supports the following routed contact types:
Voice
Email
Outbound
Web communications (Web chat)
SMS text messages
Fax messages
Scanned documents
Voice mail messages
Avaya Contact Center Select also supports peer-to-peer Instant Messaging. To support the email-
based contact types, you must add an email server to your solution. To support the Web
communications contact type, you must add a Web communications server to your solution.
The Avaya Contact Center Select server is supported only in a workgroup. Do not add the Avaya
Contact Center Select server to a Windows domain.
Avaya Contact Center Select is quick to deploy and offers a feature rich voice and multimedia
solution. Avaya Contact Center Select provides sample configuration data to support rapid
deployment and integration with IP Office. You can modify the sample data to meet your solutions
requirements and add to the data as your solution expands. You can also use the sample data to
learn more about Avaya Contact Center Select. The sample data includes the following data:
Supervisors and agents
Skillsets
Orchestration Designer voice flow applications

Solution overview
Activity codes
CDN (Route Points)
Multiplicity Presentation Classes
Real-time reports
Historical reports
User data synchronization account for IP Office
Avaya Contact Center Select provides a simplified voice prompt management utility. The contact
center supervisor can perform prompt management work without requiring administrator access to
the Avaya Media Server server. Avaya Contact Center Select provides a number of status
monitoring utilities to monitor the integration points with the IP Office platform. Avaya Contact Center
Select also provides an always-on graphical troubleshooting dashboard running on the server.
Licensing
Avaya Contact Center Select supports the following licensed agent packages:
Name Description Notes
Agent licenses Agent licenses determine the number of agents that can log
on to Contact Center.
Licensing is available for the following types of agents:
voice agent
outbound agent
email agent (covering FAX messages, SMS text
messages, voice mail messages, and scanned document
messages)
Web communications agent (or Web chat agent)
Avaya Contact Center Select supports the following licensed features:

Multiplicity Multiplicity is the ability of an agent to handle multiple
concurrent multimedia contacts. At any one time an agent
can be active on a voice and multimedia contact. However,
when one contact is active; the others automatically are on
hold. The maximum number of concurrent multimedia or
non-voice contacts that an agent can be assigned is five.
Web Based If Web Reporting server is enabled, agents and supervisors
Statistics can use Agent Desktop to view real-time reports for call
handling, skillset data, and state information on Agent
Desktop.

Licensing

Remote Agent Remote Agent is a solution that extends a Contact Center to
an agent's preferred environment, allowing them to handle
skillset calls regardless of location. Remote Agent solutions
connect contact center calls to the agent's telephone (home
telephone or mobile), without the agent needing special
hardware.
Outbound Use the Multimedia server and the Outbound Campaign
Management Tool in Contact Center Manager Administration
to create progressive outbound campaigns on which calls
are passed to agents and made from the Contact Center.
If your Avaya Contact Center Select integrates with IP Office Server Edition, then IP Office Server
Edition requires the following licenses:
One Avaya IP Endpoint license for Avaya Contact Center Select integration.
One Server Edition Release 9 license. One license for each node in the Small Community
Network (SCN).
Endpoint licenses either Avaya or Third-Party depending on the IP phones used in your
solution. Provision one license for each endpoint. If your solution uses digital phones only from
an IP Office 500V2 Expansion then you do not require endpoint licenses.
One CTI Pro license.
Voicemail Pro Additional Voicemail Channels, up to a maximum of 350.
Trunk licenses to support the trunks used in your solution.
Voicemail Pro Recording Administrators. One instance on each node of the SCN that the call
are recorded from. If all recording is to be done on the Primary node then one instance is
required. This license enables Contact Recorder.
If your Avaya Contact Center Select integrates with IP Office 500V2 (non-Server Edition), then IP
Office 500V2 requires the following licenses:
One Avaya IP Endpoint license for Avaya Contact Center Select integration.
Advanced Edition license.
Preferred Edition License.
Essential Edition License.
Endpoint licenses either Avaya or Third-Party depending on the IP phones used in your
solution. If your solution uses only digital telephones then you do not require endpoint licenses.
One CTI Pro license.
Voicemail Pro Additional Voicemail Channels.
Trunk licenses to support the trunks used in your solution.
Voicemail Pro Recording Administrators. One instance on each node of the Small Community
Network (SCN) that the calls are recorded from. If all recording is to be done on the Primary

Solution overview
node then one instance is required. This license enables Contact Recorder. Contact Recorder
requires a separate Application Server.
The Avaya Contact Center Select base software bundle provisions one Contact Recorder system
license plus 30 Voicemail Pro ports for Call Recording.
An Avaya Contact Center Select voice agent license provisions one Voicemail Pro port for Call
Recording.
Avaya Contact Center Select uses Avaya WebLM as the license provider. Each Avaya WebLM
instance supports a single Avaya Contact Center Select.
User Data Synchronization

Avaya Contact Center Select provides unified administration for contact center agents and IP Office
users. The users (agents and supervisors) that you configure in Avaya Contact Center Select are
automatically mirrored to the connected IP Office.
When you create an agent in Avaya Contact Center Select, a local Windows user account is created
on the Avaya Contact Center Select server, and a matching user account is created in IP Office.
When you modify agent details in Avaya Contact Center Select, the corresponding IP Office user
details are automatically updated. If you delete an agent in Avaya Contact Center Select, the
corresponding IP Office user is not deleted.
The data synchronization mechanism works in one direction; from Avaya Contact Center Select to
IP Office. The Avaya Contact Center Select administrator can manually force a data synchronization
from Avaya Contact Center Select.
Topology
In a contact center solution using Avaya Contact Center Select and an IP Office telephone system,
the following network and connectivity topology considerations apply.
Avaya Contact Center Select (ACCS) supports the following deployment options:
Avaya Contact Center Select DVD
Avaya Contact Center Select Software Appliance
Avaya Contact Center Select Hardware Appliance

Topology
Figure 1: Typical Avaya Contact Center Select DVD deployment

Solution overview
Figure 2: Typical Avaya Contact Center Select software appliance solution

Topology
Figure 3: Typical Avaya Contact Center Select hardware appliance solution
The following connectivity and network layout conditions apply to all Avaya Contact Center Select
solutions:
The Avaya Contact Center Select server exists in a workgroup. Do not add the Avaya Contact
Center Select server to a Windows domain.
Each Avaya Contact Center Select connects to a single IP Office Server Edition Primary
server. Avaya Contact Center Select does not support connecting to an IP Office Secondary
server. Alternatively, each Avaya Contact Center Select can connect to a single IP Office
500V2 Standard Mode with an Advanced Edition license.
A Small Community Network (SCN) is a system of networked IP Office telephone systems that
can, among other features, share extension numbers and user names. Each IP Office SCN
supports a single connected Avaya Contact Center Select. Avaya Contact Center Select
connects to the IP Office Server Edition Primary server of the SCN.
To support an IP Office SCN, Avaya Contact Center Select must connect to an IP Office Server
Edition Primary server in that SCN network.
To support the email-based multimedia contact types, you must install and commission an
email server in your solution.
To support the Web Communications (Web chat) contact type, you must install and
commission a Web chat server in your solution.
Each Avaya WebLM instance supports a single Avaya Contact Center Select.
Each Avaya Media Server instance supports a single Avaya Contact Center Select.

Solution overview
A single instance of Contact Center Manager Administration (CCMA) can manage only a single
Avaya Contact Center Select.
The Avaya Contact Center Select server and the connected IP Office telephone system must
be located in the same campus location.
If you are using the Avaya Contact Center Select Software Appliance, the Avaya Contact
Center Select virtual machine, the WebLM virtual machine, and the Avaya Media Server virtual
machine must all be hosted on VMware servers located at the same campus location. The
Avaya Contact Center Select Software Appliance supports hosting the Avaya Contact Center
Select virtual machine, the WebLM virtual machine, and the Avaya Media Server virtual
machine on one VMware host server. The Avaya Contact Center Select virtual machine host
server and the connected IP Office telephone system must be located at the same campus
location.
Each Supervisor client computer communicates with the Avaya Contact Center Select server.
Each Agent Supervisor client computer has Agent Desktop software and Microsoft Internet
Explorer installed on it. The Supervisor uses Internet Explorer to access the Contact Center
Manager Administration Web client. The Supervisor uses Contact Center Manager
Administration to perform basic agent configuration and to run reports. The Agent Supervisor
uses Agent Desktop software to handle customer calls, to accept emergency or supervisor
calls from agents and to observe calls or Web communication contacts. Each Supervisor
computer with Agent Desktop requires an associated IP Office telephone.
Each Agent client computer communicates with the Avaya Contact Center Select server. Each
Agent computer has Agent Desktop software and Microsoft Internet Explorer installed on it.
The Agent uses Internet Explorer to download the Agent Desktop client software. The Agent
uses Agent Desktop software to handle customer calls. Each Agent computer requires an
associated IP Office telephone.
Multicast or Unicast must be enabled on the underlying data network between the clients and
the Avaya Contact Center Select server for supervisor and agents.
IP Office supported versions

Each Avaya Contact Center Select connects to a single IP Office Server Edition Primary server.
Avaya Contact Center Select does not support connecting to an IP Office Secondary server. A
Small Community Network (SCN) is a system of networked IP Office telephone systems that can
share extension numbers and user names. Each IP Office SCN supports a single connected Avaya
Contact Center Select. The Avaya Contact Center Select server and the connected IP Office server
must be located at the same campus location.
To support an IP Office SCN, Avaya Contact Center Select must connect to an IP Office Server
Edition Primary server in that SCN network.
Avaya Contact Center Select supports only the following versions of IP Office:
IP Office Server Edition Release 9.0.3
IP Office 500V2, Release 9.0.3 software, Standard Mode, Advanced Edition license

Overview of solution configuration
Avaya Contact Center Select does not support other versions of IP Office.
Avaya Contact Center Select does not support IP Office 500V2 Basic mode.
Overview of solution configuration

This section provides an overview of how to install and commission an Avaya Contact Center Select
and IP Office platform-based solution. By describing the commissioning steps, this section also
describes how Avaya Contact Center Select integrates with IP Office.
Avaya Contact Center Select uses the IP Office TAPID interface and SIP open standards to
integrate with the IP Office platform. Avaya Contact Center Select uses the IP Office TAPID
interface to monitor and control the agent endpoints of the IP Office platform. The IP Office TAPID
interface gives Avaya Contact Center Select CTI call control of the IP Office users and extensions
representing Avaya Contact Center Select agents. Avaya Contact Center Select uses a SIP User
Extension Number to register and integrate with IP Office. This gives Avaya Contact Center Select
SIP session management of the IP Office voice calls.
IP Office configuration for Avaya Contact Center Select
Configure IP Office to support integration with Avaya Contact Center Select. This configuration
overview does not include IP Office basic configuration for system settings, licensing, or networking.
Using the IP Office Manager:
1. Configure the Avaya Contact Center Select Service User account details. On the System >
ACCS tab, configure the CCMA Address, CCMA Username, and CCMA Password.
2. Configure the System Voice over IP (VoIP) Domain Name. The Avaya Contact Center Select
server uses this domain name for treatments and contact routing.
3. Add a user with the following specifications. Avaya Contact Center Select uses this SIP User
Extension Number to register with IP Office:
a. Device type set to All Other Phone Types.
b. Extension type set to SIP Extension. For example, 6000.
c. A numerical Base Extension number.
d. On the User, enable Call Waiting On.
e. On the User > Telephony > Supervisor Settings tab, configure the Login Code.
4. Configure an IP Office solution short code to map a telephone number to the Avaya Contact
Center Select SIP User Extension Number. For example, create a short code 6000|>>3000.
All customer calls to telephone number 3000 are forwarded to 6000 and routed to Avaya
Contact Center Select. If 3000 is configured as a CDN (Route Point), Avaya Contact Center
Select treats the customer call and routes it to a contact center agent.
5. Add a H.323 or SIP extension for each Avaya Contact Center Select agent. Avaya Contact
Center Select agents use these IP Office extensions to handle voice contacts.

Solution overview
Avaya Contact Center Select installation

During deployment, configure Avaya Contact Center Select to connect to IP Office.
Using the Avaya Contact Center Select Ignition Wizard (configuration utility):
1. Configure the IP Office platform details.
2. Configure the Service User account details.
3. Configure the Domain Name to match the IP Office VoIP domain name.
4. Configure a CDN (Route Point) number to match the Code number used by the IP Office
short code.
5. Configure the SIP User Extension Number to match the above IP Office user with a SIP
extension.
6. Configure the Avaya Contact Center Select server details, licensing, and optional multimedia
settings.
7. Start Avaya Contact Center Select.
At start up, Avaya Contact Center Select uses the SIP User Extension Number details to register
itself as a SIP device with IP Office. This registration permits the following functionality:
Incoming calls destined for an Avaya Contact Center Select Route Point are delivered to the
Avaya Contact Center Select server.
Authorizes the Avaya Contact Center Select server to send outgoing SIP calls to IP Office (for
agent routing of Avaya Contact Center Select calls).
Enables Avaya Contact Center Select specific functionality on the IP Office platform.
Continue to commission Avaya Contact Center Select by adding option features as appropriate.
Install Agent Desktop software on all agent computers. Continue to maintain Avaya Contact Center
Select by making frequent data backups.
Simple voice call flow example

The following example shows how a customer call to IP Office is treated by Avaya Contact Center
Select and then routed to an agent. By describing a sample call flow, this section also describes
how Avaya Contact Center Select integrates with IP Office.
The following diagram shows the communication links between Avaya Contact Center Select and IP
Office.

Simple voice call flow example
1. A Customer dials a number and the call arrives at an IP Office platform. For example, the
customer dials 3000.
2. An IP Office short code (for example, 6000|>>3000) reroutes the customer call to Avaya
Contact Center Select.
3. IP Office sends a SIP INVITE message to Avaya Contact Center Select.
4. When the SIP INVITE message arrives at Avaya Contact Center Select, it matches the call
to one of its configured Route Point URIs and then anchors the customer call on an Avaya
Media Server conference port.
5. The Avaya Media Server establishes a Real-Time Transport Protocol (RTP) media and voice
path with the customer. Avaya Contact Center Select treats the customers call using this
conference port for the remainder of the call lifetime.
6. When Avaya Contact Center Select has identified a suitable available agent to handle this
call, it sends a SIP INVITE message to IP Office. When the SIP INVITE message arrives at
IP Office, it is sent to the destination agent H.323 desk phone.
7. IP Office sends a H.323 request to the agent desk phone to indicate that a new customer call
has arrived. The agent phone rings and IP Office sends a SIP 180 Ringing message (and a
corresponding TAPID Offering CTI message) back to Avaya Contact Center Select. Avaya
Contact Center Select uses this trigger to inform the Agent Desktop that a call is alerting on
the desk phone. In this way, both the agent desk phone and the Agent Desktop software
client show the customer call as ringing.
8. When the agent answers the customer call using Agent Desktop software, Avaya Contact
Center Select sends a TAPID AnswerCall request to IP Office. This causes the agent desk

Solution overview
phone to go off hook and answer the call. IP Office sends a SIP 200 OK message (and
corresponding TAPID Connected CTI message) to Avaya Contact Center Select. Avaya
Contact Center Select uses CTI to notify Agent Desktop that the customer call has been
answered.
9. When the call is answered, Real-Time Transport Protocol (RTP) is sent from the agent desk
phone to Avaya Media Server. Avaya Media Server conferences the agent and the
customer, the customer and the agent can now communicate. The agent has answered the
customers phone call.
10. The call remains active until the customer or the agent releases the call.
Sample Orchestration Designer voice flow applications

Avaya Contact Center Select provides a number of sample Orchestration Designer flow applications
that treat and route customer voice contacts. Orchestration Designer flow applications contain
instructions that determine the sequence of steps that a contact follows after the contact arrives at
Avaya Contact Center Select. These steps can include call treatments (such as music or ringback),
call routing (such as skill-based routing), or interaction with the caller (entering account numbers).
Applications perform two major functions: they define the path a contact follows, and they provide
treatments to a contact as the contact moves through Contact Center. You can also use the
applications to track and record information about each step in the progress of a contact, and use
this information to analyze how your contact center functions to improve service. Orchestration
Designer flow applications are stored in an Avaya Contact Center Select database. Task Flow
Executor, a component and service of Avaya Contact Center Select, runs the flow applications to
treat customer contacts. A contact is not always answered immediately by an agent. You can
provide treatments to the voice contacts while they wait in a queue. These treatments can tell callers
the estimated amount of time before their call is answered, or play music to callers while they wait in
queue. Additionally, you can use time of day, day of week, or contact center activity to determine
how a contact is handled.
Avaya Contact Center Select provides a number of sample voice Orchestration Designer flow
applications:
Customer Service. This is the main application. It welcomes the customer to the contact center,
performs some basic boundary checking, and plays a menu offering the customer a small
selection of options (talk to the help desk, talk to support, enter your PIN, or leave a message).
Voice_Skill1. This application forwards customer calls to voice skillset Skill1.
Voice_Skill2. This application forwards customer calls to voice skillset Skill2.
Collect_Digits. This application asks the customer to enter their PIN number using the digits on
their phone. The application then plays the number back to the customer and asks them to
confirm the PIN number.
Avaya Contact Center Select also provides a number of sample multimedia Orchestration Designer
flow applications for the supported multimedia contact types.

Sample Orchestration Designer voice flow applications
The following diagram shows how customer voice contacts to Avaya Contact Center Select are
routed and treated by the sample Orchestration Designer flow applications.
Sample Voice Prompt variables

The following table shows the audio media files used by the sample Orchestration Designer flow
applications. Orchestration Designer uses these audio .WAV files to play messages (prompts) to the
customer. The table shows which Orchestration Designer flow application uses each media file. The
table also provides a transcript of the audio in each media file.
Prompt name Prompt variable name Prompt transcript Orchestration Designer
in Orchestration flow using this prompt
Designer
Welcome_CS Welcome_CS Welcome to the Contact Customer_Service
Center.
Menu_Selection_CS Menu_Selection_CS Press 1 to speak to an Customer_Service
agent at the help desk.
Press 2 to speak to an
agent in the support
center.
Press 3 to Enter your
Pin Number or any 8
Digits of your choosing.
Press 4 to leave a
voice mail.
Press * to repeat this
menu.

Solution overview

Designer
Voicemail_CS Voicemail_CS Please wait while we Customer_Service
direct you to our voice
messaging system
mailbox.
EnterDigits_CD EnterDigits_CD Please enter your pin Collect_Digits
number or digits up to a
maximum of 8 digits
followed by the # key.
ConfirmDigits_CD ConfirmDigits_CD The digits you entered Collect_Digits
were ...
ValidateDigits_CD ValidateDigits_CD If that is correct press 1 Collect_Digits
followed by the # key or
press 2 if you wish to
retry followed by the #
key.
InvalidEntry_CS InvalidEntry_CS That is an invalid entry Customer_Service
please try again.
NoData_Entry_CS NoData_Entry_CS You have not entered Customer_Service
any data Please try
again.
Emergency_CS Emergency_CS The contact center is Customer_Service
now in emergency mode
and closed. We will
reopen shortly.
OutOfHours_CS OutOfHours_CS The contact center is Customer_Service
now closed as it is out of
hours.
Holidays_CS Holidays_CS The contact center is Customer_Service
now closed for holidays.
OutOfService_CS OutOfService_CS All departments are out Customer_Service
of service at this time.
Please call back at a
later time.
PromptSubmenu_CS PromptSubmenu_CS Press 0 to speak to an Customer_Service
agent, Press 1 to leave a submenu 1 and 2
voice mail, press, Press
9 to return to the main
menu.
FirstRAN_CD FirstRAN_CD This is the first Collect_Digits Queuing
announcement. Please Tab
wait while we try to
connect you to our
agents.

Multimedia contacts processing

Designer
SecondRAN_CD SecondRAN_CD This is the second Collect_Digits Iterate
announcement. All our Queue Tab
agents are still busy
please wait.
You can modify these media files and replace them with your own recordings. You can record your
own voice prompts for the customer, or record voice prompts suitable for your locale (language and
dialect). Avaya Contact Center Select provides optimum playback performance with .WAV files
encoded as Linear 16-bit PCM, 8KHz Mono with a sampling rate of 128kbits/sec.
Multimedia contacts processing

Avaya Contact Center Select receives multimedia contacts through two external interface points: the
email server and the External Web server.
Email server contacts
Email server contacts are retrieved from a POP3 or IMAP capable email server using the Inbound
Message Handler (IMH). The IMH runs at regular intervals. You can configure the settings for the
IMH (such as the time between intervals and the number of email retrieved from each mailbox
during each run) using Contact Center Manager Administration.
The IMH logs on to the mailboxes on the email server as listed in the Email Manager. It parses
email in the mailboxes and stores them in the Contact Center Multimedia database. Any
attachments associated with an email are stored in the Inbound attachment folder, as specified in
Contact Center Manager Administration. After an email is successfully stored in the Contact Center
Multimedia database, it is deleted from the email server.
The IMH passes a received email to the Contact Center Multimedia rules engine, which applies
rules relevant to the email based on the To address, and invokes the Outbound Message Handler
(OMH) to send automatic responses, if any.
External Web server transactions
Contact Center Multimedia receives contacts from the External Web server through the Contact
Center Multimedia Web services. The Web services provide a Java API. This enables contacts to be
written into the Contact Center Multimedia database, retrieved from the database, and have their
status queried.
Contacts received through the Web services do not pass through the Rules Engine. The External
Web server determines the skillset and priority assigned to the contact.
A set of sample pages is distributed with Contact Center Multimedia to provide Java Server Pages
(JSP) script examples of how a Web server can access the Web services. You must create your
own Web pages, with customized look, feel, and business logic.

Solution overview
Simple email message flow

Avaya Contact Center Select provides routed contact support for email messages. Customers send
email messages requesting information or support to a published email address. Avaya Contact
Center Select connects to the hosting email server and scans this mailbox (published email
address) at regular intervals. Avaya Contact Center Select retrieves the customer's email messages
from the email server, processes them (by keywords), and stores them in the database. Avaya
Contact Center Select then generates a multimedia (email) contact for each email stored in the
database, and routes it to an appropriate and available agent.
The following diagram shows how Avaya Contact Center Select retrieves customer email messages
and routes the messages as multimedia contacts to contact center agents.
When you install Avaya Contact Center Select, you configure the email server and a default
recipient mailbox. The default settings ensure email messages go only to an agent with the ability to
handle email messages. You can customize your contact center with additional skillsets, rule groups
and email servers.
To further enhance your customer service, you can configure routing rules to use in rule groups.
Use keyword groups and sender groups to decide how to route contacts. Configure which skillset
and priority the email contact is assigned to based on the input for routing contacts. Use automatic
suggestions for the agent to reply quickly to an email or automatic responses to send a reply to the
customer without agent interaction. You can close the contact immediately after the automatic
response.
Avaya Contact Center Select supports Email Open Interfaces. You can develop a custom Web
service that the Avaya Contact Center Select Email Manager can call when an email message is
processed. The custom Web service can perform custom tasks such as manipulating the originating
email and modifying the rule routing options.
For more information about configuring Avaya Contact Center Select email contacts and enhancing
the customer experience, see Avaya Contact Center Select Advanced Administration.

Call Recording
Call Recording
Avaya Contact Center Select supports IP Office Call Recording. IP Office Call Recording provides
regulatory type recording, including the option to pause automatic recording for Payment Card
Industry (PCI) security compliance. Avaya Contact Center Select supports the Call Recording pause
and resume feature when it is initiated from a physical phone set. By default, Avaya Contact Center
Select agents have both inbound and outbound call recording enabled.
IP Office Call Recording has two main components:
Voicemail Pro Voice Recording Library (VRL) records the inbound and outbound agent calls.
IP Office Contact Recorder stores the recorded calls and associated meta data.
The recorded calls are stored in industry standard .WAV files. When each call is completed, Contact
Recorder compresses the audio .wav file and updates the database with a record of the call. These
files are stored in a hierarchy of folders on the IP Office server. Each recording results in a .wav file
and the associated metadata stored in an XML file:
Each .wav file contains the actual audio of the recording. Use the Contact Recorder Search
and Replay application to locate and playback these recordings.
Each .xml file contains metadata about the associated .wav recording file. The following are
some examples of call recording metadata parameters:
- Original CLI (P-Asserted-Identity)
- Agent name
- Skillset
- Agent number
- conference parties
- start time of the recorded call
- end time of the recorded call
IP Office Call Recording is a licensed feature. Recordings consume Voicemail Pro channel licenses.
Pause Recording when on Hold: If an Avaya Contact Center Select call is being recorded and the
agent puts the call on hold, IP Office Call Recording puts the recording in a suspended state (not
terminated), adds a short beep to the recording, and when the call is retrieved from hold the
recording is resumed. This entire call is stored in a single .wav file.
User Pause recording: If an Avaya Contact Center Select call is being recorded, and if the agent
needs to collect payment card details from a customer, the agent can pause the recording to comply
with Payment Card Industry (PCI) requirements. IP Office Call Recording puts the recording in a
suspended state (not terminated) and adds a short beep to the recording. After collecting the
payment card details, the agent resumes call recording. This entire call is recorded and stored in a
single .wav file.
The Agent Desktop user interface does not have a pause button. Agents and agent supervisors
must use their physical phone to pause and resume voice contact recording.

Solution overview
Limitations
The following are some of the limitations of Avaya Contact Center Select (ACCS) solutions:
In the event of an IP Office outage, Avaya Contact Center Select remains active and continues
to attempt to reconnect with the IP Office server until it is brought back into service.
ACCS registers with IP Office as a SIP User. ACCS must refresh this active registration
repeatedly every 180 seconds to prevent the registration expiring. If ACCS fails to refresh the
registration, IP Office begins to terminate all active ACCS calls.
- In the event of an ACCS service or network outage of less than 180 seconds, SIP
registration with IP Office might expire and active ACCS calls might begin to terminate.
- In the event of an ACCS service or network outage of greater than 180 seconds, SIP
registration with IP Office expires and IP Office begins to terminate all active ACCS calls.
If an ACCS agent is directly part of an IP Office conference call and the agent invokes hold on
this call, music-on-hold is not streamed by IP Office even if the number of parties on this
conference drops to two. Agents can identify whether they are part of this scenario by checking
their phone set display for the Conference keyword.
For CDN to CDN conference, join, barge-in, or emergency call scenarios, if an IP Office
softphone agent is a party on this multi-party conference call and invokes hold, music-on-hold
might be played into the active multi-party audio stream for a short period of approximately 500
milliseconds before being terminated.
If a customer dials an agent and this first agent then initiates a consultation with a second
agent, the second agents phone displays the customers phone number while the consultation
call is ringing. After the second agent answers the consultation call, their phone then displays
the phone number of the first agent. This is how IP Office processes consultations.
Call Intrude: The IP Office Call Intrude feature permits an agent to join or barge-in on another
agents call. ACCS implements Call Intrude as a Join conference. The intruded agents call is
briefly placed on-hold to allow the conference to complete. The intruded party might notice the
Held state change and consult call leg appear briefly as the operation completes. Hold music
might be played briefly to the Intruded party call.
Manual transfer from softphone: A transfer completed manually on the IP Office softphone
appears to Agent Desktop as a Join transfer where a Join is carried out on the main and
consult calls with the transferring party then dropped from the call.
IP Office supports third-party integrations using the IP Office TAPI interface. These third-party
integrations can potentially interfere with the operation of Avaya Contact Center Select. You
must configure, implement, and monitor third-party integrations to avoid interfering with Avaya
Contact Center Select. Third-party applications implementing the IP Office TAPID interface are
not supported for controlling Agent devices.
Not all features invoked on the physical phoneset are reflected in Agent Desktop. The following
scenarios are some examples of this:
- Paging: Agents receiving an incoming Page call cannot answer this call using Agent
Desktop. A Page call can be answered only on the users phone. A Page call which is
alerting on a users phone is displayed in Agent Desktop as a connected call. Agent Desktop

Avaya Security Advisories
displays this call as connected if the user answers the Page. Agent Desktop drops this Page
call if another user answers the Page.
- Hold Reminder: If a call remains in the Held state longer than the IP Office system wide Hold
Timeout configuration setting, then a Hold Reminder notification is displayed on the users
phone. A Hold Reminder notification can be an audio or visual notification. Agent Desktop
does not support Hold Reminder notifications; in Agent Desktop the call remains in the Held
state. Agents can use Agent Desktop to unhold the held call.
When an ACCS agent logs on to an IP Office softphone, there is a short delay before the agent
can use Agent Desktop software to control that softphone. This short delay can be up to 12
seconds long. Agents using an IP Office softphone are unable to answer incoming calls in
Agent Desktop immediately after connecting the softphone to IP Office. However agents can
answer these calls on their softphone. This limitation applies only to calls routed to the user in
the immediate period after logging on to their softphone. If an agent attempts to answer a call
in Agent Desktop during the short timeframe where answer is unavailable an error message is
displayed in Agent Desktop. After the answer feature is available any subsequent attempts to
answer a call in Agent Desktop are successful. But there is a limitation in that there is no
notification in Agent Desktop that the Answer feature is now available.
When an agent makes an outbound call using Agent Desktop, the Agent Desktop Hold button
is immediately available. However, until the remote party answers the call and is connected,
any attempt to Hold the call in Agent Desktop results in an error message being displayed.
Avaya Contact Center Select does not support agent operation from the telephone only. This is
commonly referred to as Telephone Mode only support. All Avaya Contact Center Select
agents must use Agent Desktop for agent functionality.
Avaya Security Advisories

Avaya Security Advisories are posted on the Avaya Security Support web site at https://
support.avaya.com/security. From the Avaya Support web site, you can register to receive email
notifications of Avaya Security Advisories.
The amount of time it takes to receive an Avaya Security Advisory varies depending on the
vulnerability classification of the advisory. For more information about vulnerability classifications,
responses, and maintenance policies, refer to the following documents:
Avaya's Product Security Vulnerability Response Policy
Avaya's Security Vulnerability Classification
Avaya's Maintenance Contract Requirements for Product Support
Avaya Product Security Support Flow

Solution overview
Upgrades and migrations

This is the first release of Avaya Contact Center Select. Migrating from Avaya Contact Center Select
to Avaya Aura Contact Center is not supported. Migrating from Avaya Aura Contact Center to
Avaya Contact Center Select is not supported.

Chapter 3: Avaya Contact Center Select
DVD
The Avaya Contact Center Select DVD software provides a context-sensitive, collaborative, voice
and multimedia customer experience solution that allows small to midsize enterprises to anticipate,
accelerate, and enhance customer interactions. Avaya Contact Center Select uses the Avaya IP
Office telephone system to provide a real-time telephony platform. Avaya IP Office is a flexible and
scalable phone system designed specifically for small and midsize enterprises. IP Office supports a
wide range of phones and devices for use in contact centers.
The Avaya Contact Center Select DVD deployment option supports Platform Vendor Independence
(PVI). PVI gives the customer the flexibility to purchase a server that meets the Avaya Contact
Center Select server requirements and conforms with the customers own corporate standards. To
use the Avaya Contact Center Select DVD deployment option, the customer must provide the
following:
Server hardware that meets the Avaya Contact Center Select Platform Vendor Independence
(PVI) specification.
Microsoft Windows 2008 Release 2 with Service Pack 1 64bit operating system and license.
The following diagram shows the topology of a typical Avaya Contact Center Select solution:

Avaya Contact Center Select is preloaded with sample users, skillsets, and contact center
parameters. You can use this sample data to rapidly commission the solution and make the first
routed call and email contact. Avaya Contact Center Select delivers quick and simplified contact
center deployment. After the basic telephony features are working, you can then configure
multimedia contacts, multiplicity, custom prompts, other enhanced features and functions to improve
your customers experience.
To deploy Avaya Contact Center Select software using the DVD software, perform the following:
Obtain a server that meets the Avaya Contact Center Select PVI requirements.
Configure the server and format the hard disk partitions to the required specifications.
Install the Microsoft Windows 2008 Release 2 with Service Pack 1 64bit operating system.
License and activate the Microsoft Windows 2008 operating system.
Obtain an Avaya Contact Center Select DVD and license.
Use the Avaya Contact Center Select DVD to install the software components and applications.
Use the Avaya Contact Center Select Configuration Ignition Wizard to rapidly deploy a
functional contact center solution.
The Avaya Contact Center Select DVD is supported only on the Microsoft Windows 2008 Release 2
with Service Pack 1 64bit operating system.

Platform Vendor Independence server specification
Note:
The Avaya Contact Center Select server is supported only in a workgroup. Do not add the
Avaya Contact Center Select server to a domain.
The Avaya Contact Center Select DVD deployment option does not support VMware.

The Avaya Contact Center Select DVD deployment option supports Platform Vendor Independence
(PVI). PVI gives the customer the flexibility to purchase a server that meets the Avaya Contact
Center Select server requirements and conforms with the customers own corporate standards. To
use the Avaya Contact Center Select DVD deployment option, the customer must provide server
hardware that meets the Avaya Contact Center Select PVI specification.
The Avaya Contact Center Select DVD deployment option supports the following PVI server
specifications:
Entry-level server specification on page 33
Mid-range server specification on page 34
High-end server specifications on page 35
The high-end server specifications support the same maximum agent capacity and call rate figures.
The mid-range server specification supports a reduced agent capacity and call rate.
For information about achieving the maximum performance from your server hardware, see Server
performance and BIOS settings on page 38.
Entry-level server specification

The following table lists the minimum specifications for an entry-level server.
Specification Configuration Comment
CPU High Speed Quad Core CPU Intel Select a CPU that exceeds the
Xeon E3-1220 3.1GHz benchmark rating for the High Speed
Quad Core CPU Intel Xeon E3-1220
3.1GHz. Relative benchmark
comparisons only apply for CPUs with
the same number of cores. You can
make CPU comparisons by viewing the
benchmarked CPU passmark rankings
here: http://www.cpubenchmark.net
AMD processors are not supported.


RAM 32 GB minimum For maximum performance, Avaya
recommends that all DIMM slots are
populated.
Disk Type and Speed ESATA, SAS, minimum 10000 RPM 15000 RPM disks recommended.
IDE drives are not supported.
Solid State Drives (SSDs) are not
supported.
Total Disk size 900 GB
RAID Hardware RAID-1 Battery backed hardware RAID controller
and duplicate drives with identical
specifications required.
DVD Drive One dual-layer DVD drive 16X or faster recommended. DVD/Blu-
Ray combo drives are supported.
Network Interface Dual NIC 1 Gbit/s or faster Only Ethernet is supported.
Note:
For information about achieving the maximum performance from your server hardware, see
Server performance and BIOS settings on page 38.
For servers operating at 40% or above the rated capacity figures for the server type, Avaya
recommends that you use a physical database disk drive, separate from the Contact Center
application and Operating System disk drives. Variations are allowed for the Windows and
Application partitions providing there is sufficient capacity to prevent excessive disk
fragmentation.
Mid-range server specification

The following table lists the minimum specifications for a mid-range server.
CPU Dual Quad Core Xeon X5667 3.07 GHz Select a CPU that exceeds the
benchmark rating for the Dual Quad Core
Xeon X5667 3.07 GHz CPU. Relative
benchmark comparisons only apply for
CPUs with the same number of cores.
You can make CPU comparisons by
viewing the benchmarked CPU passmark
rankings here: http://
www.cpubenchmark.net


populated.
Disk Type and Speed ESATA, SAS, minimum 10000 RPM 15000 RPM disks recommended.
supported.
DVD Drive One dual-layer DVD drive 16X or faster recommended. DVD/Blu-
Ray combo drives are supported.
Network Interface Dual NIC 1 Gbit/s or faster Only Ethernet is supported.
Quad NICs are required for virtualized
environments where this server is a
VMware ESXi host.
Note:
For information about achieving the maximum performance from your server hardware, see
Server performance and BIOS settings on page 38.
Application partitions providing there is sufficient capacity to prevent excessive disk
fragmentation.
High-end server specifications

The Avaya Contact Center Select DVD supports the following high-end PVI server specifications:
High-end server with 6core CPU
These high-end server specifications support the same maximum agent capacity and call rate
figures.
Application partitions providing there is sufficient capacity to prevent excessive disk fragmentation.

For information about achieving the maximum performance from your server hardware, see Server
performance and BIOS settings on page 38.
High-end 6core server specification

The following table lists the minimum specifications for a high-end server with 6core CPU.
High-end server specification for servers with 6core CPU
CPU Dual 6Core Xeon X5680 Select a CPU that exceeds the benchmark
3.33GHz rating for the Dual 6-Core Xeon X5680
3.33GHz CPU. Relative benchmark
comparisons only apply for CPUs with the
same number of cores. You can make CPU
comparisons by viewing the benchmarked
CPU passmark rankings here: http://
www.cpubenchmark.net

populated.
Disk Type and Speed ESATA, SAS, minimum 10000 15000 RPM disks recommended.
RPM
supported.
DVD Drive One dual-layer DVD drive 16X or faster recommended. DVD and Blu-
ray combo drives are supported.
Network Interface Dual 1 Gbit/s or faster Only Ethernet supported.
vMware ESXi host.
Avaya Media Server configurations
require a NIC that supports Receiver Side
Scaling (RSS) with a minimum of 4
queues.



CPU Dual Intel Xeon E5-2670 Select a CPU that equals or exceeds the
2.60GHz (or faster) benchmark rating for the Dual 8core Intel
Xeon E5-2670 2.60GHz CPU. Relative
CPUs with the same number of cores. You
can make CPU comparisons by viewing the

populated.
RPM
supported.
Network Interface Dual 1 Gbit/s or faster Only Ethernet is supported.
VMware ESXi host.
queues.

CPU Dual Intel Xeon E5-2680 2.8GHz Select a CPU that equals or exceeds the
(or faster) benchmark rating for the Dual 10core Intel


Note:
CPUs based on more than ten cores
are not supported
populated.
RPM
supported.
VMware ESXi host.
queues.
Server performance and BIOS settings

The Basic Input Output System (BIOS) of a server configures the hardware components and boots
the operating system from a storage device. The server operating system (OS) then uses the BIOS
to control the server hardware. You must configure the server BIOS settings to ensure optimum
performance from the underlying server hardware. For most BIOS settings, you must choose
between optimizing a server for power savings or for server performance. For real-time applications
such as Avaya Contact Center Select, you must always choose the server BIOS settings that
ensure the optimum performance from the underlying server hardware.

Server manufacturers provide their own motherboards, BIOS, hardware, and firmware. Determining
the BIOS configuration for your servers hardware can be challenging. There are several BIOS
settings that can significantly impact the system performance. When optimizing for system
performance, you must select the BIOS settings that enhance the system performance over those
that contribute to power savings. Other BIOS settings and recommendations are not as straight
forward. Start by consulting the manufacturers technical data for your server. Avaya recommends
that you then test your solution in order to make the best BIOS configuration decisions.
Configure the server hardware, firmware, and Operating System settings to select system
performance over power savings.
Server firmware
Firmware is a computer program that is stored on the server motherboard or on an add-on hardware
controller. The firmware stored on the server motherboard is called the Basic Input Output System
(BIOS). The BIOS is responsible for the behaviour of the system when it is first switched on and for
passing control of the server to the operating system. Firmware is also stored in hardware
components such as Redundant Array of Independent Disks (RAID) controllers.
Routinely consult the manufacturers technical data for your servers and, where appropriate, apply
the most recent BIOS and firmware updates. The steps required to update firmware or a system
BIOS vary depending on the hardware vendor and the component to be updated. Typically, the
manufacturer supplies a firmware updating utility. Keeping your server BIOS and firmware at a
supported level can improve reliability, serviceability, and help ensure optimum performance.
Power and performance management

For real-time applications such as Avaya Contact Center Select, you must always select the
hardware, BIOS, firmware, and Operating System settings that enhance the system performance
over those that contribute to power savings.
Intel Xeon CPUs offer two main power management options: C-states and Intel Turbo Boost.
Disabling C-states lowers latencies to activate the CPUs from halt or idle states to full power
on.
Intel Turbo Boost steps up the internal frequency of the processor if the workload requires
more power.
These settings depend on the OEM make and model of the server. The BIOS parameter
terminology for current Dell and HP servers are described below. Other server makes and models
can have other terminology but equivalent BIOS settings.
The following are the recommended BIOS settings for the Dell PowerEdge servers:
Set the Power Management Mode to Maximum Performance.
Set the CPU Power and Performance Management Mode to Maximum Performance.
Processor Settings: set Turbo Mode to enabled
Processor Settings: set C States to disabled
The following are the recommended BIOS settings for the HP ProLiant servers:
Set the Power Regulator Mode to Static High Mode.

Disable Processor C-State Support

Disable Processor C1E Support
Disable QPI Power Management
Enable Intel Turbo Boost
Disk caching and RAID

Hard disk drives use cache memory to improve read and write access to the disk drives. In write-
back mode caching, the disk or RAID controller writes data from the server to cache memory and
acknowledges write completion to the server. The server is free to perform other tasks while the disk
controller transfers the data from the write cache to the disk drives. This approach significantly
increases write performance.
Avaya Contact Center Select supports hardware RAID-1 and RAID-5. RAID technology provides
disk data redundancy as well as error detection and correction. For maximum security and mission-
critical solutions, Avaya recommends that all Contact Center servers contain a RAID-1 controller.
Hardware RAID-1 and RAID-5 are the only levels and types of RAID supported.
Read the hardware documentation for your server to determine how to configure disk caching.
Typically, disk caching can be configured as a BIOS setting, a RAID setting, a RAID controller
setting, or as an Operating System setting. Refer to your hardware documentation for more
information about configuring disk caching. Avaya Contact Center Select does not support
Operating System level disk caching, software disk caching, or software RAID. Avaya Contact
Center Select requires battery backed hardware RAID caching to avoid data loss and possible
database corruption on power outage.
Non-Uniform Memory Architecture (NUMA) and memory

Non-uniform memory access (NUMA) is a computer memory design used in multiprocessing, where
the memory access time depends on the memory location relative to the processor. Using NUMA, a
processor can access its own local memory faster than non-local memory (memory local to another
processor or memory shared between processors). For Avaya Contact Center Select, the server
must support and implement NUMA.
In the server BIOS settings, configure the memory operating mode for performance optimization and
disable Node Interleaving. For example, for a Dell server configure Memory Operating Mode as
Optimizer Mode, and configure Node Interleaving as Disabled. Refer to your hardware
documentation for more information about NUMA and memory performance.
Hyper-Threading
Hyper-Threading refers to Intels proprietary technology for increasing parallel computational power
(processor multi-tasking) by allowing the operating system (OS) to see and address each physical
processor core as if it were two virtual processors. It also enables the OS and applications to share
work between those virtual processors whenever possible, thereby making full use of the available
resources.

Avaya Contact Center Select DVD software specification
Typically, enabling Hyper-Threading improves server performance; however this is not always the
case. In some cases, depending on your server hardware and solution implementation, enabling
Hyper-Threading can even degrade performance. Avaya recommends that you experiment with the
Hyper-Threading option to determine the optimum BIOS setting for your specific hardware and
solution type. Avaya does not mandate that Hyper-Threading be enabled or disabled; however
some reduction in Avaya Contact Center Select CPU utilization has been observed with Hyper-
Threading enabled. The reduction depends on a number of factors such as active agent count, call
rate, and the voice telephony platform.
Unused hardware devices

On the server, disconnect or disable unused and unnecessary physical hardware devices such as:
COM ports, LPT ports, USB controllers, Network interfaces, and Storage controllers. You must
retain some USB devices for the mouse and keyboard. Disabling unnecessary hardware devices
improves server performance and security. Consult the manufacturers technical data for your
servers for information about disabling unused hardware devices in the BIOS.
Summary
For real-time applications such as Avaya Contact Center Select, choose server BIOS settings that
optimize for performance in preference to power savings. Other BIOS settings, for example to
support Hyper-Threading, are not as straight forward. Start by consulting the manufacturers
technical data for your server. Avaya recommends that you then test your solution in order to make
the best BIOS configuration decisions. By enabling or disabling the BIOS options such as the CPU
Prefetchers and CPU Hyper-Threading, the system performance can be improved effectively. When
tuning system BIOS settings for performance, you must consider the various processor and memory
options. Experiment with other options to find the optimum setting for your specific hardware and
Contact Center solution.
Configure the server hardware, BIOS, firmware, and Operating System settings to select system

The Avaya Contact Center Select DVD contains the following software components:
Contact Center Manager Server (CCMS)
Contact Center Manager Administration (CCMA)
Communication Control Toolkit (CCT)
Contact Center License Manager (LM)
Contact Center Manager Server Utility (SU)
Orchestration Designer (OD)
Contact Center Multimedia (CCMM)
Avaya Media Server (Avaya MS) MS Windows version

Contact Center Services for Avaya Media Server

Avaya Contact Center Select Firewall policy
Default Avaya Contact Center Select configuration data
Configuration Ignition Wizard
The Avaya Contact Center Select DVD is supported only on the Microsoft Windows 2008 Release 2
with Service Pack 1 64bit operating system.
Server naming requirements

Server names must adhere to RFC1123 (Requirements for Internet Hosts), which specifies that a
host name must adhere to the following:
Use only characters a to z, A to Z, and 0 to 9 can be used in a host name.
You can use a hyphen (-), but not to start or end the host name.
Host names must be 6 to 15 characters in length.
Host names must not start with a number.
Do not use the underscore character (_) and period character (.).
Do not use spaces in the host name.
The Contact Center server must be able to resolve the host name or computer name of all other
servers within the configuration. If you have a Domain Name Service (DNS) server, make sure an
entry exists for each server. If you do not have a DNS server, manually update the HOSTS file on
each server with the host name or computer name of all other servers to ensure that all clients can
interpret the server names.
If network connectivity on your network requires the use of Fully Qualified Domain Names (FQDN),
then the FQDN of each computer must be resolvable between all servers associated with Contact
Center.
Microsoft security hotfixes

You must operate your server with the most current Microsoft patches.
Review the Contact Center Portfolio Service Packs Compatibility and Security Hotfixes
Applicability List (available from Technical Support Web site) for the list of applicable Microsoft
security hotfixes to apply.
Back up the entire server, and then shut down all Contact Center services before you apply
any Microsoft security hotfixes using the Microsoft instructions.
Apply Microsoft security updates on a timely basis.

Operating system updates

Operating system updates includes service updates and service packs.
Service updates
Given the number of operating system security service updates and the complexity inherent in any
network, create a systematic and accountable process for identifying and applying service updates.
To help create such a process, you can follow a series of best practices guidelines, as documented
in the National Institute of Standards and Technology (NIST) Special Bulletin 800-40, Procedures for
Handling Security Patches.
This bulletin suggests that if an organization has no central group to coordinate the storage,
evaluation, and chronicling of security service updates into a library, then system administrators or
the contact center administrator must fulfill this role. In addition to these guidelines, whenever
possible, follow Microsoft recommendations regarding newly discovered vulnerabilities and that you
promptly install Microsoft security service updates.
Whenever possible, Avaya incorporates the most recent operating system security
recommendations and service updates in an integrated solutions testing strategy during each test
cycle. However, due to the urgent nature of security service updates when vulnerabilities are
discovered, follow Microsoft guidelines as they are issued, including any Microsoft installation
procedures and security service update rollback processes.
Finally, you must perform a full system backup before you update the system to ensure that a
rollback is possible, if required. If a Contact Center application does not function properly after you
apply a Microsoft security service update, you must remove the service update and revert to the
previous version of the application (from the backup you made before applying the service update).
For added security, always determine whether Avaya verified the Microsoft service update for
compatibility with Contact Center Manager.
For more information about updating, see the Contact Center Portfolio Service Packs Compatibility
and Security Hotfixes Compatibility List on www.avaya.com/support.
Service packs
Avaya has a policy to implement co-residency testing of all new operating service packs for
compatibility with the suite of Contact Center applications as soon as they are available. In practice,
because a service pack can contain a significant amount of new content, Avaya requires that you
wait until compatibility testing is complete before you apply the service pack. Note that operating
system service packs are typically tested with the most recent Contact Center application SP and,
therefore, an upgrade to a new service pack requires an upgrade to the most recent Avaya SP.
Before you upload a new service pack, you must perform a full system backup (for system rollback
as in the updating scenario).

Important:
Service pack compatibility for all Contact Center applications is documented in the Contact
Center Portfolio Service Packs Compatibility and Security Hotfixes Applicability List on the Web
site at www.avaya.com/support.
Java Runtime Environment updates

Contact Center supports only specific versions of Java Runtime Environment (JRE). The Contact
Center Installer installs a supported JRE version, and Contact Center service packs install required
JRE updates. During installation, Contact Center disables JRE automatic updates on the contact
center servers.
Important:
Updating to an unsupported version of JRE can cause the contact center to stop working and
can require the reinstallation of the contact center server.
Dynamic Host Configuration Protocol support

Contact Center applications (CCMS, CCMA, CCT, CCMM, LM, and Avaya Media Server) do not
support Dynamic Host Configuration Protocol (DHCP). All Contact Center servers must have a static
IP address.
Agent Desktop client computers support both DHCP and static IP addresses.
Third-party software requirements

Due to the mission-critical, real-time processing that Contact Center applications perform, you must
not install any other application class software on the server. You can install certain utility class
software on the server, providing it conforms to the guidelines in this section.
Application class software generally requires a certain amount of system resources and must not be
installed on a server running Contact Center applications. The installation of third-party applications
can cause Contact Center applications to operate outside of the known engineering limits and can
create potential unknown system problems (for example, CPU contentions, increased network traffic
loading, disk access degradations).
Certain third-party utility class software applications, such as hardware diagnostics or backup tools,
generally require less system resources during the normal operation of Contact Center applications
and are permitted. Exceptions are utilities such as screen savers, which can cause system problems
and degrade performance.
Antivirus software is classified as a utility and is subject to the generic guidelines in the following
section.
Generic guidelines for utility-class software applications

The following are generic guidelines for utility-class software:
During run-time, the utility must not degrade the contact center application beyond an average
percentage of CPU use (see each specific application section in this document for the

recommended maximum CPU usage level). Furthermore, the utility must not lower the
minimum amount of free hard disk space required by contact center application and the
Windows Operating system.
The utility must not cause improper software shutdowns or out-of-sequence shutdowns.
The utility must not administer the contact center application.
If the utility has a database, it must not affect the contact center application database.
Disk compression utilities must not be used.
Memory tweaking utilities used to reclaim memory that is unused by Microsoft must not be
used.
The installation or uninstallation of the third-party software must not impact or conflict with the
contact center application (for example, it must not cause DLL conflicts). If such conflicts are
discovered, a server rebuild might be necessary.
The implementation personnel must perform tests to ensure these conditions and
recommendations are met before you place the Contact Center application into production.
Support personnel can ask for the results of the testing during fault diagnosis. As part of fault
diagnosis, the distributor or end user might be asked to remove third-party software.
HyperTerminal must not be installed on the server as it interferes with the operation of Contact
Center.
Guidelines for the use of antivirus software

This section describes the Avaya Contact Center Select antivirus software requirements.
Avaya Contact Center Select supports the following antivirus products:
Symantec AntiVirus 11.0.5, 11.0.6, or 12
McAfee 8.8
Microsoft ForeFront 2010
You can deploy antivirus products from other vendors subject to the following guidelines:
Infected file quarantine policy on the server and client: antivirus software can be configured to
clean up the detected virus automatically and files must be quarantined if infected files cannot
be cleaned. Contact Avaya to verify whether the quarantine file is part of our product files or
dependent system file. If a virus is detected, remove the server from the network immediately
during virus eradication to prevent further virus propagation.
Do not connect a contact center application platform directly to the Internet to download virus
definitions or updated files. Furthermore, Avaya recommends that you do not use a contact
center application client PC to connect to the Internet. Instead, download virus definitions and
updated files to another location on the customer network and manually load them from this
interim location onto the contact center application platform.
Perform the previous steps to download Contact Center application service packs (SP). This
method limits access to the Internet, and thus reduces the risk of downloading infected files.

Scan all SP files, DVD-ROMs, and floppy disks before you upload or install to the server. This
practice minimizes any exposure to infected files from outside sources.
Capacity considerations: running virus scan software can place an additional load on a contact
center application platform. The implementation personnel must run the performance monitor
tool on the server to gauge CPU usage. If the antivirus software scan causes the platform
average CPU usage to exceed the recommended percentage for longer than 20 minutes, the
antivirus software must not be loaded onto the contact center application platform.
Product Support do not provide support on the configuration of antivirus software, but offer
guidance where possible. Direct questions or problems on antivirus software to the appropriate
vendor.
If performance or functionality issues are raised to Avaya support personnel as part of the fault
diagnosis, you might be asked to remove third-party utility software or antivirus software.
Several maintenance tasks are automatically activated at 12:00 midnight. Therefore, you must
schedule virus scans at a time other than midnight.
Avaya recommends that you exclude the following files and folders from scans (both real-time and
scheduled):
F:\Avaya\Contact Center\Database\
<additional database drive>:\Avaya\Database\
TSM_OAM files located in the following folders:
- D:\Avaya\Contact Center\Manager Server\iccm\bin\data
- D:\Avaya\Contact Center\Manager server\iccm\data
- D:\Avaya\Contact Center\Manager Server\iccm\sdm\log
OAMContainer*.log located at D:\Avaya\Contact Center\Common Components\CMF
D:\Avaya\Contact Center\Manager Server\bin\tools2.exeFile access errors
occur in the Scan Activity log if you do not exclude this file from scanning.
D:\Avaya\Contact Center\Manager Server\iccm\logs (SIP logs)
D:\Avaya\Contact Center\Manager Server\iccm\sgm\config\ (SIP log
configuration files)
D:\Avaya\Contact Center\Common Components\CMF
The folder where you store Server Packs and patches
Contact Center Multimedia interacts with an external email system and enables agents to send
attachment files from their computers to the Avaya Contact Center Select server. Both methods of
retrieving data are potential sources of software infection.
Avaya recommends the following guidelines for antivirus software:
Antivirus software must be installed on the email server to ensure that problems are caught at
source.
Agent computers require antivirus software to ensure that attachments sent to the Avaya
Contact Center Select server do not have a virus. Contact Center Multimedia does not block

Avaya Contact Center Select DVD licensing
specific attachment file types. Third-party antivirus software must be installed on the Portal
Server according to guidelines in this document for such utilities.
Ensure the antivirus software is configured to permit outbound email messages. For example,
configure the McAfee antivirus software Access Protection option not to block Prevent mass
mailing worms from sending mail.
Exclude the Contact Center Multimedia partition from being scanned.
If firewalls on individual computers are enabled on the Agent Desktop computer, the Report
Listener might be flagged as trying to access the Internet. The properties must be configured to
allow access for the Report Listener to Contact Center Multimedia through the firewall.
You must not enable the Microsoft Updater to Auto-Run. Microsoft Updater is configured to
alert level so you can schedule updates for off- peak hours.
Warning:
Running a Virus Scan on the Contact Center Multimedia attachment folder, which contains
thousands of files, can use significant CPU time on a server and can cause drastic slowdown in
agent's response times. Avaya recommends that you run scans, if necessary, during off-peak
hours.
To avoid database integrity problems, Avaya recommends that you exclude all CACHE.DAT files,
journal files, the cache.cpf file, and any Cach-related files from antivirus scans.
Cach software is installed in <Install_drive>:\Avaya\Cache\CacheSys. Databases and
journal files are installed in <Install_drive>:\Avaya\Contact Center\Databases.
Avaya Contact Center Select DVD licensing

The Avaya Contact Center Select DVD deployment option uses a Nodal Enterprise license delivered
as a WebLM XML file. This license file is used to control access to licensed features such as
multimedia contacts and multiplicity.
Contact Center License Manager provides central control and administration of licensing for Avaya
Contact Center Select. Each Contact Center License Manager includes a local instance of WebLM.
When the Contact Center License Manager service starts, it extracts WebLM license keys from the
local WebLM instance. Contact Center License Manager then converts the WebLM license keys into
local PLIC license keys and distributes the keys the Avaya Contact Center Select applications as
required.
Obtain the network interface MAC address of the Avaya Contact Center Select server.
Use the MAC address to obtain a nodal WebLM license file from the Avaya Product Licensing
and Delivery System (PLDS).
You load the license file onto the Avaya Contact Center Select server as you run the
configuration utility when you are deploying the Avaya Contact Center Select server. When
Contact Center License Manager loads the license, if the unique number in the license does

not match the Avaya Contact Center Select server MAC address, then License Manager shuts
down and Avaya Contact Center Select cannot process contacts. If the unique number in the
license matches the Avaya Contact Center Select server MAC address, then License Manager
provides license keys, and Avaya Contact Center Select processes customer contacts.


populated.
RPM
supported.
VMware ESXi host.
queues.

software appliance
For increased productivity, efficiency, and flexibility, Avaya Contact Center Select supports the
VMware Open Virtual Appliance (OVA) deployment method. A virtual appliance contains a
preinstalled, preconfigured Operating System and an application stack optimized to provide a
specific set of services. You can use a single Open Virtual Appliance (OVA) package to distribute a
Virtual Appliance. An Avaya Contact Center Select OVA package includes all of the Open
Virtualization Format (OVF) information required to create an Avaya Contact Center Select Virtual
Appliance on a VMware host.
The Avaya Contact Center Select software appliance consists of the following VMware Virtual
Appliances:
Avaya Contact Center Select OVA
Avaya Media Server OVA
Avaya WebLM OVA
The following diagram shows a typical virtualized contact center solution using the Avaya Contact
Center Select, Avaya Media Server, and Avaya WebLM Virtual Appliances installed on a single
VMware host server:

Avaya Contact Center Select software appliance
You can use VMware vSphere or vCenter and these Avaya Contact Center Select OVA packages to
create virtual machines in your virtualized environment. The OVA packages are created as VMware
hardware version 8 archives.
The Avaya Contact Center Select Virtual Appliances are supported only with the following
virtualization environments:
ESXi 5.0
ESXi 5.1
ESXi 5.5
Avaya Contact Center Select supports the Avaya WebLM guest co-resident on the same VMware
host server or deployed on a separate VMware host server.
Avaya Contact Center Select supports the Avaya Media Server guest co-resident on the same
VMware host server or deployed on a separate VMware host server.
For more information about the Avaya Contact Center Select software appliance Open Virtual
Appliance (OVA) packages, see the following:
Avaya Contact Center Select OVA on page 51
Avaya Media Server OVA on page 57
Avaya WebLM OVA on page 59


Deploy the Avaya Contact Center Select OVA to provide contextsensitive and skill-based routing
for customer voice and multimedia contacts.
The Avaya Contact Center Select OVA creates and configures a virtual machine (guest) containing
contact center application software. The resulting virtual machine contains a Microsoft Windows
operating system, hard disk drive partitions, third-party components, system configuration, and
Avaya Contact Center Select application software.
The Avaya Contact Center Select Open Virtual Appliance (OVA) contains the following software:
Microsoft Windows 2008 Release 2, Service Pack 1, 64bit operating system
Firewall policy
Configuration Ignition Wizard
VMware Tools. Do not update the VMware Tools software unless instructed to do so by Avaya.
The Windows 2008 operating system on the Avaya Contact Center Select OVA is not activated.
Important:
You must supply and install a valid Windows operating system license on the server and
activate it within 30 days of the initial power-up. Otherwise the Avaya Contact Center Select
server stops working.
The following table shows the operating system on the Avaya Contact Center Select OVA.
Operating System International Minimum Service Pack
Versions Supported Supported
Windows Server 2008 Release 2, English Service Pack 1
64-bit, Service Pack 1.
The Avaya Contact Center Select OVA package has the following hardware characteristics:
vCPU Minimum Virtual memory Number Virtual disk storage reservation
CPU speed reservation of NICs
16 16GB 1 Drive Letter Size (GB)

vCPU Minimum Virtual memory Number Virtual disk storage reservation

CPU speed reservation of NICs
OS C: 80
CC software D: 120
CCMS/CCT F: 210
database
CCMM database H: 200
610 GB total
HD drive speed 10000 RPM minimum
Deploy the Avaya Contact Center Select OVA using
Thick Provision Lazy Zeroed. Avaya Contact Center
Select does not support thin provisioning in
production environments.
Each Avaya Contact Center Select solution requires a Linux-based Avaya Media Server. Each
Avaya Contact Center Select solution also requires an additional, separate, Avaya WebLM licensing
manager server.

Center.



Service updates

Service packs
Important:

center servers.
Important:

IP address.


section.

used.
Center.

McAfee 8.8

vendor.
scheduled):


source.
Warning:
hours.

Deploy the Avaya Media Server OVA to provide the conference, announcement, and dialog services
required by Avaya Contact Center Select.
The Avaya Media Server OVA creates and configures a virtual machine (guest) containing Avaya
Media Server software. The resulting virtual machine contains a Linux operating system, hard disk
drive, third-party components, system configuration, firewall settings, and Avaya Media Server
application software.

You can deploy the Avaya Media Server OVA on the same VMware host server as the Avaya
Contact Center Select OVA and the Avaya WebLM OVA. Alternatively, you can deploy the Avaya
Media Server OVA standalone on a separate VMware host server.
The Avaya Media Server OVA contains information about the guest server specification, guest
operating system, and application software. This OVA contains the following components:
Red Hat Enterprise Linux 6.5 - 64bit
Avaya Media Server 7.6 software
Contact Center Services for Avaya Media Server
IP tables firewall file application
VMware Tools. Do not update the VMware Tools software on this virtual machine unless
instructed to do so by Avaya.
The Avaya Media Server OVA is not supported in High Availability solutions. Virtualized Avaya
Media Server does not support High Availability.
Avaya Media Server is a software based media processing platform. Avaya Contact Center Select
includes an enhanced version of Avaya Media Server which contains an additional component
Contact Center Services for Avaya Media Server. The Contact Center Services packaged
application provides the conference, announcement, and dialog services required by SIP-enabled
Contact Center.
The Avaya Media Server OVA package has the following default hardware configuration:
vCPU Minimum Virtual memory Number of Virtual disk storage required
CPU speed required NICs
12 12GB 1 Size 80 GB
Deploy the Avaya Media Server OVA
using Thick Provision Lazy Zeroed.
Avaya Media Server does not support
thin provisioning in production
environments.
In a virtualized Avaya Contact Center Select environment, you can use VMware to load the Avaya
Media Server OVA package into a virtual machine (guest) in your contact center solution. The
virtualized Avaya Contact Center Select server can then use the virtualized Avaya Media Server as
a voice media processor.
The Avaya Media Server OVA creates two Linux accounts; root and amsuser (for Element
Manager). You must use VMware console to log on to the Avaya Media Server guest as the root
administrator and set an initial password, before you can gain access to the system either locally,
using SSH, or using Element Manager.
Deploy the Avaya Media Server OVA using Disk Format - Thick Provision Lazy Zeroed. Avaya
Media Server does not support thin provisioning in production environments.

WebLM OVA
WebLM OVA
Deploy the Avaya WebLM OVA to provide solution licensing. You can deploy the Avaya WebLM
OVA on the same VMware host server as the Avaya Contact Center Select Voice and Multimedia
Contact Server OVA and the Avaya Media Server OVA. Alternatively, you can also deploy the
Avaya WebLM OVA standalone on a separate VMware host server.
Each Avaya Contact Center Select supports one Avaya WebLM license manager server. Each
Avaya WebLM license manager server supports one Avaya Contact Center Select. For increased
efficiency and flexibility, the Avaya WebLM licensing manager supports the VMware Virtual
Appliance and Open Virtualization Archive (OVA) deployment mechanisms. In a virtualized Avaya
Contact Center Select environment, you can use VMware to load the Avaya WebLM OVA package
onto a separate virtual machine in your contact center solution. The virtualized Avaya Contact
Center Select server can then use the virtualized WebLM server as the license manager.
The Avaya WebLM OVA contains a hardened Linux operating system.
The Avaya WebLM OVA requires the following:
vCPU Minimum CPU speed Virtual memory Number of NICs Virtual disk storage
reservation reservation
1 1 GB 1 shared 30 GB
The Avaya WebLM OVA uses the following network mapping:

WebLM Server VM Interface Application
Eth0 License management
The Avaya WebLM server for VMware is packaged as a vAppliance ready for deployment using
either VMware vSphere Client or VMware vCenter.
Deploy the Avaya WebLM OVA using Disk Format - Thick Provision Lazy Zeroed. Avaya WebLM
does not support thin provisioning in production environments.
VMware host server specification

The Avaya Contact Center Select software appliance is a set of VMware Open Virtual Appliance
(OVA) virtualized servers; an Avaya Contact Center Select OVA, an Avaya Media Server OVA, and
a WebLM OVA. You can deploy the Avaya Contact Center Select software appliance (3x OVAs) on
a VMware ESXi host server that meets the 8core or 10core High-end Platform Vendor
Independence server specifications.
Platform Vendor Independence (PVI) gives the customer the flexibility to purchase a server that
meets the Avaya Contact Center Select server requirements and conforms with the customers own
corporate standards. To use the Avaya Contact Center Select software appliance deployment

option, the customer must provide VMware ESXi host hardware that meets the Avaya Contact
Center Select PVI specification.
The Avaya Contact Center Select software appliance is supported on VMware ESXi hosts that meet
the following PVI specifications:
These high-end server specifications support the same maximum agent capacity and call rate
figures. The Avaya Contact Center Select software appliance is not supported on the Mid-range or
Entry-level specifications.


populated.
RPM
supported.

VMware host server specification

VMware ESXi host.
queues.

CPU Dual Intel Xeon E5-2680 2.8GHz Select a CPU that equals or exceeds the
(or faster) benchmark rating for the Dual 10core Intel
Note:
CPUs based on more than ten cores
are not supported
populated.
RPM
supported.


VMware ESXi host.
queues.
Virtualization considerations
Using virtualization in a contact center enterprise solution requires careful up-front planning,
engineering, and implementation. While the technical and business advantages are clear,
virtualization imposes extra considerations when designing the contact center solution architecture.
Environmental isolation allows multiple operating systems to run on the same VMware host
machine. While virtualization offers these forms of isolation, virtualization environments do not
provide performance isolation. The behavior of one virtual machine can adversely affect the
performance of another virtual machine on the same host. Most modern virtualization environments
provide mechanisms that you can use to detect and reduce performance interference. You must
carefully engineer your virtualized contact center solution to avoid performance interference.
If you plan to install non-Contact Center software applications on the other guests of a host server
with Contact Center installed, you must carefully analyze the impact of these applications on the
contact center solution and provide extra performance isolation to safeguard Contact Center
functionality.
Important:
Deploy Contact Center on an enterprise-grade virtual environment with the most recent
hardware that supports hardware-assisted virtualization. Avaya recommends that you apply
virtualization planning, engineering, and deployment with full organizational support for
virtualization rather than organically growing a virtualization infrastructure.
VMware features
Avaya Contact Center Select is a collection of real-time applications running on the MS Windows
Server 2008 R2 SP1 operating system. Avaya Contact Center Select provides real-time call control,
multimedia handling, and statistical reporting.
Avaya Media Server is a real-time media processing application running on the Red Hat Enterprise
Linux (RHEL) operating system. Avaya Media Server provides the real-time conferencing and media
processing capabilities for Avaya Contact Center Select.

Some VMware features require CPU, Disk I/O, or networking resources to function. Running these
VMware features can cause resource constraints and impact the real-time performance of the
Avaya Contact Center Select and Avaya Media Server Virtual Machines (VMs). These features are
therefore not supported while Avaya Contact Center Select or Avaya Media Server are active.
Some VMware features are not supported by Avaya Contact Center Select or Avaya Media Server.
Some other VMware features are supported only while the Avaya Contact Center Select or Avaya
Media Server Virtual Machines are stopped for maintenance.
The following table shows the Avaya Contact Center Select and Avaya Media Server level of
support for VMware features.
VMware Feature Supported on Supported during Supported on Supported during
active Avaya Avaya Contact active Avaya Avaya Media
Contact Center Select VM Media Server VM Server VM
Center Select maintenance maintenance
VM window window
Cloning No Yes No No
Distributed Power No Yes No Yes
Management (DPM)
Distributed Resources No Yes No Yes
Scheduler (DRS)
Distributed Switch Yes Yes No No
Fault Tolerance No No No No
High Availability (HA) No No No No
Snapshots No See Avaya Contact No See Avaya Media
Center Select Server VMware
VMware snapshot snapshot
considerations on considerations on
page 68 page 69
Storage DRS No Yes No Yes
Storage Thin No N/A No N/A
Provisioning
Storage vMotion No Yes No Yes
Suspend & Resume No N/A No N/A
vMotion No Yes No No
VMware vSphere Host considerations

When planning virtual machines (guests) on your host system, the total resources needed by the
virtual machines running on the host server must not exceed the total capacity of the host. It is good
practice to under-commit CPU and memory resources on the host. If the host CPU capacity is
overloaded, Contact Center does not function correctly.

Important:
Avaya Contact Center Select is not supported on an over-committed host where the total virtual
resources from all virtual machines hosted exceeds the physical resources of the host.
Hardware-Assisted Virtualization
Most recent enterprise-level processors from Intel support virtualization. There are two generations
of virtualization support: the first generation introduced CPU virtualization; the second generation
included CPU virtualization and added memory management unit (MMU) virtualization. For the best
performance, make sure your system uses processors with at least second-generation hardware-
assist features.
Virtual Machine File System (VMFS)
VMware virtual machines and snapshots are stored in a Virtual Machine File System (VMFS)
datastore. To support Avaya Contact Center Select on a virtual machine, the VMware datastore
containing Contact Center must be VMFS 5.54 or later. If you upgrade an existing VMware host
server, ensure the associated datastore is upgraded to VMFS 5.54 or later.
Hardware-Assisted CPU Virtualization (Intel VT-x)
The first generation of hardware virtualization assistance includes VT-x from Intel. These
technologies automatically trap sensitive interrupts, eliminating the overhead required to do so in
software. This allows the use of a hardware virtualization (HV) virtual machine monitor (VMM).
Hardware-Assisted MMU Virtualization (Intel EPT)
More recent enterprise-level processors also include a feature that addresses the overheads due to
memory management unit (MMU) virtualization by providing hardware support to virtualize the
MMU. VMware vSphere supports this feature in Intel processors, where it is called Extended Page
Tables (EPT).
Storage Area Network (SAN)
A Storage Area Network (SAN) is a dedicated storage network that provides access to consolidated
block level storage. SANs are used to make storage devices such as disk arrays, accessible to
servers so that the devices appear as locally attached to the operating system.
When Avaya Contact Center Select is installed on virtual machines it supports a SAN. You must
monitor the Contact Center demand on the SAN storage device. Adhere to your vendor-specific
SAN configuration recommendations to ensure the SAN storage device meets the demands of
Contact Center.
Disk drive provisioning
Provision sufficient hard disk drive space on the host server to support all the guest virtual
machines, an ISO library, and provision additional space for snapshot image storage.

Server performance and BIOS settings

The Basic Input Output System (BIOS) of a server configures the hardware components and boots
the operating system from a storage device. The server operating system (OS) then uses the BIOS
to control the server hardware. You must configure the server BIOS settings to ensure optimum
performance from the underlying server hardware. For most BIOS settings, you must choose
between optimizing a server for power savings or for server performance. For real-time applications
such as Avaya Contact Center Select, you must always choose the server BIOS settings that
ensure the optimum performance from the underlying server hardware.
Server manufacturers provide their own motherboards, BIOS, hardware, and firmware. Determining
the BIOS configuration for your servers hardware can be challenging. There are several BIOS
settings that can significantly impact the system performance. When optimizing for system
performance, you must select the BIOS settings that enhance the system performance over those
that contribute to power savings. Other BIOS settings and recommendations are not as straight
forward. Start by consulting the manufacturers technical data for your server. Avaya recommends
that you then test your solution in order to make the best BIOS configuration decisions.
Server firmware
Firmware is a computer program that is stored on the server motherboard or on an add-on hardware
controller. The firmware stored on the server motherboard is called the Basic Input Output System
(BIOS). The BIOS is responsible for the behaviour of the system when it is first switched on and for
passing control of the server to the operating system. Firmware is also stored in hardware
components such as Redundant Array of Independent Disks (RAID) controllers.
Routinely consult the manufacturers technical data for your servers and, where appropriate, apply
the most recent BIOS and firmware updates. The steps required to update firmware or a system
BIOS vary depending on the hardware vendor and the component to be updated. Typically, the
manufacturer supplies a firmware updating utility. Keeping your server BIOS and firmware at a
supported level can improve reliability, serviceability, and help ensure optimum performance.
Power and performance management

For real-time applications such as Avaya Contact Center Select, you must always select the
hardware, BIOS, firmware, and Operating System settings that enhance the system performance
over those that contribute to power savings.
Intel Xeon CPUs offer two main power management options: C-states and Intel Turbo Boost.
Disabling C-states lowers latencies to activate the CPUs from halt or idle states to full power
on.
Intel Turbo Boost steps up the internal frequency of the processor if the workload requires
more power.

These settings depend on the OEM make and model of the server. The BIOS parameter
terminology for current Dell and HP servers are described below. Other server makes and models
can have other terminology but equivalent BIOS settings.
The following are the recommended BIOS settings for the Dell PowerEdge servers:
Set the Power Management Mode to Maximum Performance.
Set the CPU Power and Performance Management Mode to Maximum Performance.
Processor Settings: set Turbo Mode to enabled
Processor Settings: set C States to disabled
The following are the recommended BIOS settings for the HP ProLiant servers:
Set the Power Regulator Mode to Static High Mode.
Disable Processor C-State Support
Disable Processor C1E Support
Disable QPI Power Management
Enable Intel Turbo Boost
Disk caching and RAID

Hard disk drives use cache memory to improve read and write access to the disk drives. In write-
back mode caching, the disk or RAID controller writes data from the server to cache memory and
acknowledges write completion to the server. The server is free to perform other tasks while the disk
controller transfers the data from the write cache to the disk drives. This approach significantly
increases write performance.
Avaya Contact Center Select supports hardware RAID-1 and RAID-5. RAID technology provides
disk data redundancy as well as error detection and correction. For maximum security and mission-
critical solutions, Avaya recommends that all Contact Center servers contain a RAID-1 controller.
Hardware RAID-1 and RAID-5 are the only levels and types of RAID supported.
Read the hardware documentation for your server to determine how to configure disk caching.
Typically, disk caching can be configured as a BIOS setting, a RAID setting, a RAID controller
setting, or as an Operating System setting. Refer to your hardware documentation for more
information about configuring disk caching. Avaya Contact Center Select does not support
Operating System level disk caching, software disk caching, or software RAID. Avaya Contact
Center Select requires battery backed hardware RAID caching to avoid data loss and possible
database corruption on power outage.
Non-Uniform Memory Architecture (NUMA) and memory

Non-uniform memory access (NUMA) is a computer memory design used in multiprocessing, where
the memory access time depends on the memory location relative to the processor. Using NUMA, a
processor can access its own local memory faster than non-local memory (memory local to another

processor or memory shared between processors). For Avaya Contact Center Select, the server
must support and implement NUMA.
In the server BIOS settings, configure the memory operating mode for performance optimization and
disable Node Interleaving. For example, for a Dell server configure Memory Operating Mode as
Optimizer Mode, and configure Node Interleaving as Disabled. Refer to your hardware
documentation for more information about NUMA and memory performance.
Performance management and VMware

For VMware host servers, to allow the VMware kernel to control CPU power saving while
maximizing server performance when required, it is possible to set power management in the BIOS
to OS Control Mode. The VMware hypervisor can then provide balanced performance and power
management. This BIOS setting and VMware feature combination does not meet the real-time
performance requirements of Avaya Contact Center Select. Avaya Contact Center Select does not
support the BIOS OS Control Mode settings or its equivalents.
Virtualization technology
When virtualization technology is enabled, the BIOS enables processor virtualization features and
provides virtualization support to the operating system through the DMAR table. In general, only
virtualized environments such as VMware take advantage of these features.
For VMware host servers, enable all available Virtualization Technology options in the hardware
BIOS. For Intel based hosts: Enable Intel virtualization (VT-x) and if available enable Extended Page
Tables (EPT)The available virtualization settings vary by hardware provider and BIOS version. Read
your hardware provider's documents covering virtualization support to determine which settings to
configure.
Hyper-Threading
Hyper-Threading refers to Intels proprietary technology for increasing parallel computational power
(processor multi-tasking) by allowing the operating system (OS) to see and address each physical
processor core as if it were two virtual processors. It also enables the OS and applications to share
work between those virtual processors whenever possible, thereby making full use of the available
resources.
Typically, enabling Hyper-Threading improves server performance; however this is not always the
case. In some cases, depending on your server hardware and solution implementation, enabling
Hyper-Threading can even degrade performance. Avaya recommends that you experiment with the
Hyper-Threading option to determine the optimum BIOS setting for your specific hardware and
solution type. Avaya does not mandate that Hyper-Threading be enabled or disabled; however
some reduction in Avaya Contact Center Select CPU utilization has been observed with Hyper-
Threading enabled. The reduction depends on a number of factors such as active agent count, call
rate, and the voice telephony platform.
Unused hardware devices

On the server, disconnect or disable unused and unnecessary physical hardware devices such as:
COM ports, LPT ports, USB controllers, Network interfaces, and Storage controllers. You must

retain some USB devices for the mouse and keyboard. Disabling unnecessary hardware devices
improves server performance and security. Consult the manufacturers technical data for your
servers for information about disabling unused hardware devices in the BIOS.
Summary
For real-time applications such as Avaya Contact Center Select, choose server BIOS settings that
optimize for performance in preference to power savings. Other BIOS settings, for example to
support Hyper-Threading, are not as straight forward. Start by consulting the manufacturers
technical data for your server. Avaya recommends that you then test your solution in order to make
the best BIOS configuration decisions. By enabling or disabling the BIOS options such as the CPU
Prefetchers and CPU Hyper-Threading, the system performance can be improved effectively. When
tuning system BIOS settings for performance, you must consider the various processor and memory
options. Experiment with other options to find the optimum setting for your specific hardware and
Contact Center solution.
Configure the server hardware, BIOS, firmware, and Operating System settings to select system
VMware networking best practices

There are many different ways of configuring networking in a VMware environment. Review the
VMware networking best practices documentation before deploying Avaya applications on an ESXi
host. This section is not a substitute for the VMware documentation. For improved performance and
best practice, Contact Center uses Network Adapter type VMXNET 3.
The following are some suggested networking best practices:
Separate network services to achieve greater security and performance. Create a vSphere
Standard Switch with dedicated NICs for each service. Separate VMware Management, iSCSI
(SAN traffic), and VM networks to separate physical NICs. If separate switches are not
possible, consider port groups with different VLAN IDs.
All physical NICs that are connected to the same vSphere Standard Switch must be connected
to the same physical network.
Configure all VMkernal vNICs to the same MTU (IP Maximum Transmission Unit).
Configure Contact Center to use Network Adapter type VMXNET 3.
For more information about VMware networking best practices, refer to the VMware documentation.
Avaya Contact Center Select VMware snapshot considerations

VMware snapshots save the current state of the virtual machine, so you can return to it at any time.
Snapshots are useful when you need to revert a virtual machine repeatedly to the same state, but
you don't want to create multiple virtual machines.

The following considerations apply when using snapshots with Avaya Contact Center Select on
VMware:
Snapshots must be taken during an Avaya Contact Center Select maintenance window. Do not
take a snapshot of a Contact Center virtual machine while Contact Center is running.
Snapshots have a negative impact on the performance of a virtual machine over time. You
must Consolidate snapshots at the end of the maintenance window, before putting the Contact
Center virtual machine back into production. For more information about consolidating
snapshots, refer to VMware documentation.
Create a snapshot for the Contact Center virtual machines all at the same time. Likewise, when
you restore a snapshot, restore all snapshots to ensure the data is consistent across the
Contact Center suite.
When restoring snapshots, carefully consider the possible impact from out-of-date antivirus
definitions, missed Microsoft Windows OS and security updates, and lapsed domain accounts
on the contact center. Isolate the restored virtual machine until these issues are resolved.
By default, a Windows Server 2008 machine account password is changed every 30 days. This
is an important consideration when reverting to a snapshot of a virtual machine that has been
in use for more than 30 days, as it can cause the machine to lose its connection to the
Windows domain. If this issue occurs, rejoin the Windows Server 2008 virtual machine to the
domain.
VMware snapshots are not a replacement for Avaya Contact Center Select database backup (and
restore) procedures and practices. You must continue to perform regular and frequent Contact
Center backups. For more information about maintenance, see Deploying Avaya Contact Center
Select Software Appliance.
Avaya Media Server VMware snapshot considerations

VMware snapshots save the current state of the virtual machine, so you can return to it at any time.
Snapshots are useful when you need to revert a virtual machine repeatedly to the same state, but
you don't want to create multiple virtual machines.
The following considerations apply when using snapshots with Avaya Media Server on VMware:
Snapshots must be taken during an Avaya Media Server maintenance window. Do not take a
snapshot of an Avaya Media Server virtual machine while the contact center is running.
Snapshots have a negative impact on the performance of a virtual machine over time. You
must Consolidate snapshots at the end of the maintenance window, before putting the Avaya
Media Server virtual machine back into production. For more information about consolidating
snapshots, refer to VMware documentation.
When restoring snapshots, carefully consider the possible impact from out-of-date antivirus
definitions, missed Linux operating system updates and security updates. Isolate the restored
virtual machine until these issues are resolved.
VMware snapshots are not a replacement for Avaya Media Server database backup (and restore)
procedures and practices. For more information about maintenance, see Deploying Avaya Contact
Center Select Software Appliance.

Guidance for storage requirements

Input/Outputs per Second (IOPS) is a measure of the maximum number of reads and writes to non-
contiguous storage locations performed per second. IOPS measurements are associated with
smaller files and more continuous changes, and comprise the workloads most typical in real-time
enterprise applications such as Avaya Contact Center Select.
In a virtualized environment, any given storage array must be designed to have an IOPS capacity
exceeding the sum of the IOPS required for all resident applications.
For a fully loaded Avaya Contact Center Select instance, the IOPS is:
Average: 105
Maximum: 1488
These IOPS figures include Avaya Contact Center Select and the underlying operating system
loads.
Performance monitoring and management

You must continuously monitor and measure the performance of the Contact Center host server.
You can use VMware vSphere vCenter to measure the critical host performance metrics in real-
time. VMware vCenter aggregates and archives performance data so that data can be visualised
and reported on.
Configure VMware vCenter statistics collection to collect 5 minute and 30 minute Interval Duration
data for the host at Statistics Level 3. Retain the 5 minute Interval Duration data for 3 days and
retain the 30 minute Interval Duration for 1 week.
Generate performance reports using vCenter Report Performance and archive these reports to
provide a baseline performance reference. Generate and store 1-day and 1-week reports. Store the
associated vCenter Report Summary with the performance reports. You must analyze performance
reports after changes to the host to assess the impact of the change on the host.
Monitor, acknowledge, and resolve VMware vCenter alarms. In particular, you must immediately
investigate and resolve host CPU usage and host memory usage alarms.
In addition, the command-line tools esxtop and resxtop are available to provide a fine-grained
look at real-time metrics. There are a number of critical CPU-related counters to watch out for:
If the load average listed on the first line of the CPU Panel is equal to or greater than the
number of physical processors in the system, this indicates that the system is overloaded.
The usage percentage of physical CPUs on the PCPU line can indicate an overloaded
condition. In general, 80 percent usage is a reasonable ceiling in production environments. Use
90 percent as an alert to the VMware administrator that the CPUs are approaching an
overloaded condition, which must be addressed.
%RDY - The percentage of time a schedulable entity was ready to run but is not scheduled to a
core. If %RDY is greater than 10 percent, then this can indicate resource contention.

%CSTP - The percentage of time a schedulable entity is stopped from running to allow other
vCPUs in the virtual machine to catch up. If %CSTP is greater than 5 percent, this usually
means the virtual machine workload is not using VCPUs in a balanced fashion. High %CSTP
can be an indicator of a system running on an unconsolidated snapshot.
For more information about using esxtop or resextop, see the VMware Resource Management
Guide.
Memory Reservations
Use VMware Reservations to specify the minimum amount of memory for a Contact Center virtual
machine. VMware Reservations maintain sufficient host memory to fulfill all reservation guarantees.
ESX does not power-on a virtual machine if doing so reduces the amount of available memory to
less than the amount reserved. Using reservations can reduce the total number of virtual machines
that can be hosted on a VMware host server. After all resource reservations have been met, ESX
allocates the remaining resources based on the number of shares and the resource limits configured
for your virtual machine.
Troubleshooting VMware
Virtualization platform performance issues can result with Contact Center performance problems.
The virtualization platform includes the host and the running virtual machines on the host. The
Contact Center performance problems can include (but are not limited to) high CPU usage, link
instability, defaulted or abandoned calls.
You must logically and systematically investigate any Contact Center performance issues to rule out
virtualization performance problems. All deviations from the published specifications must be
investigated and resolved before the Contact Center software investigation is initiated. For more
information, refer to the VMware vSphere documentation.
To support troubleshooting VMware resourcing issues, collect information about the following
VMware Key Performance Indicators (KPIs).
VMware vSphere Host KPIs:
Physical CPU
- PCPU - Physical CPU usage.
- CPU load average - Average CPU load average of host.
Physical Memory
- SWAP/MB - Memory swap usage statistics.
VMware vSphere Virtual Machine (VM) KPIs:

vCPU
- CPU RDY - Time VM was ready to run, but was not provided CPU resource.
- CPU WAIT - Percentage of time spent in the blocked or busy wait state.
- AMIN - Reservation allocated.

- ASHRS - CPU shares allocated.

- CPU CSTP - Amount of time a Symmetric Multi-Processing (SMP) VM was ready to run, but
was delayed due to co-vCPU scheduling contention.
Disk I/O
- GAVG - Average guest operating system read latency per read operation.
- DAVG/rd - Average device read latency per read operation.
- DAVG/wr - Average device write latency per write operation.
- RESETS/s - Number of commands reset per second.
- ABRTS/s - Number of disk commands aborted per second.
Network
- %DRPTX - Percentage of packets dropped when transmitting.
- %DRPRX - Percentage of packets dropped when receiving.
Memory
- MCTLSZ - Amount of physical memory reclaimed memory balloon statistics.
Software Appliance Licensing

Contact Center License Manager supports only the Virtualized Environment deployment of Avaya
WebLM server.
When Contact Center License Manager starts, it extracts WebLM license keys from the remote
WebLM server. Contact Center License Manager then converts the WebLM license keys into local
PLIC license keys and distributes the keys to the Avaya Contact Center Select applications as
required. Contact Center License Manager distributes PLIC license keys to Contact Center Manager
Server, Contact Center Manager Administration, Communication Control Toolkit, Contact Center
Multimedia, and Avaya Media Server as required.
When Contact Center License Manager requests licenses from a remote Avaya WebLM server, it
reserves all the Contact Center licenses available on that server. Contact Center therefore supports
only the PLDS standard license file (SLF) type. Avaya Contact Center Select does not support the
WebLM Enterprise model. Contact Center supports WebLM in nodal contact centers. WebLM does
not support Contact Center corporate licensing.
Contact Center License Manager distributes nodal license keys to all configured Avaya Media
Servers in the solution. Configure Avaya Media Server as a Media Server in Contact Center
Manager Administration. Contact Center License Manager, when restarted, pushes license keys to
that Avaya Media Server. Do not configure WebLM licensing on Avaya Media Server servers.
How to obtain a license
Avaya Contact Center Select uses a remote WebLM server to provide nodal licensing control.
1. Obtain the Avaya WebLM host ID from the WebLM user interface.

Software Appliance Licensing
2. Use the WebLM host ID to obtain WebLM license keys from the Avaya Product Licensing
3. Enter these license keys on the remote Avaya WebLM server. Contact Center License
Manager connects to the remote WebLM server and uses the Contact Center-specific
license keys from it to control Contact Center licensed features. Contact Center does not
import the license file to a Contact Center server; WebLM stores the license file on the
WebLM server.
You can use the License Manager Configuration Utility to check which Contact Center features are
licensed and how many agent licenses are available.

hardware appliance
This section describes the Avaya Contact Center Select hardware appliance. The Avaya Contact
Center Select hardware appliance is a physical rack mount server with the application software
already loaded and partially preconfigured.
To deploy the Avaya Contact Center Select hardware appliance, you must activate the Windows
operating system using the provided MS Windows product key, configure the server network setting,
and then use a simple configuration wizard to rapidly commission the solution. At install time, the
Avaya Contact Center Select hardware appliance server automatically launches a simple
configuration wizard that you use to rapidly deploy a functional contact center solution. The Avaya
Contact Center Select hardware appliance server is preloaded with sample users, skillsets, and
contact center parameters. You can use this sample data to rapidly commission the solution and
make the first routed call and email contact. The Avaya Contact Center Select hardware appliance
server delivers quick and simplified contact center deployment. After the basic telephony and email
features are working, you can then configure multimedia contacts, multiplicity, custom prompts, and
other enhanced features and functions to improve your customers experience.
You must activate the Microsoft Windows operating system on the Avaya Contact Center Select
hardware appliance using the provided Microsoft Windows product key. The provided Microsoft
Windows product key is displayed on a sticker attached to the top of the Avaya Contact Center
Select hardware appliance server.
The following diagram shows the topology of a typical Avaya Contact Center Select hardware
appliance solution:

Hardware Appliance server specification
Hardware Appliance server specifications on page 75

Avaya Contact Center Select hardware appliance software specifications on page 77
Hardware Appliance Licensing on page 83
Hardware Appliance server specification

The Contact Center Hardware Appliance is a Dell R620 rack mount server preconfigured to support
Contact Center.
Contact Center is a collection of real-time applications running on the Microsoft Windows Server
2008 R2 SP1 operating system. Contact Center provides real-time call control, multimedia handling,
and real-time statistical reporting.
Important:
The Contact Center Hardware Appliance server supplied by Avaya is optimized to provide the
real-time computational, networking, and logging resources required by Contact Center. You
must not modify the Hardware Appliance server, unless instructed to do so by Avaya:
Do not add additional internal hardware devices to this server.
Do not change or upgrade the server BIOS version or settings.

Avaya Contact Center Select hardware appliance
Do not change the server hardware settings.

Do not update the server firmware.
Do not change or upgrade the device drivers.
Do not modify the hard disk partitions.
Do not change the Windows Update application settings on the server.
Do not upgrade the Java Runtime Environment (JRE) supplied on the Hardware Appliance.
Due to the real-time processing that Contact Center applications perform, you must not install any
other application class software on the server. You can install only the supported antivirus and
remote support utility class software on this server.
Install only the Microsoft Windows Server 2008 R2 SP1 Operating System patches and hotfixes
supported by Contact Center. For more information about the supported Operating System patches,
see the Contact Center Portfolio Service Packs Compatibility and Security Hotfixes Compatibility
List on www.avaya.com/support.
The following table lists the server specifications for the Contact Center Hardware Appliance Dell
R620 server.
Specification Quantity Configuration Comment
Form factor 1 Rack mount, 1U chassis PowerEdge R620 rack mount server.
CPU 2 Intel Xeon E5-2670 2.60GHz,
20M Cache, 8.0GT/s QPI,
Turbo, 8C, 115W,
DDR3-1600MHz
RAM 8 4GB RDIMM, 1333 MHz, Low
Volt, Dual Rank
Hard Disk 2 900 GB, SAS 6 Gbps, 2.5 The 900 GB hard disk is pre-configured
inch, 10K RPM Hard Drive with Operating System, application, and
database partitions.
RAID Controller 1 PERC H710 Integrated RAID
Controller, 512MB NV Cache
RAID Type N/A RAID-1 2x 900 GB hard disk drives
Optical Drive 1 16X DVD +/-RW Drive SATA
with SATA Cable
Network Interface 4 1 Gbps NICs on motherboard Only Ethernet supported.
Power supply 2 750 Watt AC auto-sensing, hot
pluggable Power Supply
Power cables 2 Power cables Localized to region.
Additional 2 front USB ports
interfaces
2 back USB ports
Front video connector

Avaya Contact Center Select hardware appliance software specifications
Specification Quantity Configuration Comment

Additional 1 Rack mount kit
hardware
Weight 55 lbs approximately
25 kilograms approximately
BTU/HR 2891 BTU/hr maximum per
750 W power supply.
Avaya Contact Center Select hardware appliance software

specifications
Avaya Contact Center Select is offered as a hardware appliance server. The Avaya Contact Center
Select hardware appliance server contains the following software:
Microsoft Windows 2008 Release 2 with Service Pack 1 64bit operating system. The
operating system is not activated until the end customer applies the Microsoft Windows license
attached to the server.
Avaya Media Server (Avaya MS) with Quick Fix Engineering (QFE) patches
Service Packs
Firewall policy
Configuration wizard
The Windows 2008 operating system on the shipped hardware appliance server is not activated.
The Contact Center hardware appliance provides a Microsoft Windows Server 2008 product license
key. The Microsoft Windows Server 2008 product license key is printed on a label attached to the
top of the Contact Center Hardware Appliance server. You must activate the Microsoft Windows
operating system within 30 days of the initial power-up. Otherwise the Avaya Contact Center Select
hardware appliance server stops working.
The following table shows the operating system on the Avaya Contact Center Select hardware
appliance server.

Operating System International Minimum Service Pack

Versions Supported Supported
Windows Server 2008 Release 2, English Service Pack 1
64-bit, Service Pack 1.

Center.



Service updates
Service packs
Important:


center servers.
Important:

IP address.

section.


used.
Center.

McAfee 8.8

vendor.
scheduled):
source.

Hardware Appliance Licensing

Warning:
hours.
Hardware Appliance Licensing

The Avaya Contact Center Select Hardware Appliance deployment option uses a Nodal Enterprise
license delivered as a WebLM XML file. This license file is used to control access to licensed
features such as multimedia contacts and multiplicity.
Contact Center License Manager provides central control and administration of licensing for Avaya
Contact Center Select. Each Contact Center License Manager includes a local instance of WebLM.
When the Contact Center License Manager service starts, it extracts WebLM license keys from the
local WebLM instance. Contact Center License Manager then converts the WebLM license keys into
local PLIC license keys and distributes the keys the Avaya Contact Center Select applications as
required.
Obtain the network interface MAC address of the Avaya Contact Center Select server. The
Hardware Appliance server has a pull-out information tag on the servers front panel. The
Avaya Contact Center Select server networking MAC address is printed on the underside of
this information tag.
Use the MAC address to obtain a nodal WebLM license file from the Avaya Product Licensing
You load the license file onto the Avaya Contact Center Select server as you run the
configuration utility when you are deploying the Avaya Contact Center Select server. When
Contact Center License Manager loads the license, if the unique number in the license does
not match the Avaya Contact Center Select server MAC address, then License Manager shuts
down and Avaya Contact Center Select cannot process contacts. If the unique number in the

license matches the Avaya Contact Center Select server MAC address, then License Manager
provides license keys, and Avaya Contact Center Select processes customer contacts.

Chapter 6: Solution capacity limits and
supported features
This section specifies the maximum capacity limits of Avaya Contact Center Select. This section
also specifies the telephony features and devices supported by Avaya Contact Center Select.
Avaya Contact Center Select maximum capacity limits on page 85
Avaya Contact Center Select maximum configuration limits on page 88
Avaya Contact Center Select supported features on page 88
Supported Telephony Features on page 94
Supported Telephony Devices on page 102
Remote access support on page 104
Communication Control Toolkit supported functionality on page 104
Avaya Contact Center Select maximum capacity limits

The maximum capacity for your solution is determined by your Avaya Contact Center Select
deployment and the IP Office voice and call recording platform.
Avaya Contact Center Select (ACCS) supports the following deployment options:
Avaya Contact Center Select DVD installed on an Entry-level PVI server.
Avaya Contact Center Select DVD installed on a Mid-range PVI server.
Avaya Contact Center Select DVD installed on a High-end 6core PVI server.
Avaya Contact Center Select Software Appliance (3x OVAs) deployed on a VMware ESXi host
server that meets the High-end 8core PVI server specification.
Avaya Contact Center Select Software Appliance (3x OVAs) deployed on a VMware ESXi host
server that meets the High-end 10core PVI server specification.
Avaya Contact Center Select Hardware Appliance.
You can install the Avaya Contact Center Select DVD on any server that meets the Platform Vendor
Independence (PVI) server specifications. The Avaya Contact Center Select DVD supports three

Solution capacity limits and supported features
levels of PVI server specification; Entry-level, Mid-range, and a High-end PVI server specification.
The maximum capacity figures for the Avaya Contact Center Select DVD depend on which PVI
server specification is used. The High-end specification supports Avaya Contact Center Select to its
maximum rated capacity.
The Avaya Contact Center Select software appliance is a set of VMware Open Virtual Appliance
(OVA) virtualized servers; an Avaya Contact Center Select OVA, an Avaya Media Server OVA, and
a WebLM OVA. You can deploy the Avaya Contact Center Select software appliance (3x OVAs) on
a VMware ESXi host server that meets the High-end 8core or 10-core server specifications. These
high-end server specifications support the same maximum agent capacity and call rate figures.
The Avaya Contact Center Select hardware appliance is a physical rack mount server with the
application software already loaded and partially preconfigured. The supplied rack mount server
supports Avaya Contact Center Select to its maximum rated capacity.
The following table specifies the maximum capacity values supported by the Avaya Contact Center
Select deployment types for each supported IP Office configuration.
Type Maximum IP Office (IPO) configuration
Capacity
IPO SE IPO SE - IPO SE - IPO IPO IPO IPO
- R620 DL360 DL120 500V2 500V2 500V2 500V2
SIP SIP TDM TDM
trunks trunks trunks trunks
no CR with CR no CR with CR
Entry- Maximum logged-in 60 60 60 60 30 40 30
Level agents
Server Maximum CCMA 10 10 10 10 10 10 10
(ACCS supervisors
DVD) Maximum System 1200 1200 1200 1200 600 800 600
Contact Rate See
Note 1
Maximum 150 / 150 / 300 150 / 150 / 150 / 150 / 150 /

multimedia rate 300 300 300 300 300 300
(WCph / Eph) See
Note 2
Mid- Maximum logged-in 150 150 125 60 30 40 30

Range agents
Server Maximum CCMA 30 30 30 30 30 30 30
(ACCS supervisors
DVD) Maximum System 3000 3000 2500 1200 600 800 600
Contact Rate See
Note 1
Maximum 300 / 300 / 600 300 / 300 / 300 / 300 / 300 /

multimedia rate 600 600 600 600 600 600
(WCph / Eph) See
Note 2

Avaya Contact Center Select maximum capacity limits
Type Maximum IP Office (IPO) configuration

Capacity
IPO SE IPO SE - IPO SE - IPO IPO IPO IPO
- R620 DL360 DL120 500V2 500V2 500V2 500V2
SIP SIP TDM TDM
trunks trunks trunks trunks
no CR with CR no CR with CR
High-End Maximum logged-in 250 250 125 60 30 40 30
Server agents
(ACCS Maximum CCMA 50 50 50 50 30 40 30
DVD or supervisors
3x OVA Maximum System 5000 5000 2500 1200 600 800 600
ESXi Contact Rate See
host) Note 1
See Note Maximum 600 / 600 / 600 / 600 / 600 / 600 / 600 /
3 multimedia rate 1200 1200 1200 1200 1200 1200 1200
(WCph / Eph) See
Note 2
Hardware Maximum logged-in 250 250 125 60 30 40 30

Appliance agents
Maximum CCMA 50 50 50 50 30 40 30
supervisors
Maximum System 5000 5000 2500 1200 600 800 600
Contact Rate See
Note 1
Maximum 600 / 600 / 600 / 600 / 600 / 600 / 600 /

multimedia rate 1200 1200 1200 1200 1200 1200 1200
(WCph / Eph) See
Note 2
Note 1: The Maximum System Contact Rate is the maximum supported contact rate for all contact types
combined. The Maximum System Contact Rate is the maximum number of voice and multimedia contacts
Avaya Contact Center Select can handle in one hour. For a voice only solution, the Maximum System
Contact Rate is the maximum voice call rate (BHCC).
Note 2: Multimedia contact rates are applicable only if Contact Center Multimedia (CCMM) is part of the
solution. Web Chats per hour (WCph). Email contacts per hour (Eph).
Note 3: The Avaya Contact Center Select software appliance is supported only on the High-end 8core or
10-core servers.
The rated capacities for the high end server types are the same whether virtualized or non-virtualized.
IP Office Call Recording (CR) is supported with IP Office 500V2. Avaya Contact Center Select supports
Call Recording up to the maximum number of supported logged-in agents. Above this maximum limit, no
one can leave a voicemail or record any other calls.

Figure 4: The maximum capacity values supported by the ACCS deployment types for each supported
IP Office (IPO) configuration
Avaya Contact Center Select maximum configuration

limits
The following table specifies the maximum overall configuration values supported by Avaya Contact
Center Select.
Parameter Maximum value
Maximum configured agents 1000
Maximum agents skillsets 500
Maximum skillsets per agent 20
Maximum agents per skillset 250
Maximum supervisors per skillset 50
Maximum supervisors per system 50
Avaya Contact Center Select supported features

The following table specifies the main features supported by Avaya Contact Center Select:

Feature Supported Provider

Voice Skills Based Routing Yes Avaya Contact Center Select
FIFO Queuing Yes Avaya Contact Center Select
Longest Idle Agent queuing Yes Avaya Contact Center Select
ANI Number Available Yes Avaya Contact Center Select
ANI Number Routing Yes Avaya Contact Center Select
DNIS Number Available No
DDI Number Routing Yes Avaya Contact Center Select
Night Service Yes Avaya Contact Center Select
Threshold overflow for skills Yes Avaya Contact Center Select
Visual External Alarm for Yes Avaya Contact Center Select
exceeded threshold
Voice Contact Classification Yes Avaya Contact Center Select and
Agent Desktop
Multi-parameter Screen Pop per Yes Avaya Contact Center Select
contact type per skillset
Music On Hold Yes IP Office
Multi Source Music on Hold No
OnHold Announcements No
Skill Announcements Yes Avaya Contact Center Select
Agent Ext In/DN Key Yes Avaya Contact Center Select and
IP Office with three line
appearance
Coverage to Voicemail Pro Yes Direct calls to an agent station
receive the configured coverage
treatment. Calls routed from
Avaya Contact Center Select to
Agents do not receive coverage
treatment.
Play Prompt and Collect Digits Yes Avaya Contact Center Select
Wallboards with API Yes Dev Connect and Avaya Contact
Center Select
Activity /Work Codes Yes Avaya Contact Center Select
Aux/Not Ready Reason Codes Yes Avaya Contact Center Select
After Call Work Codes Yes Avaya Contact Center Select
Real Time Display Indication Yes Avaya Contact Center Select
ACW/Act/AUX/NotRdy Codes
Three Line Operation (3 call Yes Avaya Contact Center Select and
appearance lines) IP Office
Browser Based Agent Desktop Yes Avaya Contact Center Select and
Agent Desktop

Feature Supported Provider

Browser Based Supervisor Yes Avaya Contact Center Select and
Desktop Agent Desktop
Supervisor Administration client
use Internet Explorer based
CCMA.
Supervisor Agent client
uses .NET-based Agent Desktop
thick client.
Toll Free Queuing Yes Avaya Contact Center Select
Telephone Only Mode operation No
TLS transport type No
SIP telephone support No
Report Creation Wizard No
Media Server Zoning No
Contact Center Network Based No
Routing
Mission Critical High Availability No
Remote/Off-Site agent support Yes
IPv6 networking No
Database customization import No
new Customer defined fields
The following table specifies the multimedia features supported by Avaya Contact Center Select:
Feature Sub feature Supported Provider
Multimedia Skills Based Yes
Routing
Multimedia Management Yes Avaya Contact Center
& Reporting Select
Multiplicity Yes Avaya Contact Center
Select
Email Contact Handling Yes Avaya Contact Center
Select
Email Auto Response Yes Avaya Contact Center
Select
Email Auto Acknowledge Yes Avaya Contact Center
Select
Customer Contact Yes Avaya Contact Center
History Select
Email Real Time Yes Avaya Contact Center
Reporting Select


Screen Pop based on Yes Avaya Contact Center
Email Select
Fax Contact Types Yes Avaya Contact Center
Select
Scanned Documents Yes Avaya Contact Center
Select
SMS Contact Inbound Yes Avaya Contact Center
Select
Web Communications Yes Avaya Contact Center
Select
Web Chat Yes Avaya Contact Center
Select
Web Call-back Yes Avaya Contact Center
Select
Co-browsing No
Outbound Preview/Progressive Yes Avaya Contact Center
Select
Self Service Integration
Self Service Data and No
CTI to external IVR
On board Avaya Media Yes
Server IVR - play prompt
and collect digits
Workforce Optimization
Bulk Voice Recording No Avaya Contact Center
Select
Selective Recording No Using IP Office buton
Agent Initiated No Using IP Office buton
Quality Monitoring No
Workforce Management/ No
Forecasting
External Threshold No
Alerter/Alarms
Multi-Site Reporting Yes For distributed agents in
an SCN network.
Supervisor /Agent Instant No
Messaging
OPEN QUEUE Contact No
Types
SOA Enabled IPO-CC No


IM (Routed) Contact No
Types
Predictive Outbound No
Agent Desktop No
Softphone H.323 or
SIP
Agent Greeting No
The following table specifies the reporting features supported by Avaya Contact Center Select:
Unified Multi Channel Yes Avaya Contact Center
Real-time and Historical Select
Reporting
Predefined Real-time and Yes Avaya Contact Center
Historical Reports Select
Customer Customizable Yes Avaya Contact Center
Reports Select
Customer Definable Yes Using third-party tools
Reports interfacing using Avaya
Contact Center Select
ODBC
Historical Reports
Scheduled Yes Avaya Contact Center
Select
Interval Yes Avaya Contact Center
Select
Daily Yes Avaya Contact Center
Select
Weekly Yes Avaya Contact Center
Select
Monthly Yes Avaya Contact Center
Select
Quarterly No
Skillset Yes Avaya Contact Center
Select
Trunk No
Agents Yes Avaya Contact Center
Select
Abandoned Contacts Yes Avaya Contact Center
Select


Overflow Contacts Yes Avaya Contact Center
Select
Threshold Exceeded Yes Avaya Contact Center
Select
Contact Classification Yes Avaya Contact Center
Select
Source Of Disconnect Yes Avaya Contact Center
Select
Agent Station Key No
Email Report Yes Avaya Contact Center
Notifications Select
System Status Reports Yes Avaya Contact Center
Select
The following table specifies Avaya Contact Center Select product interoperability:
Product name Supported

Avaya Aura Workforce Optimization (WFO) No. Use IP Office call
recording.
Proactive Outreach Manager (POM) No

Avaya Aura Experience Portal No
Avaya IQ Reporting No
Avaya Control Manager Agent and Supervisor Administration No
Avaya Proactive Contact No

Avaya one-X Agent No
Social Media Manager No

Avaya Aura Presence Services No
Microsoft Lync Peer-to-peer IMs are
supported. Routed IMs
are not supported.
The following table specifies the Open Interfaces supported by Avaya Contact Center Select:
Open Interface name Supported
Real-time Statistics Multicast (RSM) Yes
Real-Time Display (RTD) Yes
Database Integration Wizard (DIW) and Host Data Exchange (HDX) Yes
Contact Center Multimedia (CCMM) Advanced Email Services Yes
Contact Center Manager Administration (CCMA) Open Interfaces Only for IP Office user
data synchronization with

Open Interface name Supported

Avaya Contact Center
Select
Contact Center Multimedia Open Interfaces Only for standard Web
Chat communications.
(Not supported for Agent
Desktop or Outbound.)
Contact Center Multimedia Outbound Open Interfaces No
Communication Control Toolkit (CCT) Open Interfaces No
Open Queue No
Open Networking No
Meridian Link Services (MLS) No
Communication Control Toolkit .NET SDK No
Contact Center Manager Server (CCMS) Open Interfaces No
Avaya Contact Recording APIs No
Supported Telephony Features

The following tables list the IP Office telephony features available to a non-agent IP Office user and
specify which features are supported on an Avaya Contact Center Select agent station.
Basic Call Handling:
IP Office IP Office user station Avaya Contact Center Notes
telephony support Select agent station
feature name support
Personal CC Personal calls CC calls
calls calls
Tones Yes Yes No No Agent Desktop does not play
specific tones dependent on
geography.
Caller ID Yes Yes Yes Yes
Call Screening Yes No No No
Hold Yes Yes Yes Yes
Toggle Calls Yes Yes No No Toggle calls is not applicable to
Avaya Contact Center Select
agents with 3-line appearance.
Hold Call Yes Yes No No Same as Auto-hold-allowed.
Waiting
Hold Music Yes Yes Yes Yes Provided by IP Office.
(Music on
Hold)


telephony support Select agent station
feature name support
calls calls
Park Yes No No No
Automatic Yes No No No
Callback
Direct Inward Yes Yes Yes Yes
Dialing (DID/
DDI)
Transfer Yes Yes Yes Yes
Distinctive and Yes No No No
Personalized
Ringing
Personalized Yes Yes No No
Ringing
Message Yes No No No Supported on some physical
Waiting stations. Not supported by
Indication Agent Desktop.
(MWI)
Contact Center (CC) calls are
prevented from going to
voicemail so cannot result in
MWI light on telephone.
However, an agent handling a
CC call sees the MWI light on
their telephone if a personal
call results in a new voicemail
message while handling the
CC call.
Visual Voice Yes No No No Supported on some IP

Office stations only and not by
Agent Desktop.
Contact Center (CC) calls are
prevented from going to
voicemail so cannot result in
messages that can be
processed using Visual Voice
on telephone. However, an
agent servicing a CC call can
use Visual Voice on their
telephone while servicing the
CC call.
Advanced Call Handling:


telephony feat support Select agent station
ure name support
calls calls
Absence Text Yes Yes No No
Call Tagging Yes Yes No No The Call Tagging feature is
equivalent to the Avaya
Contact Center Select Call
Attached Data feature.
Reclaim Call Yes No No No
Hunt Group Yes Yes No No Ability of a user to enable and
Enable/Disable disable their membership of
hunt groups.
Call Waiting Yes N/A Yes N/A If an Avaya Contact Center
Select agent is active on a call,
then another CC call is not
routed to that agent.
If an Avaya Contact Center
Select agent is active on
personal call, a CC call is not
routed to the agent.
Do Not Disturb No No No No Avaya Contact Center Select
(DND) agents use NotReady (with
reason code).
Dial Plan N/A N/A N/A N/A Refers to the dial plan
configuration on the IP Office.
Configure a dial plan to route
calls to extensions and agents.
Paging Yes Yes No No Telephone must have a
loudspeaker.
Intrude Yes Yes No No Avaya Contact Center Select
Supervisors can use Observe
or Barge-in features.
Inclusion Yes Yes No No
Private Call Yes Yes No No
Hot Desking Yes Yes N/A N/A This feature allows a number
of users non-exclusive use of
the same extension. Once
logged in, any calls to that user
are routed to the physical
extension they are logged in at.
Remote Hot Yes Yes N/A N/A This feature is the same as
Desking Hot Desking but refers
specifically to a user


ure name support
calls calls
configured on a particular node
logging in to an extension
configured on another node in
the Small Community Network
(SCN).
Relay On/Off/ N/A N/A N/A N/A
Pulse
Pickup Yes No No No
Call Recording Yes Yes No No
Telecommuter No No No No
Mode
Twinning and No No No No
Mobility
Key and Lamp Operation:

ure name support
Personal calls CC Personal calls CC calls
calls
Appearance N/A N/A N/A N/A
Buttons
Line N/A N/A N/A N/A Three lines maximum. A Line
Appearance Appearance is a
representation of a trunk line
on the IP Office system where
the indicator tracks the activity
on the Line. Only external calls
can be answered or made on
Line Appearances.
Call Yes Yes No* No* Individual calls are represented
Appearance individually on Agent Desktop,
Buttons but there is no concept of
selecting a particular call
appearance button which
corresponds to the telephone.
Alerting/Ring Yes No No No IP Office blocks Avaya Contact
Tone for Center Select calls from
Covered Calls covering.


ure name support
Personal calls CC Personal calls CC calls
calls
Bridged No No No No
Appearance
Buttons
External Call Yes No No No
Lamp
Indication
Call Coverage Yes No Yes No IP Office blocks Avaya Contact
Center Select calls from
covering.
Call Coverage Yes N/A No N/A
Buttons
Outbound Call Handling:

ure name support
calls calls
Account Codes Yes Yes No No
Authorization Yes Yes No No
Codes
Dial Emergency Yes N/A No No The Dial Emergency feature is
equivalent to the ACCS
Emergency Call feature.
Call Barring N/A N/A N/A N/A Avaya Contact Center Select
independent
Alternate Route Selection (ARS):

ure name support
calls calls
Maximum Call Yes Yes Yes Yes Avaya Contact Center Select
Length independent
Transferable Yes N/A No N/A Avaya Contact Center Select
Dial Out independent
Privilege


ure name support
calls calls
Idle Line Yes N/A No N/A Avaya Contact Center Select
Preference independent
Alternate Route N/A N/A N/A N/A Configure IP Office to select
Selection appropriate trunk to route calls
on.
Forwarding:
ure name support
calls calls
Coverage to Yes No No No
Operator
Forward on Yes No No No
Busy
Forward on No Yes No No No
Answer
Forward Yes No No No
Unconditional
Unconditional Yes No No No
Forward to
Voicemail
Forward Hunt Yes No No No
Group
Follow Me Yes No No No
Avaya telephone features:

ure name support
Personal CC calls Personal calls CC calls
calls
Programmable Yes Yes No No
Buttons
Busy Lamp Yes Yes No No Avaya Contact Center Select
Field (BLF) independent
Indicators


ure name support
Personal CC calls Personal calls CC calls
calls
Call History Yes Yes No No
Language Yes Yes No No Agent Desktop language is
determined by the OS settings
on the Agent Desktop client
computer, not from the
language configured for the IP
Office extension.
Centralized Yes Yes No No
Personal
Directory
Centralized Yes Yes No No
System
Directory
Self- No No No No Avaya Contact Center Select
Administration agents are not allowed to
modify telephone properties.
On Hook Dialing Yes Yes Yes Yes
Inbound Call Handling. Applies only in Failover Mode to IP Office Hunt Groups:
ure name support
calls calls
Incoming Call Yes Yes Yes Yes IP Office system configuration
Routing decides where incoming calls
are routed. Once call routing is
configured, calls to agents are
displayed on the telephone and
in Agent Desktop.
Hunt Groups Yes N/A Yes N/A
Multi-site Yes N/A Yes N/A
Networking/
Small
Community
Networking
(SCN)
Distributed Hunt
Night Service Yes N/A Yes N/A
Time Profiles Yes No Yes No


ure name support
calls calls
Queuing Yes N/A Yes N/A Configure system to limit the
number of calls that can be
waiting to be serviced in a hunt
group. For example, when all
parties in the group are busy.
Announcements Yes N/A Yes N/A Configure system to play
announcements to calls waiting
to be services in a hunt group.
Contact Center features:

ure name support
Personal CC calls Personal CC calls
calls calls
Acquire Call Yes No No No Acquire Call can behave like
(Call Steal) Reclaim Call or Call Pickup
depending on how it is invoked
and the state of the two users
involved.
Monitor Calls Yes No No No A user can monitor other
partys calls by listening in.
Queue N/A N/A N/A N/A Queue Threshold Alert applies
Threshold Alert only in Failover Mode to IP
Office Hunt Groups.
Login N/A N/A N/A N/A Login applies only in Failover
Mode to IP Office Hunt Groups.
System Short Codes:

ure name support
calls calls
User Short Yes Yes No No
Codes
System Short Yes Yes No No
Codes


ure name support
calls calls
Post-Dialing Yes Yes No No
Short Codes
Incoming Yes Yes No No
Number Short
Codes
Miscellaneous Features:
ure name support
calls calls
Conference Yes Yes Yes Yes
Calls
Coaching/Silent Yes Yes No No
Intrusion/
Whisper Page
Dial On Pickup No No No No This IP Office feature is also
known as Hotline. The feature
automatically dials a specified
extension when the telephone
is taken off hook. Do not
configure this feature for
Avaya Contact Center Select
agents.
Off Hook N/A N/A N/A N/A Analog station feature not
Operation supported by Avaya Contact
Center Select.
E911 Yes N/A Yes N/A
Emergency Call
Supported Telephony Devices

This section specifies the telephony connection types and devices supported in an Avaya Contact
Center Select solution. The Avaya Contact Center Select solution supports all of the IP Office
platform trunks types. There is no direct integration between the Avaya Contact Center Select and

Supported Telephony Devices
IP Office trunking interfaces. The Avaya Contact Center Select contact center functionality is
independent of these IP Office trunks.
The following table list the stations and telephone types supported by Avaya Contact Center Select.
Agent Phone Phone Model Avaya Contact Center Notes
Select Supported
Analogue All Models No
Digital 9500 Series Yes
1400 Series Yes
5400 Series Yes
2400 Series
IP: H.323 96x1 Yes
96x0 Yes
1600 Series Yes
5600 Series Yes
4610/4620x
IP: SIP All Models No
DECT All Models No
Wi-Fi Wireless All No
Models
Avaya Communication No
Server 1000
IP Office Softphone Yes Supported as co-resident
softphone on agent
workstation with Agent
Desktop. Not supported
as Integrated softphone.
The following table shows the Avaya Contact Center Select agent experience for various phone
types.
Phone Type Skillset on Agent Desktop Skillset on the phone PSTN Recording
Ringing Connected Ringing Connected Number Indication
96x0 (9640) Yes Yes Yes Yes Yes Yes

96x1 (9641) Yes Yes Yes Yes Yes Yes
56xx (5610) Yes Yes Yes No Yes Yes
16xx (1616) Yes Yes Yes Yes Yes Yes
Softphone Yes Yes Yes Yes Yes No
95xx (9504) Yes Yes Yes Yes Yes No

Phone Type Skillset on Agent Desktop Skillset on the phone PSTN Recording
Ringing Connected Ringing Connected Number Indication

14xx (1408) Yes Yes Yes Yes Yes Yes
Remote access support

Avaya Contact Center Select supports remote access using the following:
Microsoft Windows Remote Desktop
IP Office Support Services (IPOSS)
Both of these support remote troubleshooting and technical support.
Communication Control Toolkit supported functionality

This section compares the features supported by Avaya Contact Center Select using Avaya IP
Office with the features supported by Avaya Aura Contact Center using Avaya Aura
Communication Manager or Avaya Communication Server 1000 (CS 1000).
Communication Control Toolkit and Agent Desktop implement and use these features. Agent
Desktop is a client of Communication Control Toolkit so they support the same features.
The following tables list the basic Communication Control Toolkit call control functions.
Table 1: Basic Communication Control Toolkit and Avaya Aura Agent Desktop functions
Event SIP-enabled Avaya AML-based Avaya Avaya Contact Center

Aura Contact Center Aura Contact Center Select using IP Office
with Avaya Aura or using CS 1000
CS 1000
Make Call Yes Yes Yes

Hold Current Call Yes Yes Yes
The CS 1000 Swap The CS 1000 Swap
Hold switch feature is Hold switch feature is
not supported. not supported.
For CS 1000, the Auto

Hold Allowed (AHA)
feature must be
configured.


CS 1000
Unhold Call Yes (Retrieve Call) Yes (Retrieve Call) Yes

Drop Current Call (Release) Yes Yes Yes
Blind Transfer Call No Yes No
Initiate Supervised Transfer Yes Yes Yes
Complete Transfer Yes Yes Yes
Initiate Conference Call Yes (up to six parties Yes (up to six parties) Yes
on CS 1000)
Complete Conference Call Yes Yes Yes
Call Forward No Yes No
Cancel Call Forward No Yes No

Join Conference Yes, Avaya Aura only No Yes
Deflect Calls No No No
Get Status Yes Yes Yes
Get Call Capabilities Yes Yes Yes
Get Data Yes Yes Yes
Delete Data Yes Yes Yes
Append Data Yes Yes Yes
Make Set Busy (Do Not No Yes (on Agent No
Disturb) Terminals only)
Get/Set UUI Yes No (UUI attached as Yes
call data)
Send DTMF (for example, Yes Yes Yes
credit card number to IVR)
DTMF is not supported
in Knowledge Worker
solutions.
Mute/Unmute No No No
Consult Yes Yes (but must Yes
designate as transfer or
conference)
Park/Unpark No No No
Message Waiting Indicator No No No
HER (Host Enhanced No Yes No
Routing)
Answer Yes Yes Yes

The fast transfer functionality does not support completing a fast transfer call to an external trunk
number. This functionality is for predictive dialing environments in which the application sends a
MakeCall request to an external customer number and, when the customer answers, the application
sends the FastTransfer request to blind transfer the customer to a live agent.
The following table lists the Contact Center specific functions supported by Agent Desktop and
Communication Control Toolkit.
Table 2: Contact Center-specific functions

CS 1000
Agent Login Yes Yes Yes
Agent Logout Yes Yes Yes
Set Ready Yes Yes Yes
Set Not Ready Yes Yes Yes
ACD Set Activity Code Yes Yes Yes
ACD Set Not Ready/Reason Yes Yes Yes
Code
ACD Set After Call Work Item Yes Yes Yes
Code
Work Ready Key support No No No
Agent Whisper No No No
Observe call Yes No Yes
Set Call treatment No Yes No
Barge In Yes No Yes
Call Supervisor Yes Yes Yes
Emergency Key Yes Yes Yes
Redirect to another skillset No, must transfer to a No No, must transfer to a
CDN (Route Point) CDN (Route Point)
Return a call to the queue No No No
skillset that it came from
Redirect to another skillset No No No
Return a call to the queue No No No
skillset that it came from
The following table lists the events delivered by Communication Control Toolkit.

Table 3: Communication Control Toolkit events

CS 1000
Ringing Event Yes Yes Yes
Dialtone Event No No No
Busy Event No No No
Offering Event Yes Yes Yes
Ringback Event Yes Yes Yes
Inbound Connected Event Yes Yes Yes
Outbound Connected Event Yes Partial Yes
Connected Event Yes Yes Yes
Disconnected Event Yes Yes Yes
Held Event Yes Yes Yes
Unheld Event Yes Yes Yes
OnHold Pending Conference Yes Yes Yes
Event
Onhold Pending Transfer Yes Yes Yes
Event
Transferred Event Yes Yes Yes
Conference Event Yes Yes Yes
Initiated Transfer Event Yes Yes Yes
Initiated Conference Event Yes Yes Yes
Session Disconnect Event Yes Yes Yes
(includes shutdown)
Device Forward Event No No No
Status Change Event Yes Yes Yes
Notice Message Waiting No No No
Event
Notice No Message Waiting No No No
Event
Agent Logged out Event Yes Yes Yes
Agent Logged in Event Yes Yes Yes
Agent Ready Event Yes Yes Yes
Agent Not Ready Event Yes Yes Yes
Agent Busy Event No No No
Agent Work Ready Event No No No
Activity Code Entered Yes Yes Yes


CS 1000
WalkAway Activated No No No
WalkAway Return No No No
Emergency Invoked No No No
Call Supervisor Invoked No No No

Chapter 7: Administration client computer
requirements
This section provides the configuration requirements for the browser-based Avaya Contact Center
Select administration client computers. Install this client computer to configure and administer Avaya
Contact Center Select resources, to monitor performance, and to generate (real-time and historical)
reports. You can also use this client computer to upload and download data using the Configuration
Tool spreadsheets.
Administrator computer hardware requirements

The following table lists the minimum hardware requirements for the Administrator client computer.
This specification also applies to the Supervisor client computer and to computers that run Agent
Desktop Displays.
Table 4: Client computer minimum hardware requirements
Hardware item Minimum requirements Additional information

CPU 1 Gigahertz (GHz) or faster CPU Physical Address Extension (PAE), NX
with support for PAE, NX, and processor bit (NX), and Streaming SIMD
SSE2 Extensions 2 (SSE2) are features of the
processor. These CPU features are
required to run Microsoft Windows 7.0 and
Microsoft Windows 8.1.
Dual- and quad-CPU systems are
supported with or without Hyper-Threading
enabled.
AMD processors of the same or higher
specification are also supported.
RAM 1 Gigabyte (GB) (32-bit) or 2 GB Additional memory is required, if you run
(64-bit) other memory intensive applications.
Hard disk space 16 GB (32-bit) or 20 GB (64-bit)
Hard disk partitioning No specific partitioning
requirements
Hard disk speed > 7200 RPM

Administration client computer requirements

Floppy drive Not required If a floppy drive is installed, it must be A.
DVD ROM Not required
Network interface One network interface card 100 Mb/s Ethernet or higher is
recommended.
Video card Microsoft DirectX 9 graphics device 1024 x 768 pixels minimum resolution
with WDDM driver
Keyboard One keyboard
Mouse One mouse
Client operating system requirements

The following table lists the operating system requirements for client computers.
Table 5: Client operating system requirements
Operating system International versions Minimum service pack

supported
Windows 7 (32-bit and 64-bit) English
French (FR)
German (DE)
Italian (IT)
Latin Spanish (ES)
Brazilian Portuguese (PT-BR)
Russian (RU)
Simplified Chinese (Zh-CN)
Windows 8.1 English
French (FR)
German (DE)
Italian (IT)
Latin Spanish (ES)
Russian (RU)
Windows Server 2008 Release 2 English
Standard Edition and Enterprise Editions
French (FR)
64-bit
German (DE)


supported
Italian (IT)
Latin Spanish (ES)
Russian (RU)

This section describes the third-party software requirements for the administration client computer.
The following components are required on the administration client PC:
Microsoft Internet Explorer 8.0 (32-bit version only), 9.0 (32-bit version only), 10.0 (32-bit
version only), and 11.0 (32-bit version only).
Note:
You must run Internet Explorer in compatibility mode for Contact Center Manager
Administration and Communication Control Toolkit.
Microsoft Excel 2007 or later (for Configuration Tool only)
Contact Center Manager Administration supports only the 32-bit version of Microsoft Internet
Explorer.

Chapter 8: Agent Desktop computer
requirements
This section provides the configuration requirements for the Agent Desktop client computers. Agent
Desktop is a single-interface client application used by contact center agents to interact with
customers. Agents download and install Agent Desktop client software from the Avaya Contact
Center Select server. Avaya Contact Center Select agents use the Agent Desktop software in
conjunction with an IP Office provisioned telephone.
Note:
Agent Desktop does not support touch screen devices or tablets.
Agent Desktop localized languages

Agent Desktop is supported in the following localized languages:
English
French
German
Italian
Latin Spanish
Brazilian Portuguese
Russian
Simplified Chinese
A single Avaya Contact Center Select solution, with the localization language patches installed,
supports all of the Agent Desktop localized languages. For example, a single English language
Voice and Multimedia Contact Server supports the English, Chinese, French, and Russian language
versions of Agent Desktop client software.
Avaya Contact Center Select supports Agent Desktop client operating systems that use a different
language family to the Contact Center server.

Agent Desktop computer hardware requirements
Agent Desktop computer hardware requirements

The following table lists the minimum hardware requirements for a computer running Agent Desktop
software.
Table 6: Agent Desktop computer minimum hardware requirements

CPU 1 Gigahertz (GHz) or faster CPU Physical Address Extension (PAE), NX
with support for PAE, NX, and processor bit (NX), and Streaming SIMD
SSE2 Extensions 2 (SSE2) are features of the
processor. These CPU features are
required to run Microsoft Windows 7.0 and
Microsoft Windows 8.1.
Dual- and quad-CPU systems are
supported with or without Hyper-Threading
enabled.
RAM 1 Gigabyte (GB) (32-bit) or 2 GB Additional memory is required, if you run
(64-bit) other memory intensive applications at the
same time as Agent Desktop.
Hard disk space 16 GB (32-bit) or 20 GB (64-bit)
Hard disk partitioning No specific partitioning
requirements
Hard disk speed > 7200 RPM
Floppy drive Not required If a floppy drive is installed, it must be A.
DVD ROM Not required
Network interface One network interface card 100 Mb/s Ethernet or higher is
recommended.
Video card Microsoft DirectX 9 graphics device 1024 x 768 pixels minimum resolution
with WDDM driver
Keyboard One keyboard
Mouse One mouse
Agent Desktop does not support touch screen devices or tablets.
Client operating system requirements

The following table lists the operating system requirements for client computers.

Agent Desktop computer requirements
Table 7: Client operating system requirements

supported
Windows 7 (32-bit and 64-bit) English
French (FR)
German (DE)
Italian (IT)
Latin Spanish (ES)
Russian (RU)
Windows 8.1 English
French (FR)
German (DE)
Italian (IT)
Latin Spanish (ES)
Russian (RU)
Windows Server 2008 Release 2 English
Standard Edition and Enterprise Editions
French (FR)
64-bit
German (DE)
Italian (IT)
Latin Spanish (ES)
Russian (RU)
Agent Desktop client network infrastructure requirements

Agent Desktop is a client application which communicates with the Avaya Contact Center Select
server. For optimal Agent Desktop operation, the underlying contact center network infrastructure
must provide adequate latency and bandwidth between the agent computer and the Avaya Contact
Center Select server.

This section provides a high-level overview of the data that is passed between Agent Desktop and
the Avaya Contact Center Select server. It also sets out the recommended network values and likely
impacts on agents if these values are not met. This section also describes the performance of Agent
Desktop in varying Round Trip Time (RTT) and bandwidth environments.
Important:
Agent Desktop performance degrades as network Round Trip Time increases and network
bandwidth decreases.
Network Latency
Network latency is a measure of the time delay experienced in a system, measured in Round Trip
Time (RTT). RTT is the average Round Trip (packet) Time as measured using the ping command
for a 1024-byte (1KB) data size.
For optimal performance, Avaya recommends a RTT of less than 80ms from the Agent Desktop
client computer to the following Avaya Contact Center Select components:
The RTT from the Agent Desktop client PC to the Avaya Contact Center Select server must be less
than 120ms.
RTT impacts on Voice traffic

This section describes how the underlying RTT and latency of the network affects the experience of
handling voice traffic in Agent Desktop.
Agent Desktop used with a physical desk phone

The CCT component sends Computer Telephony Integration (CTI) signals to Agent Desktop, for
example to prompt Agent Desktop to alert an incoming contact. These CTI signals are passed
across the network as data. However, if the agent is using a physical desk phone, voice packets are
transported across a network.
The following table details the time taken for the contact to alert on the Agent Desktop, compared to
the time taken for the same contact to ring on the agents phone, where the phone is subject to a
constant RTT of 1ms.
RTT (ms) Delay between desk phone ring and Delay between clicking Accept button on
call alert on Agent Desktop Agent Desktop and active voice path
1ms LAN <0.5 Seconds <0.5 Seconds
50ms 0.5 Seconds 1.0 Seconds
120ms 1.0 Seconds 2.5 Seconds
RTT impact on Multimedia Contacts

Contact Center Multimedia contacts are also affected by network latency. Agent Desktop downloads
Customer contacts from the Avaya Contact Center Select server and displays their contents as soon
as they are fully retrieved.
The table below shows how varying RTTs affect multimedia contact display times in this case,
email contacts on Agent Desktop. The Customer Details/Customer History Display column
indicates how much time passes between the email being opened on the Agent Desktop and the
additional context information being loaded and displayed. These sample times are for ideal
laboratory conditions.
RTT (ms) Email Display Customer Details/Customer History Display
1ms LAN 2 Seconds 0 Seconds
50ms 3 Seconds Additional 3 Seconds
This data was generated using a 20KB email message, a customer history containing 30 contacts of
20KB each, in a network where bandwidth is not limiting the data transfer. Email messages of
different sizes generate different results.
Bandwidth
The network bandwidth available to Agent Desktop client computers for communication with Avaya
Contact Center Select servers is critical to Agent Desktop performance. If voice traffic is carried on
the same network, this traffic is often prioritized above other network traffic this bandwidth is
therefore not available to Agent Desktop. In many cases agents use other third party applications
over the same network. The bandwidth requirements of these third party applications must be
considered as part of the overall bandwidth calculations (in addition to bandwidth allocated for voice
soft phones and for Agent Desktop).
Several factors affect the recommended bandwidth for Agent Desktop. Depending on which Contact
Center Multimedia (CCMM) features are in use on a given Customer deployment, not all factors
apply. Indicative calculations to estimate the actual bandwidth usage are presented below for the
various contact types and features. To calculate the required bandwidth, the relevant figures for the
deployed features and supported contact types can be combined to derive an overall figure.
The network usage can be one of two types:
Constant These require dedicated, permanently available network use for the lifetime of the
traffic consumption. Examples of this type of traffic include; statistics display in Agent Desktop,
update of live Web chat contacts.
Many factors influence constant traffic levels, for example the number of agents with a large
number of assigned skillsets, the number of active supervisors running RTDs in unicast mode,
and large numbers of skillsets in use (large data packet) even for multicast.
Bursty The display of multimedia contacts and multimedia contact history is bursty traffic. A significant
traffic amount of data is downloaded to the Agent Desktop over a number of seconds. The frequency
of these download is driven by agent activity.
These require high usage of the available network for short times to download bursts of data.
The time window that this data takes to download depends on the available network
bandwidth at that time. Since this is not constant network consumption, a Kilo bits per second

value is not reflective of the bandwidth required and a Kilo bit value has been provided
instead.
Bandwidth impacts on Voice

If the agents are using a physical desk phone for voice or any other application which utilizes
network bandwidth, this needs to be factored into the engineering of the network to meet the
expected performance levels on Agent Desktop.
Retrieve Customer History on voice contacts

The Agent Desktop Customer History feature enables agents to retrieve voice callers multimedia
Customer history, from the Avaya Contact Center Select server, when a voice contact is accepted.
Agent Desktop Customer History is an optional feature which is enabled in the CCMM
Administration tool. These historical contacts can be of any multimedia contact type. Agent Desktop
Customer History requires adequate bandwidth to function and it must be included in your network
bandwidth planning calculations.
To calculate the impact of a voice callers multimedia Customer history on bandwidth, consider voice
contacts as an additional Multimedia contact type and add the number of voice contacts to your
multimedia calculation for bandwidth calculations.
Multimedia Contact bandwidth requirements

This section details the bandwidth requirement of Agent Desktop Customer History for the following
multimedia contact types:
Email messages
Fax messages
Scanned Documents (SD)
SMS text messages
Outbound contacts
Web Communications (WCs)
This section also details the bandwidth requirement for voice contact types if multimedia history
display is enabled.
Some multimedia contact supports attachments and these attachments must also be included in
network calculations:
Email contacts are of variable size. The average email size is a reasonable estimate, and is
used for Agent Desktop calculations.
Fax messages are delivered as email attachments. Fax messages must be included in the
attachment size and rate estimates.
Outbound contacts from Avaya Contact Center Select solution do not have attachments.
SMS test messages from customers. SMS test messages do not have attachments.
Web chat messages do not have attachments.
The Agent Desktop Customer History feature enables agents to retrieve multimedia Customer
history (containing up to 30 previous contacts), from the Avaya Contact Center Select server, when

a multimedia contact is accepted. Agent Desktop Customer History requires adequate bandwidth to
function and it must be included in your network bandwidth planning calculations. Retrieving Agent
Desktop Customer history from the Avaya Contact Center Select server uses the bursty type of
network data, and where the Customer history feature is enabled, it must be included in all network
bandwidth calculations.
Example of calculating the bandwidth requirements of Agent Desktop Customer history downloads
(based on ideal laboratory conditions ):
N = Number of agents working on multimedia (MM) contacts. If the feature to display multimedia
history with voice calls is activated, then N must include voice agents.
C = Maximum number of multimedia contacts per hour for the entire contact center solution. If the
feature to display multimedia history with voice calls is activated, then C must include voice traffic
per hour to all those agents.
avg_contact_size = average size of a contact in Kbits (not Kbytes). (Kbits = KBytes * 8). In many
cases this is the average size of the incoming or outgoing email.
att_rate_in = percentage of incoming contact attachments. Contact attachments apply to email
messages and fax messages.
att_rate_out = percentage of incoming email messages that are responded to with agent attached
attachments in the reply.
avg_att_size = average size of an attachment in Kbits . Contact attachments apply to email
messages and fax messages.
Note:
In-line attachments must also be included in the bandwidth calculations as regular attachments.
A key factor in calculating the minimum bandwidth for processing multimedia contacts is an
assessment of the number of active agents that accept contacts in any one second period. The
available bandwidth is shared across all of these agents in this time period.
The long term average number of agents active in any one second is calculated as follows:
naverage = Roundup( C / 3600 )
This equates to the average number of agents clicking the Accept button on the Agent Desktop at
any one time. However, since the length of time it takes an agent to handle a contact is random, the
number of agents clicking the Accept button is random. It is incorrect to engineer a bandwidth
solution based solely on this average, as nearly 50% of the time more than naverage agents are
clicking the Accept button.
Therefore the number of active agent per second is calculated with a factor F as follows:
nactive = Roundup( F* C / 3600 )
where F is an engineering factor between 3 and 10. A higher value for F must be used when N, the
total number of agents processing multimedia contacts and multimedia history with voice contact, is
lower than 50. The choice of value F is your decision. F reflects the amount of extra bandwidth to
build into your network to handle both the inherently random distribution of agent activity which
results in natural peaks of use and any data spike events attributable to your particular Contact
Center business models, such as initial shift start times, promotions and emergencies. A higher
value reduces the level of bandwidth limitation caused by the overlapping of multiple agent
download of multimedia contacts.

Once F is defined, the minimum bandwidth (in Kbits per second) can be estimated as follows:
BWMMmin =
nactive * ( (avg_contact_size * 64) + 2000) + avg_att_size * (att_rate_in% + att_rate_out%) / 100 )
Kbps
Important:
The minimum recommended bandwidth available for processing multimedia contacts BWMMmin
must be greater than 10 Mbits per second.
The time to download and display contacts on Agent Desktop is directly impacted by the bandwidth
available between the Avaya Contact Center Select server and Agent Desktop at the time when the
contact is accepted in Agent Desktop. The impact of bandwidth limitation is observed as a delayed
display of contact and contact history in the Agent Desktop.
The following table demonstrates the impact of limiting bandwidth on multimedia contact display
times on Agent Desktop. The data was generated using a 20KB email message, a Customer history
of 30 contacts of 20KB size each, with a fixed RTT of 80ms.
Available bandwidth Email display Customer Details/Customer History Display
1Mbps 3 Seconds Additional 6 Seconds
3Mbp 3 Seconds Additional 3 Seconds
5Mbps 3 Seconds Additional 2 Seconds
Retrieve Customer History on Voice contacts

This optional feature enables Agent Desktop to retrieve voice callers multimedia Customer history
(containing up to 30 previous contacts), from the Avaya Contact Center Select server, at the time a
voice contact is accepted. These historical contacts can be of any multimedia contact type. If this
feature is activated, the size of this history can be added to your network planning by considering
voice as an additional multimedia contact type and adding the number of voice contacts to your
multimedia calculation.
Web Communication (WC) network bandwidth calculation

Processing web communications, after they have been received by the agent requires a constant
level of bandwidth.
Network usage type: Constant
c = Number of WC contacts per hour
avg_session_length = Average length in seconds of WC session
Data size: 50 Kbps per active WC contact
WC network bandwidth requirement (Kbps):
WCBW = (c * 50Kbps * avg_session_length)/ 3600
Presence network bandwidth calculation

Presence updates require a constant level of bandwidth.

Network usage Type: Constant
N = Number of agents working on MM contacts
avg_pres = Average number of presence updates per user per hour
Data size: 7 Kb per Presence update
Presence network bandwidth requirement (in Kbps) = (N* 7Kb * avg_pres)/ 3600
CCMM Search network bandwidth calculation

Bandwidth must be provided for an agent carrying out multimedia searches.
Network usage Type: Bursty
N = Number of agents running searches
average_search = Average number of searches per hour
Data transmitted: 1280Kb per search
CCMM Search bandwidth requirement (in Kbps) = (1280Kb * average_search * N)/3600
CCMM Pull Mode network bandwidth calculation

Pull Mode allows agents to work outside the normal Avaya Contact Center Select routing mode.
They personally select individual contacts from the Avaya Contact Center Select queues. Their view
of the Avaya Contact Center Select queue is automatically updated using the same web services as
the Avaya Contact Center Select CCMM search feature, and so uses the same bandwidth.
N = Number of agents working in Pull Mode
c = Number of contacts per hour per agent
Data transmitted: 1280Kb per search
CCMM Pull Mode search bandwidth requirement (in Kbps) = (1280Kb * c * N)/3600
Web Statistics network bandwidth calculation

Network usage Type: Bursty
N = Number of agents
avg_skills = Average number of skillsets per agent
Data transmitted: 3.2 Kb per skillset once a minute
Web Statistics bandwidth requirement: (3.2 Kb * avg_skills * N)/60
Agent Desktop downloads by agent

Agent Desktop is a smart client which is downloaded from the Avaya Contact Center Select server
over the network onto each agent computer on initial install. On each software update (service pack
or patch) the updated Agent Desktop is re-downloaded onto each agent computer. The download
requirements of Agent Desktop must be considered when planning the bandwidth requirements to
remote agents.

Agent Desktop network ports
Summary of total bandwidth requirements

You must sum up all the applicable bandwidth demands listed above to arrive at a minimum
bandwidth for the site. Calculate the cumulative bandwidth for all multimedia features.
Agent Desktop network ports

Agent Desktop uses the following network ports to communicate with Contact Center components.
Feature Component Port number
HTTP (Web services) CCMM 80
HTTP (Web services) CCMM 443 (if SSL is enabled for CCMM)
CCT CCT 29373
Voice History CCMS 57772
Web Statistics CCMS 9086

port matrix
This section lists the ports used by Avaya Contact Center Select. The Avaya Contact Center Select
server contains the following components:
Avaya Media Server (Avaya MS)
These components use the following ports.
Contact Center Manager Server port requirements

Contact Center Manager Server uses ports for communication between its own components. Most
ports do not have implications for external network components like firewalls; however some ports
might be used externally and therefore can affect an external firewall. In particular, port 10000 is a
hard-coded port used to enable interoperability between Contact Center applications and external
third-party applications (applications developed using the Real-Time Data (RTD) API).
No third-party application installed on Contact Center Manager Server can use the ports listed in the
following table as it can cause the Contact Center Manager Server application to malfunction.
The following table shows the ports that Contact Center Manager Server uses.
Table 8: Contact Center Manager Server port usage
CCMS port number Functionality

445 TCP port used Windows File and Printer Sharing for Microsoft Networks.
Required when copying data between active and standby servers using
Windows File Sharing.

Contact Center Manager Administration port requirements
CCMS port number Functionality

1550 HDX CAPI
1972 Cach database, and Cach shadowing
4422 HDX NameService
1266812670 TraceControl
10000 Hardcoded Toolkit Name Service
1000110082 Networking
10038 NCP_CHANNELThis channel is used to communicate between the NCP of
one node to the NCP of another node. The NCP on one node sends sanity
messages to the other node through this port.
10039 ASM_CHANNELDifferent modules like NCP and TFE send messages to
ASM through this channel.
10040 NCP_ASM_CHANNELASM uses this channel to send messages to NCP.
10060 ASM_ServiceThe ASM service runs on this port. The Service Control
Manager can send messages such as START, STOP, and RESTART to the
ASM service through this port.
10062 NCP_ServiceThe NCP service runs on this port. The Service Control
Manager can send messages such as START, STOP, and RESTART to
NCP on this port.
3998 License Manager destination portThis is the first of 10 consecutive ports
required for license management.
39994007 License Manager client source port
3389 Remote Desktop Connection for support
50605061 SIP Proxy
5070 For communication with coresident Avaya Media Server
90809083 Web Services Open Interfaces
9086 CC Web Statistics
9100 XMPP Web Service Server Port
9120 XMPP Web Service Client Port
57012 System Management and Monitoring Component (SMMC) system tray. Used
by the High Availability feature.
Contact Center Manager Administration port requirements

The following table shows the ports that Contact Center Manager Administration uses.

Avaya Contact Center Select port matrix
Table 9: Contact Center Manager Administration port usage
CCMA port number Functionality

TCP 80 For Internet Explorer communication.
TCP 443 For secure HTTP communication (only applicable if SSL is enabled for secure
Internet Information Services (IIS) communication).
TCP Ports 389 and 636 For Active Directory Lightweight Directory Services (AD-LDS) functionality.
Port 389 is for LDAP, and port 636 is for SSL.
When you install CCMA on a server that runs Window Server 2008, these
ports usually appear by default in the Port Configuration for AD-LDS
installation window. If the values 50000 and 50001 appear instead, port
numbers 389 and 636 are already taken. In this case, you can either accept
the new values, or choose other ports for security reasons.
TCP Port 445 Windows File and Printer Sharing for Microsoft Networks. Required when
copying data between active and standby servers using Windows File Sharing.
TCP Port 3389 For remote desktop connection.
TCP Port 25 (SMTP) For the Historical Reporting component to send email notifications when
reports are printed and saved.
3899, 6366 For AD-LDS when CCMA is co-resident with Avaya Media Server.
TCP Port 8200 For the Emergency Help component on the client PC.
UDP ports 6020, 6030, For the CCMA server to receive IP multicasting data from CCMA Server
6040, 6050, 6060, 6070, (needed for Real-Time Reporting and Agent Desktop Displays).
6080, 6090, 6100, 6110,
6120, 6130
UDP ports 7020, 7030, For the CCMA server to send IP multicasting data to client PCs (needed for
7040, 7050, 7060, 7070, Real-Time Reporting and Agent Desktop Displays).
7080, 7090, 7100, 7110,
7120, 7130
UDP ports 7025, 7035, For the CCMA server to send IP unicast data to client PCs. This is an optional
7045, 7055, 7065, 7075, method of sending the data required for Real-Time Reporting. If you do not
7085, 7095, 7105, 7115, use the multicast method, then you must configure the unicast option. You can
7125, 7135, 7140, 7150, also use a combination of the two methods.
7145 and 7155
TCP Port 10000 Used by the Nameservice process on the CCMA server (nbnmsrvc.exe). It
permits communication between the CCMA server and the server in Contact
Center Manager Server.
Important:
The default port for the third-party software. This conflicts with the default
port used by the CCMA Toolkit NameService. To avoid issues with
CCMA functionality when using Veritas Backup Exec, you must change
the default port of Veritas Backup Exec to another port number that is not
being used by the network.
Default UDP port 3998 License Manager destination port.

Communication Control Toolkit port requirements
CCMA port number Functionality

Default UDP ports 3999 - License Manager destination source port.
4007
Communication Control Toolkit port requirements

The following table shows the port numbers required for Communication Control Toolkit (CCT).
Table 10: Communication Control Toolkit port usage
CCT port number Functionality

1972 Cach database, and Cach shadowing High Availability solutions.
3998 License Manager (LM) destination port, which is the first of 10 consecutive
ports required for license management.
3999 - 4007 LM client source ports.
5000 To connect to the server in CCMS.
8081 Default port of the Apache Tomcat Server which hosts the CCT Web
Administration.
8085 For CCT services to access the CCT database.
8098 For the Contact Management Framework on the CCT server.
8099 For the Contact Management Framework on the CCT server.
8087 For CCT CMF component.
9000 For CCT WebAdmin component.
9010 For CCT CMF component.
11110 Used by the CCT Server service for the CMF Web Service - Callback port.
11111 Used by the CCT Server service for the CMF Web Service - Web server port.
29373 Listens for requests from CCT client applications.
29374 Data Access Layer Service listens for requests from CCT Remote
Administration Console.
Contact Center Multimedia port requirements

The following table lists the configurable Multimedia ports.

Table 11: Contact Center Multimedia ports
Port Host Client Network interface Functionality

1972 Contact Center Contact Center Contact Center Port opened on
Multimedia Manager Multimedia Cach database for
Administration database reporting. Cach
Server database, and
Cach shadowing
in High Availability
solutions.
445 Windows File and Windows File and Windows File and Windows File and
Printer Sharing for Printer Sharing for Printer Sharing for Printer Sharing for
Microsoft Networks. Microsoft Networks. Microsoft Networks. Microsoft Networks.
Required when
copying data
between active and
standby servers
using Windows File
Sharing.
110 Email server Email Manager Email server POP3 Receiving email
143 Email server Email Manager Email server IMAP Receiving email
995 Email server Email Manager POP3 over SSL Receiving secure
(optional) email (optional)
993 Email server Email Manager IMAP over SSL Receiving secure
110 Email server Email Manager POP3 over TLS Receiving secure
143 Email server Email Manager IMAP over TLS Receiving secure
25 Email server Email Manager SMTP Sending email
25 Email server Email Manager SMTP over TLS Sending secure
80 Contact Center Any Web services SOAP protocol Accessing http Web
Multimedia Server client (Agent services
Desktop, OCMT,
and third-party Web
services)
29373 Communication Agent Desktop Communication Remote access
Control Toolkit Control Toolkit from clients to
Server Communication
Control Toolkit
server (for Agent
Desktop
application)
57012 System System System High Availability
Management and Management and Management and

Avaya Media Server port requirements
Port Host Client Network interface Functionality

Monitoring Monitoring Monitoring
Component Component Component
(SMMC) system (SMMC) system (SMMC) system
tray tray tray

The following table shows the port numbers required for Avaya Media Server on Windows Server
2008.
Table 12: Avaya Media Server port usageWindows Server 2008
Port Type Permit in TCP Description

Filter
1027 TCP Yes License Server
1028 TCP No System Monitor mchb
3306 TCP Yes MySQL
3389 TCP Yes Remote Desktop
3867 SCTP No Diameter over SCTP
3868 TCP No Diameter over TCP
3869 TCP No Diameter over TLS
4001 TCP No IvrMP MSLink
4004 TCP No Sip UA MSLink
4005 TCP No Resource Manager ExtSess
4014 TCP No SIP UA cmd i/f
4015 TCP No Resource Manager and i/f
5060 TCP Yes SIP over TCP
5060 UDP No SIP over UDP
5061 TCP Yes SIP over TLS
6080 TCP No Agent Greeting
7080 TCP No ConfMP MSLink
7410 TCP Yes SoapServer
7411 TCP Yes SoapServer TLS
8080 TCP Yes EM/UCM HTTP
8443 TCP Yes EM/UCM HTTP(s)
11004 TCP No DiamC MSLink
11014 TCP No DiamC and i/f


Filter
19899 TCP Yes Resource Manager CPLink
19999 TCP Yes IvrMP ssdata
20005 TCP Yes CStore MSLink
20007 TCP Yes CStore RTFT
20009 TCP Yes IvrMP RTFT
21000 TCP No Voice XML Interpreter IPC
51000 TCP No Resource Manager IPC
51001 TCP No Legacy MPS Alarm deamon
51003 TCP No CCXML Interpreter IPC
The following table shows the port numbers required for Avaya Media Server on Linux.
Table 13: Avaya Media Server port usageLinux

Filter
1027 TCP Yes License Server
1028 TCP No System Monitor mchb
3306 TCP Yes MySQL
3867 SCTP No Diameter over SCTP
3868 TCP No Diameter over TCP
3869 TCP No Diameter over TLS
4001 TCP No IvrMP MSLink
4004 TCP No Sip UA MSLink
4005 TCP No Resource Manager ExtSess
4014 TCP No SIP UA cmd i/f
4015 TCP No Resource Manager cmd i/f
5060 TCP Yes SIP over TCP
5060 UDP No SIP over UDP
5061 TCP Yes SIP over TLS
6080 TCP No Agent Greeting
7080 TCP No ConfMP MSLink
7410 TCP Yes SoapServer
7411 TCP Yes SoapServer TLS
8080 TCP Yes EM HTTP
8443 TCP Yes EM HTTP(s)
11004 TCP No DiamC MSLink


Filter
11014 TCP No DiamC and i/f
19899 TCP Yes Resource Manager CPLink
19999 TCP Yes IvrMP ssdata
20005 TCP Yes CStore MSLink
20007 TCP Yes CStore RTFT
20009 TCP Yes IvrMP RTFT
20011 TCP No Resource Manager IPC
21000 TCP No Voice XML Interpreter IPC
UDP Port Range is required for media processing. All starting UDP ports are configurable.
Table 14: Required UDP Port Range
Operating System UDP Port Range

Windows Server 2008 20000 to 45499
Linux 6000 to 32599

Index
Numerics G
10core CPU ........................................................... 35, 37, 61 global requirements server name ............................ 42, 52, 78
6core CPU ................................................................... 35, 36 guidelines for Java Runtime Environment ............... 44, 54, 80
8core CPU ....................................................... 35, 36, 48, 60 guidelines for service packs .....................................43, 54, 79
guidelines for service updates ................................. 43, 53, 79
guidelines for utility software ....................................44, 55, 80
A
Agent Desktop requirements ............................................. 112 H
antivirus software .....................................................45, 55, 81
Avaya Media Server ............................................................ 57 hardware ..............................................................................74
Avaya Media Server port requirements ............................. 127 hardware appliance ....................................................... 74, 75
Avaya Security Advisory ...................................................... 29 Hardware Appliance ............................................................ 83
hardware-assisted virtualization .......................................... 63
hardware requirements ................................3337, 48, 60, 61
B hardware requirements, Administrator ...............................109
BIOS .............................................................................. 38, 65 hardware requirements, Agent Desktop ............................ 113
High-end solution .........................................3537, 48, 60, 61
host considerations vmware ................................................ 63
C Hyper-Threading ............................................................40, 67
call recording ....................................................................... 27
capacity limits ...................................................................... 85 I
CCMA port requirements ................................................... 123
CCMM port requirements .................................................. 125 interactions with external multimedia servers ...................... 25
CCMS port requirements ................................................... 122 IOPS .................................................................................... 70
CCT port requirements ...................................................... 125 IP Office support .................................................................. 18
CCT supported functionality .............................................. 104
client requirements ............................................................ 109 J
configuration ........................................................................ 19
Java Runtime Environment guidelines .................... 44, 54, 80
D
L
data synchronization ............................................................14
DHCP .......................................................................44, 54, 80 licensing ...................................................................47, 72, 83
disk caching ................................................................... 40, 66 Licensing ..............................................................................12
DVD ................................................................... 31, 33, 41, 47 limitations .............................................................................28
localized languages ........................................................... 112
E
M
email message flow example ...............................................26
Entry-level server .................................................................33 maximum capacity ............................................................... 85
ESXi host specification ........................................................ 59 Mid-range server ..................................................................34
external server interactions ..................................................25 multimedia external server interactions ............................... 25
F N
firmware ......................................................................... 39, 65 naming server requirements .................................... 42, 52, 78
functions of telephony server .............................................104 network requirements ........................................................ 114
NUMA ............................................................................ 40, 66

Index
O T
Open Virtual Appliance ........................................................ 51 Telephony Devices ............................................................ 102
operating system Java Runtime Environment guidelines telephony features ............................................................... 94
..................................................................................44, 54, 80 telephony server functions .................................................104
operating system packs guidelines ..........................43, 54, 79 third-party software ............................................................ 111
operating system requirements ................................. 110, 113 touchscreen ....................................................................... 113
operating system service update guidelines ............43, 53, 79 touch screen ...................................................................... 113
P U
performance ...................................................................38, 65 unused hardware ........................................................... 41, 67
performance management .............................................39, 65 utility software guidelines .........................................44, 55, 80
port matrix ..........................................................................122
port requirements Avaya Media Server ............................. 127
port requirements CCMA ................................................... 123
V
port requirements CCMM .................................................. 125 videos .................................................................................... 8
port requirements CCMS ................................................... 122 virtualization .........................................................................67
port requirements CCT ...................................................... 125 Virtualization ........................................................................ 71
ports ...................................................................................121 virtualization considerations .................................................62
PVI ....................................................................................... 33 VMware ................................................................................67
vmware host ........................................................................ 63
R VMware host specification ................................................... 59
VMXNET ..............................................................................68
RAID .............................................................................. 40, 66
remote access support ...................................................... 104
requirements Java Runtime Environments ..............44, 54, 80
W
requirements port Avaya Media Server ............................. 127 WebLM ................................................................................ 59
requirements port CCMA ................................................... 123
requirements port CCMM .................................................. 125
requirements port CCMS ................................................... 122
requirements port CCT ...................................................... 125
requirements server name .......................................42, 52, 78
requirements service packs ..................................... 43, 54, 79
requirements service updates ..................................43, 53, 79
requirements utility software .................................... 44, 55, 80
S
sample flows ........................................................................ 22
security ................................................................................ 29
server name requirements .......................................42, 52, 78
service packs guidelines ..........................................43, 54, 79
service updates guidelines ...................................... 43, 53, 79
snapshot considerations ................................................ 68, 69
software ............................................................................... 74
software appliance ...............................................................49
software specifications .........................................................77
software utility guidelines .........................................44, 55, 80
support
contact ............................................................................ 9
supported main features ...................................................... 88
supported multimedia features ............................................ 88
supported reporting features ................................................88


Avaya Contact Center Select Solution Description 01.01 June 2014

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Avaya Contact Center Select Solution Description 01.01 June 2014

Uploaded by

Copyright:

Available Formats

Avaya Contact Center Select Solution

4 Avaya Contact Center Select Solution Description June 2014

Guidelines for the use of antivirus software........................................................................55

June 2014 Avaya Contact Center Select Solution Description 5

Agent Desktop network ports................................................................................................121

6 Avaya Contact Center Select Solution Description June 2014

Category Title Description Audience

June 2014 Avaya Contact Center Select Solution Description 7

Category Title Description Audience

Viewing Avaya Mentor videos

8 Avaya Contact Center Select Solution Description June 2014

About this task

June 2014 Avaya Contact Center Select Solution Description 9

10 Avaya Contact Center Select Solution Description June 2014

June 2014 Avaya Contact Center Select Solution Description 11

Avaya Contact Center Select supports the following licensed features:

12 Avaya Contact Center Select Solution Description June 2014

Name Description Notes

June 2014 Avaya Contact Center Select Solution Description 13

User Data Synchronization

14 Avaya Contact Center Select Solution Description June 2014

Figure 1: Typical Avaya Contact Center Select DVD deployment

June 2014 Avaya Contact Center Select Solution Description 15

Figure 2: Typical Avaya Contact Center Select software appliance solution

16 Avaya Contact Center Select Solution Description June 2014

Figure 3: Typical Avaya Contact Center Select hardware appliance solution

June 2014 Avaya Contact Center Select Solution Description 17

IP Office supported versions

18 Avaya Contact Center Select Solution Description June 2014

Overview of solution configuration

June 2014 Avaya Contact Center Select Solution Description 19

Avaya Contact Center Select installation

Simple voice call flow example

20 Avaya Contact Center Select Solution Description June 2014

June 2014 Avaya Contact Center Select Solution Description 21

Sample Orchestration Designer voice flow applications

22 Avaya Contact Center Select Solution Description June 2014

Sample Voice Prompt variables

June 2014 Avaya Contact Center Select Solution Description 23

Prompt name Prompt variable name Prompt transcript Orchestration Designer

24 Avaya Contact Center Select Solution Description June 2014

Prompt name Prompt variable name Prompt transcript Orchestration Designer

Multimedia contacts processing

June 2014 Avaya Contact Center Select Solution Description 25

Simple email message flow

26 Avaya Contact Center Select Solution Description June 2014

June 2014 Avaya Contact Center Select Solution Description 27

28 Avaya Contact Center Select Solution Description June 2014

Avaya Security Advisories

June 2014 Avaya Contact Center Select Solution Description 29

Upgrades and migrations

30 Avaya Contact Center Select Solution Description June 2014

June 2014 Avaya Contact Center Select Solution Description 31

32 Avaya Contact Center Select Solution Description June 2014

Platform Vendor Independence server specification

Entry-level server specification

June 2014 Avaya Contact Center Select Solution Description 33

Specification Configuration Comment

Mid-range server specification

34 Avaya Contact Center Select Solution Description June 2014

Specification Configuration Comment

High-end server specifications

June 2014 Avaya Contact Center Select Solution Description 35

High-end 6core server specification