0% found this document useful (0 votes)
22 views16 pages

R17 CMS Capacities

Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
22 views16 pages

R17 CMS Capacities

Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 16

Avaya Call Management System

Capacities

Release 17
July 2014
© 2014 Avaya Inc. All Rights Reserved. Concurrent User License (CU). End User may install and use the Software on
multiple Designated Processors or one or more servers, so long as only the
Notice licensed number of Units are accessing and using the Software at any given
While reasonable efforts have been made to ensure that the information in this time. A “Unit” means the unit on which Avaya, at its sole discretion, bases the
document is complete and accurate at the time of printing, Avaya assumes no pricing of its licenses and can be, without limitation, an agent, port or user, an
liability for any errors. Avaya reserves the right to make changes and e-mail or voice mail account in the name of a person or corporate function
corrections to the information in this document without the obligation to notify (e.g., webmaster or helpdesk), or a directory entry in the administrative
any person or organization of such changes. database utilized by the Software that permits one user to interface with the
Software. Units may be linked to a specific, identified Server.
Documentation disclaimer
Named User License (NU). You may: (i) install and use the Software on a
“Documentation” means information published by Avaya in varying mediums single Designated Processor or Server per authorized Named User (defined
which may include product information, operating instructions and performance below); or (ii) install and use the Software on a Server so long as only
specifications that Avaya generally makes available to users of its products. authorized Named Users access and use the Software. “Named User”, means
Documentation does not include marketing materials. Avaya shall not be a user or device that has been expressly authorized by Avaya to access and
responsible for any modifications, additions, or deletions to the original use the Software. At Avaya’s sole discretion, a “Named User” may be, without
published version of documentation unless such modifications, additions, or limitation, designated by name, corporate function (e.g., webmaster or
deletions were performed by Avaya. End User agrees to indemnify and hold helpdesk), an e-mail or voice mail account in the name of a person or corporate
harmless Avaya, Avaya's agents, servants and employees against all claims, function, or a directory entry in the administrative database utilized by the
lawsuits, demands and judgments arising out of, or in connection with, Software that permits one user to interface with the Software.
subsequent modifications, additions or deletions to this documentation, to the
Shrinkwrap License (SR). You may install and use the Software in
extent made by End User.
accordance with the terms and conditions of the applicable license
Link disclaimer agreements, such as “shrinkwrap” or “clickthrough” license accompanying or
applicable to the Software (“Shrinkwrap License”).
Avaya is not responsible for the contents or reliability of any linked websites
referenced within this site or documentation provided by Avaya. Avaya is not Heritage Nortel Software
responsible for the accuracy of any information, statement or content provided
on these sites and does not necessarily endorse the products, services, or “Heritage Nortel Software” means the software that was acquired by Avaya as
information described or offered within them. Avaya does not guarantee that part of its purchase of the Nortel Enterprise Solutions Business in December
these links will work all the time and has no control over the availability of the 2009. The Heritage Nortel Software currently available for license from Avaya
linked pages. is the software contained within the list of Heritage Nortel Products located at
http://support.avaya.com/LicenseInfo/ under the link “Heritage Nortel
Warranty Products”. For Heritage Nortel Software, Avaya grants Customer a license to
Avaya provides a limited warranty on its hardware and Software (“Product(s)”). use Heritage Nortel Software provided hereunder solely to the extent of the
Refer to your sales agreement to establish the terms of the limited warranty. In authorized activation or authorized usage level, solely for the purpose specified
addition, Avaya’s standard warranty language, as well as information regarding in the Documentation, and solely as embedded in, for execution on, or (in the
support for this Product while under warranty is available to Avaya customers event the applicable Documentation permits installation on non-Avaya
and other parties through the Avaya Support website: equipment) for communication with Avaya equipment. Charges for Heritage
http://www.avaya.com/support Nortel Software may be based on extent of activation or use authorized as
Please note that if you acquired the Product(s) from an authorized Avaya specified in an order or invoice.
reseller outside of the United States and Canada, the warranty is provided to
Copyright
you by said Avaya reseller and not by Avaya. “Software” means computer
programs in object code, provided by Avaya or an Avaya Channel Partner, Except where expressly stated otherwise, no use should be made of materials
whether as stand-alone products or pre-installed on hardware products, and on this site, the Documentation, Software, or hardware provided by Avaya. All
any upgrades, updates, bug fixes, or modified versions thereto. content on this site, the documentation and the Product provided by Avaya
including the selection, arrangement and design of the content is owned either
Licenses by Avaya or its licensors and is protected by copyright and other intellectual
THE SOFTWARE LICENSE TERMS AVAILABLE ON THE AVAYA WEBSITE, property laws including the sui generis rights relating to the protection of
http://support.avaya.com/LicenseInfo/ ARE APPLICABLE TO ANYONE WHO databases. You may not modify, copy, reproduce, republish, upload, post,
DOWNLOADS, USES AND/OR INSTALLS AVAYA SOFTWARE, transmit or distribute in any way any content, in whole or in part, including any
PURCHASED FROM AVAYA INC., ANY AVAYA AFFILIATE, OR AN code and software unless expressly authorized by Avaya. Unauthorized
AUTHORIZED AVAYA RESELLER (AS APPLICABLE) UNDER A reproduction, transmission, dissemination, storage, and or use without the
COMMERCIAL AGREEMENT WITH AVAYA OR AN AUTHORIZED AVAYA express written consent of Avaya can be a criminal, as well as a civil offense
RESELLER. UNLESS OTHERWISE AGREED TO BY AVAYA IN WRITING, under the applicable law.
AVAYA DOES NOT EXTEND THIS LICENSE IF THE SOFTWARE WAS
Third-party components
OBTAINED FROM ANYONE OTHER THAN AVAYA, AN AVAYA AFFILIATE
OR AN AVAYA AUTHORIZED RESELLER; AVAYA RESERVES THE RIGHT Certain software programs or portions thereof included in the Software may
TO TAKE LEGAL ACTION AGAINST YOU AND ANYONE ELSE USING OR contain software (including open source software) distributed under third party
SELLING THE SOFTWARE WITHOUT A LICENSE. BY INSTALLING, agreements (“Third Party Components”), which may contain terms that expand
DOWNLOADING OR USING THE SOFTWARE, OR AUTHORIZING OTHERS or limit rights to use certain portions of the Software (“Third Party Terms”).
TO DO SO, YOU, ON BEHALF OF YOURSELF AND THE ENTITY FOR Information regarding distributed Linux OS source code (for those product that
WHOM YOU ARE INSTALLING, DOWNLOADING OR USING THE have distributed Linux OS source code) and identifying the copyright holders of
SOFTWARE (HEREINAFTER REFERRED TO INTERCHANGEABLY AS the Third Party Components and the Third Party Terms that apply is available
“YOU” AND “END USER”), AGREE TO THESE TERMS AND CONDITIONS in the Documentation or on Avaya’s website at:
AND CREATE A BINDING CONTRACT BETWEEN YOU AND AVAYA INC. OR http://support.avaya.com/ThirdPartyLicense/
THE APPLICABLE AVAYA AFFILIATE ( “AVAYA”). You agree to the Third Party Terms for any such Third Party Components.

Preventing Toll Fraud


Avaya grants you a license within the scope of the license types described
"Toll fraud" is the unauthorized use of your telecommunications system by an
below, with the exception of Heritage Nortel Software, for which the scope of
unauthorized party (for example, a person who is not a corporate employee,
the license is detailed below. Where the order documentation does not
agent, subcontractor, or is not working on your company's behalf). Be aware
expressly identify a license type, the applicable license will be a Designated
that there can be a risk of Toll Fraud associated with your system and that, if
System License. The applicable number of licenses and units of capacity for
Toll Fraud occurs, it can result in substantial additional charges for your
which the license is granted will be one (1), unless a different number of
telecommunications services.
licenses or units of capacity is specified in the documentation or other materials
available to you. “Designated Processor” means a single stand-alone Avaya Toll Fraud intervention
computing device. “Server” means a Designated Processor that hosts a
If you suspect that you are being victimized by Toll Fraud and you need
software application to be accessed by multiple users.
technical assistance or support, call Technical Service Center Toll Fraud
License type(s) Intervention Hotline at +1-800-643-2353 for the United States and Canada. For
additional support telephone numbers, see the Avaya Support website:
Designated System(s) License (DS). End User may install and use each
http://www.avaya.com/support. Suspected security vulnerabilities with Avaya
copy of the Software only on a number of Designated Processors up to the
products should be reported to Avaya by sending mail to:
number indicated in the order. Avaya may require the Designated Processor(s)
securityalerts@avaya.com.
to be identified in the order by type, serial number, feature key, location or other
specific designation, or to be provided by End User to Avaya through electronic
means established by Avaya specifically for this purpose.
Trademarks
The trademarks, logos and service marks (“Marks”) displayed in this site, the
Documentation and Product(s) provided by Avaya are the registered or
unregistered Marks of Avaya, its affiliates, or other third parties. Users are not
permitted to use such Marks without prior written consent from Avaya or such
third party which may own the Mark. Nothing contained in this site, the
Documentation and Product(s) should be construed as granting, by implication,
estoppel, or otherwise, any license or right in and to the Marks without the
express written permission of Avaya or the applicable third party.
Avaya is a registered trademark of Avaya Inc.
All non-Avaya trademarks are the property of their respective owners, and
“Linux” is a registered trademark of Linus Torvalds.
All other trademarks are the property of their respective owners.

Downloading documents
For the most current versions of documentation, see the Avaya Support
website:
http://www.avaya.com/support

Contact Avaya Support


See the Avaya Support website: http://support.avaya.com for product notices
and articles, or to report a problem with your Avaya product.
For a list of support telephone numbers and contact addresses, go to the
Avaya Support website: http://support.avaya.com, scroll to the bottom of the
page, and select Contact Avaya Support.
Contents

Chapter 1: Avaya CMS capacities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7


Using the capacity limits . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
Capacity descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
CMS R17, R17 R2, and R17 R3 Capacities . . . . . . . . . . . . . . . . . . . . . . . . . 10
Capacities in a VMWare configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
Optimizing CMS reporting efficiency . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
Skill based reporting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
Recommendations for custom reports . . . . . . . . . . . . . . . . . . . . . . . . . 14
Resources for system performance analysis . . . . . . . . . . . . . . . . . . . . . 15

Avaya CMS R17.0 Capacities July 2014 5


6 Avaya CMS R17.0 Capacities July 2014
Chapter 1: Avaya CMS capacities

This document describes the supported hardware platforms and capacities for the Avaya Call
Management System (CMS) Release 17 (R17), Release 17 R2 (R17 R2), and Release 17 R3
(R17 R3) software that can currently be purchased from Avaya.
This document includes the following topics:
● Using the capacity limits on page 7
● Capacity descriptions on page 7
● CMS R17, R17 R2, and R17 R3 Capacities on page 10
● Optimizing CMS reporting efficiency on page 14

Using the capacity limits


The capacities described in the following topics are the maximum limits that can be supported
by a particular CMS hardware platform. You must verify that none of the capacity limits is
exceeded for a particular hardware platform.
If you exceed even one of the capacity limits for a given hardware platform, you require the next
higher capacity hardware platform. For example, if you have less than 200,000 calls per hour,
but between 201 and 400 Supervisors, you must purchase a Dell R720 server.

Capacity descriptions
The following topics describe the measurements you must use to determine which CMS
hardware platform is required.

Peak busy hour call volume


The busy hour call volume capacity is the call volume during the busiest hour of the day.
Calculate the busy hour call volume by adding each trunk seizure or line appearance seized
during the busiest hour for all calls.

Avaya CMS R17.0 Capacities July 2014 7


Chapter 1: Avaya CMS capacities

Concurrent supervisors
The concurrent supervisors capacity is the total maximum number of CMS supervisors and
CMS terminal emulator logins that exist during the peak busy hour. The concurrent supervisors
capacity is not the number of authorized logins, but the number of logins actually used.
Note:
Note: This capacity limit is the sum of the login count from each client type, CMS
Supervisor Web client and CMS Supervisor PC Client.
Calculate the number of concurrent supervisors by counting the maximum number of supervisor
logins and terminal emulator logins that exist during the busy hour period. Each login counts as
one. Do not count the number of reports. This calculation must be 1600 or less.

Third-party software
The third-party software capacity is the number of external or third party interface applications.
Some examples of third-party interfaces are Blue Pumpkin, ODBC, wallboards, Geotel,
Operational Analyst, TCS, and IEX.
Calculate the amount of third-party software by counting the number of third party applications
used.

! Important:
Important: The one exception to this rule is Geotel, which counts as two applications.
Do not count each instance of the application. If you use wallboards, count the wallboards as
one application. Do not add up the total number of wallboards.

Agent/skill pairs
The agent/skill pairs capacity is the total number of agent/skill pairs.
Calculate this capacity by multiplying the number of agents by the number of skills each agent
can log in to. The number of agents and the number of skills are based on the switch
administration. For example, if there are 20 agents, and each agent is administered with 5 skills,
you would multiply agents by their skills for a value of 100 agent/skill pairs. You must count the
total number of skills administered for the agent, not the number of skills used by the agent.

Reports per Supervisor session


The reports per Supervisor session capacity is the average number of simultaneous real-time
reports each supervisor will run.

Report elements
The report elements capacity is the average number of report elements.
A report element is an entity that is monitored by an average real-time report. Report elements
are not the lines of data rendered on the report but the element that is chosen to run the report
against. Some examples of elements are VDNs, skills, and vectors.

8 Avaya CMS R17.0 Capacities July 2014


Capacity descriptions

Calculate this capacity by counting each element. You would count one element if a report is run
for one skill. It does not matter if the report has lines of data for each agent in the skill.

Active agent traces


The active agent traces capacity is the number of agent traces running on the CMS.

Average refresh rate


The average refresh rate capacity is the average refresh rate for real-time reports.
Calculate this capacity by averaging the refresh rates set by your report users. For example, if
one-half of the users use a 30-second refresh rate, and the other half use a 10-second refresh
rate, you would calculate an average of 20.

Percent refresh rate at three seconds


The percent refresh rate at 3 seconds capacity is the percentage of real-time report users that
require a refresh rate of 3 seconds.

Avaya CMS R17.0 Capacities July 2014 9


Chapter 1: Avaya CMS capacities

CMS R17, R17 R2, and R17 R3 Capacities


The following tables list the capacities for each hardware platform being sold for the new CMS
R17 installations or for the existing platforms being upgraded to CMS R17. Only T5120, T5220
and Netra X4270 systems can be upgraded to R17.

New shipments

Capacity R17 Low End R17 Midsize R17 R2 High End


Hardware Hardware Hardware
Platform Platform Platform
(Dell R620 low) (Dell R620 mid) (Dell R720)

Memory 8GB 16GB 64GB


Peak busy-hour call 10,000 200,000 400,000
volume
Concurrent 30 200 1,600
supervisors1
Concurrent Agents 4002 5,000 10,000
Third-party software 3 3 7
Agent skill pairs3 24,000 200,000 800,0002
Reports per 5 5 10
Supervisor session
Report elements 5 5 12
Active agent traces 200 1,000 5,000
30 seconds Average 10% at 3 50% at 3 100% at 3
refresh rate seconds seconds seconds
Internal Call History (ICH) 4,000 per 20 mins 4,000 per 20 mins 4,000 per 20 mins
records
External Call History 200,000 per 20 200,000 per 20 mins 200,000 per 20
(ECH) records mins mins
1. The total capacity of concurrent CMS Supervisors is the combined capacity of CMS Supervisor PC clients
and CMS Supervisor Web clients.
2. This concurrent agent capacity is effective in CMS R17 R3 in the ASD configurator.
3. CMS supports a system wide limit of 800,000 agent skill pairs, with a per ACD limit of 100,000 agent skill
pairs. See Maximum values with multiple ACD deployment for more information.

10 Avaya CMS R17.0 Capacities July 2014


CMS R17, R17 R2, and R17 R3 Capacities

The Dell R720 introduces new CMS system wide capacities. The new CMS system wide
capacities come with restrictions, so review Maximum values with multiple ACD deployment for
specific restrictions when using the higher system wide capacities.
Note:
Note: All per ACD capacities remain unchanged.
New system wide capacities

CMS attribute System wide capacity Per ACD capacity

Agent skill pair 800,000 100,000


Total VDNs 54,000 30,000
Total splits or skills 54,000 8,000
Total trunks 40,000 12,000
Total trunk groups 8,000 2,000
Total vectors 32,000 8,000
Total call work codes 4,000 1999
Agent trace records 5,100,000 5,100,000
(AAR)

The following table represents the maximum values with multiple ACD deployment on a Dell
R720 system supporting 800,000 agent skill pairs:
Maximum values with multiple ACD deployment

Basic Maximum Values

Agent/skill pairs 300k 300k 400k 500k 800k


Interval length (30) 30 15 30 30 30
Interval data days saved 31 31 15 31 15
Daily data days saved 1825 730 1825 730 730

Note:
Note: There is no impact on daily, weekly, and monthly limits. When the capacity limit of
agent skill pairs crosses 200,000, there is an impact on the interval data storage.

Avaya CMS R17.0 Capacities July 2014 11


Chapter 1: Avaya CMS capacities

Upgrades

Capacity Netra Sun Enterprise Sun Enterprise SPARC T4-1


X4270 T5120 4-core T5220
or T5120 8-core

Memory 4GB 4GB or 8GB 16GB 32GB 32GB 64GB


Peak busy-hour 200,000 200,000 250,000 400,000 400,000 400,000
call volume
Concurrent 200 200 400 800 800 1600
supervisors1
Concurrent 5,000 5,000 10,000 10,000
Agents
Third-party soft- 3 3 5 7 7 7
ware
Agent skill pairs2 200,000 200,000 200,000 200,000
Reports per 5 5 8 10 10 10
Supervisor
session
Report elements 5 5 8 12 12 12
Active agent 200 200 400 600 2,000 5,000
traces
30 seconds 10% at 3 10% at 3 seconds 50% at 3 100% at 3 100% at 3 100% at 3
Average refresh seconds seconds seconds seconds seconds
rate
Internal Call 4,000 per 4,000 per 20 4,000 per 20 mins 4,000 per 20 mins
History (ICH) 20 mins mins
records

External Call 200,000 200,000 per 20 200,000 per 20 mins 200,000 per 20 mins
History (ECH) per 20 mins
records mins
1. The total capacity of concurrent CMS Supervisors is the combined capacity of CMS Supervisor PC clients and CMS
Supervisor Web clients.
2. CMS supports a system wide limit of 200,000 agent skill pairs, with a per ACD limit of 100,000 agent skill pairs.

12 Avaya CMS R17.0 Capacities July 2014


Capacities in a VMWare configuration

Capacities in a VMWare configuration

Parameter Medium VMware Large VMware


configuration — about configuration — about
equivalent to midsized Dell equivalent to high-end
R620 with Linux Enterprise T4 with
Solaris

Peak busy-hour call volume 200,000 400,000


Concurrent supervisor sessions1 200 1,6002
Concurrent Agents 5,000 10,000
Third-party software 3 7
Agent skill pairs3 200,000 800,0003
Reports per Supervisor session 5 10
Report elements 5 12
Percentage of supervisors that 50% 100%
can run reports with a 3 second
refresh rate
Active agent traces 1,000 5,000
Internal Call History (ICH) records 4,000 per 20 mins 4,000 per 20 mins
External Call History (ECH) 200,000 per 20 mins 200,000 per 20 mins
records
1. This value is the total number of active CMS Supervisor PC client and CMS Supervisor Web client
sessions.
2. Of the 1600 sessions supported, only 800 can be CMS Supervisor Web client sessions.
3. Supporting 800,000 agent skill pairs requires greatly increased disk space for interval data. Customers
should create up to 8 additional disk volumes. See Deploying Avaya Call Management System in an
Avaya Customer Experience Virtualized Environment for full details on disk space usage recommenda-
tions.

Avaya CMS R17.0 Capacities July 2014 13


Chapter 1: Avaya CMS capacities

Optimizing CMS reporting efficiency


Avaya provides a powerful solution with CMS that enables you to create custom reports
designed to fit your individual needs. However, the overall capability of the CMS server is limited
by the memory and CPU of each server.
This section includes the following topics:
● Skill based reporting on page 14
● Recommendations for custom reports on page 14
● Resources for system performance analysis on page 15

Skill based reporting


The CMS server is optimized for skill based reporting. Avaya recommends that you create and
use reports on skills instead of Agent Group reports. Skills that do not receive actual calls can
be created on the Communication Manager. You can use these skills to provide reporting for the
agents that are placed in that skill.
To use Agent Group reports, follow the recommendations provided in Recommendations for
custom reports on page 14.

Recommendations for custom reports


When you design and use custom Agent Group reports, consider the following
recommendations to optimize system performance:
● Agent Groups
- The size of agent groups are recommended to be 99 agents or lesser. Agent groups of
size 99 agents or less are recommended because system performance can be
adversely affected.
Note:
Note: The agent group capacity of 99 agents or lesser is only available on Dell R720,
VMware large configuration, and Oracle T4.
- If possible, report on consecutive Agent IDs in the same report
- If possible, limit Agent Group reports and use skill based reports
● Number of agents or other elements in historical or real time reports

14 Avaya CMS R17.0 Capacities July 2014


Optimizing CMS reporting efficiency

- Carefully examine the number of agents, skills, VDNs, trunks, or other elements in one
report. Limit the number of agents or other elements in a single report as much as
possible.
● Custom report design
- In historical reports, there should be no input for multiple dates when running against
the interval database tables. Existing reports that allow multiple dates should be
modified to gain access to the appropriate daily/weekly/monthly table instead of the
interval table.
- Any historical report that takes longer than a few seconds to complete should be
reviewed for modification to improve performance.
- Any real-time report that takes more than a few milliseconds to refresh should be
reviewed or modified to improve performance.

Resources for system performance analysis


Customers can work with Avaya Professional Services to design and use custom reports in a
manner that maximizes system performance. The Avaya Professional Services organization
provides services that include a performance analysis of custom reports on a CMS system.
Avaya Professional Services can also provide recommendations on how to efficiently design
current or future reports in a manner that minimizes impact to CMS performance.

Avaya CMS R17.0 Capacities July 2014 15


Chapter 1: Avaya CMS capacities

16 Avaya CMS R17.0 Capacities July 2014

You might also like

pFad - Phonifier reborn

Pfad - The Proxy pFad of © 2024 Garber Painting. All rights reserved.

Note: This service is not intended for secure transactions such as banking, social media, email, or purchasing. Use at your own risk. We assume no liability whatsoever for broken pages.


Alternative Proxies:

Alternative Proxy

pFad Proxy

pFad v3 Proxy

pFad v4 Proxy