Collaboration Sizing Tool Field Reference

Collaboration Sizing Tool Field Reference
Page 1 of 118

This chapter provides a systematic reference, defining the function and meaning of the input fields in the Collaboration Sizing
Tool interface.
z
Starting Page
Identify Components
Unified Contact Center Enterprise
Unified Contact Center Express
Unified Communications Manager
Cisco Emergency Responder
Cisco Expressway
Voice Messaging
Cisco TelePresence
Cisco TelePresence Management Suite
Conferencing and Collaboration
Cisco Unified Presence (Unified Communications Manager IM and Presence Service)
Cisco MediaSense
Cisco Intercompany Media Engine
Management
Gateways Page
Solution Sizing Summary
Create Bill of Materials
Copyright 2015, Cisco Systems, Inc. All rights reserved.
Starting Page
This page appears when you run the Unified Communications Sizing Tool for the first time. The starting page provides the
following options:
z
Customer Name -This optional field lets you enter your customer name. This customer information is displayed when
you export your solution to PDF from the Solution Sizing Summary page. If you leave this information blank, nothing is
displayed beside Customer name in the PDF report.
Solution Name This mandatory field lets you save your solution by name. You can later review and add to the
solution. The solution name is saved as an .xml file in the MySavedSolutions folder in the user's default document
location.
My Saved Solutions The My Saved Solutions lists any saved solutions by name. You can open a saved solution by
clicking the solution name in the listing. If you have not saved any solutions, this box is empty.
New Unified Communications SolutionThis option lets you select a specific release of Cisco Unified Communications
Manager, and automatically restricts the sizing options to the components that are compatible with the selected Unified
CM release. To create a system release sizing scenario, specify the suggested components as listed in the System
Release column (on the page that appears after you click New Unified Communications Solution.
Load a Previously Saved Solution from XMLThis option is best for working on other solutions saved from the current
tool, or saved from prior versions of the tool.
If you are on another page in the sizing tool, and you wish to return to the Starting Page, click the Home option in the menu bar
that appears at the top and bottom of the sizing tool pages.
file:///C:/Users/Saidul/AppData/Local/Temp/~hhB9F9.htm
9/15/2015
Page 2 of 118
Identify Components
The following table describes the function of each field in the Components/Options section on the Identify Components page.
The fields provide drop-down lists containing the relevant component releases.
Specify the appropriate component release to include that component in the solution. Choose None if you do not want to
include the component.
Components / Options
Field
Description
This scenario will be sized based

on the following Unified CM
release
For a solution based on System Release, select the appropriate Unified CM

release from the drop-down list. When you select the Unified CM release,
the supported system release components are listed in the System Release
Column to the right of the input fields.
If you are defining a solution based on Compatible Components, the dropdown list will provide Unified CM releases from which you can choose, as a
base for the solution.
Customer Collaboration
Use the drop-down list provided to specify an appropriate release of Unified

CCE or Unified CCX for your solution. The default is "None". For a "System
Release" solution, specify the appropriate component as suggested in the
System Release column that appears to the right of the input field.
If you have a 3rd party Contact Center and the call flows are the same as
with a Cisco Unified Contact Center solution, use the Cisco Unified Contact
Center section to size the UC solution and disregard the output related to
the Cisco Unified Contact Center servers.
For example, if the call flows with a 3rd party Contact Center are the same
as the call flows with Unified CCE and CVP, use the Unified CCE section in
this tool and select CVP as an IVR to size the UC solution, and disregard
the output related to the Unified CCE/CVP servers. Similarly, if the call flows
with a 3rd party Contact Center are the same as the call flows with Unified
CCE and IP-IVR, use the Unified CCE section in this tool and select IP-IVR
as an IVR to size the UC solution, and disregard the output related to the
Unified CCE/IP-IVR servers.
E-911
Use the drop-down list provided to specify an appropriate release of Cisco

Emergency Responder if required for your solution. The default is "None".
For a "System Release" solution, specify the appropriate component as
suggested in the System Release column that appears to the right of the
input field.
Cisco Expressway
Use the drop-down list provided to specify an appropriate release of Cisco

Expressway if required for your solution. The default is "None". For a
"System Release" solution, specify the appropriate component as
input field.
Voice Messaging
Use the drop-down list provided to specify a voice messaging component

release (Unity Connection or 3rd Party) if required for your solution. The
default is "None". For a "System Release" solution, specify the appropriate
component as suggested in the System Release column that appears to the
right of the input field.
Cisco TelePresence
Use the drop-down list provided to specify an appropriate release of

TelePresence if required for your solution. The default is "None". For a
9/15/2015
Page 3 of 118
input field.
Conferencing
Use the drop-down list provided to specify a Conferencing and Collaboration

component release (Unified Meeting Place or 3rd Party) if required for your
solution. The default is "None". For a "System Release" solution, specify the
appropriate component as suggested in the System Release column that
appears to the right of the input field.
Cisco Unified Presence
Use the drop-down list provided to specify an appropriate Cisco Unified

Presence release if required for your solution. The default is "None". For a
input field.
Starting with Unified CM Release 9.0(1), a section of fields for Unified
Communications Manager IM and Presence Service (formerly known as
Cisco Unified Presence) will be automatically provided in the Unified CM
sections of the sizing tool.
Media Streaming & Recording
Use the drop-down list provided to specify a Cisco MediaSense release if

required for your solution. The default is "None". For a "System Release"
solution, specify the appropriate component as suggested in the System
Release column that appears to the right of the input field.
Collaboration Management
Use the drop-down list provided to specify an appropriate release of Prime

Collaboration if required for your solution. The default is "None". For a
input field.
Use the drop-down list provided to specify a Cisco Intercompany Media

Engine component if required for your solution. The default is "None". For a
input field.
Unified Contact Center Enterprise

If you select a version of Unified Contact Center Enterprise on the Identify Components page described in the previous section,
the Unified CCE Components page is available when you click Continue. The relevant Unified CCE pages are listed Under the
Unified Contact Center Enterprise heading in the navigation list on the right side of the tool.
z
Components
Inbound Page
Outbound Page
Unified CCE Options Page
Reporting Page
Unified CVP
IP IVR
9/15/2015
Page 4 of 118
Components
This page provides fields that let you indicate the general characteristics of the Unified Contact Center Enterprise deployment.
The following table describes the function of each field on the Unified CCE Components page.
UCCE Components/Options
Field
Description
Inbound Traffic
Click Yes in the drop-down list if the Unified CCE deployment has agents
that receive inbound calls.
Outbound Traffic
Click Yes in the drop-down list if the Unified CCE deployment has agents
that place outbound calls.
VRU Platform Type
Indicate whether Unified CVP or Unified IP IVR provides the voice response
portion of the solution.
Inbound Page
The Unified CCE Inbound page provides a BHCA calculator (to help estimate/calculate BHCA), a section of fields for Inbound
information, and a section for call flow information.
z
BHCA Helper
UCCE Inbound
Unified CCE InboundCall Flows Table
BHCA Helper
There is a BHCA Helper tool near the top of the inbound page. You can run a few scenarios with the BHCA Helper which will
suggest a value for BHCA based on the number of concurrent agents, traffic percentages, and the time an agent is occupied.
The following table describes the function of each field on the Inbound BHCA Helper tool.
Unified CCE : Inbound BHCA Helper Tool
Field
Description
Input Source
Agents
Enter the total logged on agents in

the system. Default is 120. Range is
0 - 12000. This value is used to
calculate the Total BHCA.
This value is determined by specific customer

business requirements.
ATT (Agent Talk Time)
Enter the Agent Talk Time. This will

be used to calculate the time an
agent is occupied (average call
handle time), which is the sum of the
agent talk time and the agent wrapup time. Default is 120. Range is
greater than 0. This value impacts

9/15/2015
Page 5 of 118
the Agent BHCA, which incorporates

the Service Level Goals and Target
Answer Time.
Wrap-Up
Enter the agent wrap-up time. This

will be used to calculate the time an
agent is occupied (average call
handle time), which is the sum of the
agent talk time and the agent wrapup time. Default is 60. Range is
greater than 0. This is similar to
Agent Talk Time for calculating
Agent BHCA.

Self Service traffic %
Enter the percentage of calls that

constitute self service traffic (not
handled by agents). Default is 50%.
Range is 1 - 99%.

Agent Traffic %
Enter the percentage of calls that are This value is determined by specific customer
handled by agents. Default is 50%.
Range is 0.10 - 100%. This value is
used to determine BHCA. It is
inversely proportional to the Self
Service Traffic percentage.
BHCA
The BHCA is the average number of

call attempts per hour per device
during the busy hour.
This field is display only.
UCCE Inbound
The following table describes the function of each field on the Inbound section of the Inbound page.
UCCE Inbound
Field
Description
Input Source
Number of Incoming
Calls Per Hour
Enter the Total Inbound Busy Hour

Call Attempts (BHCA) for the total
number of inbound calls that are
presented to the call center. The
BHCA is the number of calls that
occur in the busiest one-hour period.
Range is greater than 0.
For existing deployments, this is obtained from

the call detail record using the standard ICM
reporting facility by counting the number of
incoming calls that terminate at a Unified CCE
inbound component. See BHCA Helper .
CCE 10.0 provides the ability for

customers to use the Voice Callback
feature when used in conjunction
with Social Miner. Although these
Voice Callback requests are
outbound calls from the Contact
Center, they need to be accounted
for in the inbound BHCA .
The total number of agents required
will be calculated based on the
number of Incoming calls/hour
9/15/2015
Page 6 of 118
(Carried BHCA) and the number of

agents assigned in outbound call
flows.
Service Level Goals

must be answered within the number business requirements.
of seconds specified in the Target
Answer Time field. This value is the
average of all calls answered
immediately when agents are
available along with those calls that
are queued when no agents are
available. For example, if the target
answer time is 3 seconds and the
SLG is 95%, no more than 5% of
incoming calls will wait longer than 3
seconds. A higher SLG percentage
increases the number of agents
required to meet the service level
goal. Range is 1 - 99%.
Target Answer Time

(sec)
Enter the target answer time that is

used with the SLG percentage to
determine the service level goal for
the Unified CCE system that you are
designing. A shorter target answer
time increases the number of agents
goal. Range is greater than 0.

Call Blocking Probability Enter the highest acceptable

at VGW
percentage of calls that may be
blocked when the solution is unable
to process a call. The default is 1%,
which means that the solution is
sized to process 99% of all calls
without blocking.

Call Blocking Probability Enter the highest acceptable

at VRU
percentage of calls that may be
blocked at the VRU when the
solution is unable to process a call.
Default is 0.1%. Range is 0.01 10%. The default value is highly
recommended to help ensure that
calls are allocated sufficient
resources.
This value is specified by the business

requirements that the solution is designed to
meet.
Call Blocking Probability at VRU

affects VRU ports Queue, Call
Treatment (also in Outbound) and
Agents as well. It will have the
inverse impact on Call Blocking
Probability at VGWs.
Average Number of
Agents Per Supervisor
Enter the average number of agents

per supervisor. Range is 1 - 50.
The number of supervisors needed
for a particular Agent group is
assigned.
% Local Agents
Enter the percentage of agents that

will be using the Contact Center
Calculate the average number of agents per

supervisor by dividing the total number of
agents by the total number of supervisors.
For existing deployments, cross reference DNs

assigned to agents with information from
9/15/2015
Page 7 of 118
locally. Range is 0 - 100%.
Unified CM and calculate the local endpoint.

Verify the protocol configured for those phones.
% Mobile Agents
Displays the percentage of mobile

agents. This value depends on the
value entered in the Percentage of
Local Agents field. Range is 0 100%
Obtain this percentage by dividing the number

of mobile agents by the total number of agents
and multiply by 100.
% Mobile Agents Nailed

Up
Enter the percentage of agents using

the Contact Center remotely and that
will require a dedicated (nailed-up)
connection. Range is 0 - 100%.
This can be configured or chosen by the agent

during login. Obtain this number by dividing the
number of agents that utilize a dedicated
connection by the total number of mobile
agents and multiply by 100.
% Mobile Agents Call By Displays the percentage of agents

Call
using the Contact Center remotely
and that establish a new connection
for each call. This value depends on
the value entered in the % Mobile
Agents Nailed Up field. Range is 0 100%. Call by Call Traffic Mix
Obtain this value by dividing the number of

agents who establish new connections for each
call by the total number of mobile agents and
multiply by 100.
VRU Platform
This field is display only. The content of the

field depends on the platform selected in the
UCCE Component selection page.
This field displays the VRU platform

type. (IP IVR or CVP)
Unified CCE InboundCall Flows Table

The following table describes the function of each field in the Call Flow section of the Inbound page. Use these fields to identify
the type of traffic you expect in the call center and create an entry for each type of activity. Each Call Flow entry (up to 10 call
flow entries are possible) determines the Percent of Total calls that each call flow represents, and then specifies up to
seventeen additional parameters that define the behavior of the call flow.
UCCE InboundCall Flows Table
Field
Description
Input Source
% Total Calls
Enter the percentage of calls that are

expected to be of this type. This
value defines the portion of the
Percentage of Total Calls that is
represented by this call flow. The
sum of all percentages for all call
flows must equal 100%. Default is
100%. Range is 0 - 100%. The
remaining fields in this table are
specific to the call flow being defined
and further define the behavior of this
call flow.
For existing deployments, in Unified CM

Configuration Manager go to Configure ICM >
Calls > Call Type Bulk Edit > Retrieve and
manually analyze the results.
Average Treatment time Enter the average time, in seconds,

- VRU (sec)
that will be required for calls defined
by this call flow when transferred to a
VRU. Default is 60. Range is greater
than 0.

9/15/2015
Page 8 of 118
Average Call Talk Time

(sec)
Enter the average talk time, in

seconds, for the call flow being
defined. Default is 180. Range is
greater than 0.

Average Wrap-Up Time

(sec)
Enter the average wrap-up time, in

seconds, required by the agent after
completing calls defined by this call
flow. Default is 60. Range is greater
than 0.

Wait Before Abandon

Tolerance (sec)
Enter the length of time, in seconds,

that callers can be expected to wait
before the call is disconnected for
calls defined by this call flow. Default
is 150. Range is greater than 0.

% Transfer
Enter the percentage for calls

defined by this call flow that will be
transferred to another agent. Default
is 10%. Range is 0 - 100%.

After Transfer Talk Time Enter the average talk time after
For existing deployments, determine this value
transfer in seconds for calls defined
by interviewing or observing agents handling
by this call flow. Default is 60. Range actual calls.
is greater than 0.
% Conference
Enter the percentage of calls defined For existing deployments, this value can be
by this call flow that will generate an obtained from call details using the standard
ad hoc three-way conference with a ICM Reporting Facility using agent statistics.
supervisor or another agent. Default
is 5%. Range is 0 - 100%.
% Calls Silent Monitor

(UCM)
Enter the percentage of calls defined

by this call flow that will be monitored
by a supervisor or another agent
using the Unified CM silent
monitoring feature. Default is 0%.
Range is limited by the average
number of agents managed by each
supervisor (the value entered in the
Agents Per Supervisor field above)
because the supervisor can only
monitor one agent at a time. For
example, if each supervisor manages
an average of 10 agents, the
maximum range is 10% (1/Agents
Per Supervisor).
% Calls Recorded by
UCM (BIB)

by this call flow that will be recorded
using the Unified CM call recording
feature for later review, analysis, or
legal compliance. Default is 0%.
Range is 0 - 100%.
% Calls Recorded by
CUBE

by this call flow that will be recorded
using Cisco Unified Border Element,
for later review, analysis, or legal
compliance. Default is 0%. Range is
0 - 100%.
9/15/2015
% Calls with Post Call

Survey

by this call flow that will be
transferred to a Dialed Number
Identification Service (DNIS) number
that prompts the caller to complete a
post call survey. Default is 0%.
Range is 0 - 100%.
Average Treatment
Time for Post Call
Survey (sec)
Enter the average length of time, in

seconds, for callers in this call flow to
complete a post call survey. Default
is 120. Range is greater than 0.
% Calls with Courtesy

Callback

by this call flow that will offer callers
the option to be called back by the
system instead of waiting on the
phone for an agent. Callers who
been queued by Unified CVP can
hang up and subsequently be called
back when an agent is close to
becoming available (preemptive
callback) Default is 0%. Range is 0 100%.
% Calls with Whisper

Announcements

by this call flow that cause the
system to play a message or tone to
an agent before a call is connected
so that the agent responds correctly
to the caller (usually in situation
where the agent is representing
multiple brands). Default is 0%.
Range 0 - 100%.
AHT (Average Handle

Time) for Whisper
Announcements (sec)
Enter the average duration, in

seconds, of the whisper tone or wave
file (or both) that are played to an
agent before a call is connected
using this call flow. Default is 30.
% Calls with Agent

Greeting

by this call flow that will provide an
agents customized greeting to callers
before the agent handles the live call.
Default is 0%. Range is 0 - 100%.
AHT for Agent Greeting

(sec)
Enter the average duration, in

seconds, of the agents custom
greeting that is provided to callers
before the call is connected using
this call flow. Default is 5. Range is
greater than 0.
Page 9 of 118
A post call survey is typically used by a contact

center to determine whether a customer was
satisfied with their call center experience (did
they find the answer they were looking for using
the self service or did they have a pleasant
experience with the contact center agent, and
so forth).
Outbound Page
9/15/2015
Page 10 of 118
The Outbound page provides a Unified CCE Outbound section that contains fields for describing outbound dialing and
campaigns. For descriptions of the fields available in the outbound page see Unified CCE Outbound.
z
Unified CCE Outbound
Unified CCE Outbound

The following table describes the function of each field in the Unified CCE Outbound page.
UCCE Outbound
Field
Description
Input Source
Outbound Dialer Type
Select whether outbound calls will be For existing deployments, in the ICM
initiated using SCCP or SIP from the Configuration Manager go to Outbound
pull-down selection list. Default is
Option > Dialer to determine the value.
SIP Dialer.
% Agents Calls
Recorded
Enter the percentage of Agents calls

recorded. Default is 0%. Range is
0% to 100%.
This value depends on the business

requirements of the customer.
Dialing Mode
Select the outbound dialing mode

from the pull-down selection list.
Options include Predictive (the dialer
automatically calls several numbers
and only passes a call to an agent
when a person has been contacted),
Preview (the dialer passes call
information to the agent before the
number is dialed), or Direct Preview
(the dialer passes the call to the
agent at the same time the number is
being dialed, so the agent hears the
ringback). Default is Predictive.
For existing deployments, in the ICM

Configuration Manager go to Outbound
Option > Dialer > Dialing mode to determine
the value.
Select Input Type
Specify either Ports or Agents as the

input type. The default is Agents

Number of Agents/Ports Enter number of Agents if you

selected agents in the input Type.
Otherwise enter the number of dialer
ports

Campaign Table
% Transfer to Agents
Enter the percentage of outbound

calls that are transferred and
answered by an agent. Default is 0%.
Range is 0 - 100%.
Agent AHT
Enter the expected Agent Average

Hold time in seconds. Default is 120.
Range is >= 0.
For existing deployments, obtain this value by

interviewing agents or observing call center
activity.
Wrap-up
Enter the average length of wrap up

time required for agents after

9/15/2015
Page 11 of 118
handling the outbound call. Default is

60. Range is greater than 0.
% Transfer to IVR
Enter the percentage of outbound

calls that will be transferred to an
IVR. Default is 0%. Range is 0 100%.
For existing deployments, obtain this value

from call details using the standard ICM
Reporting Facility.
AHT in IVR
Specify the average hold time in

seconds for Interactive Voice
Response (IVR). The default is 25.
For existing deployments, obtain this value by

interviewing agents or observing call center
activity.
Hit Rate
Enter the percentage of customer Hit This value depends on the business
(Answered) Calls among dialed calls. requirements of the customer.
PCB per Hour
Enter the number of PCB records to

be dialed by the dialer per hour.

PCB Agents only
Enter the number of Agents

dedicated for PCB only calls.

VRU Ports
Displays the number of Voice

Response ports assigned to the
campaign.
VGWs Ports
Displays the number of Voice

Gateways ports assigned to the
campaign.
Agents
Displays the number of Agents

assigned to the campaign for making
outbound calls.
Dialer Ports
Displays the number of dialer ports

assigned to the campaign for making
outbound calls.
Min Dialers Required
Displays the minimum number of

dialers required for a given
configuration. This is calculated
based on the number of Dialer Ports
required (total number of Dialer
Port /1500). Max ports per dialer is
1500.
Recommended
CPS/System
Displays the max dialer CPS

Required for a given configuration.
This is calculated based on ((30/4)
*Min Dialers Required), where 30
CPS is recommended for outbound
for 4k deployment.
Unified CCE Options Page

If you select Unified CCE as a component for your solution, the relevant Unified CCE pages will be listed Under the Unified
Contact Center Enterprise heading in the navigation list on the right side of the tool. The following sections are provided on the
Unified CCE Options page:
9/15/2015
UCCE Options: Desktop
Unified CCE Option: Skill Group or Precision Queue
Unified CCE Option: Extended Call Context
Unified CCE Option: Central Controller Platform
Unified CCE Option: PG Platform
UCCE Option: Finesse Platform
Output
Page 12 of 118
UCCE Options: Desktop

The following table describes the function of each field in the Desktop section of the Unified CCE options page.
Unified CCE OptionsDesktop
Field
Description
Input Source
Desktop Security
Select TLS ON to enable CTI OS

security and OFF to disable CTI OS
security. CTI OS offers a security
option based on Transport Layer
Security (TLS). Default is OFF.
For example, in Unified CCE 7.5, the value of

the SecurityEnabled registry key is 1 if security
is ON. This registry key can be found under
HKEY_LOCAL_MACHINE\SOFTWARE\Cisco
Systems,
Inc.\Ctios\CTIOS_InstanceName\CTIOS1
\Server\Security .
Desktop Type
Select the agent desktop type.

Options are CAD (Cisco Agent
Desktop), CTIOS (Cisco Toolkit
Desktop), and Finesse. Default is
CTIOS.
This depends on the type of Desktop software

that has been installed on the agent's desktop.
Unified CCE Option: Skill Group or Precision Queue

The following table describes the function of each field in the Skill Group or Precision Queue section of the Unified CCE Options
page.
UCCE Options Skill Group or Precision Queue
Field
Description
Input Source
Skill Group and/or

Precision Queue Per
Agent
Enter the average number of skill

groups and/or Precision Queues to
which each agent belongs. Range is
1 - 50.
For existing deployments, obtain the average

number of skill groups assigned per agent. Log
into the Administrative Workstation, and open
the Configuration Manager Tool. Navigate to
Peripherals > Agent > Agent Explorer >
Retrieve > Agent > Skill Group Membership.
Based on the number of skill groups assigned
to each individual agent and the number of
agents, calculate the average number of skill
groups per agent.
A skill group is a collection of agents

that share a common set of skills.
Unified Contact Center agents are
assigned one or more skills by
associating the agent with the
desired skill. Agent desktop, security
9/15/2015
Page 13 of 118
and Skill group per agent affect

Agent PG capacity. Total skill groups
also affect the capacity of the Unified
Contact Center central controller.
Average Skill Group Per Enter the average number of skill
Team
groups per team. Range is greater
than the value in the Avg Skill Group
per Agent and less than total skill
group per PG.
For existing deployments, use the ICM

Configuration Manager to view each agent
team and find the corresponding agent
members. For each agent member
configuration of the team, count the total
number of unique skill groups for that team.
Divide the total number of unique skill groups
for all teams by the number of teams to get the
average.
Concurrent Number of
Active Skill Groups
Enter the total number of skill groups

and/or precision queues per
peripheral gateway. Total Skill
Groups and Precision Queue
(system wide) per PG cannot be over
4000.
For existing deployments, use the ICM

Configuration Manager to find the total number
of skill groups configured and then divide that
number by the number of PGs.
Total Skill Group Per

System
Enter the total number of skill groups For existing deployments, check the maximum
in the system. Total Skill Group +
number of skill groups that are created in the
Precision Queue cannot be > 27,000 overall system. Log into the Administrative
Workstation, and open the Configuration
Manager. Navigate to Peripherals > Skill
Group > Skill Group Explorer. The Skill
Group Explorer will give you the total number of
skill groups.
Total Precision Queue

Per System
Total Precision Queue/System
Enter the total number of Precision Queues in

the system. Default is 1000. Maximum is 3000
PQ /system.
Unified CCE Option: Extended Call Context

The Extended Call context section provides fields to identify average usage. The following table describes the function of each
field in the ECC section of the Unified CCE Options page.
Unified CCE Options PageECC
Field
Description
Input Source
Scalars
Enter the number of ECC scalars

defined in Unified CCE that are
persistent. An ECC variable can
either be a scalar variable or an
array. Only persistent scalars have
impact on the sizing of the overall
system. Range is greater than 0.
For existing deployments, log into the

Administrative Workstation and open the
Configuration Manager Tool. Navigate to Tools
> List Tools > Expanded Call Variable List >
Retrieve. Manually count the number of scalar
variables for which the persistent check box is
selected.
Arrays
Enter the total number of ECC arrays

that are defined in Unified CCE that
are persistent. An ECC variable can
either be a scalar variable or an
array. Only persistent arrays have

Retrieve. From the ECC variable list, manually
9/15/2015
Elements
Page 14 of 118
impact on the sizing of the overall

system. Range is greater than 0.
count the number of variables that have both

array and persistent check boxes selected.
Enter the average number of ECC

array elements for persistent arrays
that exist in Unified CCE. This entry
is used when the ECC variable is an
array. Range is > 0.

Retrieve.
Manually navigate to each ECC array variable
to determine the number of elements. Divide
the total number of elements by the number of
arrays to determine the average number of
elements across all the defined persistent
arrays. Enter this average into the Elements
field.
Unified CCE Option: Central Controller Platform

The following table describes the function of each field in the Central Controller Platform section of the Unified CCE Options
page.
Unified CCE Options: Central Controller Platform
Field
Description
Input Source
CCE Release
CCE Release
This field displays the specified Unified CCE

Release for your solution.
Virtual Machines
Indicate whether the solution should

size Unified Contact Center
Enterprise installed on a Virtual
Machine (VM) platform such as
Cisco Unified Computing Systems
(Yes) or not (No).
For more information and best practices on

deploying Unified Communications on the
Unified Computing System platform in a virtual
environment, go to www.cisco.com/go/ucvirtualized.
Secure IP
Communications
Select ON or OFF. When enabled,

the Sizing Tool reduces resource
capacity and functional limitation
formula for the following by 25 per
cent:.
z
Maximum call rate limit

supported by the deployment
Maximum agent capacity on

Agent Peripheral Gateways
Maximum port capacity

supported by VRU Peripheral
Gateways
Maximum call rate (calls per

second) limit supported by
VRU Peripheral Gateways
Maximum port capacity

supported by the (Outbound
Option) SIP Dialer
9/15/2015
Server Type
Indicate the type of Virtual Machine

upon which UCCE is running.
Page 15 of 118
This field is determined by customer

deployment.

The following table describes the function of each field of the Unified CCE OptionPG Platform section.
Field
Description
Input Source
PG Platform
Select the type of server. For virtual

machines (VMs), Open Virtualization
Archive (OVA) templates are shown
for various numbers of endpoints.
Verify the server class of the actual hardware.
PG Server VM Type
Select the appropriate B-series

(blade) or C-series (chassis) Cisco
Unified Computing System server
hardware for peripheral gateways.
Virtualization rules and recommendations are

available on the Cisco DocWiki at
docwiki.cisco.com under the category Systems
and the topic Unified Communications
Virtualization.

Field
Description
Input
Source
Finesse Platform Select the type of Finesse platform. Currently only a single OVA template is
supported, namely, Finesse_2000_agents.
Finesse Server
VM Type
Select the Finesse server type. Choose from the currently supported C-Series
UCS hardware options that appear in the drop-down list.
Output
The following table describes the function of each field in the Output section of the Unified CCE Options page.
Unified CCE OptionOutput
Field
Description
Total APG VMs Required with

Redundancy
Displays the suggested number of agent peripheral gateway (APG)

servers that require redundant configuration.
9/15/2015
Page 16 of 118
If the number of VRU Ports is <= 1000, the tool displays "Generic PG"
with the following criteria:
z
If the number of Active SGs is >= 2000, tool displays "Large

Generic PG".
If the number of Active SGs is < 2000, tool displays "Small

Generic PG".
If the number of VRU ports is >1000, the tool displays "UCM Agent".
Finesse
Displays Finesse platform after BHCA value is entered.
Router
Displays the suggested platform and quantity of router as required for

the Unified CCE deployment. A call router, makes all routing decisions
about how to route a call or customer contact.
Logger
Displays the suggested platform and quantity of logger as required for

the Unified CCE deployment. A logger is a database server that stores
contact center configuration and reporting data.
AW/HDS
Displays the suggested platform and quantity of AW/HDS as required for

the Unified CCE deployment.
Reporting Page
The Unified CCE Reporting page identifies how many Cisco Unified Intelligence Center servers are required to support an
implementation based on the number of reporting users and the sizes and types of reports used. In addition, profiles can be
specified for Analyst, Manager, Supervisor, and View Only, user types.
z
Reporting
User Profile: Analyst
User Profile: Manager
User Profile: Supervisor
User Profile: Agent
User Profile: View Only
Reporting
The following table describes the function of each field in the Cisco Unified Intelligence Center (CUIC) section of the Reporting
page.
For Cisco Unified Intelligence Center for reporting, you have the option of defining multiple reporting profiles for four different
types of users: Analysts, Manager, Supervisor, and View Only. Analysts are those users who generate the largest number of
reports and are the heaviest users of the system. Analysts are followed in the amount of usage by Managers, Supervisors, and
Display-Only users. You can access these profiles by clicking Hide/Show profiles button on the Reporting page. The fields for
these profiles are described in User Profile: Analyst, User Profile: Manager, User Profile: Supervisor, and User Profile: View
Only.
For existing deployments, run a user profile to estimate how many users in your network fall into each profile type. To provide a
9/15/2015
Page 17 of 118
model to start from, default values for typical usage are included for several profiles. You can modify these numbers based on
your experience with your existing system.
Cisco Unified Intelligence Center (CUIC)
Field
Description
CUIC Release Version
The release version for CUIC.
Real Time AWDs
Enter the number of AWDs. Default is 2. Range is 010.
Analyst
Enter the number of users defined as analysts in the

Unified CCE implementation. Default is 0.
An analyst is typically
responsible for overall contact
center activity, and researching
exception cases on an ad hoc
basis. Because of this, an
analyst typically uses a larger
number of reports then other
users. Approximately 10% of
contact center reporting users
fall into this category.
Manager
Enter the number of users defined as managers in

the Unified CCE implementation. Default is 0.
Managers need a broad view of

real-time data and tend to be
more focused on the half-hour
and daily summary historical
reports. Approximately 20% of
Supervisor
Enter the number of users defined as supervisors in

the Unified CCE implementation. Default is 0.
Supervisors require real-time

views of their teams and
historical comparisons for
trending. These users may
have a dashboard that models
the wallboard data using
gauges and charts, as well as a
full grid, real-time report
showing all of their agents.
Approximately 90% of contact
center reporting users fall into
this category.
Agent
Enter the number of users defined as agents in the

Unified CCE implementation. Default is 0.
An agent is typically
responsible for overall contact
center activity, and researching
exception cases on an ad hoc
basis. Because of this, an
analyst typically uses a larger
number of reports then other
users. Approximately 90% of
View Only
Enter the number of users that will have display only

access to reports generated by Unified CCE, Unified
CVP, or Unified Expert Advisor. Default is 0.
View Only users represent

casual users of contact center
information and display boards.
Approximately 10% of contact
center reporting users fall into
this category.
Total CUIC Reporting

Users
Displays the total number of users retrieving reports

from Unified CCE, Unified CVP, or Unified Expert
Input Source
9/15/2015
Page 18 of 118
Advisor (the total of the Analyst, Manager,

Supervisor, and Display Only fields above).
Output
Platform
Displays the recommended Unified Intelligence

Center server configuration. To override the
recommendation, select another server from the pulldown selection list.
For more information and best

practices on deploying Unified
Communications on the Unified
Computing System platform in
a virtual environment, go to
www.cisco.com/go/ucvirtualized.
Server Type
Select the appropriate B-series (blade) or C-series

(chassis) Cisco Unified Computing System server
hardware for peripheral gateways. This field only
appears if a VM OVA template is chosen in the
Platform field. Default value is based on the OVA
template chosen in the PG Platform field.
Virtualization rules and

recommendations are available
on the Cisco DocWiki at
docwiki.cisco.com under the
category Systems and the topic
Unified Communications
Virtualization.
Total <Server Type> VM Shows the number/type of CPUs, amount of memory,

Resources Needed
and hard disk capacity for Virtual Machine (VM)
implementations on Unified Computing System
(UCS) platforms.
User Profile: Analyst

The following table describes the function of each field in the Advanced Settings section for Analyst users on the Unified CCE
Reporting page.
Cisco Unified Intelligence Center Analyst User Profile
Field
Description
Input Source
Live Data Reports

Number of Reports
Enter the number of live data reports For existing deployments, estimate this value
that a typical analyst user would view based on an analysis of typical reporting usage.
on a dashboard display or access as
needed from an administration menu.
A separate number of reports can be
defined for each of three sample
analyst profiles.
Average Rows per

Report
Enter the average number of rows

displayed per report for each profile.
Default for 50 for all three profiles
Enter an estimated average number
of rows of data that will appear in
each live data analyst report. Range
is 0 - 8,000. By default, sample
values are provided for three
different analyst report profiles;
adjust these values accordingly to
match your requirements.
For existing deployments, estimate this number

based on the expected grouping of agents, skill
sets, or call types in each report. Examine a
typical report and count the number of rows or
average them across several reports
9/15/2015
Page 19 of 118
1=Grid, 2=Chart,
3=Gauge
Enter the desired viewing format for For existing deployments, determine the
live data analyst reports. If analysts
preferred viewing format based on an analysis
want to view the data in table form,
of typical reporting usage.
enter 1. If analysts want to view the
data as a pie, bar, or line chart, enter
2. If analysts want to view the data in
a gauge, such as a speedometer,
enter 3. By default, each format is
assigned to one of the three analyst
reporting profiles.
Refresh Rate (sec)
Enter the type of report you want to

display. Default is 1 or grid.
Refresh Rate (sec)
Enter how often you want to refresh

the live data report. Default is 1
second.
Enter the expected frequency (in
seconds) for updates to live analyst
reports. Default is every 30 seconds.
Range is any interval equal to or
greater than 15 seconds.
For existing deployments, users with Unified

Intelligence Center premium licensing can view
and modify the refresh rates using the Report
Definition Properties page in Unified IC
Administration. For Unified Intelligence Center
standard license users, the refresh rate is fixed.
Real Time Reports

Number of Reports
Enter the number of real-time reports For existing deployments, estimate this value
that a typical analyst user would view based on an analysis of typical reporting usage.
analyst profiles.
Average Rows per

Report

each real-time analyst report. Range
is 0 - 8,000. By default, sample
values are provided for three
different analyst report profiles;
1=Grid, 2=Chart,
3=Gauge
real-time analyst reports. If analysts preferred viewing format based on an analysis
reporting profiles.
Refresh Rate

seconds) for updates to real-time
analyst reports. Default is every 30
seconds. Range is any interval equal
to or greater than 15 seconds.

average them across several reports

Historical Reports
9/15/2015
Page 20 of 118
Number of Reports
Enter the number of historical reports For existing deployments, estimate this value
that analysts typically have open at
based on an analysis of typical reporting usage.
any one time. A separate number of
reports can be defined for each of
three sample analyst profiles.
Average Number of
Rows per Report

each historical report read by
analysts. Range is 0 - 8,000. By
default, sample values are provided
for three different analyst report
profiles; adjust these values
accordingly to match your
requirements.
1=Grid, 2=Chart,
3=Gauge
historical analyst reports. If analysts preferred viewing format based on an analysis
reporting profiles.
Refresh Rate (min)

minutes) for updates to historical
analyst reports. Default is every 30
minutes. Range is any interval equal
to or greater than 30 minutes.

Data Source
Select the device supplying the

reporting data to the analyst reports:
Unified CCE, Unified CVP, or Unified
EA (Expert Advisor). Default is
Unified CCE. A different source can
be selected for each of the three
reporting profiles.
For existing deployments, determine the

distribution of load between the various data
sources. Most reports are extracted from the
Unified CCE database, which impacts the
server requirements for Unified CCE.
Specifying multiple data sources reduces the
load on a single source.

average them across several reports.
User Profile: Manager

The following table describes the function of each field in the Manager User Profile.
Cisco Unified Intelligence CenterManager User Profiles
Field
Description
Input Source
Enter the number of live data eports

that a typical manager user would
view on a dashboard display or
access as needed from an
administration menu. A separate
For existing deployments, estimate this value

Live Data Reports

Number of Reports
9/15/2015
Page 21 of 118
number of reports can be defined for

each of three sample manager
profiles.
Average Rows per
Report

each live data manager report.
Range is 0 - 8,000. By default,
sample values are provided for three
different manager report profiles;

1=Grid, 2=Chart,
3=Gauge
live data manager reports. If
managers want to view the data in
table form, enter 1. If managers want
to view the data as a pie, bar, or line
chart, enter 2. If managers want to
view the data in a gauge, such as a
speedometer, enter 3. By default,
each format is assigned to one of the
three manager reporting profiles.
Refresh Rate (sec)

seconds) for updates to live data
manager reports. Default is every 30

Real Time (RT) Reports

Number of Reports
that a typical manager user would
each of three sample manager
profiles.
Average Rows per

Report

each real-time manager report.
different manager report profiles;
1=Grid, 2=Chart,
3=Gauge
real-time manager reports. If
Refresh Rate (sec)

9/15/2015

Page 22 of 118

Historical Reports
Number of Reports
that managers typically have open at based on an analysis of typical reporting usage.
any one time. A separate number of
reports can be defined for each of
three sample manager profiles.
Average Rows per

Report

managers. Range is 0 - 8,000. By
for three different manager report
requirements.
1=Grid, 2=Chart,
3=Gauge
historical manager reports. If
Refresh Rate (min)

minutes. Range is any interval equal
to or greater than 30 minutes.

Data Source

reporting data to the manager
reports: Unified CCE, Unified CVP,
or Unified EA (Expert Advisor).
Default is Unified CCE. A different
source can be selected for each of
the three reporting profiles.


User Profile: Supervisor

The following table describes the function of each field for the Supervisor user profile.
Cisco Unified Intelligence Center Supervisor User Profile
Field
Description
Input Source
9/15/2015
Page 23 of 118
Live Data Reports

Number of Reports
Enter the number of live data reports

that a typical supervisor user would
each of three sample supervisor
profiles.

Average Rows per

Report

each real-time supervisor report.
different supervisor report profiles;

1=Grid, 2=Chart,
3=Gauge
Enter the desired viewing format for

live data supervisor reports. If
supervisors want to view the data in
table form, enter 1. If supervisors
want to view the data as a pie, bar,
or line chart, enter 2. If supervisors
want to view the data in a gauge,
such as a speedometer, enter 3. By
default, each format is assigned to
one of the three supervisor reporting
profiles.

Refresh Rate (sec)

supervisor reports. Default is every
30 seconds. Range is any interval
equal to or greater than 15 seconds.


Number of Reports
that a typical supervisor user would
each of three sample supervisor
profiles.
Average Rows per

Report

each real-time supervisor report.
different supervisor report profiles;

Grid(=1),Chart
(=2),Gauge(=3)

real-time supervisor reports. If

9/15/2015
Page 24 of 118

profiles.
Refresh Rate (sec)

30 seconds. Range is any interval
equal to or greater than 15 seconds.

Historical Reports
Number of Reports
that supervisors typically have open based on an analysis of typical reporting usage.
at any one time. A separate number
of reports can be defined for each of
three sample supervisor profiles.
Average Rows per

Report

supervisors. Range is 0 - 8,000. By
for three different supervisor report
requirements.

Grid(=1),Chart
(=2),Gauge=(3)

historical supervisor reports. If
profiles.

Refresh Rate (min)

30 minutes. Range is any interval
equal to or greater than 30 minutes.

Data Source

reporting data to the supervisor

9/15/2015
Page 25 of 118
User Profile: Agent

The following table describes the function of each field for the Agent user profile.
Cisco Unified Intelligence Center User Profile: Agent
Field
Description
Input Source
Live Data Reports

Number of Reports
Enter the number of live data reports For existing deployments, estimate this value
that a typical agent user would view based on an analysis of typical reporting usage.
supervisor profiles.
Average Rows per

Report

each live data agent report. Range is
0 - 8,000. By default, sample values
are provided for three different
supervisor report profiles; adjust
these values accordingly to match
your requirements.
1=Grid, 2=Chart,
3=Gauge
live data supervisor reports. If agents preferred viewing format based on an analysis
enter 1. If agents want to view the
2. If agents want to view the data in a
gauge, such as a speedometer, enter
3. By default, each format is
assigned to one of the three agent
reporting profiles.
Refresh Rate (min)

agent reports. Default is every 30


User Profile: View Only

The following table describes the function of each field for View Only user profiles.
Cisco Unified Intelligence CenterView Only User Profile
Field
Description
Input Source
9/15/2015
Page 26 of 118
Live Data Reports

Number of reports
Enter the number of live data reports

that a typical view only user would
view on a dashboard display. A
separate number of reports can be
view only user profiles.

Average Rows per

Report

live data view only user reports. If
view only users want to view the data
in table form, enter 1. If view only
users want to view the data as a pie,
bar, or line chart, enter 2. If view only
users want to view the data in a
assigned to one of the three view
only user reporting profiles.

Grid(=1),Chart
(=2),Gauge(=3)

each live data view only user report.
different view only user report
requirements.

Refresh rate (sec)

view only user reports. Default is
every 30 seconds. Range is any
interval equal to or greater than 15
seconds.


Number of reports
that a typical view only user would
view on a dashboard display. A
separate number of reports can be
view only user profiles.
Average Rows per

Report

real-time view only user reports. If
view only users want to view the data

Grid(=1),Chart
(=2),Gauge(=3)

each real-time view only user report.

9/15/2015
Page 27 of 118

different view only user report
requirements.
Refresh rate (sec)

every 30 seconds. Range is any
seconds.

Historical Reports
Number of reports
that view only users typically have
open at any one time. A separate
each of three sample view only user
profiles.
Grid(=1),Chart
(=2),Gauge(=3)
historical view only user reports. If
view only users want to view the data of typical reporting usage.
Average Number of
Rows per Report

each historical report read by view
only users. Range is 0 - 8,000. By
for three different view only user
report profiles; adjust these values
requirements.

Refresh rate

every 30 minutes. Range is any
minutes.

Data Source

reporting data to the view only user

9/15/2015
Page 28 of 118
Unified CVP
The Unified Customer Voice Portal (Unified CVP) options implemented in the solution can be sized as part of a System Release
Sizing or Compatible Components Sizing scenario.
The following table describes the function of each field in the Unified CVP page.
Unified CVP (Unified Customer Voice Portal)
Field
Description
Software Release
Displays the Unified CVP release

For existing deployments, log into the Unified
version compatible with the Unified
CVP OAMP Server Console Server and
CM release (for System Release and navigate to Help > About.
Compatible Component sizing
scenarios). For Individual Product
sizing scenarios, you can select the
Unified CVP release version from the
drop-down list.
Call/VXML Server
Platform
Select the hardware platform option

from the drop-down list.

physical hardware that is used for the
deployment. Options include Media
Convergence Server (MCS) platforms or Virtual
Machine (VM) platforms such as Cisco Unified
Computing Systems.
Unified CVP Reporting

Server Platform
Select the hardware platform from

the drop-down list.

Computing Systems.
Unified CVP
Deployment Model
Displays the functional deployment

model. Note that this field is not
editable.
The functional deployment model provides

organizations with a mechanism to route and
transfer calls across a VoIP network, to offer
IVR services, and to queue calls before being
routed to a selected agent. The most common
usage scenario for this functional deployment
model is for organizations wanting a pure IPbased contact center.
Busy Hour Call Attempts Enter the average number of call

attempts per hour per device during
the busy hour. There is no default.
Input Source
The optional Unified CVP reporting server can

collect summary information on call events. It
stores this information in an Informix database.
Average Messages Per

Call for Detail VXML
Reporting
Average Messages per Call for Detail Enter the average message per call if detail
VXML Reporting
VXML reporting is required. Range is greater
than or equal to 0.
HTTPS
Indicate whether HTTPS is enabled

(On) or disabled (Off).
Redundancy
This field refers to the CVP

Verify the configuration of external components
redundancy model. You need at least that invoke the Unified CVP server to determine
N+1 CVP servers if your deployment the deployment model that has been chosen.
For existing deployments, log into the server

using Telnet/SSH and look at the %
CVP_HOME%\conf\security\ directory. If
HTTPS is enabled, there is a properly signed
certificate file ending in .crt and another file of
the same name ending in .key.
9/15/2015
Page 29 of 118
has one datacenter that is

centralized. In the case of a
geographic redundancy (two data
centers for example), you would
deploy as a 1:1 redundancy. The
sizing tool determines the number of
CVP servers required based on your
scenario (no redundancy), and then it
either adds one server if redundancy
is N+1 or it adds a multiple number
of required of required servers by two
if it is a 1:1 redundancy. Select the
type of redundancy required for the
solution. Options include None, N+1,
1:1.
Comprehensive App
Model
Select VXML or Micro-App. Default is For existing deployments, log into the Unified
VXML.
CVP OAMP Server and navigate to Device
Management. Then click Unified CVP VXML
Server. If Unified CVP VoiceXML server is
listed, then choose VoiceXML for this option;
otherwise choose Micro-App.
Transfer to Agents
Using SIP REFER
Indicate whether the Unified CVP is

allowed to transfer calls to an agent
using SIP refer (Yes) or not (No).
Default is No.
% Subsequent Network
Transfer By Agents
Enter the percentage of calls that will

be transferred from the receiving live
agent to another destination. Range
is 0 - 100%.
For existing deployments, use the Call Detail

Records to determine the total number for
transfers, including both network and local
activity.
Related Tasks
Describe Unified CVP options
IP IVR
The following table describes the function of each input field on the Unified IP IVR page.
Unified CCEIP IVR Section
Field
Description
Input Source
Software Release
Displays the Unified IP IVR software

version number.
For existing deployments, verify the installed

version of the software.
Platform
Select the hardware platform option

from the pull-down list.

Computing Systems.
Server Type

Virtualization rules and recommendations are

available on the Cisco DocWiki at
docwiki.cisco.com under the category Systems
9/15/2015
Page 30 of 118
hardware. This field only appears if a and the topic Unified Communications
VM OVA template is chosen in the
Virtualization.
Platform field. Default value is based
on the OVA template chosen in the
previous field.
Redundancy
Select the type of redundancy

required for the solution. Options
include None, N+1, 1:1. Default is
N+1.
Output
These fields provide information on

the Unified IP IVR VMs suggested for
the solution. Information may include:
VMs, vCPUs, RAM, vDISK, and
vNICs
Unified Contact Center Express

A Unified Contact Center Express system can be sized in one of two ways:
z
As part of a Systems Release Sizing scenario.
As part of a Compatible Components Sizing scenario.
For more information on sizing Unified CCX, see the following links:
z
Options
Output
CCX Inbound
CCX Outbound
Related Information
Unified Contact Center sizing solution
Options
The following table describes the function of each input field on the Options section of the Unified Contact Center Express
Options page (for System Release Sizing or Compatible Components Sizing).
Unified Contact Center Express Options
Field
Description
Input Source
Package Type
Select the type of package

(Standard, Enhanced, or Premium)
from the pull-down selection list.
Default is Standard. The package
type selection determines the other
fields that appear in this section.
For existing deployments, in Unified Contact

Center Express Administration, go to Help >
About to display the Unified CCX package
installed.
9/15/2015
Page 31 of 118
Desktop Type
Select the agent desktop type.

Options are CAD (Cisco Agent
Desktop) and Finesse. Default is
CAD.
This depends on the type of Desktop software

that has been installed on the agent's desktop.
High Availability
Deployment
Indicate whether the Unified CCX

deployment is designed for high
availability (Yes) or not (No). This
field is only available if the Package
Type selection is either Enhanced or
Premium.

Center Express Administration, go to System >
License Information. If High Availability
Enabled: 1 is displayed, Unified CCX is
configured for high availability.
Type of High Availability Select whether the high availability

Deployment
configuration for the Unified CCX
provides backup servers within the
same physical location (LAN) or at
different locations (WAN). This field
is only available if the Package Type
selection is either Enhanced or
Premium and the High Availability
Deployment field is set to Yes.
Total Number of
Concurrent Agents
Handling Inbound Calls
Enter the maximum number of

concurrent agents tasked with
handing incoming calls. Default is 10.
Range is 1 - 400.
For existing deployments, this value is based

on the maximum number of seats purchased.
In Unified Contact Center Express
Administration, go to System > License
Information to display the Unified CCX seats
available.
Of the Total, Number of

Concurrent Agents
Handling Preview
Outbound Calls
Enter the number of concurrent

agents, within the Total Number of
Concurrent Agents Handling Inbound
Calls value above, that use preview
dialing to place outbound calls.
Default is 0. Range is 0 to the value
entered in the Total Number of
Calls field. This field is only available
if the Package Type selection is
Premium.
For existing deployments, preview outbound

seats are not licensed but an upper limit may
have been configured. In Unified Contact
System Parameters and examine the value in
the Number of Outbound seats field. If no
value is set, use the corresponding value
previously entered in the Cisco Unified Contact
Center Express/IPIVR Configuration & Ordering
Tool that was used to design the initial
deployment (if available).

Concurrent Agents
Handling
Predictive/Progressive
Outbound Calls

agents that use predictive or
progressive dialing to place outbound
calls. Default is 0. Range is 0 to 150.
This field is only available if the
Package Type selection is Premium
and the Desktop Type selection is
Finesse.

Concurrent Agents
Handling Emails

agents, within the Total Number of
Calls value above, that handle
Emails. Default is 0. Range is 0 to
the lesser of two values: 120 or the
value entered in the Total Number of
Calls field. This field is only available
if the Package Type selection is
Premium.
For existing deployments, use the

corresponding value previously entered in the
Cisco Unified Contact Center Express/IPIVR
Configuration & Ordering Tool that was used to
design the initial deployment (if available).
9/15/2015
Page 32 of 118
Number of Supervisors
Enter the number of supervisors

managing the agents. Range is 0 32.

corresponding values previously entered in the
Maximum Number of
Customer Service
Queues (CSQs)
Required

queues required to process customer
service calls. Default is 0. Range is 0
- 150.
For existing deployments, generate a Contact

Service Queue Activity Report (by CSQ) and
count the queues that handle customer service
calls.
Do You Want to Add

Any of the Following
Products: CR, QM, or
AQM?
Select any optional software

products to use with Unified CCX such as Compliance Recording (CR),
Quality Manager (QM), or Advanced
Quality Manager (AQM) - from the
pull-down selection list or choose no
optional products (No). This field is
only available if the Package Type
selection is Premium.

License Information to determine if any of
these products are installed.
Do You Want to Add a

CR Server?
Select whether you want to add a

Compliance Recording server (CR
Only) or no optional product (No).

License Information to determine if a CR
server is installed.
Number of Named (Not

Concurrent) Compliance
Recording (CR) Users
Required
Enter the number of all named users

(unique users, based on licensing)
that will be monitored and recorded
by a Compliance Recording server.
Range is 0 - 3,600. This field is only
available if you have added the
optional Compliance Recording (CR)
product.

License Information to determine if any
named CR users are configured.
Number of Concurrent
Compliance Recording
Users Required
Enter the number of all concurrent

users that will be monitored and
recorded by a Compliance Recording
server at any given time. Range is 0 1,200. This field is only available if
you have added the optional
Compliance Recording (CR) product.

Total Number of
Compliance Manager
Concurrent Endpoint
Recording Sessions for
All Sites
Enter the total number of endpoints

at all sites that will be monitored and
recorded by a Compliance Recording
server at any given time. Range is 0 1,200. This field is only available if
you have added the optional
Compliance Recording (CR) product.

Total Number of
Compliance Manager
Concurrent ServerBased Recording
Sessions at Central Site
Only

at the central site that will be
monitored and recorded by a
Compliance Recording server at any
given time. Range is 0 - 1,200. This
field is only available if you have
added the optional Compliance
Recording (CR) product.


Concurrent) Quality


9/15/2015
Page 33 of 118
Manager (QM) Users

Required

by Quality Manager (QM). Range is 0 named QM users are configured.
- 3,600. This field is only available if
you have added the optional QM
product.
Quality Manager Users
Required

recorded by Quality Manager (QM) at
any given time. Range is 0 - 1,200.
This field is only available if you have
added the optional QM product.

Total Number of Quality

Manager Concurrent
Endpoint Recording
Sessions for All Sites

recorded by Quality Manager (QM) at

Total Number of Quality

Manager Concurrent
Server-Based Recording
Only

monitored and recorded by Quality
Manager (QM) at any given time.
optional QM product.


Concurrent) Advanced
Quality Manager (AQM)
Users Required

by Advanced Quality Manager
(AQM). Range is 0 - 3,600. This field
is only available if you have added
the optional AQM product.

named AQM users are configured.
Advanced Quality
Manager Users
Required

recorded by Advanced Quality
Manager (AQM) at any given time.
optional AQM product.

Total Number of
Advanced Quality
Manager Concurrent
Endpoint Recording


Total Number of
Advanced Quality
Manager Concurrent
Only

monitored and recorded by
Advanced Quality Manager (AQM) at


Indicate whether you want to add a
Workforce Management Workforce Management (WFM)
Server?
Server to the solution (Yes) or not

License Information to determine if a WFM
9/15/2015
Page 34 of 118
(No). This field is only available if the server is installed.

Package Type selection is Premium.
Number of Configured
Enter the total number of all users to
Workforce Management be configured on the Workforce
(WFM) Users
Management (WFM) server. Range
is 0 - 900. This field is only available
if you have added the optional WFM
product.

named WFM users are configured.

Concurrent) Advanced
Quality Manager (AQM)
Users Required

monitored and recorded by Quality
Manager (QM) at any given time.
optional QM product.

Advanced Quality
Manager Users
Required


Total Number of
Advanced Quality
Manager Concurrent
Endpoint Recording


Total Number of
Advanced Quality
Manager Concurrent
Only

monitored and recorded by
Advanced Quality Manager (AQM) at


Indicate whether you want to add a
Workforce Management Workforce Management (WFM)
Server?
Server to the solution (Yes) or not
(No). This field is only available if the

License Information to determine if a WFM
server is installed.
Number of Configured
Enter the total number of all users to
Workforce Management be configured on the Workforce
(WFM) Users
Management (WFM) server. Range
is 0900. This field is only available if
you have added the optional WFM
product.

License Information to determine if any named
WFM users are configured.
Total Number of
Concurrent Workforce
Management (WFM)
Users


users that will have their
performance and schedules traced
by a Workforce Management (WFM)
server at any given time. Range is 0 300. This field is only available if you
have added the optional WFM
product.
9/15/2015
Page 35 of 118
Codec for Unified CCX

Based Recording and
Playback Session
Select the codec required to digitize

agent audio recordings for storage
and playback. Options are G.711 or
G.729. This field is only available if
the Package Type selection is
Enhanced or Premium.

the Codec field.
Number of Unified CCX

Based Simultaneous
Recording and Playback
Sessions
Enter the number of simultaneous

recording/playback sessions that
may occur at any given time. Range
is 0 - 64. This field is only available if
Enhanced or Premium.

the Recording Count field. If no value is set,
use the corresponding value previously entered
in the Cisco Unified Contact Center
Express/IPIVR Configuration & Ordering Tool
that was used to design the initial deployment
(if available).
Number of Simultaneous Enter the maximum number of

Silent Monitoring
sessions at any given time when
Sessions
supervisors may monitor agent
conversations. Range is 0 - 32. This
Type selection is Enhanced or
Premium.


Remote Monitoring
Sessions
supervisors may monitor agent
conversations at remote sites. Range
is 0 - 32. This field is only available if
Premium.


Finesse Workflow Based simultaneous Finesse workflow
Recording Sessions
based recording sessions that may
occur at any given time. Range can
be 0-400, but it cannot be more than
Total Number of Concurrent Agents
Handling Inbound Calls. This field is
selection is Premium and the
Desktop Type selection is Finesse.
Number of Simultaneous Enter the maximum number of chat
Agent Chat Sessions
sessions over the web that agents
might be engaged in at any given
time. Range is 0-50.
For existing deployments, check the value in

the Historical Reports > Chat Traffic
Analysis > Peak Chat field. For new
deployments enter the anticipated value.

Historical Reporting
Sessions
supervisors may view historical
reports. Range is 0 - 16.

the Number of HR session licenses field. If
no value is set, use the corresponding value
previously entered in the Cisco Unified Contact
Center Express/IPIVR Configuration & Ordering
Tool that was used to design the initial
deployment (if available).
Number of Simultaneous Enter the maximum number of Skills

Skills Manager Sessions Manager sessions that the
supervisors may be running at any
Enter the number of supervisors in the

deployment.
9/15/2015
Page 36 of 118
given time. Range is 0-Total Number

of Supervisors.
Number of Inbound IVR
Ports

concurrent inbound IVR ports in use.
Range is 1 - 300.

License Information to display the IVR ports
licensed. The number of IVR ports licensed
may be more than the maximum number of IVR
ports in use for inbound calls. You can find out
the maximum number of inbound IVR ports in
use by using the corresponding value
previously entered in the Cisco Unified
CCX/IPIVR Configuration & Ordering Tool that
was used to design the initial deployment (if
available).
Number of Outbound
IVR Ports

concurrent outbound IVR ports in
use. Range is 1 - 300.

License Information to display the IVR ports
licensed. The number of IVR ports licensed
may be more than the maximum number of IVR
ports in use for outbound calls. You can find out
the maximum number of outbound IVR ports in
use by using the corresponding value
previously entered in the Cisco Unified
CCX/IPIVR Configuration & Ordering Tool that
was used to design the initial deployment (if
available).
Number of VXML Ports

concurrent IVR ports running
VoiceXML. Range is 0 - 80. This field
is only available if the Package Type

Simple or Complex
Grammar for ASR Ports
Select whether the solution needs to

recognize speech with simple or
complex grammar. Complex
grammar reduces performance and
may require multiple servers. This
Type selection is Premium.

Number of ASR Ports
Enter the maximum number of IVR

ports using automatic speech
recognition (ASR). Range is 0 - 100.
This field is only available if the

Number of TTS Ports
Enter the maximum number of IVR

ports using text-to-speech (TTS)
ports. Range is 0 - 160. This field is

Do You Want to Add an

IPCC Gateway PG?
Indicate whether you want to add an

IPCC Gateway PG (peripheral
gateway) to the solution (Yes) or not
(No). An IPCC Gateway PG allows
Unified CCX to appear as a
traditional ACD connected to a
Unified Intelligent Contact
Management Enterprise (Unified

9/15/2015
Page 37 of 118
ICME) system.
Percentage of Unified
CCX Calls being
Recorded
Enter the percentage of Unified CCX

calls being recorded. Range is 0% to
100%.
Output
The following table describes the function of the fields on the Output section of the Unified Contact Center Express Options
page . The particular fields that appear in the Output section depend on the values specified in the Unified Contact Center
Express | Options section.
Unified Contact Center ExpressOutput Section
Field
Description
BHCC Values
Inbound
Displays the calculated busy hour call completion (BHCC) capacity for incoming
calls that the solution can support.
Outbound
Displays the calculated busy hour call completion (BHCC) capacity for outgoing calls
that the solution can support.
Selected Unified CCX

Package Type
Displays the Package Type selection chosen.
Unified CCX Servers

Primary Platform
Displays the recommended Unified CCX server platform. To override the

recommendation, select another server from the pull-down selection list. The server
you select affects the Unified CCX Server Available Capacity value.
Server Type
Displays the recommended B-series (blade) or C-series (chassis) Cisco Unified

Computing System server hardware type. To override the recommendation, select
another server type from the pull-down selection list. This field only appears if a VM
OVA template is chosen in the Primary Platform field. Default value is based on the
OVA template chosen in the previous field. Virtualization rules and
recommendations are available on the Cisco DocWiki at docwiki.cisco.com under
the category Systems and the topic Unified Communications Virtualization.
Standby Platform
Displays a suggested standby server for High Availability deployments. To override

this value, select an appropriate option from the drop list provided. The Default value
is "None"
Unified CCX Server

Available Capacity
Displays the available capacity (percentage of resources free) available on the

selected Unified CCX server platform.
CR/QM/AQM, and Recording Servers

Base CR/QM/AQM Server
Displays the minimum server platform required to support CR/QM/AQM. To override

the recommendation, select another server from the pull-down selection list. The
server you select affects the CR/QM/AQM Server Available Capacity value.
CR/QM/AQM Server
Available Capacity

selected Compliance Recording, Quality Manager, and/or Advanced Quality
Manager server platform.
9/15/2015
Page 38 of 118
SPAN-based Recording
Server at Central Site
Displays the minimum server platform required to support CR/QM/AQM using

Switched Port Analyzer (SPAN) to capture voice packets directly from the IP
network. To override the recommendation, select another server from the pull-down
selection list. The server you select affects the Central Site Recording Server
Available Capacity value.
Central Site Recording

Server Available Capacity

selected Switched Port Analyzer (SPAN)-based recording server platform.
Type and Number of

Additional SPAN-based
Recording Servers with
QM/CR Sessions <= 50
If you specified "CR Only" in the Unified Contact Center Express Options section,
select the server platform and enter the number of additional Switched Port Analyzer
(SPAN)-based recording servers that will also support up to 50 Quality Manager or
Compliance Recording sessions. If "QM only" or "AQM only" or "CR, QM, and AQM"
is specified in the Unified Contact Center Express Options section, then select the
server platform and enter the number of additional Switched Port Analyzer (SPAN)based recording servers that will also support up to 25 Quality Manager or
Compliance Recording or Advanced Quality Manager sessions.
Type and Number of

QM/CR Sessions > 50 but
<= 60
(SPAN)-based recording servers that will also support between 51 and 60 Quality
Manager or Compliance Recording sessions. If "QM only" or "AQM only" or "CR,
QM, and AQM" is specified in the Unified Contact Center Express Options section,
then select the server platform and enter the number of additional Switched Port
Analyzer (SPAN)-based recording servers that will also support between 26 and 30
Quality Manager or Compliance Recording or Advanced Quality Manager sessions.
Type and Number of

QM/CR Sessions > 60 but
<= 100
Type and Number of

QM/CR Sessions > 100
but <= 150
Workforce Management Server

WFM Server
Displays the required Workforce Management (WFM) server platform. To override

the recommendation, select another server from the pull-down selection list. The
server you select affects the WFM Server Available Capacity value.
Server Type
Specify the WFM server VM Type
WFM Server Available

Capacity

selected Workforce Management (WFM) server platform.
9/15/2015
Page 39 of 118
CCX Inbound
The following table describes the function of each field in the Inbound page for Unified Contact Center Express (available for
System Release Sizing and Compatible Components Sizing scenarios). Use these fields to identify the type of traffic you expect
in the call center and create an entry for each type of activity.
Unified Contact Center Express Inbound
Field
Description
Input Source
Service Level Goal

(SLG)

must be answered within the number business requirements.
of seconds specified in the Target
Answer Time field. This value is the
average of all calls answered
immediately when agents are
available along with those calls that
are queued when no agents are
available. For example, if the target
answer time is 3 seconds and the
SLG is 95%, no more than 5% of
incoming calls will wait longer than 3
seconds. A higher SLG percentage
increases the number of agents
goal. Range is 1 - 99%.
Target Answer Time
Enter the target answer time that is

used with the SLG percentage to
determine the service level goal for
the Unified CCX system that you are
designing. A shorter target answer
time increases the number of agents
goal. Range is greater than 0.

Percentage of Incoming
Calls through Unified
Border Element (IP-IPGW)
Enter the percentage of incoming

H.323 or SIP based calls through
Cisco Unified Border Element (IP-IP
gateway). Range is 0 - 100%.
This is determined by the choice of gateway

protocol and whether the incoming calls are
configured to arrive through Cisco Unified
Border Elements or regular Gateways. If more
than one type of access is used then CDR or
RTMT may be used to estimate the
percentages of BHCA through the Cisco
Unified Border Element. If all calls arrive
viaCisco Unified Border Elements, enter 100%.
Unified Contact Center Express - Self Service

Average Call Treatment
Time (sec)
Enter the average time, in seconds,

that will be required for calls handled
by the call center. Range is greater
than 0.
For existing deployments, in the Unified CM

Inbound BHCA
Enter the total number of inbound

calls that are presented to the call
center during the busiest one-hour
period of the day. Range is greater
than 0.
For existing deployments, this value can be

obtained from call detail records using the
standard ICM reporting facility by counting the
number of incoming calls that terminate at a
Unified CCX inbound component.
Unified Contact Center Express -Traffic Mix

Percentage of Total
Enter the percentage of calls that are For existing deployments, in the Unified CM
9/15/2015
calls
Page 40 of 118
expected to be of this type. This is

the first field in each traffic mix
profile, which defines the percentage manually analyze the results.
of the Total Incoming BHCA that is
represented by this traffic mix. The
sum of all percentages for all must
equal 100%. The remaining fields in
this table are specific to the traffic
mix profile being defined. They
further define the behavior of the
traffic mix. Default is 50%. Range is
0 - 100%.
Average Talk Time (sec) Enter the average talk time, in

seconds, for the traffic mix profile
being defined. Default is 180. Range
is greater than 0.

Avg. Wrap-Up Time

(sec)

required by the agent to wrap up
after completing calls defined by this
traffic mix profile. Default is 60.

Avg. Call Treatment

Time - VRU (sec)

that will be required for calls defined
by this traffic mix profile when
transferred to a VRU. Default is 60.

Wait before Abandon Tolerance (sec)
Enter the length of time, in seconds,

that callers can be expected to wait
before the call is disconnected for
calls defined by this traffic mix profile.
Default is 150. Range is greater than
0.

Percent of Calls
Transferred
Enter the percentage for calls

defined by this traffic mix profile that
will be transferred to another agent.

Percent of calls
conferenced
Enter the percentage of calls defined For existing deployments, this value can be
by this traffic mix profile that will
obtained from call details using the standard
generate an ad hoc three-way
ICM Reporting Facility using agent statistics.
conference with a supervisor or
another agent. Default is 5%. Range
is 0 - 100%.
CCX Outbound
The following table describes the function of the fields in the Unified Contact Center Express Outbound sections. The Unified
CCX Outbound page is available when the Unified CCX Package Type field on the Options page is set to Premium.
Unified Contact Center Express - Outbound
Field
Description
Input Source
9/15/2015
Page 41 of 118
Unified Contact Center Express - Direct Preview Outbound Traffic

Average Busy Hour Call Enter the average amount of time, in
Holding Time per Agent seconds, an agent is involved in each
(sec)
direct preview outbound call during the
busiest hour of the day. Average holding
time is the sum of the agent talk time and
the agent wrap-up time. Range is greater
than 0.

Configuration Manager go to Configure
ICM > Calls > Call Type Bulk Edit >
Retrieve and manually analyze the results.
Average Number of
Outbound Calls per
Agent during Busy Hour
Enter the average number of direct

preview outbound calls handled by each
agent during the busiest hour of the day.
During direct preview calls, the dialer
passes the call to the agent at the same
time the number is being dialed, so the
agent hears the ringback. Range is
greater than 0.

Dialing Mode
Select the outbound dialing mode from

the pull-down selection list, either IVR
Predictive (the dialer dynamically
determines the number of telephone
numbers to call for each agent and only
passes a call to an agent when a person
has been contacted), IVR Progressive
(the dialer calls a fixed number of
telephone numbers per agent and only
has been contacted), Agent Preview, or
Agent Progressive. Default is IVR
Predictive.

Option > Dialer > Dialing mode to
determine the value.
Number of Outbound
Ports
Enter the number of dialer ports assigned

to the selected campaign for making
outbound calls. Default is 0. Range is
equal to or greater than 0.
For existing deployments, in ICM

Option > Dialer > Port Map Selection
tab.
Campaigns
Answering Machine
Enter the percentage of outbound calls
Calls Transferred to IVR answered by an answering machine that
will be transferred to an IVR. Default is
50%. Range is 0 - 100%.

Average Holding Time in Enter the number of seconds allowed for

IVR
the IVR to handle the call (the sum of the
agent talk time and the agent wrap-up
time). Default is 60. Range is greater than
or equal to 1.
Answered Calls
Transferred to IVR

answered by a person that will be
transferred to an IVR. Default is 30.
Range is 0 - 100%.

Average Holding Time in Enter the expected average hold time in

IVR
seconds. Average hold time is the sum of
the agent talk time and the agent wrap-up
time. Default is 25. Range is equal to or
greater than 1.
9/15/2015
Page 42 of 118
Unified Contact Center Express - Predictive/Progressive Outbound Traffic

Dialing Mode
Select the outbound dialing mode from

the pull-down selection list, either
Predictive (the dialer dynamically
determines the number of telephone
numbers to call for each agent and only
has been contacted), or Progressive (the
dialer calls a fixed number of telephone
numbers per agent and only passes a call
to an agent when a person has been
contacted). Default is Predictive.
Number of Agents
Enter the number of agents assigned to

the selected campaign for making
outbound calls. Default is 0. Range is
equal to or greater than 0.
Abandoned/Answering
Machine Calls
Transferred to IVR

answered by an answering machine that
will be transferred to an IVR. Default is
50%. Range is 0 - 100%.

Option > Dialer > Dialing mode to

Average Holding Time in Enter the number of seconds allowed for

IVR
the IVR to handle the call (the sum of the
agent talk time and the agent wrap-up
time). Default is 60. Range is greater than
or equal to 1.
Answered Calls
Transferred to Agents

answered by a person that will be
transferred to an agent. Default is 30.
Range is 0 - 100%.

Average Holding Time at Enter the expected average hold time in

Agents
seconds. Average hold time is the sum of
the agent talk time and the agent wrap-up
time. Default is 25. Range is equal to or
greater than 1.

Options for the Cisco Unified Communications Manager pages are grouped together under the heading Unified
Communications Manager in the navigation list on the right of the sizing tool page. The sizing options for Cisco Unified
Communications Manager include the following:
z
Deployment Model Page
Endpoints Page
Traffic Mix Page
Dial Plan Page
Applications Page
Media Page
Output Page
9/15/2015
Page 43 of 118
Deployment Model Page

The Deployment Model page allows the user to describe/verify settings for a deployment. This populates the tool with accurate
numbers for evaluating expansion of the deployment.
The following table describes the function of each field on the Unified Communications Manager: Deployment Model page.
Unified Communications ManagerDeployment Model Section
Field
Description
Input Source
Software Release
Displays the Unified CM release to

be used for sizing, based on the
version chosen when the sizing
scenario was defined.
For existing deployments, the Unified CM

Administration Page lists the Unified CM
version in the About menu.
Unified CM Trace Level
Select a value from the drop-down

list to represent the default Unified
CM Trace Level. Choose the
Detailed setting for any Unified CM
Trace Level setting higher than Error.
In most cases, the trace level is set
to Error. The Detailed setting sizes
the solution to support trace settings
that may be used for advanced
troubleshooting. The default setting
is Default.
For existing deployments, the trace level on

Unified CM is set per server, service, and
service group through the Serviceability Web
page in the trace configuration settings.
Trace Compression
Select On or Off option based on

whether trace compression is
enabled or disabled in this solution.
The default for releases prior to 8.0 is
Off. For releases 8.0 and above,
trace compression is always On and
cannot be turned Off. For existing
deployments, the Enterprise
Parameters Configuration screen in
the Unified CM Administration web
page includes the configuration for
Trace Compression.
For existing deployments, the Enterprise

Parameters Configuration screen in the Unified
CM Administration web page includes the
configuration for Trace Compression.
Database Complexity
Select the complexity of the

database used with this solution
(Simple or Complex). Estimate the
complexity based on the
implementation, especially the
complexity of the dial plan. This
setting increases the capacity of the
solution results, which may be
required for configurations with a
complex dial plan database. Enabling
this flag enables the tool to use
higher cost values for performance. It
invokes a multiplier to increase
solution capacity for dial plan
constructs that may increase the
BHCA. For example, complex
translation patterns may increase the
BHCA because a single user-initiated
This is the user estimate regarding complexity.

Set this flag to complex to help ensure that the
solution capacity will support higher dial plan
complexity under all call volume scenarios.
9/15/2015
Page 44 of 118
call may generate multiple calls. The

default is Simple.
Number of Regions
Enter the number of regions used in For existing deployments, the Find and List
this solution. Regions are used for
Regions screen in the Administration web page
controlling codec selection; one or
provides the number of configured Regions.
more regions are typically configured
for each physical location. The
number entered here should be the
actual or final anticipated number of
regions for the entire system, even if
multiple clusters are expected.
Default is 1. Range is 1 - 200,000.
Number of
Sites/Branches
Enter the total number of locations

anticipated for the entire solution.
Locations are used to control
bandwidth usage on the network and
typically correspond to the number of
physical locations. There is an upper
limit to the number of locations that
may be configured within a single
cluster. Default is 1. Range is 1 100,000.
For existing deployments, the Find and List

Locations screen in the Unified CM
administration web page provides the number
of locations.
Number of Device Pools Enter the number of device pools

included in this solution. Default is 1.
Range is 1 - 100,000.
For existing deployments, from Unified CM

Administration go to System > Device Pools to
determine this value.
CDR
Select On or Off to determine

whether Call Detail Records on the
Unified CM servers are enabled or
disabled in this solution. The default
for Unified CM is Off. The default for
this field represents the Unified CM
default.
For existing deployments, refer to the product

documentation for CDR Analysis and Reporting
to verify whether CDR is enabled.
CMR
Select On or Off to determine

For existing deployments, refer to the product
whether Call Management Records
documentation for CDR Analysis and Reporting
are enabled or disabled (On or Off) in to verify whether CMR is enabled.
this solution. The default is Off.
Endpoints Page
The Endpoints page provides the following sections:
z
Devices
Clients
Users
9/15/2015
Page 45 of 118
Devices
The following table describes the function of each field in the Devices section of the Endpoints page.
Use the fields in this section to specify the number of phones on the system, the protocol, and if security is enabled for the
phone.
For SIP phones, also specify whether En-bloc or KPML dialing is used. En-bloc dialing occurs when all digits are collected at
the phone and then sent together as a block to the Unified CM. Key Press Markup Language (KPML) is a standards-based
protocol that sends individual key presses to the Unified CM. KPML increases the load on the Unified CM server.
Certain phone models support only En-bloc dialing, while newer models support either En-bloc or KPML. Phones that support
both En-bloc and KPML default to KPML.
Unified Communications Manager: EndpointsDevices
Field
Description
Input Source
Number of SCCP Non

Secure Phones
For Audio Only, enter the total

number of SCCP non-secure phones
using audio only. Default is 0. Range
is 0 - 10,000,000.

Phones screen in the Unified CM
Administration web page provides the number
of phones. The filter mechanism may be used
to distinguish protocol or security profile.
For Audio and Video, enter the total

number of SCCP non-secure phones
using audio and video. Range is 0 10,000,000.

to distinguish protocol or security profile.

number of SCCP secure phones
is 0 - 10,000,000.

phones screen in the Unified CM Administration
web page provides the number of phones. The
filter mechanism may be used to distinguish
protocol or security profile.

number of SCCP secure phones
using audio and video. Range is 0 10,000,000.


number of SIP non-secure phones
using En-bloc dialing with audio only.
Phone models 3911, 7905G, 7912G
or G A, 7940G, and 7960G, when
configured for SIP, are capable only
of En-bloc dialing and should be
counted in this field. All other phones
using SIP can support either En-bloc
or KPML. KPML is the default
behavior for phones that support it.
Count every SIP non-secure phone
using En-bloc dialing in this field.
Default is 0. Range is 0 - 10,000,000.

Administration go to Device > Phone and
evaluate by searching by Device Protocol
cross-referenced with Device Pool Setup for
Security or Dialing, Manual process.

using En-bloc dialing with audio and
video. Range is 0 - 10,000,000.

Number of SCCP
Secure Phones
Number of SIP Non

Secure Phones En-bloc
dialing
Number of SIP Secure
9/15/2015
Phones En-bloc dialing
Number of SIP Non

Secure Phones KPML
dialing
Number of SIP Secure

Phones KPML dialing
Page 46 of 118
number of SIP secure phones using

En-bloc dialing. Phone models 3911,
7905G, 7912G or G A, 7940G, and
7960G, when configured for SIP, are
only capable of En-bloc dialing and
should be counted in this field. All
other phones using SIP can support
either En-bloc or KPML. KPML is the
default behavior for phones that
support it. Count every SIP secure
phone using En-bloc dialing in this
field. Default is 0. Range is 0 10,000,000.


En-bloc dialing with audio and video.
Range is 0 - 10,000,000.


using KPML dialing using only audio.
KPML is a method for transferring
Dual-Tone Multi frequency (DTMF)
digits over a network, which requires
extra processing on the Unified CM
cluster. Phone models 3911, 7905G,
7912G or G A, 7940G, and 7960G,
when configured for SIP, are only
capable of En-bloc dialing and
should not be counted in this field. All
other phone models that use SIP can
support either En-bloc or KPML.
KPML is the default behavior for
phones that support it. Count every
SIP non-secure phone using KPML
dialing in this field. Default is 0.
Range is 0 - 10,000,000.


using KPML dialing using audio and
video. Range is 0 - 10,000,000.


KPML dialing with audio only. KPML
is a method for transferring DualTone Multi frequency (DTMF) digits
over a network, which requires extra
processing on the Unified CM
cluster. Phone models 3911, 7905G,
7912G or G A, 7940G, and 7960G,
when configured for SIP, are only
capable of En-bloc dialing and
should not be counted in this field. All
other phone models that utilize SIP
can support either En-bloc or KPML.
KPML is the default behavior for
phones that support it. Count every

9/15/2015
Page 47 of 118
SIP secure phone using KPML

dialing in this field. Default is 0.
Range is 0 - 10,000,000.
KPML dialing with audio and video.
Range is 0 - 10,000,000.

Number of Mobile Client For Audio Only enter the total

Devices
number of mobile client devices such
as Cisco Jabber for iPhone and
Cisco Jabber for Android configured
on the system. Range is 010,000,000.
For new deployments, the value entered in this

field should correspond to the expected number
of users that will be provisioned for mobile
client devices. For existing deployments, the
Find and List Phones screen in the Unified CM
of configured endpoints. The filter mechanism
may be used to distinguish enpoints based on
device type.
For Audio and Video enter the total

number of mobile client devices such
as Cisco Jabber for iPhone and
Cisco Jabber for Android configured
on the system. Range is 010,000,000.

field should correspond to the expected number
of users that will be provisioned for mobile
client devices. For existing deployments, the
Find and List Phones screen in the Unified CM
of configured endpoints. The filter mechanism
may be used to distinguish enpoints based on
device type.
Enter the total number of analog

phones using VG2xx, VG3xx, and
ATAs. Range is 0 - 10,000,000.

Analog Phones on
VG2xx/ VG3xx/ATA
Series Gateways
Clients
The following table describes the function of each field in the Clients section of the Endpoints page.
Unified Communications Manager: Endpoints Clients Section
Field
Description
Number of IP
Communicators (SCCP) number of Cisco IP Communicator
instances running the SCCP protocol
is 0 - 10,000,000. For Audio and
Video, enter the total number of
Cisco IP Communicator instances
running the SCCP protocol using
both audio and video. Range is 0 10,000,000.
Number of IP
Communicators (SIP)
Input Source
to distinguish phones by their type and
protocol.
Enter the total number of Cisco IP

Communicator instances running the Phones screen in the Unified CM
9/15/2015
Number of Unified
Personal
Communicators
Page 48 of 118
SIP protocol. Note that these are

Audio Only. Range is 0 10,000,000.

to distinguish phones by their type and
protocol.

number of Cisco Unified Personal
Communicator instances using audio
only. Note that the system will count
as devices only those instances that
run in softphone mode and not in
deskphone control mode. Default is
0. Range is 0 - 10,000,000. For
Audio and Video, enter the total
number of Cisco Unified Personal
Communicator instances using both
audio and video. Range is 0 10,000,000.

to distinguish phones by their type.
Number of Unified Client For Audio Only, enter the total

Services Frameworks
number of Cisco Unified Client
Services Framework instances using
audio only. The system counts as
devices only those instances that run
in softphone mode and not in
deskphone control mode. Default is
0. Range is 0 - 10,000,000. For
Audio and Video, enter the total
number of Cisco Unified Client
Services Framework instances using
both audio and video. Range is 0 10,000,000.

to distinguish phones by their type. Jabber for
iPad client can be included in this input. If video
calling is not going to be used, then enter
number in the Audio only column input. If
Jabber for iPad will be using video, then enter
the number in the Audio & Video column input.
For iPad, consider these as "softphone mode".
Jabber for Windows and Mac clients can also
be included as Unified Client Services
Frameworks endpoints.
Users
The following table describes the function of each field in the Users section of the Endpoints page.
Unified Communications Manager: Endpoints Users Section
Field
Description
Input Source
Total Number of Devices Displays the total number of phones This field is display only.
using the solution, which is the total
of all phones of any protocol, security
setting, audio, audio and video, and
dialing mechanism.
Total Number of Busy
Hour Users
Enter the maximum number of users

who may initiate or receive calls
during the busiest hour of the day.
The default is the value displayed in
the Total Number of Devices field.
Range is greater than 0 and less
than the value displayed in the Total
Number of Devices field.
For existing deployments, this number may be

derived from the Total Number of System
Users field. Typically most, but not all, users
may be using the system at its busiest hour.
9/15/2015
Total Number of System Enter the number of users supported

Users
by the deployment. In some
scenarios there may be more users
than phone devices, or there may be
more phones than users. This
number is used to estimate call
volumes and patterns. Specify the
total number of actual users of the
system, which is not necessarily the
number of user accounts configured
on the system. Default is 0. Range is
greater than 0 and less than the
value displayed in the Total Number
of Devices field.
Page 49 of 118
For existing deployments, this total requires

detailed knowledge of the deployment because
the actual number of users may not correspond
to any values configured in the system.
Traffic Mix Page

The sections on the Traffic Mix page determine the overall BHCA for the system and define how that overall BHCA is
subdivided by call flow (by specified percentages). The significance of this information is that different call flows have various
impacts to the system sizing. The Traffic Mix page provides the following sections:
z
Unified Communications Manager: Traffic Mix
PSTN Traffic
Expressway B2B Traffic
Intercluster Traffic
Intracluster Traffic

The following table describes the function of each field in the Traffic Mix section of the Traffic Mix page.
Field
Description
Input Source
User Pattern
The suggested pattern of usage

related to levels of BHCA and ACHT
is configured in the next two fields.
The tool auto-populates those fields.
The values provided may be
manually overridden by entering
values into the BHCA and ACHT
fields. Default is Moderate BHCA,
Moderate ACHT.
This field allows selection of predetermined

values. If you are relying on the preset user
patterns to set BHCA and ACHT, the choice is
based on rough estimation of the deployment
environment.
This field specifies the number of calls per hour
during the busiest hour of the day. The values
change depending on what you select. For
example, if you select Moderate BHCA,
Moderate ACHT, the suggested values are as
follows:
z
Low BHCA is two non-conferencing
9/15/2015
Page 50 of 118
calls per user per hour.

z
Moderate BHCA is four nonconferencing calls per user per hour.
High BHCA is six non-conferencing

calls per user per hour.
The suggested values for call holding time are

one minute for short ACHT, three minutes for
moderate ACHT, five minutes for ACHT.
Average Busy Hour Call Enter the average number of call
Attempts (BHCA) per
attempts per hour per device during
User Excluding
the busy hour. Range is 0.25 - 12.
Scheduled Conference
Calls and Unified CCE
Agents
For existing deployments, if highly reliable

numbers for BHCA and ACHT are required it is
possible to collect Call Detail Records for CDR
analysis. CDR Analysis and Reporting provide
summary reports that give a basic snapshot
view of BHCA.
Total BHCA Excluding

Agents
Displays the calculated total BHCA

for the entire solution based on the
number of busy hour users and the
average BHCA per user entered
above.
Average Call Holding

Time (ACHT) Excluding
Calls (min)
Enter the Average Call Holding Time

per user excluding scheduled
conference calls and Unified CCE
calls. Default is 3.00. The range is
0.50 minutes to the maximum
determined by the Average Busy
Hour Call Attempts (BHCA) per User
entered above. It is 60 minutes/hour
divided by the BHCA in calls/hour,
which gives a result in minutes.
For existing deployments, it is possible to

collect Call Detail Records for CDR analysis.
An analysis of the CDR records would be
necessary to determine the average call
duration.
Traffic Split Scenario
Select whether the traffic is mostly

For existing deployments, analysis of Call
on-net (Predominately On-Net),
Detail Records can provide verification of any
offnet (Predominately Off-Net), or
assumptions.
balanced between the two (Balanced
On-Net Off-Net). This specifies an
approximation of the ratio of calls
that stay entirely within the system
being sized compared to the number
of calls that originate or terminate
from an external system (an example
of an external system is the PSTN).
This is used to adjust call traffic
calculations. Predominantly means
about 80% or more. Default is
Balanced On-Net Off-Net.
PSTN Traffic
The following table describes the function of each field in the PSTN Traffic section of the Traffic Mix page.
Unified Communications Manager: Traffic MixPSTN Traffic Section
9/15/2015
Page 51 of 118
Field
Description
BHCA Incoming from

PSTN
For existing deployments, this value is obtained

Enter the estimated percentage of
from Call Detail Records (calling and called).
the total non transit BHCA calls
originating on the PSTN and entering
the system. Non transit (or user calls)
can be calls
z
Incoming from PSTN
Outgoing to PSTN
Incoming from other clusters
Outgoing to other clusters
Incoming from other

enterprises
Outgoing to other enterprises
Inter-cluster calls (to and from

other users within same
clusters)
Input Source
The default values are

z
25% incoming from PSTN
25% outgoing to PSTN
50% intra-cluster calls
The default BHCA is 4, which means

that during a busy call, a user will
z
Receive one call from PSTN

(1 out of 4 or 25%)
Make one call to PSTN (1 out

of 4 or 25%)
Receive one call from one of

the other users in the same
cluster and a call from one of
the users in the same cluster
(total of two calls or 50%)
The range is 0 to 100%.

BHCA Outgoing to
PSTN

the total non Transit BHCA calls
originating on the system and
destined for the PSTN. Range is 0 100%.
For existing deployments, this value is obtained

from Call Detail Records (calling and called).
Total PSTN BHCA

Displays the total BHCA of calls to
and from the PSTN calculated as the
sum of the above two fields
(percentages) This percentage is
applied on the Total Non Transit
BHCA from the Input section of this
page.
9/15/2015
Page 52 of 118
Percentage of Total
PSTN BHCA through
H323 Trunks (GK
Controlled)

total PSTN BHCA coming through
H323 GK controlled gateways.
Range is 0 - 100%.

protocol and allows the number of each type of
gateway to be expressed as a percentage of
the BHCA. If more than one type of gateway is
used then CDR or RTMT may be used to
estimate the percentages of BHCA that each
type of gateway represents. If all gateways are
of a single gateway type, enter 100%.
Percentage of Total
PSTN BHCA through
H323 Trunks (Non-GK
Controlled)
Enter the percentage of the Total

PSTN BHCA calls to and from the
PSTN that are connected through
H.323 gateways controlled by an
H.323 gatekeeper. Range is 0 100%. The arbitrary default for the
four gateway types is 100% MGCP.
Because MGCP has the least impact
and H.323 the highest impact,
specifying H.323 will cause the
system to be sized with greater
capacity than using the default.

Percentage of Total
PSTN BHCA through
MGCP Trunks

PSTN BHCA calls that use MGCP
gateways. Range is 0 - 100%. The
arbitrary default for the four gateway
types is 100% MGCP. MGCP has
the least impact and H.323 the
highest impact. Because MGCP has
the least impact and H.323 the
highest impact, specifying H.323 will
cause the system to be sized with
greater capacity than using the
default.

Percentage of Total
PSTN BHCA coming
through SIP Trunks

PSTN BHCA that use SIP gateways
or SIP trunks to other types of SIP
devices. Unified CM does not
distinguish between SIP gateways
and SIP Trunks. Enter the total
number of SIP trunks configured on
the Unified CM. Range is 0 - 100%.

used, then CDR or RTMT may be used to
Percentage of PSTN
H.323 and SIP Trunks
BHCA through CUBE
(Unified Border Element
(IP-IP GW))
Enter the percentage of the total

PSTN BHCA that use Cisco Unified
Border Element (IP-IP GW) when
either or both H.323 and SIP trunks
are configured on the Unified CM.
Range is 0 - 100%.

protocol and whether the call traffic is
configured to be placed through the Cisco
Unified Border Element or regular PSTN
gateways. If more than one type of access is
estimate the percentages of BHCA through
each type of PSTN access methods. If all call
traffic is through Cisco Unified Border
Elements, enter 100%.
Note
The total values entered in the Percentage of PSTN BHCA for H.323 (with and without GK control), SIP, and MGCP
fields must total 100%. The value in the Percentage of traffic through Cisco Unified Border Element is expressed as a
percentage of the total PSTN BHCA.
9/15/2015
Page 53 of 118
Expressway B2B Traffic

The following table describes the function of each field in the Expressway B2B Traffic section of the Traffic Mix page.
Unified Communications Manager : Traffic Mix Expressway B2B Traffic Section
Field
Description
Input Source
BHCA Incoming from

Other Enterprises
Enter the percentage of the total non- For existing deployments, this value can be
transit BHCA for calls incoming from obtained from the call detail record (calling and
other enterprises. Range is 0 - 100%. called).
BHCA Outgoing to Other Enter the percentage of the total non- For existing deployments, this value can be
Enterprises
transit BHCA for calls outgoing to
obtained from the call detail record (calling and
other enterprises. Range is 0 - 100%. called).
Total Expressway B2B
BHCA
Displays the total Expressway B2B

busy hour call attempts (BHCA) as
the sum of the above two fields
(percentages).
Percentage of InterEnterprise Active Calls

Transferred to PSTN
due to Poor Quality
Enter the percentage of active VoIP For existing deployments, this value can be
calls between enterprises that should obtained from the call detail record (calling and
be transferred to TDM circuits in the called).
PSTN due to poor voice quality.
Range is 0 - 100%.
Intercluster Traffic
For smaller deployments only a single cluster may be necessary, while multiple clusters may be necessary with larger
deployments. In other cases the number of individual separate clusters may be dictated by other design considerations such as
a geographical scope or because clusters are being created for distinct functions or administrative domains. For planning new
deployments it is suggested to not complete this section until all other sections are complete. Then if the results indicate that
multiple clusters are required, revisit this section to evaluate the inter cluster BHCA and refine the results.
The following table describes the function of each field in the intercluster BHCA section of the Traffic Mix page.
Unified Communications Manager: Traffic MixIntercluster Traffic Section
Field
Description
Input Source
BHCA Incoming From

Other Clusters
Enter the percentage of the total non- For existing deployments, this value can be
transit Busy Hour Call Attempts
(BHCA) for calls incoming from other called).
clusters via intercluster trunks. Do
not include calls between Unified CM
clusters that are through gateways.
Range is 0 - 100%.
BHCA Outgoing to Other Enter the percentage of the total non- For existing deployments, this value can be
clusters
transit BHCA for calls outgoing to
other clusters via intercluster trunks. called).
Do not include calls between Unified
9/15/2015
Page 54 of 118
CM clusters that are through

gateways. Range is 0 - 100%.
Total Intercluster BHCA
Displays the total BHCA of calls over This field is display only.
intercluster trunks calculated as the
sum of the above two fields
(percentages). The resulting
percentage is applied on the Total
Non Transit BHCA from the Input
section of this page.
Percentage of total IC
BHCA through H.225
trunks (GK controlled)

intercluster busy hour call attempts
(BHCA) between clusters that pass
through H.225 gatekeeper controlled
intercluster trunks. Default is 0%.
Range is 0 - 100%.
If more than one intercluster trunk type is used,

the traffic mix can be determined using the call
detail records (CDR) or Unified CM RTMT to
type of gateway represents.
BHCA through
Intercluster Trunks (GKcontrolled )
Enter the percentage of the Total ICT

BHCA between clusters through
intercluster trunks controlled by an
H.323 gatekeeper. Default is 0%.
Range is 0 - 100%.
If more than one intercluster trunk type is used,

the traffic mix can be determined using the call
detail records (CDR) or Unified CM RTMT to
In most deployments, a single type of

ICT is used, so you will enter 100%
for the type used, and set the other
three fields to 0%. If more than one
type of ICT is used, set the
percentages to reflect the traffic
pattern.
BHCA through
Intercluster Trunks
(Non-GK-controlled)

BHCA between clusters through
intercluster trunks that are not
controlled by an H.323 gatekeeper.
If more than one ICT type is used, the traffic

mix can be determined using the CDR or RTMT
to estimate the percentages of BHCA that each

pattern.
BHCA through SIP
Intercluster Trunks

BHCA between clusters through SIP
intercluster trunks. Default is 100%.
Range is 0 - 100%.
If more than one ICT type is used then the

traffic mix can be determined using the CDR or
RTMT to estimate the percentages of BHCA
that each type of gateway represents.

pattern.
Percentage of
Intercluster H.323 and
SIP Trunks BHCA
through CUBE (Unified
Border Element (IP-IP

BHCA between clusters over H.323
and SIP trunks through Cisco Unified
Border Element (IP-IP GW). Default
is 0%. Range is 0 - 100%.
If any of the Intercluster call traffic is configured

to go through the Cisco Unified Border
Element, then the percentage of ICT traffic
through the Cisco Unified Border Element may
be determined by using CDR or RTMT. If all
9/15/2015
GW) )
Note
Page 55 of 118
Intercluster traffic goes through Cisco Unified

Border Elements, then enter 100%.
The total values entered in the Percentage of total ICT BHCA through H.225, ICT (with or without GK control), and SIP
trunk fields must total 100%. The value in the Percentage of traffic through Cisco Unified Border Element is expressed
as a percentage of all ICT BHCA.
Intracluster Traffic
The following table describes the function of each field in the Intracluster Traffic section of the Traffic Mix page.
Unified Communications Manager: Traffic MixIntracluster Traffic Section
Field
Description
Percentage of
Intracluster BHCA
Enter the percentage of the total non- This value is equal to total BHCA minus
transit BHCA that remains within the Intercluster and PSTN.
cluster (to and from phones). Default
is 50%. Range is 0 - 100%.
Total Intracluster BHCA
Displays the total Intracluster BHCA

calculated based on the percentage
entered in the field above.
Percentage of
Intracluster BHCA IP to
IP
Enter the percentage of total

Intracluster BHCA traffic that is from
an IP phone to an IP phone. Range
is 0 - 100%. The percentage in this
field, plus the field below, must add
up to 100%.
Under special circumstances where this is less

than 100%, CDR analysis can be used or the
system designer may determine the value.
Percentage of Total
Intracluster BHCA IP to
PSTN to IP (VoPSTN)

Intracluster BHCA traffic that is
routed over the PSTN between two
IP phones that are on the same
cluster.
For existing deployments, this can obtained

from the call detail record (a non-trivial effort,
based on Device Name/Type value). Normally
set to 0%. Under special circumstances where
this is higher than 0% CDR analysis can be
used or the system designer may determine the
value.
Typically, this call flow occurs only

during failure scenarios. However,
some systems are designed to route
calls between IP phones on the
same cluster over the PSTN. This
parameter allows these scenarios to
be represented.
Input Source
Range is 0 - 100%. The percentage

in this field, plus the field above,
must add up to 100%.
9/15/2015
Page 56 of 118
Dial Plan Page

The Dial Plan page provides the following field sections:
z
Softphone and Deskphone Control Modes
Directory Numbers (DNs) and Shared Lines
Partitions
Routes
Service Advertisement Framework / Call Control Discovery
Global Dial Plan Replication (GDPR)
Hunt Pilot
Softphone and Deskphone Control Modes

Cisco Unified Personal Communicator and Cisco Unified Client Services Framework clients can operate either as standalone in
a softphone mode or as a desktop application with which the user can control their deskphones. When used in the deskphone
control mode, these applications use CTI services in the Unified CM and must be counted in the CTI device count. In addition,
Cisco Unified Mobile Communicator clients also use CTI services when enabled in deskphone call log integration mode.
Directory Numbers (DNs) and Shared Lines

The following table describes the function of each field in the general section of the Dial Plan page.
Unified Communications Manager: Dial PlanDirectory Numbers (DNs) and Shared Lines Section
Field
Description
Input Source
Total Number of DNs
Enter the total number of directory

numbers. Default is the total phones.
Range is the total number of phones
to 254 times the total number of
phones.

Administration go to Call Routing > Directory
Number and click Find without applying any
filters. The system displays a list of directory
numbers with the total shown at the top. For a
new system, the total amount of directory
numbers can be estimated by multiplying the
number of expected users by the average
number of DNs each user will be assigned.
Number of DNs Shared

Across Additional
Endpoints
Enter the total number of directory

numbers that are shared across
multiple endpoints. Range is 0 to the
total number of DNs.

determined using the Cisco Unified Reporting
Tool. This tool can be accessed by using the
Navigation drop-down menu in Unified CM
interface. From the Cisco Unified Reporting
screen, click Unified CM Shared Lines to
display a list of shared lines. For a new system,
this number can be estimated based on
expected business functions of each user.
Average Number of
Additional End Points
Enter the average number of

additional endpoints sharing directory determined using the Cisco Unified Reporting
9/15/2015
sharing DNs
numbers. Range is 1 - 20.
Page 57 of 118
Tool. This tool can be accessed by using the

Navigation drop-down menu in Unified CM
interface. From the Cisco Unified Reporting
screen, click Unified CM Shared Lines to
display a list of shared lines with the number of
endpoints sharing the line. For a new system,
this number can be estimated based on
expected business functions of each user.
Partitions
The following table describes the function of each field in the Partitions section of the Dial Plan page.
Unified Communications Manager: Dial Plan Partitions Section
Field
Description
Input Source
Number of Partitions
Enter the number of partitions. Range is For existing deployments, from Unified
1 - 400,000.
CM Administration go to Call Routing >
Class of Control > Partition to
Number of Calling Search

Spaces
Enter the number of calling search

spaces. Range is 1 - 400,000.
For existing deployments, from Unified

Class of Control > Calling Search
Space to determine the value.
Number of Translation
Patterns
Enter the number of translation patterns.

Translation patterns are an advanced
dial plan construct. Range is 1 1,000,000.

Translation Pattern to determine the
value.
Routes
The following table describes the function of each field in the Routes section of the Dial Plan page.
Unified Communications Manager: Dial PlanRoutes Section
Field
Description
Input Source
Number of Route Patterns
Enter the number of routing patterns.

Range is 1 - 1,000,000.

Route/Hunt > Route Pattern to
Number of Route Lists
Enter the number of route lists. Range is For existing deployments, from Unified
0 - 200,000.
Route/Hunt > Route List to determine
the value.
Number of Route Groups
Enter the number of route groups.
9/15/2015
Page 58 of 118
Range is 0 - 200,000.

Route/Hunt > Route Group to
Service Advertisement Framework / Call Control Discovery

The following table describes the function of each field in the Service Advertisement Framework / Call Control Discovery
(SAF/CCD) section of the Dial Plan page.
Unified Communications Manager: Dial PlanSAF/CCD Section
Field
Description
Input Source
Number of Advertised DN
Patterns
Enter the number of hosted directory

number patterns advertised to other call
control entities on a Service
Advertisement Framework (SAF)
network. Range is 0 - 1,000,000.

Call Control Discovery > Hosted DN
Pattern to determine the value.
Number of Learned DN
Patterns
Enter the number of directory number

patterns learned from remote call
control entities on a Service
Advertisement Framework (SAF)
network. Range is 0 - 1,000,000.

Call Control Discovery > Requesting
Service to determine the value.
Global Dial Plan Replication (GDPR)

The following table describes the function of each field in the Global Dial Plan Replication (GDPR) section of the Dial Plan page.
Unified Communications Manager: Dial Plan Global Dial Plan Replication (GDPR) Section
Field
Description
Input Source
Alternate Numbers
Added to Local Digit
Analysis
Alternate Numbers Not
Added to Local Digit
Analysis
Number of Provisioned
URIs
Imported Patterns
Imported URIs
Alternate Numbers
URIs Without URI
9/15/2015
Page 59 of 118
Specific PSTN Failover

URIs With URI Specific
PSTN Failover
Patterns
Hunt Pilot
The following table describes the function of each field in the Hunt Pilot section of the Dial Plan page.
Unified Communications Manager: Dial Plan Hunt Pilot Section
Field
Description
Input Source
Number of Hunt Pilots
Enter the number of hunt pilots.

Range is 1 - 100,000.

Administration go to Call Routing >
Route/Hunt > Hunt Pilot > Find to determine
the value.
Number of Hunt Lists
Enter the number of lists configured

for hunt groups. Range is 1 200,000.

Route/Hunt > Hunt List > Find to determine
the value.
Number of
Circular/Sequential Line
Groups
Enter the number of

circular/sequential line groups.
Range is 0 - 200,000.

Route/Hunt > Line Group > Find to determine
the value.
Average Number of
Members in a Circular
Line Group
Enter the average number of phones For existing deployments, from Unified CM
assigned to a single line group.
Range is 0 - 100.
the value.
Total Number of
Broadcast Line Groups
Enter the total number of broadcast

line groups. Range is 0 - 10,000

the value.
Average Number of
Members in a Broadcast members in a broadcast line group.
Line Group
Range is 0 - 15.

the value.
Applications Page
The Unified Communications Manager Applications page provides the following field sections:
z
Extension Mobility
Cisco Unified Mobility
9/15/2015
Page 60 of 118
Unified CM Assistant
Web Dialer
Attendant Console
3rd Party Application CTI Integration
BLF Presence
Clients
CTI Controlled Device
Applications: Agents
Unified Communications Manager: 3rd Party Routing Rules Application
Extension Mobility
The following table describes the function of each field in the Extension Mobility section of the Applications page.
For some fields in this section, the upper range is determined by the value of the Total Number of Busy Hour Users field (see
the Endpoints Page).
Unified Communications Manager: Applications PageExtension Mobility Section
Field
Description
Number of Extension
Mobility Users Using the
Extension Mobility Cross
Cluster Feature
Enter the number of users employing

the Extension Mobility Cross Cluster
(EMCC) feature. This feature allows an
enterprise user of one Cisco Unified
Communications Manager cluster
(home cluster) to log in to a Cisco
Unified IP Phone of another Cisco
cluster (visiting cluster) during travel as
if the user is using the IP phone at the
home office. Range is 0 to the value
entered into the Number of Busy Hour
Users field on the Endpoint page of the
component.
Input Source
Max Logins per Minute

Required for Extension
Extension Mobility logins per minute
Mobility Cross Cluster Users expected during the busiest hour of
Extension Mobility usage for cross
cluster users. Range is 1 to the value
entered for the preceding Number of
Extension Mobility Users Using the
Extension Mobility Cross Cluster
Feature. field.
Total Number of Extension
Mobility Users
Enter the number of users enabled for

Extension Mobility. Range is 0 to the
value entered into the Total Number of
System Users field on the Endpoint
page of the Unified Communications
Manager component.

total number of Device Profiles
configured from the Unified CM
Administration Device > Device
Settings > Device Profile page for
each Unified CM in the solution.
Max Logins per Minute
9/15/2015
Required
Page 61 of 118
Extension Mobility logins per minute

expected during the busiest hour of
Extension Mobility usage. This value is
compared with Extension Mobility login
capacity numbers for the type of server
selected. Range is 1 to the value
entered in the Total Number of
Extension Mobility Users field.
Extension Mobility-related counters of

the Real Time Monitoring Tool (RTMT)
during the peak hours to extract trend
information.
Cisco Unified Mobility

The following table describes the function of each field in the Cisco Unified Mobility section of the Applications page.
For some fields in this section, the upper range is determined by the value of the Total Number of System Users field (see the
Endpoints Page).
Unified Communications Manager: Applications Page Cisco Unified Mobility Section
Field
Description
Input Source
Total Number of
Mobility Users
Enter the number of users expected to use

Cisco Unified Mobility. Default is 0, because
of the system and PSTN gateway utilization
implications when enabling users to take
advantage of Cisco Unified Mobility
features.
For new deployments, the value entered in

this field should correspond to the expected
number of users that have mobile client
devices or that will be using Cisco Unified
Mobility features.
With Unified CM version 10.0(1) and later,

the default value is either 0 or the value
entered in the Number of Mobile Client
Devices input on the Endpoints page.
Mobile client device users are always
configured for Unified Mobility and as such
this value of this field must be equal to or
greater than the number of mobile client
devices configured on the system.
Users should only be enabled for Cisco
Unified Mobility if they have a mobile client
device or if they need to use features such
as Mobile Connect, Mobile Voice Access
and Enterprise Feature Access 2-Stage
Dialing, and Single Enterprise Voicemail
Box.
Range is 0 to the value entered in the Total
Number of System Users field on the
Endpoint page of Cisco Unified
Communications Manager section.
Keep in mind the following high-level
guidelines with regard to user capacities:
z
For existing deployments, the value entered

in this field can be determined by finding the
total number of Remote Destination Profiles
plus mobile client devices (Cisco Dual Mode
for iPhone, Cisco Dual Mode for Android,
etc.) configured on the system using the
Find and List Remote Destination Profiles
and Find and List Phones under Cisco
Administration. For version 7.0 and later,
these pages can be found from Cisco
Unified CM Administration by going to
Device > Device Settings> Remote
Destination Profiles and Device > Phone.
For deployments of Cisco Unified
Communications Manager 5.x and earlier,
determining the total number of mobility
users must be done on the Cisco Unified
MobilityManager application server. This
can be done on the Find and List Cisco
Mobile Connect Users page. For Cisco
Unified MobilityManager version 1.2, this
page can be found from Cisco Unified
MobilityManager Administration by going to
User > User Information.
With Cisco Unified CM versions 6.x

and later, the maximum number of
mobility users supported per cluster
is 15,000 (with MCS-7845 or OVA
template equivalents if running on
virtualized servers). Note that
9/15/2015
Page 62 of 118
support of a maximum 15,000 users

per cluster is based on a single
Remote Destination or Mobility
Identity per user. If more than one
Remote Destination or Mobility
Identity per user is configured, the
number of mobility users decreases.
z
Average Number of
Remote Destinations
or Mobility Identities
per User
With Cisco Unified CM versions 5.x

and earlier, one or more Cisco
Unified MobilityManager application
servers are required and the
maximum number of mobility users
supported per cluster is 4,500 (with
MCS-7845 servers). To achieve the
maximum number of users per
cluster, three Cisco Unified
MobilityManager application servers
are required. Note that with Cisco
5.x and earlier, the type of servers
deployed within the cluster may limit
the maximum number of mobility
users supported because of CTI
capacity limitations
Enter the average number of remote

destinations and/or mobility identities each
user will have. Default for this field is 1,
because large numbers of remote
destinations per user result in a significant
increase in PSTN gateway utilization.
Range is 14 for Cisco Unified
Communications Manager versions 5.x and
earlier, or 110 for Cisco Unified
Communications Manager versions 6.x and
later
For new deployments, the value entered in

this field should correspond to the average
number of Remote Destinations/Mobility
Identities or off-system phone numbers
mobile client device and Cisco Unified
Mobility users will have. A remote
destination or mobility identity is typically a
mobile phone, but additional off-system
phones such as a home phone can be
defined.
For existing deployments, the value entered
in this field can be determined by finding the
number of Remote Destinations and
Mobility Identities configured on the system
and associated to Remote Destination
Profiles and mobile client devices using the
Find and List Remote Destinations page
under Cisco Unified CM Administration and
dividing by the total number of Remote
Destination Profiles and mobile client
devices configured on the system. For
example, if there are 200 Remote
Destination Profiles and 200 Cisco Jabber
for Android devices configured on the
system and 600 Remote Destinations and
200 Mobility Identities associated to these
profiles/devices on the system, you divide
800 Remote Destination/Mobility Identities
by 400 Remote Destination Profiles/mobile
client devices and determine that you have
an average of 2 Remote Destinations or
Mobility Identities per user ([600+200]/
[200+200]= 2).
For Cisco Unified Communications Manager
versions 5.x and earlier where a Cisco
Unified MobilityManager application server
9/15/2015
Page 63 of 118
is required, determining the number of

remote destinations configured on the
MobilityManager applications server is a
manual process. The Cisco Mobile Connect
User Group Configuration page for each
user must be viewed and the number of
Associated Remote Destinations for all
users must be tallied
Average BHCA for
Two Stage Dialing
(Mobile Voice
Access, Enterprise
Feature Access)
Enter the average BHCA for mobile voice

access and enterprise feature access twostage dialing per user. Default is 0. Range is
0 to the average busy hour call attempts
(BHCA) per user excluding scheduled
conference calls and Unified CCE agents.
Average BHCA for

Automatic Enterprise
Dialing (Dial-viaOffice)
Enter the average BHCA for Dial-via-Office

automatic enterprise dialing per mobile
client device user. Default is 0. Range is 0
to the average busy hour call attempts
conference calls and Unified CCE agents.
If highly reliable numbers for automatic

enterprise dialing BHCA are required, it is
possible to collect Call Detail Records for
CDR analysis. An analysis of the CDR
records would be necessary to determine
this average BHCA.
The following table describes the function of each field in the Unified CM Assistant section of the Applications page.
Endpoints Page).
Unified Communications Manager: ApplicationsUnified CM Assistant Section
Field
Description
Input Source
Total Number of
Unified CM Assistants
Enter the total number of Assistants

handling Manager calls that will be
included in the solution. Range is 0 to 50%
of the Total Number of System Users
configured on the Endpoint page of the
component.
For existing deployments, the number of

configured assistants for a specific cluster
can be verified in the Unified CM
Administration pages by going to Bulk
Administration > Managers/Assistants >
Generate Assistant Reports.
Average Number of
Lines or DNs per
Enter the average number of lines or DNs

required on the Unified CM Assistant.
Range is 0 - 254.
For existing deployments, determining this

value requires accessing every Unified CM
Assistant phone in the system, recording
the number of DNs configured on the
phone, and then taking an average across
all the Unified CM Assistant phones. From
Unified CM Administration go to Device >
Phone and locate each phone that is
operated by a Unified CM Assistant.
Total Number of
Unified CM Managers
Enter the total number of Managers that

will be included in the solution. Range is 0
to 50% of the Total Number of System
Users configured on the Endpoint page of
the Unified Communications Manager
component.

configured managers for a specific cluster
can be verified in the Unified CM
Administration pages by going to Bulk
Administration > Managers/Assistants >
Generate Manager Reports.
9/15/2015
Page 64 of 118
Average Number of
Lines or DNs per
Unified CM Manager
Enter the average number of lines or DNs

required on the Unified CM Manager.
Range is 0 - 254.
For existing deployments, determining this

value requires accessing every Unified CM
Manager phone in the system, recording
the number of DNs configured on the
phone, and then taking an average across
all the Unified CM Manager phones. From
Unified CM Administration go to Device >
Phone and locate each phone that is
operated by a Unified CM Manager.
Incoming BHCA per

Unified CM Manager
Enter the average number of incoming call

attempts in the busiest hour for a Unified
CM Manager. Incoming call attempts for
the Unified CM Managers will be handled
by the Unified CM Assistants. Range is
0.25 - 12.
For existing deployments, the Call Detail

Records (CDRs) of the call processing
agent may be used to analyze calls to
Unified CM Manager directory numbers.
Number of Lines or
DNs on Unified CM
Manager Assistant CTI
Route Point
Enter the total of DNs required on the

Unified CM Assistant CTI route point. With
multiple clusters, enter the average
number of DNs on each cluster Unified CM
Assistant CTI Route Point. The CTI Route
Point DNs are required to uniquely match
all the Unified CM Manager DNs and
redirect them to the Unified CM Assistant
service. CTI Route Point DNs may contain
wildcards to match contiguous Unified CM
Manager DNs. Range is 0 to 15% of the
value entered into the Total Number of
System Users field on the Endpoints page
of the Unified Communications Manager
component. The number of DNs required
to uniquely match Unified CM Manager
DNs and redirect them to the Unified CM
Assistant service should not approach the
maximum value.
For existing deployments, for each Unified

CM cluster, from Unified CM
Administration go to System > Service
Parameters. Select a server running the
Cisco IP Manager Assistant service, then
select the Cisco IP Manager Assistant
service. Make note of the associated CTI
Route Point, and then go to Device > CTI
Route Point and determine the number of
lines configured on the IPMA associated
CTI Route Point.
For more information about the operation of the Unified CM Assistant service, see the Unified Communications Solution
Reference Network Design (SRND) guides at the following URL:
http://www.cisco.com/en/US/netsol/ns818/networking_solutions_program_home.html.
Web Dialer
The following table describes the function of each field in the Web Dialer section of the Applications page. For some fields in
this section, the upper range is determined by the value of the Number of Busy Hour Users field (see the Endpoints Page).
Unified Communications Manager Applications Web Dialer Section
Field
Description
Input Source
Total Number of Web Dialer

Users
Enter the total number of Busy Hour

Users that will have the ability to initiate
Web Dialer calls. This is typically a
function of the availability of
applications to users that make use of
the Web Dialer feature. Range is 0 to
the value entered into the Total Number
For both new and existing deployments,

any user capable of logging into User
pages that has an associated phone is
capable of making Web Dialer calls.
This is typically a function of the
availability of applications to users that
make use of the Web Dialer feature.
9/15/2015
Page 65 of 118
of System Users field on the Endpoints

page of the Unified Communications
Manager component.
Average Number of Placed
Calls per User During Busy
Hour Using Web Dialer
Enter the average number of Web

Dialer initiated calls per Web Dialer
User during the busy hour. Range is 0 Average Outgoing BHCA per User.
For existing deployments, this value

can be estimated using the Web Dialerrelated counters of the Real Time
Monitoring Tool (RTMT) during the
peak hours to extract trend information
for total calls made. It does not provide
per user statistics, but rather total
numbers that can be analyzed.
Attendant Console
The following table describes the function of each field in the Attendant Console section of the Applications page.
Endpoints Page).
Unified CM Applications Attendant Console Section
Field
Description
Total Number of Attendant

Console Servers Deployed.
Enter the total number of Attendant

Console Servers being deployed.
Range is 0-100.
Total number of Cached

DNs Monitored by All of the
Attendant Console Servers
Enter the total number of DNs or

phones that are continuously monitored
by all the attendant console servers.
For existing deployments, verify the

configuration on each Unified Attendant
Console server. Alternatively, RTMT
can be used to determine the number of
devices that are CTI monitored by the
Unified Attendant Console server.
Total Number of Attendants
Enter the total number of attendants.

Range is 0 to the total number of users.

attendants can be verified for each
Unified Attendant Console server in the
system. From Attendant Admin go to
User Configuration > Operator
Management.
Average Number of BHCA

per Attendant
Enter the average number of call

attempts in the busiest hour for
Attendant Console Users.
For existing deployments, this value can

be obtained from the Call Detail
Records (non-trivial, tracked using
Device Type/Name).
Total Number of DDI

Gateway (CTI Route Points)
Enter the total number of Direct Dial In

(DDI) Gateways. Range is 0 to the total
number of users.

Direct Dial In Queues can be verified on
each Unified Attendant Console server
in the system. From Attendant Admin go
to User Configuration > Queue
Management to see the number of
queues with configured DDI numbers.
Total Number of CT
Gateway (CTI Ports)
Enter the total number of call park

queues. Range is 0 to 0.2 times the total Call Park Queues can be verified on
number of users.
each Unified Attendant Console server
Input Source
9/15/2015
Page 66 of 118
in the system. From Attendant Admin go

to System Configuration > System
Device Management and count the
number of contiguous numbers
configured for Park Devices .
Total Number of Service and Enter the average number of call
Call Park Queues (CTI
attempts in the busiest hour for
Ports)
Attendant Console Users. Default is 0 if
Total Number of Attendant Console
Servers Deployed is 0, or 1 if Total
Number of Attendant Console Servers
Deployed is greater than 0. Range is 0255 * "Total Number of Attendant
Console Servers Deployed" - "Total
Number of DDI Gateway (CTI Route
Points).

be obtained from Call Detail Records
(non-trivial, tracked using Device
Type/Name).
For more information on the operation of the Unified CM AC service, see the Unified Communications Solution Reference
Network Design (SRND) guides at the following URL: http://www.cisco.com/go/ucsrnd.
3rd Party Application CTI Integration

The following table describes the function of each field in the 3rd party Application CTI Integration section of the Applications
page.
Unified Communications Manager: Applications 3rd Party Application CTI Integration
Field
Description
Input Source
Number of CTI Route Points Enter the total number of CTI route
points for this solution. Range is 0 10,000,000.

CM Administration go to Device > CTI
Route Point to view the total number of
configured CTI route points.
Average Number of Lines or

DNs per CTI Route Points
Enter the average number of lines or

DNs per CTI route point. Default is 1.
Range is 0 - 254.

CM Administration go to Device > CTI
Route Point and view a representative
sample of CTI route points to determine
the average number of lines or DNs
configured.
Average BHCA per CTI

Route Point
Enter the average BHCA per CTI route

point. Default is 100. Range is 1 60,000.

be obtained from Unified CM call detail
records (CDRs), both calling and called
records.
Number of CTI Ports
Enter the total number of CTI ports.

Default is 0. Range is 0 - 10,000,000.

CM Administration go to Device >
Phone to view the total number of CTI
ports configured.
Average Number of Lines or

DNs per CTI Port

DNs per CTI port. Default is 1. Range is CM Administration go to Device >
0 - 254.
Phone to view a representative sample
of phones to determine the average
number of lines or DNs configured for
9/15/2015
Page 67 of 118
each CTI port.

Average BHCA per CTI Port
Enter the average BHCA per CTI Port.

Default is 8. Range is 1 - 1,000.

be obtained from Unified CM call detail
records (CDRs), both calling and called
records.
Product of Number of
Applications and 3rd Party
CTI Controlled Endpoints
Enter the product of the number of 3rd

party applications and the endpoints
they control. Default is 0. Range is 0 to
10,000,000.
For an existing deployment, the number

of CTI controlled devices can be
determined using the Cisco Unified
Communications Manager Real-Time
Monitoring Tool (RTMT). In RTMT, go to
CallManager > CTI Search > CTI
Devices and count the applications
associated for several devices.
Count CTI ports separately. There are

two different inputs for CTI ports and
CTI controlled endpoints in the sizing
tool.
For Cisco Contact Center, do not enter

agent phones in this tab since they are
already accounted for in the Contact
Center section.
For 3rd party Contact Center, use the
Cisco Unified Contact Center section if
the call flows are the same as with a
Cisco Unified Contact Center solution,
and disregard the output related to the
Cisco Unified Contact Center servers.
For example, if the call flows with a 3rd
party Contact Center are the same as
the call flows with UCCE and CVP, use
the UCCE section in this tool, select
CVP as an IVR to size the UC solution,
and disregard the output related to the
UCCE/CVP servers. Similarly, if the call
flows with a 3rd party Contact Center
are the same as the call flows with
UCCE and IP-IVR, use the UCCE
section in this tool, select IP-IVR as an
IVR to size the UC solution, and
disregard the output related to the
UCCE/IP-IVR servers.
each CTI controlled endpoint.
Average Number Lines or
DNs per 3rd Party CTI
Controlled Endpoint

DNs per third-party CTI port. Range is 0 CM Administration go to Device >
- 254.
each CTI port.
Number of CTI Remote

Devices
Enter the total number of CTI Remote

Devices configured on the system.
Range is 0 - Total Number of Busy Hour
Users.
For new deployments, the value entered

in this field should correspond to the
expected number of users that will be
provisioned for CTI Remote Devices.
For existing deployments, the Find and
List Phones screen in the Unified CM
Administration web page provides the
number of endpoint devices. The filter
9/15/2015
Page 68 of 118
mechanism may be used to distinguish

endpoints by device type.
Average Number of Remote
Destinations per CTI
Remote Device
Average BHCA for

Automatic Enterprise Dialing
(Extend&Conect/Dial-viaOffice)

destinations each CTI Remote devices
will have. Default for this field is 1,
destinations per CTI Remote devices
may result in a significant increase in
PSTN gateway utilization. Range is 1
10 for Cisco Unified Communications
Manager versions 9.x and later.
For new deployments, the value entered

in this field should correspond to the
average number of Remote
Destinations CTI Remote device users
will have. A remote destination in this
case is a 3rd party PBX extension or
other off-system device like a mobile
phone.
Enter the average BHCA for Extend &

Connect or Dial-via-Office automatic
enterprise dialing per CTI Remote
device user. Default is 0. Range is 0 to
the average busy hour call attempts
conference calls and Unified CCE
agents.

enterprise dialing BHCA are required, it
is possible to collect Call Detail Records
for CDR analysis. An analysis of the
CDR records would be necessary to
determine this average BHCA.
For existing deployments, the value

entered in this field is determined by
finding the total number of Remote
Destinations associated to CTI Remote
devices on the system using the Find
and List Phones page under Cisco
Unified CM Administration and dividing
by the total number of CTI Remote
example, if there are 200 CTI Remote
devices configured on the system and
300 Remote Destinations associated to
these CTI Remote devices on the
system, you divide 300 Remote
Destinations by 200 CTI Remote
devices and determine that you have an
average of 1.5 Remote Destinations per
CTI Remote device user (300/200= 1.5).
How to Specify BHCA Through 3rd Party CTI Inputs

A 3rd party application handles calls with a BHCA of 1000. The calls that arrive at the CTI Route Point are redirected to a CTI
Port for prompting (one of the 10 CTI ports total in this example). The calls are then transferred to a phone which has one CTI
controlled line (one of the 100 phones CTI controlled in this example). In this scenario, enter the following values in the 3rd
Party CTI Integration section:
z
Number of CTI Route Points: 1
Average Number of Lines or DNs per CTI Route Point: 1
Average BHCA per CTI Route Point: 1
Number of CTI Ports: 10
Average Number of Lines or DNs per CTI Port: 1
Average BHCA per CTI Port: 100 (1000 BHCA over 10 ports).
Number of CTI Controlled End Points: 100
Average Number of Lines or DNs per 3rd party CTI Controlled End Point: 1
Note
The 100 CTI controlled phones also need to be accounted for in the Endpoints tab.
9/15/2015
Page 69 of 118
BLF Presence
The following table describes the function of each field in the BLF Presence section of the Applications page.
Unified Communications Manager: Applications BLF Presence
Field
Description
Input Source
Total Number of DNs Being

Monitored
Enter the total number of DNs being

monitored using the Busy Lamp Field
feature. Range is 0 to the total number
of BLF speed dial entries configured
across the device information pages.
For existing deployments, query the

BLF Speeddial configuration in the
Device information pages.
Average number of Phones

monitoring a DN
For existing deployments, query the

Enter the average number of phones
that are monitored using the Busy Lamp BLF Speeddial configuration in the
Device information pages.
Field feature. Range is 1 - 30.
Clients
The following table describes the function of each field in the Clients section of the Applications page.
Unified Communications Manager: Applications Clients
Field
Description
Enter the percentage of Unified
Personal Communicator Personal Communicator in desktop
in Deskphone Control
control mode. Range is 0 - 100%.
Mode Only
Input Source
For an existing deployment, the number of
deskphones that are under the control of
Unified Personal Communicator can be
Applications and fill in the application ID of the
Unified Personal Communicator CTI
application. All deskphones that are controlled
by that application will be shown along with the
total number.
For deployments where desktop clients are
only used in deskphone control mode, enter
100% to ensure that these devices are not
counted against the endpoint capacity of
Unified CM.
Percentage of Client
Services Framework in
Deskphone Control
Mode Only
Enter the percentage of Unified

Client Services Framework in
desktop control mode. Range is 0 100%.
For an existing deployment, the number of

deskphones that are under the control of
Unified Client Services Framework can be
9/15/2015
Page 70 of 118

Applications and fill in the application ID of the
Unified Client Services Framework CTI
application. All deskphones that are controlled
by that application will be shown along with the
total number.
For deployments where desktop clients are
only used in deskphone control mode, enter
100% to ensure that these devices are not
counted against the endpoint capacity of
Unified CM.
Percentage of Mobile
Clients with Deskphone
Call Log Integration
Enter the percentage of mobile

clients with deskphone call log
integration. This percentage is
applied to the sum of the values
entered in the Number of Dual Mode
Phones with Mobile Client field and
Number of Unified Mobile
Communicator/Cisco Mobile 7
Clients field on the Unified
Communications Manager Endpoints
page. Default is 0%. Range is 0 100%.

field should correspond to the percentage of
mobile clients that are enabled for desk phone
call log integration. Typically, desk phone call
log integration for mobile clients is either
enabled for 100% of users or it is disabled for
100% of users. However, it is possible that only
a percentage of mobile client users actually are
enabled for this feature.
For existing deployments, the value entered in
this field can be determined by finding the total
number of mobile clients that are configured on
the system using the Find and List Phones
page under Cisco Unified CM Administration
and counting the total number of desk phone
MAC addresses that have been associated with
the Cisco Unified Mobility Advantage CTIenabled application user account or accounts
on the Unified CM system. By dividing the total
number of associated MAC addresses by the
total number of mobile client devices that are
configured on the system, the percentage of
desk phone call log integration enabled users
can be determined.
For example, if there are a total of 375 desk
phone MAC addresses associated to all Cisco
Unified Mobility Advantage CTI-enabled
application user accounts and 500 mobile client
devices have been configured on the system,
you divide 375 MAC address associations by
500 mobile client devices and determine that
75% of mobile client users are enabled for desk
phone call log integration (375/500=.75).
Average BHCA per

Mobile Client User for
Dial-via-Office
Enter an average BHCA for mobile

client users that are capable of Dial
Via Office (DVO). This value is
applied to the sum of the values
entered in the Number of Dual Mode
Phones with Mobile Client field and
Number of Unified Mobile
Communicator/Cisco Mobile 7
Clients field on the Unified
page. Default is 0. Range is 0 to the
average BHCA per user, excluding
scheduled conference calls and
Unified CCE agents.
If highly reliable numbers for Dial-via-Office

BHCA are required it is possible to collect Call
Detail Records for CDR analysis. An analysis of
the CDR records would be necessary to
determine this average BHCA.
9/15/2015
Page 71 of 118
Percentage of Client
Enter the percentage of Client
Services Frameworks in Services Frameworks in Extend &
Extend & Connect Mode Connect mode. Default is 0%. Range
is 0100%.

field should correspond to the average number
of Client Services Framework devices expected
to be configured in Extend & Connect mode
Average Number of
Remote Destinations per destinations each mobility-enabled
CSF Device
Client Services Framework device
will have. A mobility-enabled Client
Services Framework device has one
or more Remote Destinations
associated. Default for this field is 1,
destinations per Client Services
Framework device may result in a
significant increase in PSTN gateway
utilization. Range is 110 for Cisco
versions 9.x and later.

field should correspond to the average number
of Remote Destinations Client Services
Framework device users will have. A remote
destination in this case is a 3rd party PBX
extension or other off-system device like a
mobile phone.
Average BHCA for

Automatic Enterprise
Dialing
(Extend&Connect/Dialvia-Office)

enterprise dialing BHCA are required, it is
possible to collect Call Detail Records for CDR
analysis. An analysis of the CDR records would
be necessary to determine this average BHCA.
Enter the average BHCA for Extend

& Connect or Dial-via-Office
automatic enterprise dialing per
mobility-enabled Client Services
Framework device user. Default is 0.
Range is 0 to the average busy hour
call attempts (BHCA) per user
excluding scheduled conference calls
and Unified CCE agents.
For existing deployments, the value entered in

this field can be determined by finding the total
number of Remote Destinations associated to
mobility-enabled Client Services Framework
devices on the system using the Find and List
Phones page under Cisco Unified CM
Administration and dividing by the total number
of mobility-enabled Client Services Framework
example, if there are 400 mobility-enabled
Client Services Framework devices configured
on the system and 800 Remote Destinations
associated to these Client Services Framework
devices on the system, you divide 800 Remote
Destinations by 400 mobility-enabled Client
Services Framework devices and determine
that you have an average of 2 Remote
Destinations per Client Services Framework
device user (800/400= 2).
CTI Controlled Device

The following table describes the function of each field in the CTI Controlled Device section of the Applications page.
Unified CM Applications Page - CTI Controlled Device
Field
Description
Input Source
Average Number of
Applications per CTI
Controlled Device

applications that are controlling or
monitoring the CTI devices. Default
is 0. Range is 1-10.
For existing deployments, consider all the

devices that are CTI controlled or CTI
monitored. Determine the average number of
TAPI/JTAPI applications that are
monitoring/controlling those devices.
9/15/2015
Page 72 of 118
Applications: Agents
The following table describes the function of each field in the Agents section of the Applications page.
Unified Communications Manager: Applications Agents Section
Field
Description
Input Source
Total Number of Unified

Contact Center Agents
Displays the total number of Unified

Contact Center agents used with the
Unified CM system.

ICM > Peripherals > Agent > Agent
Bulk > Agent Bulk Edit to determine
this value.
Total Number of CTI Route

Points for Unified CCE
Enter the total number of CTI route

points associated with Unified Contact
Center. Range is 0 - 100,000.

ICM > Peripherals > Agent > Agent
Bulk > Agent Bulk Edit to determine
this value.

The following table describes the function of each field in the Third-party Routing Rules Application section.
Field
Description
Input Source
Deployment has one or

more Routing Rules
Applications
Choose Yes from the drop-down list if this deployment

will be integrated with one or more third-party Routing
Rules Applications.
Percentage of Calls that

use Routing Rules
Application
Enter the percentage of incoming and outgoing calls

which will be routed by the Routing Rules Application.
Range is 0-100%.
Routing Rules Application

Transport Protocol
Specify if the Routing Rules application connection to

Unified Communications Manager uses HTTP or
HTTPS.
Third-party Routing Rules

Application partner
integration guide
Media Page
The following table describes the function of each field in the Unified CM Media page.
Unified Communications Manager: Media
Field
Description
Input Source
9/15/2015
Page 73 of 118
Unified Communications Manager: MediaMusic On Hold (MOH)

Percentage of Users
Simultaneously Receiving
Unicast MOH Streams
Enter the maximum percentage of

Busy Hour Users that will receive
unicast MOH at a given time during
the busy hour. Range is 0 - 100%.

estimated utilizing the MoH-related counters
of the Real Time Monitoring Tool (RTMT)
during the peak hours to extract trend
information.
Number of Audio Sources

Designated for Multicast
MoH
Enter the number of audio sources per

cluster that will be delivered via
multicast streaming. Range is 0 - 51.
A Unified CM cluster supports up to
51 different MoH audio files, one Live
feed plus 50 audio files.

multicast audio sources can be verified for
each Unified CM cluster. in Unified CM
Administration go to Media Resources >
Music On Hold Audio Source. View each
audio source and verify if the Allow
Multicasting checkbox has been selected.
Unified Communications Manager: MediaMedia Resources

Percentage of IP to IP
Intracluster Calls through
RSVP Agents/Off-box HW
or SW MTPs and
Transcoders
Enter the percentage of IP to IP calls

within a cluster that pass through
RSVP agents, off-box hardware or
software MTPs, and transcoders.
Range is 0 - 100%.

obtained using a combination of the Real
Time Monitoring Tool (RTMT) for call types
and Call Detail Records (CDRs) for the
overall volume.
Percentage of IP to IP
intercluster Calls through
RSVP Agents/HW
MTPs/Transcoders
Enter the percentage of IP to IP calls

between different clusters that pass
through RSVP agents, hardware
MTPs, and transcoders. Range is 0 100%.

obtained using a combination of the Real
Time Monitoring Tool (RTMT) for call types
and Call Detail Records (CDRs) for the
overall volume.
Total number of RSVP

Agents/Off-box HW or SW
MTPs and Transcoders
Enter the total number of RSVP

Agents/HW MTPs/Transcoders.
Range is 0 - 200,000.

Administration go to Media Resources
Configuration > MTPs or Transcoders >
Find to determine this value.
Percentage of Calls being

Conferenced
(Unscheduled
Conferences)
Enter the percentage of unscheduled

conference calls. Default is 0.1%.
Range is 0 - 5%.

obtained using Call Detail Record (CDR)
data.
Total Number of
Conferencing Resources
Enter the total number of conferencing For existing deployments, in Unified CM

resources. Default is the value
Administration go to Media Resources >
entered into the Percentage of
Conference Bridge to determine this value.
Unscheduled Conference Calls field
divided by 32 (because each
resource/bridge can support 32
simultaneous unscheduled
conferences). Range is 0 - 200,000.
Output Page
The Unified CM Output page provides the following sections:
z
Platform and Cluster Size Selection
Call Processing Servers
Minimal System Requirements
9/15/2015
Page 74 of 118
Platform and Cluster Size Selection

The following table describes the function of each field in the Platform and Cluster Size Selection section of the Output page.
Unified Communications Manager: Platform and Cluster Size Selection
Field
Description
Platform
Select the Unified Communications Manager server type from the pulldown selection list. For deployments of MCS-7815 or MCS-7816, there
is no concept of Call Processing server pairs or separate Publisher and
TFTP servers. These servers can only be deployed in pairs with 1:1
redundancy When you select MCS-7815 or MCS-7816 from the Unified
CM server type pull-down selection list, the MIn IPT server pairs pulldown selection list is changed to Number of Unified CM Call Processing
Servers per Cluster. For virtual machines (VMs), Open Virtualization
Archive (OVA) templates are shown for various numbers of endpoints. If
a VM value is selected, an additional Server Type field appears allowing
you to specify the B-series or C-series Cisco Unified Computing System
hardware. Note that for contact center deployments, the number shown
in OVA templates represents subscribers, not the number of agents.
Processing requirements for agents are higher than for other
subscribers, and you must chose an OVA template with a higher number
than the total number of agents. For example, VM-UCM_1000 will not
support 1000 agents; you need to select a higher capacity OVA template
such as VM-UCM_7500.
Server Type
Select the appropriate B-series (blade) or C-series (chassis) Cisco

Unified Computing System server hardware. This field only appears if a
VM OVA template is chosen in the Unified CM Server Type field. Default
value is based on the OVA template chosen in the Unified CM Server
Type field. Virtualization rules and recommendations are available on the
Cisco DocWiki at docwiki.cisco.com under the category Systems and the
topic Unified Communications Virtualization.
Maximum Unified CM Call Processing Select the desired number of server pairs per cluster from the pull-down
Server Pairs per Cluster
selection list. Default is 4 server pairs, which means that in a CUCM
cluster you can have maximum of 8 subscriber nodes. The default option
will always try to give you the minimum number of cluster required for a
solution. The default should be selected in almost all cases. In some
cases, you can select other than the default value for this field. For
example, to deploy more Unified CM clusters than needed, just to
distribute the call processing load on different cluster.
Unified CCE Deployment
Select the Unified Contact Center deployment type from the pull-down
selection list. The only option is Separated Users and Agents. Mixing
Admin phones and agent phones on the same subscriber node is not
recommended. Separate these phones in different nodes for practical
maintenance reasons.
Call Processing Servers
9/15/2015
Page 75 of 118
The following table describes the function of each field in the Call Processing Servers section of the Output page.
Unified Communications Manager: Call Processing Servers
Field
Description
Call Processing Capacity Utilized per

Call Processing VM
Displays the percentage of IPT and IPCC (Unified CCE) Call processing
utilization per server.
Memory Capacity Utilized per Call

Processing VM
Displays the percentage of IPT and IPCC (Unified CCE) memory

capacity utilization.
Endpoints Capacity Utilized per Call

Processing VM
Displays the percentage of IPT and IPCC (Unified CCE) phone capacity
CTI capacity utilized per Call

Processing VM
Displays the percentage of IPT and IPCC (Unified CCE) CTI capacity
Agents Capacity Utilized per VM
Displays the percentage of agent capacity utilization per server.
Minimal System Requirements

The following table describes the function of each output field in the Minimal System Requirements section of the Output page.
Unified Communications Manager : Minimal System Requirements
Field
Description
Estimated Minimum Number of

Clusters
Displays the estimated minimum number of clusters
Publisher Servers
Displays the number of recommended Publisher/Trivial File Transfer

Protocol (TFTP) servers.
TFTPs VMs
Displays the number of recommended TFTP virtual machines.
Minimal Number of Unified CM Call

Processing VM Pairs Number of
Unified CM Call Processing Servers
Displays the recommended number of Unified CM call processing

servers.
Minimal Number of IM & Presence

Servers
Displays the recommended number of IM & Presence Servers.
Unified Communications Manager:

Total Number of Servers (minimal)
Displays the recommended minimal number of servers.
Cisco Emergency Responder

This page lets you describe the characteristics of the Cisco Emergency Responder component.
z
Cisco Emergency Responder Section
9/15/2015
Page 76 of 118
Capacity Utilization
Cisco Emergency Responder Section

The following table describes the function of each field on the E-911 section of the Cisco Emergency Responder page.
Cisco Emergency Responder E-911
Field
Description
Input Source
Software Release
Each system release is tested with the

corresponding Unified CM and ER product
versions. Later versions of ER also support
earlier versions of Unified CM.
Select the desired version of Cisco

Emergency Responder version
compatible with the selected version
of Unified CM. The default ER
version is selected automatically
when you select the Unified CM
version in the sizing tool Identify
Components page.
Number of Endpoints (IP This is the total Number of IP Endpoint Devices This field is display only and is based
Phones) in UCM Setting and Clients entered on the Unified CM
on the number of IP Endpoint
Devices and Clients entered for
Endpoints page.
Unified CM.
Number of Manual
This is the total Number of Analog Phones
Endpoints (Analog
entered on the Unified CM Endpoints page.
Phones) in UCM Setting
This field is display only and is based

on the number of Analog Phones
entered for Unified CM.
Number of Roaming
Phones (including
EMCC logins and
phones physically
relocated across cluster)
This is the number of IP Endpoints Devices and

Clients tracked by one ER Server Group, but
registered to a Unified CM Cluster integrated
with another ER Server Group.
Enter the number of IP Endpoint

Devices and Clients physically
relocated from one Unified CM
Cluster to another plus the expected
number of concurrent Extension
Mobility Cross Cluster Logins.
Number of ERLs
Configured in CER
Setting
An emergency response location (ERL) is a

building, area within a building, or outside area
(if you extend phone service outdoors) that is to
be treated as a single location for emergency
response purposes. All telephones within the
ERL are treated as coming from the same
location.
Enter the number of distinct

emergency response locations
(ERLs) needed to provide the
desired precision of location for
emergency response.
Number of Switches
Configured in CER
Setting
Cisco ER can track IP Endpoint Devices by

Switch Port when connected to supported
Cisco LAN Switches.
If IP Endpoint Devices will be tracked

by connected Switch Port, enter the
number of supported Cisco LAN
Switches to which IP Endpoint
Devices will be connected. If IP
Endpoint Devices will be tracked only
by IP Subnet, enter 0.
Number of Switch Ports

for the Switches
Configured in CER
Setting
Cisco ER can track IP Endpoint Devices by

Switch Port when connected to supported
Cisco LAN Switches.
If IP Endpoint Devices will be tracked

by connected Switch Port, then enter
the total number of ports on the
supported Cisco LAN Switches to
which IP Endpoint Devices will be
connected. If IP Endpoint Devices
will be tracked only by IP Subnet,
9/15/2015
Page 77 of 118
enter 0.
Platform
The capacities of Emergency Responder

Select a platform from the menu for
Server are determined by the platform selected. which all of the Cisco ER Capacity
Utilization Measures are less than
100%. If no such platform is available
then the Unified CM Cluster must be
split into two or more clusters.
High Availability
Deployment
Emergency Responder supports high

Enter Yes for High Availability.
availability. An Emergency Responder server
group consists of up to two Emergency
Responder servers, a primary and a standby or
backup server. This redundancy helps to
ensure that Emergency Responder remains
available in case one server becomes disabled.
Capacity Utilization
The following table describes the function of each field on the Capacity Utilization section of the Cisco Emergency Responder
page. For some fields in this section, the upper range is determined by the value of the Total Number of System Users field
(see the Endpoints Page).
Note If you exceed the maximum range for any of the fields, one of the following warning messages appears:
"Maximum system capacity exceeded. Use higher capacity platform." or "Maximum system capacity exceeded. Use
separate configurations for multiple clusters."
Cisco Emergency Responder - Capacity Utilization

Field
Description
IP Phones
Displays the percentage of endpoints (IP phones) in a Unified CM setting.
Analog Phones
Displays the percentage of manual endpoints (analog phones) in a Unified CM

setting.
Roaming Phones
Displays the percentage of roaming phones (including EMCC logins and moved
phones across cluster) in the Cisco Emergency Responder.
ERLs
Displays the percentage of ERLs configured in the Cisco Emergency Responder.
Switches
Displays the percentage of switches configured in the Cisco Emergency

Responder.
Switch Ports
Displays the percentage of switch ports configured in the Cisco Emergency

Responder.
Cisco Emergency ResponderOutput

Number of Emergency
Responder Servers
Displays the suggested number of MCS servers required. The sizing tool assumes
redundancy, and one ER group per Unified CM cluster. The sizing tool provides an
estimate based on the assumption that each Unified CM cluster will be paired with
its own, dedicated and redundant ER group. Therefore two servers are included
9/15/2015
Page 78 of 118
per Unified CM cluster. The tool also presumes that all ER servers will be of the
same type. Based on the resulting utilization you may choose to deploy multiple
Unified CM clusters connected to the same ER group, or deploy different platform
types for the ER groups of different Unified CM clusters. You can use the sizing
tool to display output for the resulting Unified CM-ER sets to ensure sufficient
capacity.
This field is visible if an MCS server type is selected in the Platform Type field from
the preceding Cisco Emergency Responder section of fields.
Number of Emergency
Responder VMs
Displays the suggested number of Emergency Responder VMs required. The

sizing tool provides an estimate based on the assumption that each Unified CM
cluster will be paired with its own, dedicated and redundant ER group. This field
appears if a VM OVA template type is selected in the Platform Type field from the
preceding Cisco Emergency Responder section of fields.
In addition, the vCPUs, Ram, vDISK, and vNics, will also be displayed if a VM OVA
template has been selected as the platform type.
Cisco Expressway
This page lets you describe the characteristics of the Cisco Expressway component.
z
Cisco Expressway
Traffic Summary
Platform Selection
Output
Cisco Expressway
This page lets you describe the characteristics of the Cisco Expressway component.
The following table describes the function of each field on the Cisco Expressway section of the Cisco Expressway page.
Cisco Expressway
Field
Description
Input Source
Software Release
Displays the Cisco Expressway release

version to be used for sizing, based on the
version chosen when the sizing scenario
was defined.
For existing deployments, the Cisco

Expressway version is listed on the main
Expressway Overview page (Status >
Overview) when logging into the system as
an administrator. See the Software Version
field.
Percentage of SIP
Endpoints and
Desktop Clients
Registered Through
Expressway
Enter the percentage of endpoints and

desktop clients registered through
Expressway. Percentage is based on total
number of hardware-based endpoints and
desktop clients input under Unified
section. Default is 5%. Range is 0 - 100%.
For an existing deployment, the total

number of video endpoints and desktop
clients capable of registering through
Expressway can be determined by using the
Find and List Phones screen in the Unified
CM Administration web page and filtering
based on those device types supported over
9/15/2015
Page 79 of 118
Expressway. Once the total number of

Expressway capable endpoints on the
system is determined, indicate the
maximum percentage of these devices that
will be concurrently registered through
Expressway at any given point in time.
For new deployments, indicate the expected
percentage of Expressway capable
endpoints you plan to deploy that will be
registered concurrently through
Expressway.
Percentage of Mobile Enter the percentage of mobile clients
Clients Registered
registered through Expressway. Percentage
Through Expressway is based on total number of mobile clients
input under Unified Communications
Manager Endpoints section. Default is
100%. Range is 0 - 100%.

number of mobile clients capable of
registering through Expressway can be
determined by using the Find and List
Administration web page and filtering based
on mobile client device types. Once the total
number of mobile client devices on the
system is determined, indicate the
maximum percentage of these devices that
will be concurrently registered through
Expressway at any given point in time.
percentage of mobile client devices you
plan to deploy that will be registered
concurrently through Expressway.
Percentage of Video Enter the percentage of video conference

Conference Calls
calls through Expressway. Percentage
Through Expressway taken based in part on overall number of
endpoints and traffic mix inputs under
Endpoints and Traffic Mix sections as well
as inputs under the Conferencing and
Collaboration section. Default is 5%. Range
is 0 - 100%.

number of video conference calls traversing
Expressway is ultimately determined by the
user call traffic patterns. If highly reliable
numbers for BHCA and ACHT are required
it is possible to collect Call Detail Records
for CDR analysis. CDR Analysis and
Reporting provide summary reports that
give a basic snapshot view of BHCA.
number of video conference calls that will
be traversing Expressway at a given point in
time.
Percentage of Audio Percentage of Video Conference Calls

Conference Calls
Through Expressway
Through Expressway
Enter the percentage of video conference

calls through Expressway. Percentage
taken based in part on overall number of
endpoints and traffic mix inputs under
Endpoints and Traffic Mix sections as well
as inputs under the Conferencing and
Collaboration section. Default is 5%. Range
is 0 - 100%.
Traffic Summary
The following table describes the function of each field on the Traffic Summary section of the Cisco Expressway page
9/15/2015
Page 80 of 118
Traffic Summary
Field
Description
Total Number of Devices Registered to Expressway Displays the total number of expected concurrent device
(5% of 0 SIP Endpoints/Desktops + 100% of 0
registrations through Expressway based on above inputs.
Mobile)
Total Number of Concurrent Video Calls Through
Expressway
Displays the total number of concurrent video calls through

Expressway based on above inputs. This field is display
only.
Total Number of Concurrent Audio Calls Through

Expressway
Displays the total number of concurrent audio calls through

Expressway based on above inputs. This field is display
only.
Total Number of Concurrent B2B Video Calls

Through Expressway
Displays the total number of concurrent B2B video calls

through Expressway based on above inputs. This field is
display only.
Total Number of Concurrent B2B Audio Calls

Through Expressway
Displays the total number of concurrent B2B audio calls

through Expressway based on above inputs. This field is
display only.
Platform Selection
The following table describes the function of each field on the Platform Selection section of the Cisco Expressway page.
Platform Selection
Field
Description
MRA Platform Type
For existing deployments, in Cisco

Select the Cisco Expressway OVA or
corresponding appliance type from the drop- Expressway Administration, go to System >
Clustering to determine the platform type.
down list provided. Options include:
z
Large (CE1000 appliance or

equivalent large OVA),
Medium (CE500 appliance or

equivalent medium OVA), or
Small (smallest OVA for Business

Edition 6000)
Input Source
For new deployments, select the appliance

or OVA size you plan to deploy. Select
different platform types to see the impact to
server/cluster counts in the Output area
below.
Default is Large.
MRA High
Availability
Deployment
Select whether the Expressway servers are

deployed with high availability. Default is
Yes, which means that Expressway servers
are deployed in redundant fashion.

Expressway Administration, go to System >
Clustering to determine if servers have
deployed in a highly available manner.
For new deployments, select the
appropriate setting based on whether
servers will be deployed in redundant
fashion. Toggle between settings to see the
impact to server/cluster counts in the Output
area below.
9/15/2015
Separate
Expressway Cluster
for B2B Traffic
Page 81 of 118
Select whether separate Expressway

servers are deployed for B2B traffic. Default
is No, which means that the same set of
Expressway servers deployed for MRA is
also used for B2B calling.

Expressway Administration go to
Configuration > Unified Communications
to determine if Unified Communications
mode has been configured as Mobile and
remote access. If so, then leave at default
value (No). If the mode has been configured
as Off, then select Yes as the Expressway
cluster is dedicated for B2B.
For new deployments, select the
appropriate setting based on whether
separate sets of servers will be deployed for
MRA and B2B traffic. Toggle between
settings to see the impact to server/cluster
counts in the Output area below.
Output
This section describes output fields associated with Cisco Expressway in the proposed solution.
Cisco Expressway - Output Section
Field
Description
Number of Expressway-E Clusters & (Number of

Expressway-C Clusters)
Displays the number of recommended Expressway E

and Expressway C clusters. Expressway C cluster
number is listed in parenthesis after the Express E
cluster number. This field is display only.
Number of Expressway-E Servers & (Number of

Expressway-C Servers)
Displays the number of recommended Expressway E

and Expressway C servers. Expressway C server count
is listed in parenthesis after the Express E server count.
Total Expressway-E & (Expressway-C) VM Resources

Needed
Displays the total number of recommended virtual

CPUs, disks, network interfaces, and memory across
the recommended total number of Expressway E and C
servers. Expressway C virtual resource counts are
listed in parenthesis after the Express E resource
counts. This field is display only.
Note that each Expressway E server is specified as
requiring two vNICs given typical edge deployments.
Voice Messaging
This page lets you describe the characteristics of a voice messaging system. For descriptions of the fields on this page, see the
appropriate messaging system from the following list:
z
Unity Connection
3rd Party Voice Messaging System
9/15/2015
Page 82 of 118
Unity Connection
A Cisco Unity Connection voice messaging system can be sized as part of a System Release Sizing or Compatible
Components Sizing scenario as discussed in Describe Voice Messaging Options. In these scenarios, the upper range for some
of the fields is determined by the value of the Total Number of System Users field for the Unified CM (see the Endpoints Page).
The following tables describe the function of each field of the Voice Messaging sizing tool sections, assuming that Unity
Connection was the voice messaging system specified when the sizing scenario was defined.
Unity Connection Voice Messaging
Field
Description
Input Source
Voice Messaging
System
Displays the type of voice messaging system

initially specified when the sizing scenario was
defined (Unity Connection or 3rd Party).

on the component chosen when the
sizing scenario was defined.
VoiceMail Integration
Type
Select the voicemail integration type: SCCP or

SIP. The default is SCCP.
Unity Connection
Release
Displays the release version of Unity

Connection used for sizing calculations.

on the version chosen when the
sizing scenario was defined.
This is set by user preference.
Unity Connection
Configuration
Select whether Unity Connection will be used

strictly for voicemail (Voicemail Only),
integrated voice and Email messaging
(Integrated Messaging), or Unified Messaging
where voicemails are synchronized into the
Email inbox (Unified Messaging/Integrated
Messaging).
Note
This is set by user preference.
Unified Messaging and Integrated

Messaging can be deployed on the
same server.
Unity Connection Voice MessagingSite Type

Field
Description
Input Source
Total of <x> Site Types

Specified
This field displays the number of Unity

Connection site types that have been
described.
Display Only
Add Unity Connection

Site
Click this option to add a Unity Connection site

type. When you add a site type, input fields for
that site type will be available in the Site Type
field section. You can only add a new site type
if there are enough users left (not assigned to
an existing site type) to be assigned to the new
site type.
Edit a Site Type
Click this option to edit an existing Unity

Connection site type. When you choose this
option, a drop-down list appears allowing you to
select the Site Type that you want to edit.
9/15/2015
Page 83 of 118
Delete a Site Type
Click this option if you wish to delete an existing

site type. When you click the option, a dropdown list will appear that allows you to choose
the particular site type to be deleted.
Number of Type 1 Sites
Sites are used here to define a physical site

and user base with similar voicemail
requirements. Each site will have a single
server or number of servers. Unity Connection
supports 5 sites, 5 primary servers or 50,000
users (whichever limit is reached first).
Number of Voice
Messaging Users per
Site
Enter the number of voice messaging users per This corresponds to the number of
site. Default is 0.
users configured for voicemail at a
single site.
Number of Voice
Messaging Users with
Jabber Client per Site
Enter the number of voice messaging users

with Jabber Client per site. Default is 0.
This corresponds to the number of

users configured for voice messaging
that also have Jabber Client at a
single site.
Calls Re-directed to
VoiceMail System
During Busy Hour
Enter the percentage of incoming calls that are

redirected to the voice message system during
the busiest hour. Default is 20%. Range is 0 100%.
For existing deployments, on the

Cisco Unity Connection Serviceability
Web Admin, go to Tools > Reports
> Port Activity Report.
Average Message
Length
Enter the average number of minutes expected

for each voice message. This typically depends
on the type of business and the general sector
supported by the voicemail system. For
example, in a hospital environment, messages
might be very long on average as opposed to a
financial setting. Default is 1.00. Range is 0.50
- 5.00.
This is a set by user preference and

may be verified on existing
deployments through analysis of
CDR records on the call processing
system.
Percentage of Users
Checking Voice
Messages during the
Peak Voice Messaging
System Usage
Enter the percentage of users that are

expected to access the messaging system at
the busiest time, which typically will be to check
an important broadcast message or at the start
of the workday. Default is 10%. Range is 0 100%.
This is set by user preference and

deployments by monitoring CDR
records on the call processing node
to determine the average call
duration to the voicemail system. The
CDR records would be analyzed to
determine whether there is a period
during the day where the call volume
is drastically higher than the average.
Peak Voice Messaging

System Usage Interval
(min)
Enter the typical frequency at which users

check their voice messages during the busiest
time of the day (for example, every 5 minutes,
every 10 minutes, and so forth). Default is
10.00 minutes. Range is 3.00 - 60.00 minutes.

system.
Average Messages
Retrieval Session
Length (min)
Enter the average length of time users spend

listening to voice messages when checking
messages during the busiest time of the day.
For example, if the average user listens to
three voice messages of four minutes each
time they access voicemail, then this value
would be 12 minutes. Default is 3.00. Range is
1.00 - 30.00.

system.
Blocking Probability
Enter the highest acceptable percentage of
This is set by user preference
9/15/2015
Page 84 of 118
calls that may be blocked when the system is

operating at maximum usage and can no
longer process new calls. Default is 1%. Range
is 0.01 - 10%. If blocking is not acceptable, set
this value to the minimum value, which is
0.01%.
regarding the level of response

provided by the system. This is
determined by the system
provisioning which they are trying to
simulate using this tool. If you size a
system so that during the busy hour
there is a possibility that the system
might block a user leaving a voice
message, this should be carefully
noted. Otherwise, this value should
be 1%.
Unity Connection Inbox

Users
Displays the number of users with Unity Inbox

feature enabled. Default is Yes.
For existing deployments, determine

if the Unity Inbox feature has been or
will be enabled for any users.
IMAP Non-IDLE Clients
Indicate whether IMAP Non-IDLE clients will be IMAP Non-Idle clients include
used with Unity Connection (Yes) or not (No).
products such as Cisco Unified
Default is No.
Mobility Advantage, Cisco Unified
Personal Communicator, and IBM
Sametime Voicemail plug-ins. IMAP
Non-Idle Clients do not support IMAP
IDLE functionality. Verify Client
specification for determination.
IMAP IDLE Clients
Indicate whether IMAP IDLE Clients will be

used with Unity Connection (Yes) or not (No).
Default is Yes.
Determine whether IMAP IDLE

clients (such as Outlook 2007) will be
used with Unity Connection. IMAP
IDLE Clients support IMAP IDLE
functionality. Verify Client
specification for determination.
System Level Recording Select the system level recording format.

Format
Default is G.711.
Determine the recording codec used

to store voicemail messages on the
system. Options are PCM Linear,
G.711 u-law, G.711 a-law, G.729a
and G.726.
On the Line Codec
Select the on-the-line-codec format. This is the

codec that is used by endpoints to connect to
Unity Connection. Default is G.711
Determine the codec used by

endpoints to access voicemail
messages on the system. Options
are G.711 u-law, G.711 a-law,
G.729, G.722 and iLBC.
Any Voice Recognition

Sessions?
Select Yes if voice recognition will be used with Determine if Voice Recognition has
the voice messaging system. Default is Yes
been or will be enabled for any
users.
Any Text to Speech

Sessions?
Select Yes if text to speech will be used with

the voice messaging system. Default is Yes.
Determine if TTS has been or will be

enabled for any users.
Platform
Select the type of platform required. VM and

MCS options are available in a drop-down list.
Determine the physical hardware

used by Unity Connection. Options
include Media Convergence Server
(MCS) platforms or Virtual Machine
(VM) platforms such as Cisco Unified
Computing Systems.
Server Type
Select the appropriate B-series (blade) or Cseries (chassis) Cisco Unified Computing
System server hardware. This field only
appears if a VM OVA template is chosen in the
Platform field. Default value is based on the
Virtualization rules and

recommendations are available on
the Cisco DocWiki at
docwiki.cisco.com under the
category Systems and the topic
9/15/2015
VMWare ESXi 5.5

Latency Sensitivity
Option Set to High
Page 85 of 118
OVA template chosen in the Platform field.
Unified Communications
Virtualization.
Select whether the ESXi latency sensitivity is

set to High for the Unity Connection VM.
Default is No.
Selecting Yes will subtract a vCPU

from the Total Unity Connection VM
Resources Needed.
With VMWare release 5.5 and later,
if using the latency sensitivity feature,
you may remove the requirement of
dedicating one physical core per
physical server. This requires the
Unity Connection VM Latency
Sensitivity to be set to High while at
least one other VM is set to Normal.
High Availability
Deployment
Indicate if the Unity Connection deployment is

designed for High Availability (Yes), High
Availability Jabber (Yes with HA for Jabber
Client), or not (No). High Availability concept in
Cisco Unity Connection is called Active/Active
High Availability and consists of a Publisher
Server and a Subscriber Server for
redundancy. When selecting this field the
server number should increase by a multiple of
2. Default is Yes.
High Availability refers to Unity

Connection Active/Active High
Availability. Active/Active High
Availability feature adds a Subscriber
Server for redundancy. As such
selecting this option will double the
server requirement.
Unity Connection Voice Messaging - Output

Field
Description
Suggested Number of VMs Needed

for each Type 1 Site (including
Redundant Servers)
Displays the suggested number of servers required with IMAP or Cisco

PCA and without IMAP or Cisco PCA. If a VM is selected in the Platform
field in the preceding section, the information in these output fields will
be relevant to the specified VM.
Maximum Voice Recognition Sessions Displays the maximum number of recognition Sessions (ASR) per server
(ASR) Per VM Allowed
allowed with IMAP or Cisco PCA and without IMAP or Cisco PCA.
Maximum Text to Speech Sessions
(TTS) Per VM Allowed
Displays the maximum number of Text-to-Speech Sessions (TTS)

allowed per server with IMAP or Cisco PCA and without IMAP or Cisco
PCA.
Ports per VM
Displays the number of ports per server with IMAP or Cisco PCA and
without IMAP or Cisco PCA.
3rd Party Voice Messaging System

A 3rd Party voice messaging system can be sized as part of a System Release Sizing or Compatible Components Sizing
scenario. The following tables describe the function of each field of the Voice Messaging sizing tool sections, assuming that 3rd
Party was the voice messaging system specified when the sizing scenario was defined.
3rd Party Voice Messaging System Input Section
Field
Description
Input Source
Voice Messaging
Displays the type of voice messaging
This field is display only, and is based on
9/15/2015
Page 86 of 118
System
system initially specified when the current

sizing scenario was defined (Unity
Connection or 3rd Party).
the component chosen when the sizing

scenario was defined.
VoiceMail Integration
Type
Select the voicemail integration type:

SCCP or SMDI. The default is SCCP.
Number of Voice
Messaging Users
Enter the number of users with voice

For existing Unity deployments, from the
messaging mailboxes. Default is the same Tools Depot menu, go to Administrative
Tools > License Info Viewer.
value as the Total Number of System
Users on the Endpoints page of the Cisco
Unified Communications Manager group.
Range is 0 to the value of the Total
Number of System Users field.
Calls Redirected to
VoiceMail System During
Busy Hour
Enter the percentage of incoming calls

that are redirected to the voice message
system during the busiest hour. Default is
20%. Range is 0 - 100%.
Average Message
Length (min)
Enter the average number of minutes

expected for each voice message. This
typically depends on the type of business
and the general sector supported by the
voicemail system. For example, in a
hospital environment, messages might be
very long on average as opposed to a
financial setting. Default is 1.00. Range is
1.00 - 30.00.
Cisco TelePresence
The following table describes the function of the fields in the Cisco TelePresence page.
Cisco TelePresence
Field
Description
Software Release
Displays the software versions of TelePresence Server and Conductor.
Total Sites Configured
Displays the total number of sites configured.
Current Site ID
Conferencing System Sizing: Conference Load Needs
Conferencing System Sizing: Equipment Requirement
Current Site ID
The following table describes the function of the fields in the Current Site ID page.
Current Site ID
9/15/2015
Field
Description
Conference Type
Select whether you want the conference type to be scheduled or nonscheduled.
Page 87 of 118
Input
Source
If using a TelePresence Management Server, select Scheduled. If not

using a TelePresence Management Server, select Unscheduled.
Device Type
Select the appropriate TelePresence Server, virtual TelePresence Server,

or MCU device.
Use Conductor?
If using a MCU device, a conductor is optional. Using a conductor is

recommended.
Conference Quality
Select a maximum conference resolution.
Content Mode
Select the mechanism used to share content.
Average Meeting Size
Enter the number of participants for an average meeting.
Number of Simultaneous Enter the number of meetings being held at one time.
Meetings
Clustering Optimization
Select Yes to decrease the size of some clusters to increase efficiency.
Redundancy
Requirement
Enter the percentage of the solution that will be redundant.
Redundancy Provided
at:
Select the site at which duplicate hardware will ensure availability of

conferencing.
Licence Type
Personal Multiparty
Licence Quantity

The following table describes the function of the fields in the Conferencing System Sizing: Conference Load Needs page.
Field
Description
Single Devices (redundancy

requirements)
Displays the number of single devices, with the redundancy

requirements in parentheses.
Two Devices Clusters (redundancy

requirements)
Displays the number of two device clusters, with the redundancy

Three Devices Clusters (redundancy

requirements)
Displays the number of three device clusters, with the redundancy

Four Devices Clusters (redundancy

requirements)
Displays the number of four device clusters, with the redundancy

Licenses Required (redundancy
Displays the number of licences required, with the redundancy
9/15/2015
requirements)
Page 88 of 118

The following table describes the function of the fields in the Conferencing System Sizing: Conference Load Estimations page.
Field
Description
MSE8000 Chassis Needed
Displays the number of MSE8000 chassis needed.
Slots Available
Displays the number of slots available.
Servers Needed
Displays the number of servers needed to load the vTS 8 or 16 core

applications onto.
Appliances Needed
Displays the number of appliances needed.
Total TS8710 Licenses

Required
Displays the total number of licences required.
Total MCU8510 Licenses

Required

Required

Required

The following table describes the function of the fields in the Cisco TelePresence Management Suite page.
Field
Description
Software Release
Displays the software version of TelePresence

Management Suite.
Estimated Number of Concurrent Scheduled

Conferences
Displays an estimated number of Concurrent Scheduled

Conferences.
Estimated Number of Participants in Concurrent

Scheduled Conferences
Displays an estimated number of Participants in Concurrent

Scheduled Conferences.
Estimated Number of Controlled Devices
Displays an estimated number of Controlled Devices.
Number of Controlled Systems Endpoints
Enter the number of Controlled Systems added to

TelePresence Management Suite.
9/15/2015
Page 89 of 118
Number of Endpoints Bookable in Microsoft

Exchange
Enter the number of Endpoints Bookable in Microsoft

Exchange.
Number of Collaboration Meeting Rooms

(Premises)
Enter the number of Collaboration Meeting Rooms.

A WebEx Meetings Server, Unified MeetingPlace or a 3rd Party conferencing system can be sized as part of a System Release
Sizing or Compatible Components Sizing scenario as described in Describe Conferencing and Collaboration Options. In these
scenarios, the upper range for some of the fields is determined by the value of the Total Number of System Users field for the
Unified CM (see the Endpoints Page). For these scenarios, use the tables provided in Conferencing and Collaboration Page.
z
Conferencing and Collaboration Page
Minimal MeetingPlace Equipment Requirement
WebEx Server Sizing
System Usage
Video Usage
Teleconferencing Traffic Description
Deployment Requirements
Conferencing and Collaboration Page

The following table describes the function of each field in the following sections on the Conferencing and Collaboration page:
z
Audio Usage
Video Usage
Web Collaboration Usage
Conferencing Traffic
Conference Calls split
Note
The fields that appear in the sizing tool will depend on whether Unified Meeting Place, or 3rd Party Conferencing and
Collaboration was chosen when the sizing scenario was first defined.

Field
Description
Input Source
Conference System
Displays the conferencing system used for

sizing, based on the Identify Components
9/15/2015
Page 90 of 118
initial input for the System Release or

Compatible Component sizing scenario.
Software Release
Displays the Unified MeetingPlace release

number. This field is only available if
MeetingPlace is selected as the
Conferencing System.
Number of Knowledge Enter the total number of knowledge users

Users
that will have access to the conferencing
system. A knowledge user is a generic
term for a user that will potentially utilize
the conferencing system. The value
entered in this field will be used with
subsequent fields to determine the number
for proper sizing. The default is 100% of
the Number of Busy Hour Users field on
the Endpoints page of the Unified
Communications Manager component. The
range is 0 to the value of the Number of
Busy Hour Users field.
For existing deployments, in the Unified

MeetingPlace Administration Center, go to
User Configuration > User Profiles, the
number of user profiles on the system can
be entered in this field.
Is iLBC Codec
Required?
Indicate whether Internet Low Bandwidth

Codec (iLBC) is required for packetizing
voice during audio conferences (Yes) or
not (No). Using iLBC reduces the number
of voice ports supported by each Unified
MeetingPlace Media Server audio blade.
For existing deployments, from the Unified

MeetingPlace Application Server
Administration home page go to System
Configuration > Media Resource
Configuration to determine if the System
Media Mode is set to Software or
Hardware. If Software is selected, the
software media server does not support
iLBC. If Hardware is selected, check the
Global Audio Mode. If G.711, G.729 is
selected, then iLBC is not in use.
Alternatively if G.711, G.722, G.729, iLBC
is selected, then iLBC is allowed for
conferencing. Unified CM Region
configurations may need to be checked to
further confirm if the iLBC codec is allowed
for Unified MeetingPlace calls.
Is Video Continuous
Presence Required?
Indicate whether continuous presence (as

opposed to voice-activated switching) is
required during videoconferences (Yes) or
not (No). In continuous presence mode,
input from all (or selected) video endpoints
is displayed simultaneously and
continuously. The audio portion of the
conference follows the dominant speaker.
Default is No.

continuous presence is optimal for highly
interactive discussions between speakers
at multiple sites.
Is Line Echo
Cancellation
Required?
Indicate whether Line Echo Cancellation

(LEC) is required to reduce audible echo in
meetings (Yes) or not (No). Using LEC
reduces the number of voice ports
supported by each Unified MeetingPlace
Media Server audio blade.

Hardware. If Software is selected, note that
the software media server does not support
LEC.If Hardware is selected, LEC is built in
to the Hardware media server. Additional
echo canceller configuration settings can
be viewed by going to System
Configuration > Call Configuration >
9/15/2015
Page 91 of 118
Media Parameters.
Media Resource
Option
Select whether Software or Hardware

resources will be used for media
processing. The Hardware option requires
audio/video blade DSP resources on a
Unified MeetingPlace Media Server. The
Software option requires that Express
Media Server is enabled on the Unified
MeetingPlace Application server. Default is
Software (assuming Software is available
as an option).

Hardware.
Monthly Usage
(minutes)
Enter the expected typical amount of time

per month (in minutes) that all users spend
in conference sessions. Default is 0. Range
is equal to or greater than 0.

estimated by evaluating reports available
on the Unified MeetingPlace Administration
Center. Alternatively, the call detail records
(CDRs) of call processing agents may be
used to analyze calls to or from the
conferencing system directory number(s).
Conference System
Usage
Select whether the load on the

conferencing system is considered
Average or Heavy. Default is Average.

Actual Peak Usage

(concurrent users)
Enter the maximum number of users

participating in a conference during any
time during the day. The range is 0 to the
value of the Number of Knowledge Users
field.
For existing deployments, in the Unified

MeetingPlace Administration Center, go to
User Configuration > User Profiles, the
number of user profiles on the system can
be entered in this field.
Percentage of Audio
Users Using Higher
Complexity Codecs
Enter the percentage of all audio users that

employ higher complexity codecs (such as
G.723.1 or G.728). Default is 0%. Range is
0 - 100%. This field is only available if you
choose Yes for the Are Audio Users Using
Higher Complexity Codecs? field.

Audio Usage
Are Audio Users Using Indicate whether users require higher

Higher Complexity
complexity codecs (such as G.723.1 or
Codecs?
G.728) for audio (Yes) or not (No). Default
is No.

determined by evaluating reports available
Video Usage
Video Usage
Select the level of video usage (none, low,

medium, and high). The selected usage
level will dynamically change the value in
the Percentage of Simultaneous Users with
Audio and Video field, which can be further
revised if desired. Default is Low.

(CDRs) of the call processing agent may
be used to analyze calls to or from video
endpoint directory numbers.
9/15/2015
Page 92 of 118
Percentage of
Simultaneous Audio
Users with Video
Enter the maximum percentage of

conferencing users that will be using video
concurrently with audio. The default is
directly related to the selected Video Usage
level. Default is 1%. Range is 0 - 100%

on the MeetingPlace Administration Center.
Alternatively, the call detail records (CDRs)
of the call processing agent may be used to
analyze calls to or from video endpoint
directory numbers.
Percentage of Video
Users Using Desktop
Video Resolution
Enter the percentage of all video users

viewing video in low (desktop) resolution.
Note that the values entered in this field
and the two fields below must total 100%.
Default is 100%. Range is 0 - 100%. This
field is only available if MeetingPlace is
selected as the Conference System and
Software is selected in the Media Resource
Option field.

this field is determined by the capability of
the users' video endpoints and any
corporate policies restricting bandwidth
usage to avoid network contention
problems.
Percentage of Video
Users Using VGA
Video Resolution

viewing video in 640x480 pixel Video
Graphics Array (VGA) medium resolution.
Note that the values entered in this field
and the fields above and below must total
100%. Default is 0%. Range is 0 - 100%.
This field is only available if MeetingPlace
is selected as the Conference System and
Software is selected in the Media Resource
Option field.

problems.
Percentage of Video
Users Using HD Video viewing video in 1920x1080 pixel High
Resolution
Definition (HD) resolution. Note that the
values entered in this field and the two
fields above must total 100%. Default is
0%. Range is 0 - 100%. This field is only
available if MeetingPlace is selected as the
Conference System and Software is
selected in the Media Resource Option
field.

problems.
Web Collaboration Usage

Web Collaboration
Usage
Select the estimated level of conferences

involving web collaboration (None, Low,
Medium, or High). Default is Medium. The
selected usage level will dynamically
change the value in the Percentage of
Simultaneous Web Users field, which can
be further revised if desired. This field is
only available if MeetingPlace is selected
as the Conference System.

estimated by evaluating Reports available
Center.
Which Solution will be

Used for Scheduling
Meetings?
Select the product that will be used to

schedule meetings, either WebEx or
MeetingPlace.

Configuration > Cisco Webex
Configuration > Cisco Webex Site and
Server to determine if the Conference
Scheduling parameter is set to Schedule
and Join from Cisco Webex or Schedule
and Join from Cisco Unified MeetingPlace.
9/15/2015
Percentage of
Simultaneous Audio
Users using Web
Enter the maximum percentage of users

that will be using web collaboration
concurrently. The default is directly related
to the selected Web Collaboration Usage
level. Default is 60%. Range is 0 - 100%.
This field is only available if MeetingPlace
is selected as the Conference System.
Page 93 of 118

on the MeetingPlace Administration Center.
Required Top of the
Hour Dialin Duration
(min)
Enter the expected duration (in minutes) for For existing deployments, this value can be
all members of conferences to dial in at the obtained from the call detail records. First,
beginning of a meeting. Range is 0.1 - 15. look at the report for all calls that terminate
on the MeetingPlace directory number that
are made at the top of the hour, and notice
the portion of the hour where either 80% of
the calls arrive or the number of calls per
minute drops off significantly (that is,
number of calls per minute drops to 20% of
original value), whichever comes first.
Second, take note of the time the last call
in this bracket arrives and calculate the
time from the beginning of the hour to that
call. Round this number up to the nearest
minute. Finally, take an average dialin
duration time across several conference
sessions.
Conference
Equipment Integration
type
Select the protocol used for conferencing

equipment integration: SIP or H323.
Default is SIP.
Scenario
Select the estimated conferencing traffic

This is from user profile; CDR studies
scenario (Predominantly from IP, Balanced multiple customers.
IP and PSTN, Predominantly from PSTN).
The selected scenario will dynamically
change the input values in the
Conferencing Traffic Mix table, which can
be further revised if desired. Default is
Predominantly from IP.
Total Number
Conference calls
Processed by Unified
CM
Displays the total number of users on

conference calls during the peak time.
Check the configuration of the call

processing agent that directs calls to the
conferencing system to determine if the
SIP or H.323 protocol is used.
Conference Calls Split

Conference Calls Split This field displays the current sum of the
(must total 100%)
percentages from the remaining fields in
this section. To size the solution properly,
the percentages must have a total of 100%.
Percentage of Calls
Incoming via H.323
Gateways (GK
controlled)
Enter the percentage of conference calls

coming into the conferencing system bridge
via H.323 trunks controlled by an H.323
gatekeeper. Default is 0%. Range is 0 100%. The total of this value plus all the
other fields in the Conference Calls Split
section must equal 100%.

obtained from call detail records for
conference calls but requires some effort.
Start by cross-referencing the calling
number and called number against a
particular device name/type. Then count all
calls routed to this device over H.323
trunks, and divide that count by the total
9/15/2015
Page 94 of 118
number of calls handled by the

conferencing system to obtain the required
percentage.
Percentage of Calls
Incoming via H.323
gateways (Non GK
controlled)

via H.323 trunks that are not controlled by
an H.323 gatekeeper. Default is 20%.
Range is 0 - 100%. The total of this value
plus all the other fields in the Conference
Calls Split section must equal 100%.

trunks that are not under gatekeeper
control, and divide that count by the total
percentage.
Percentage of Calls
Incoming via MGCP
Gateways

via an MGCP gateway. Default is 0%.

calls routed to this device by MGCP
gateways, and divide that count by the total
percentage.
Percentage of Calls
Incoming via SIP
Gateways

via a SIP gateway (proxy). Default is 0%.

calls routed to this device by SIP gateways
and divide that count by the total number of
calls handled by the conferencing system
to obtain the required percentage.
Percentage of Calls
Incoming via H.225
Interlcluster Trunks
(GK controlled)

over H.225 trunks controlled by an H.323
gatekeeper. Default is 0%. Range is 0 100%. The total of this value plus all the

trunks, and divide that count by the total
percentage.
Percentage of Calls
Incoming via
Intercluster Trunks
(GK controlled)

over intercluster trunks controlled by an
H.323 gatekeeper. Default is 0%. Range is
0 - 100%. The total of this value plus all the

gatekeeper controlled intercluster trunks,
9/15/2015
Page 95 of 118
Percentage of Calls
Incoming via
Intercluster Trunks
(non GK controlled)

over intercluster trunks that are not
controlled by an H.323 gatekeeper. Default
is 0%. Range is 0 - 100%. The total of this
value plus all the other fields in the
Conference Calls Split section must equal
100%.

calls routed to this device over intercluster
trunks not controlled by a H.323
gatekeeper, and divide that count by the
total number of calls handled by the
percentage.
Percentage of Calls
Incoming via SIP
Intercluster Trunks

over SIP trunks. Default is 0%. Range is 0 100%. The total of this value plus all the

calls routed to this device over SIP trunks,
Percentage of Calls
Incoming via IP
Phones

via IP phones. Default is 80%. Range is 0 100%. The total of this value plus all the

calls routed to this device using IP phones
Percentage of Calls
Incoming via InterEnterprise Trunks

over inter-enterprise trunks. Default is 0%.

calls routed to this device over interenterprise trunks and divide that count by
the total number of calls handled by the
percentage.
Minimal MeetingPlace Equipment Requirement

The following table describes the function of the fields on the Minimal MeetingPlace Equipment Requirement section of the
Conferencing and Collaboration page. The specific fields that appear depend on the version of Unified MeetingPlace selected
and the overall solution needs.
Conferencing and Collaboration - Minimal MeetingPlace Equipment Requirement
Field
Description
9/15/2015
Page 96 of 118
Application Servers Needed (Meeting Director Co-Resides with One of the Application Servers)
Servers Needed
Displays the recommended quantity of application/audio server platforms

for the conferencing solution.
Maximum Number of Servers for

Resiliency
Displays the maximum recommended number of servers for high

availability.
Please Enter the Desired Number of

Servers for Resiliency
Enter the number of servers you desire for resiliency.
Enter the Desired Number of Servers

for Resiliency
Enter the number of servers you desire for high availability.
Meeting Director Servers Needed
Enter the number of Meeting Director servers required.
Platform
Displays the recommended platform type. To override the

recommendations, select another server from the pull-down selection list
(if available).
Server Type
Displays the suggested Cisco Unified Computing System server

hardware. To override this setting select another server from the pulldown selection list (if available).
Audio Blades
Displays the type and quantity of audio blades ( for example MP3545MS-A) recommended for the conferencing solution. These blades
are installed in the chassis unit(s) shown in the Chassis field.
Video Blades
Displays the type and quantity of video blades recommended for the
conferencing solution. These blades are installed in the chassis unit(s)
shown in the Chassis field.
Chassis
Displays the type and quantity of Unified MeetingPlace chassis (for

example MP-3545-CHASS) recommended for the conferencing solution.
WebEx Nodes (optional)

Servers Needed
Displays the recommended quantity of WebEx collaboration or Unified

MeetingPlace Web Conferencing server platforms recommended for the
solution.
Platform
Displays the type of WebEx collaboration or Unified MeetingPlace Web

Conferencing server platform recommended for the conferencing
solution. To override the recommendation, select another server from the
pull-down selection list (if available).
Server Type
Displays the suggested Cisco Unified Computing System server

hardware. To override this setting select another server from the pulldown selection list (if available).
MeetingPlace Web Servers

Servers Needed
Displays the recommended quantity of Unified MeetingPlace Web

conferencing server platforms for the conferencing solution.
Platform
Displays the type of Unified MeetingPlace Web Conferencing server

platform recommended for the conferencing solution. To override the
recommendation, select another server from the pull-down selection list
(if available).
Server Type
Displays the recommended Cisco Unified Computing System server

hardware type. To override this setting select another option from the
pull-down selection list (if available).
9/15/2015
Page 97 of 118
WebEx Server Sizing

The following table describes the function of the fields for the WebEx Server Sizing section on the Conferencing and
Collaboration page.
Conferencing and Collaboration - WebEx Server Sizing
Field
Description
Input Source
Conference System
The conferencing system to be sized. In

this release, WebEx is the only value.
This is a read-only field.
Software Release
The software release for Cisco WebEx

Meetings Server. As this is the first
release, there is only one value.
This is a read-only field.
Number of Knowledge The number of employees and external

Users
users who will host or attend Cisco
WebEx Meetings Server meetings.
Enter the number of Cisco WebEx Meetings

Server users. This number indicates
employees who host or attend meetings and
external users who attend meetings. This
number is equal to the number of user
licenses required.
For more information on resource requirements for WebEx Server sizing, see Cisco WebEx Meetings Server Planning Guide.
System Usage
The following table describes the function of the fields for the System Usage section on the Conferencing and Collaboration
page.
Conferencing and Collaboration - System Usage
Field
Description
Input Source
Optional Input:
Average number of minutes of active
User Minutes per conferences for the month, across all
Month
ports. This value is expressed in
thousands of minutes.
Enter the anticipated system usage in thousands

of minutes.
Knowledge Users The expected Cisco WebEx Meeting

Conference
Server usage level. The sizing tool
Usage
defines light usage (3.3 percent of users
active at any one time), average usage (5
percent active), and heavy usage (10
percent active).
Select Light, Average or Heavy. This input

influences the size of the Cisco WebEx Meeting
Server system required to support the specified
number of users. For example, a system set for
heavy usage requires twice as many ports as a
system set for average usage.
Optional Input:
Actual Peak
Usage
(concurrent
users)
This is an optional input. It is only required if you
This is an optional input. It is only required if you

expect system usage to be much higher than
average.
The maximum number of concurrent

Enter the maximum number of concurrent users
users of the system that occurs when the that the system must support. This number is
system is at peak usage.
significant in determining the required number of
conferencing ports.
9/15/2015
Page 98 of 118
expect the peak usage of the system to be much

higher than average.
Video Usage
The following table describes the functions of the fields for the Video Usage section on the Conferencing and Collaboration
page.
Conferencing and Collaboration - Video Usage
Field
Description
Input Source
Percentage of
Conferences with
HQ Video
The percentage of conferences that use High Quality (HQ) video, which
is 360p resolution. The maximum number of video users supported by a
given system is 50 percent of the maximum system capacity. For
example, the 250-user system supports 250 simultaneous users, of
which up to 125 of the users can be using video.
Enter the
percentage of
meetings that will
use HQ video.
Teleconferencing Traffic Description

The following table describes the function of the fields for the Teleconferencing Traffic Description section on the Conference
and Collaboration page.
Conferencing and Collaboration - Teleconferencing Traffic Description
Field
Description
Input Source
Required Top of the Hour Dial- The system may require this time to add all
Enter the number of minutes
in
participants to the meetings that usually start at that the system may use to
the beginning of the hour.
process a large number of
participants. The range is 1.5
to 7.0.
Percentage of Users that Join
Conferences from within the
Enterprise
The percentage of users that usually use their

desktop phone for the audio portion of
meetings. The remaining percentage are
assumed to be external users who will access
the audio from the PSTN. A very small
percentage of users may access the audio
using a VoIP client on their computer.
Enter the percentage of users

who will usually access
meeting audio from their
desktop phones.
Gateway/Intercluster/InterEnterprise Trunks
The call processing protocol used on IP trunks

between the Cisco Unified Communications
Manager (CUCM) and other components, such
as PSTN gateways and peer CUCMs.
Enter the protocol used by

CUCM trunks. This input
influences the conferencing
impact on CUCM, as each of
the protocols imposes a
different processing overhead
on the CUCM.
9/15/2015
Page 99 of 118
Deployment Requirements
The following table describes the function of the fields for Deployment Requirements of the WebEx Server Sizing section of the
Conferencing and Collaboration page.
Conferencing and Collaboration - Deployment Requirements
Field
Description
Input Source
Allow Users to Join If external users can participate in conferences, the

Conferences from system will add one or more Internet Reverse Proxy
the Internet
server in the DMZ of the enterprise.
Select Yes or No.
High Availability
The system can be configured in non-redundant mode

or in high-availability mode. In high-availability mode,
each of the servers in the cluster is paired.
For WebEx Meetings Server

Release 2.0(1) and prior, select
Yes or No.
For WebEx Meetings Server Release 2.5(1), for a 50user system, you can choose a Single Data Center
option. For all other system sizes, a Dual Data Center
option is also available. If you choose this option, the
Disaster Recovery option is not available.
For WebEx Meetings Server

Release 2.5(1), select None,
Single Data Center, or Dual Data
Center.
Disaster Recovery
Note
If you select Dual Data

Center, the Disaster
Recovery option is not
available.
For disaster recovery, you can configure a cold-standy

system in a second data center.
Select Yes or No.
High Availability for If the primary system is configured for high availability,
Disaster Recovery you can optionally choose to configure high availability
Site
for the disaster recovery system.
Select Yes or No.
Server Type for

800-User or 2000User Systems
Drop-down list of the Cisco Unified Computing System

servers that are applicable for these product sizes.

hardware.
Server Type for

50-User or 250User Systems
Drop-down list of the Cisco Unified Computing System

servers that are applicable for these product sizes.

hardware.
Cisco Unified Presence (Unified Communications Manager IM and

Presence Service)
Cisco Unified Presence (now known as Cisco Unified Communications Manager IM and Presence Service) is integrated into
Cisco Unified Communications Manager as a service starting with release 9.0(1). As a result, if you specify Unified CM as a
component when you first define the solution, the IM and Presence Service option automatically appears in the sizing tool
navigation list, grouped with the other Unified CM component options.
If you specify another (earlier) release of Unified CM, you have the option to specify Cisco Unified Presence (now known as as
Cisco Unified Communications Manager IM and Presence Service) as a separate optional component of the solution. In this
9/15/2015
Page 100 of 118
case, a Cisco Unified Presence option will appear in the navigation list on the right side of the sizing tool page.
Note
For deployments where Microsoft Office Communicator is integrated with Cisco Unified Presence, note that Microsoft
Office Communicator Remote Call Control (RCC) sizing is not impacted by Unified Presence server limits. Instead, RCC
sizing is determined by CTI on Unified CM by mapping Microsoft Office Communicator clients to CTI connections on a
one-to-one basis. See Computer Telephony Integration Input for more information on CTI connections.
The Cisco Unified Presence page lets you describe the characteristics of Cisco Unified Presence (now known as Cisco Unified
Communications Manager IM and Presence Service) as implemented in the proposed solution to be sized. This page includes
the following sections:
Note
For deployments where Microsoft Office Communicator is integrated with Cisco Unified Presence, note that Microsoft
Office Communicator Remote Call Control (RCC) sizing is not impacted by Unified Presence server limits. Instead, RCC
sizing is determined by CTI on Unified CM by mapping Microsoft Office Communicator clients to CTI connections on a
one-to-one basis. See Computer Telephony Integration Input for more information on CTI connections.
Input Fields
Output
Input Fields
This section lets you describe the input associated with Cisco Unified Presence (or Unified Communications Manager IM and
Presence Service) in the proposed solution. The following table describes the function of each field in the Input section of the
Cisco Unified Presence (or IM and Presence Service) page.
Cisco Unified Presence (or IM and Presence Service) Input Fields
Field
Description
Input Source
Software
Release
Displays the Cisco Unified Presence (or IM and

Presence Service) release number.
Platform
Select the platform that will be used for Cisco

Unified Presence. Identify the Cisco Unified
Presence release to be deployed, based on
Release Notes, data sheets, and features. For
virtual machines (VMs), Open Virtualization
Archive (OVA) templates are shown for various
numbers of endpoints. If a VM value is selected,
an additional Server Type field appears allowing
you to specify the B-series or C-series Cisco
Unified Computing System hardware.
For existing deployments, in Cisco Unified

Operating System Administration for Cisco
Unified Presence, go to Show > System to
determine the platform type.
High Availability Indicate if the Unified Presence deployment is

Deployment
designed for High Availability (Yes) or not (No).
Determine the high availability deployment
strategy of the Cisco Unified Presence cluster
from the Cisco Unified Presence administration
and deployment guides.
Navigate to the System Topology page and

extract the data. If there are two nodes in a
cluster, it is HA; otherwise, it is not. From
the Cisco Unified Presence administration
page, navigate to System > Topology and
extract the data. If there are two servers
9/15/2015
Page 101 of 118
(instead of one) in a subcluster, then the

subcluster deployed is Highly Available.
Note that there is no High Availability (HA)
option for Cisco Unified Presence 8.0(1).
Number of
Enter the total number of Unified Presence users
Unified
supported by the deployment. Default is equal to
Presence Users the value in the Total Number of System Users
field on the Endpoint page of the Unified
Communications Manager. Range is 0 - 15,000
users.

Presence Administration go to User
Management > Application Users to
determine this value.
Percentage of
Enter the percentage of users employing a SIPUsers in IM
based instant messaging (IM) client application.
Default is 0. Range is 0 - 100%.
Only Mode
(Remaining
Users in Full UC
Mode)
For existing deployments, analyze the

clients in use. Note that Cisco Unified
Personal Communicator Release 7.x
clients are SIP-based and Unified Personal
Communicator Release 8.x clients use
XMPP.
Percentage of
Users using
XMPP Client
(Remaining
Users Using SIP
Client)
Enter the percentage of users employing an

XMPP-based instant messaging (IM) client
application.Default is based on the value of the
previous field. Range is 0 - 100%.

XMPP.
Percentage of
XMPP Clients
over BOSH
(CAXL)
Enter the percentage of users employing thirdparty XMPP instant messaging client applications
over a Bidirectional-streams Over Synchronous
HTTP (BOSH) connection. Range is 0 - 100%.

XMPP.
Average Active
Contact List
Size per User
Enter the average contact list size maintained by

each user. For Cisco Unified Presence 6.0:
Default is 30. Range is 0 - 100. For Cisco Unified
Presence 7.x and later: Default is 100. Range is
0 - 200. Determine the target Presence User
Profile for users of the system and specify the
average contact list size.

Presence Administration go to User
Management > Application Users and
view all users. Each user's contact size list
is displayed next to their user name.
Inter-cluster
Deployment
Select whether the deployment requires

intercluster interaction between Unified Presence
servers running the same release (Unified
Presence 8.0 - Unified Presence 8.0), running
different releases (Unified Presence 8.0 - Unified
Presence 7.x), or no intercluster interaction (No).
Default is No.

Presence Administration go to Presence >
Inter-Clustering. A list of peers is
displayed (if any).
Average
Percentage of
Intercluster
Buddies per
User
Enter an average percentage of how many

members in a typical Unified Presence user's
buddy (contact) list reside in a different cluster.
Default is 25%. Range is 0 - 100%. This field is
only available if you choose a value other than
No in the Intercluster Deployment field.

obtained by analyzing each user and
examining the make-up of their contact
lists.
Federation
Deployment
Select whether the deployment includes a

federated network between the Cisco Unified
Presence server and a foreign domain with SIP
clients (SIP Based), XMPP clients (XMPP
Based), or no interdomain federation (No).
Default is No.

Presence Administration go to Presence >
Inter-Domain Federation. Determine if
any SIP or XMPP federations have been
defined.
9/15/2015
Page 102 of 118
Percentage of
Federated
Buddies
Enter an estimated percentage, for a typical

Unified Presence user, of how many members of
their buddy (contact) list reside in a foreign
network domain. Default is 10%. Range is 0 100%. This field is only available if you choose
Yes in the Federation Deployment field.

obtained by analyzing each user and
examining the make-up of their contact
lists.
Percentage of
Users with
Exchange
Connection
Enter the percentage of users with active contact

lists that will use Microsoft Exchange during a
meeting. Default is 50%. Range is 0 - 100%.
Determine the number of users likely to enable
the Microsoft Exchange integration for real-time
calendaring state.
For existing deployments, this value is not

directly available. Users are responsible for
initiating a connection with Exchange once
it has been enabled. To determine this
value, poll each user manually during the
busy hour to determine how many are
using the connection.
Exchange
Connection
Version
Select whether presence client applications

access the Microsoft Exchange servers using a
Web-based Distributed Authoring and Versioning
(WEBDAV) or Microsoft Exchange Web Services
(EWS) interface. Default is WEBDAV.
Percentage of
Above Users
with Exchange
Connection in a
Meeting
Enter the percentage of users with Microsoft

Exchange connections that participate in
meetings during the busy hour. Default is 5%.
Range is 0 - 100%.
For existing deployments, this value is not

directly available. Users are responsible for
initiating a connection with Exchange once
it has been enabled. To determine this
value, poll each user manually during the
busy hour to determine how many are
using the connection and are in a meeting.
Number of IMs
per User during
Busy Hour
Enter the number of instant messages (IM) likely

to be sent per user during the busiest hour of the
day. Default is 25. Range is 0 - 100.
For existing deployments, connect to the

Unified Presence server using RTMT and
monitor the Proxy Server for IMs received.
Divide this by the number of users in
System > Status. If not all users are
enabled for Cisco Unified Presence,
identify the users that are enabled using
Licensing > Capabilities Assignment.
Type of Chat
Enabled
Select the type of chat rooms that will be

supported: None, Adhoc Group (created on
demand), or Persistent (always there even if no
one is online chatting in them). Default is None.

Presence Administration go to Messaging
> Conferencing and view Persistent Chat
to determine whether Enable Persistent
Chat has been configured.
Number of
Group Chats
Enter the number of simultaneous chat groups.

Default is 1. Range is 0 - 3. This field is only
available if you selected Adhoc Group or
Persistent in the Type of Chat Enabled field.

determined by analyzing users and their
usage of the system.
Number of
Users per
Chatroom
Enter the average number of users per chat

room. Default is 4. Range is 2 - 100. This field is
only available if you selected Adhoc Group or
Persistent in the Type of Chat Enabled field.

usage of the system.
Average
Number of IMs
per User per
Chatroom
Enter the instant messages (IM) likely to be sent For existing deployments, this value can be
between users during a chat session. Default is
10. Range is 0 - 100. This field is only available if usage of the system.
you selected Adhoc Group or Persistent in the
Type of Chat Enabled field.
Average
Number of Call-
Enter the average number of call-related state

changes per user that occur during the busy
For existing deployments, log into the SIP

proxy server and gather PUBLISH data,
9/15/2015
Page 103 of 118
Related State
Changes per
User during
Busy Hour
hour. Default is 8. Range is 2 - 20.
number of PUBLISHs per user on voice or

video connections (IMs excluded), and
divide by the number of users.
Average
Number of
User-Initiated
State Changes
per User during
Busy Hour
Enter the average number of user-initiated state

changes per user that occur during the busy
hour. Default is 0.50. Range is 0.00 - 10.00.
Determine the activity per user related to voice
and video state changes that can occur during a
busy hour.
For existing deployments, log into the SIP

proxy server and gather PUBLISH and
MESSAGE data, number of PUBLISHs and
MESSAGEs per user on voice, video, or
instant message connections, and divide by
the number of users.
Presence Web
Service
Indicate whether 3rd party application

programming interfaces (APIs) are required for
the deployment for web services application
clients (Yes) or not (No). Default is no 3rd party
interfaces for web services (No).

Presence Administration go to System >
Security > Settings. The configuration
Enable XMPP Client to CUP Secure Mode
refers to 3rd party API usage.
Percentage of
Users on
Presence Web
Service
Enter the percentage of presence users

employing a 3rd party API for web services. This
field is only available if the Presence Web
Services field is set to Yes. Default is 5%. Range
is 0 - 100%.

only be determined by analyzing users and
their usage of the system.
Average
Number of
Presence
Entities per
User
Enter the number of entities that may request

presence information about each user from
only be determined by analyzing users and
Unified Presence servers via a 3rd party API.
their usage of the system.
This field is only available if the Presence Web
Services field is set to Yes. Default is 5. Range is
0 - 250.
Compliancy
Enabled
Indicate whether compliance logging for all

instant messaging associated with Cisco Unified
Presence is enabled (Yes) or not (No). Default is
No.

Presence Administration go to Messages >
Compliance to determine the setting.
Output
This section describes output fields associated with Cisco Unified Presence (now known as IM and Presence Service) in the
proposed solution.
Cisco Unified Presence - Output Section
Field
Description
Max Number of Users per VM
Displays the maximum number of users per Cisco Unified Presence

( now known as IM and Presence Service) server.
Max Total Number of Users Supported

per Unified Presence Server cluster1
Displays the total number of users supported per Cisco Unified

Presence (now known as IM and Presence Service) server cluster.
Number of VMs Needed
Displays the suggested number of VMs for the IM and Presence

service deployment.
Number of Clusters Needed
Displays the suggested number of clusters.
9/15/2015
Page 104 of 118
The total number of users in a Cisco Unified Presence cluster may depend on the number of users in the Unified CM cluster.
Cisco MediaSense
Cisco MediaSense can be sized as part of a System Release Sizing or Compatible Components Sizing scenario as discussed
in Describe Cisco MediaSense Options.
The following table describes the function of each field in the Cisco MediaSense page.
Cisco MediaSense
Field
Description
Input Source
MediaSense
Release
Displays the software release

of MediaSense being used.
This is set by user when identifying components for the

solution.
Percentage of
IPT Calls being
Recorded (%)
Enter the percentage of IPT

The IPT calls are handled by UCM only without UCC, and
calls being recorded. Range is are derived from number of phones, number of busy hour
0% to 100%.
users in Endpoints page, and ACHT per User in Traffic Mix
page, in the Communications Manager component.
MediaSense
Audio Call Recordings

Displays the number of
Number of
Concurrent Audio concurrent audio calls being
Calls Being
recorded.
Recorded
If UCC is not included, this field will show the calls from UCM
only. If UCC is included and UCCE is selected, this value will
add the inbound and outbound calls being recorded by UCM
(set in each workflow in inbound page) from UCCE
component. If UCC is included and UCCX is selected, this
value will add the inbound and outbound calls from UCCX
component.
Number of Audio Displays the number of audio

Calls Per Second calls per second being
handled by MediaSense.
Number of
Enter the number of audio
Concurrent Audio calls you want to play back.
Calls Being
Default is 0.
Played Back
This number is based on your requirements.
Number of
Concurrent Audio
Calls Being
Monitored
Enter the number of calls you

want to monitor. Default is 0.
Maximum is smaller than or
equal to Number of
Concurrent Audio Calls being
Recorded.
Number of
Enter the number of
Concurrent Video concurrent video playback
Played Back
sessions.
Sessions
Number of
Enter the number of HTTP
Concurrent HTTP download sessions. Default is
Download
0.
Sessions
9/15/2015
Number of
Concurrent API
Requests
Page 105 of 118
Enter the number of calls you This number is based on your requirements.
want to convert to MP4 format
file. Default is 0.
Recording duration and Retention

Number of Days
for Retaining
Recorded Calls
Enter the number of days you

want the recorded calls to be
retained before purging them
from MediaSense records .
Default is 30. Range is 1 to
120.
Number of Hours Enter the number of hours per This number is based on your requirements.
for Recording Per day during which calls will be
Day
recorded. Default is 8. Range
is 0 to 24.
Audio Recording/Playback Codec Mix
Percentage of
Total Recordings
in G.711 or G.722
(%)
Enter the percentage of

recordings that use G.711 or
G.722 codec. Default is 50%.
Range is 0 to 100%.
Percentage of
Total Recordings
in G.729 (%)
Displays the percentage of

recordings that use G.729
codec.
Percentage of
Total Recordings
Converted to
MP4 (%)

recordings being converted to
MP4 format. Default is 0%.
Range is 0 to 100%.
Size Reserved
For Uploading
Media Per Node
Enter the size reserved for

uploading Media (Video,
audio) per node.
This will affect the storage usage.
This will affect the storage usage.

This is only applicable for older clients which call the
convertSession API.
Output
Number of
Clusters
Required
Displays the number of

clusters required for the
solution.
OVA Template
Displays the available OVA

template.
Additional
Displays additional storage
Storage Required required (GB).
(GB)

Cisco Intercompany Media Engine (IME) servers can be sized as part of a System Release Sizing or Compatible Components
Sizing scenario as discussed in Describe Cisco Intercompany Media Engine Options.
The following table describes the function of each field in the Cisco Intercompany Media Engine page.
9/15/2015
Page 106 of 118

Field
Description
Input Source
Software
Release
Displays the software version of the Intercompany

Media Engine selected, based on the version chosen
when the sizing scenario was defined.
Number of
DNs Enrolled
into IME
Services
Enter the total number of directory numbers (DNs)

that will be shared/published between IME servers in
the IME distributed cache ring. Default is the same
value entered in the Total Number of DNs field on the
Unified Communications Manager Dial Plan page.
Range is 0 to the value entered in the Total Number
of DNs field on the Unified Communications Manager
Dial Plan page.

Directory Numberand click Find without
applying any filters. The system displays
a list of directory numbers with the total
that could be enrolled into IME service
shown at the top. For a new system, the
total amount of directory numbers can be
estimated by multiplying the number of
expected users by the average number of
DNs each user will be assigned.
Percentage
of Enrolled
DNs per
Server
Enter the percentage of enrolled directory numbers

allocated to each IME server. Default is 100% for the
first IME server. Range is 0100%. To add additional
IME servers and distribute the directory numbers
across multiple servers, enter a value less than 100%
in this field and then click Add. Note that the total of
the percentages assigned to all IME servers must
equal 100%. To remove a server, enter 0 in this field
and redistribute the percentages amongst the other
server(s); after you leave and then return to the Cisco
Intercompany Media Engine page, that server will no
longer appear.
Based on network design specification,

determine if load-balancing is required
and if so, have the load should be
distributed across multiple servers.
Platform
Select the Cisco Intercompany Media Engine server

type from the pull-down selection list. Default is MCS7845-I3.
Choose the server type based on the

required capacity of the IME service.
Cisco MCS-7825 servers can host up to
10,000 users, while Cisco MCS-7845
servers can host up to 40,000 users.
High
Availability
Deployment
Indicate whether the IME server deployment is

designed for High Availability (Yes) or not (No).
Default is Yes.
This field modifies the behavior of the

sizing tool and specifies the desired type
of sizing for the system. When this option
is selected, the sizing tool adds additional
servers to allow for high availability.
DNs
Displays the number of actual directory numbers

(DNs) allocated to each IME server based on previous
entries. This value is calculated by applying the value
in the Percentage of IME Enrolled DNs field to the
total number of DNs entered in the Number of DNs
Enrolled into IME Server.
Management
The following Management servers can be sized as part of a System Release Sizing or Compatible Components Sizing
scenario as described in Describe Management Options:
9/15/2015
Prime Collaboration Standard or Advanced
Prime Collaboration Assurance
Prime Collaboration Provisioning
Prime Collaboration Analytics
Page 107 of 118
Each type of service can be sized separately. The following table describes the function of each field in the Management page.
Management Applications
Field
Description
Input Source
Cisco Prime CollaborationComponents

Prime
Collaboration
Standard or
Advanced
Select Prime Collaboration Standard or Prime

Collaboration Advanced to specify if you want to
include this service in the solution. Default is
Standard.
This setting depends on user

preferences, based on the needs of a
particular solution.
Prime
Collaboration
Assurance
Select Yes or No to specify if you want to include this

service in the solution. Default is No

Prime
Collaboration
Provisioning

service in the solution. Default is No

Prime
Collaboration
Analytics

service in the solution. This field only appears if the
Assurance field is set to Yes. Default is No

Enter the total number of standard assurance

endpoints (Unified IP Phones and Unified Personal
Communicator) that may be administered using
Prime Collaboration Standard. Default is 0.
Use the total number of devices that

are associated with this cluster (up to a
maximum of 40,000). Refer to the field,
"Total Number of Devices" in Users.
Standard
Standard
Assurance
Endpoints

number of phones
Standard
Provisioning
Endpoints
Enter the total number of standard provisioning

Prime Collaboration Standard. Default is 0.
Use the total number of devices that

are associated with this cluster (up to a
maximum of 40,000). Refer to the field,
"Total Number of Devices" in Users.
number of phones
Assurance
Number of
Enter the total number of mass endpoints (Cisco IP
Mass Endpoints Phones, Cisco Cius, Cisco Jabber for Video for
TelePresence [Movi], Cisco IP Video Phone E20) that
may be administered using Prime Collaboration
Advanced. Default is 0. Range is 0 to 10,000.

Cisco Prime Collaboration user
interface. From the Home screen,
select Administration > License
Management. The Assurance License
Status displays the number of mass
endpoint assurance licenses and the
number that are currently in use.
9/15/2015
Page 108 of 118
Number of
Midrange
Endpoints
Enter the total number of midrange endpoints (Cisco

Codec, Cisco TelePresence System, Cisco
Tandberg, Cisco TelePresence SX20 Quick Set,
Polycom) that may be administered using Prime
Collaboration Advanced. Default is 0.

Status displays the number of
midrange endpoint assurance licenses
and the number that are currently in
use.
Number of
High-End
Single-Codec
Endpoints
Enter the total number of high-end single-codec

endpoints (Cisco TelePresence System, Cisco
Profile) that may be administered using Prime
Collaboration Advanced. Default is 0.

Status displays the number of high-end
single-codec endpoint assurance
licenses and the number that are
currently in use.
Number of
Multicodec
Endpoints
Enter the total number of multicodec endpoints (Cisco For existing deployments, log into the
TelePresence System) that may be administered
using Prime Collaboration Advanced. Default is 0.
Status displays the number of
multicodec endpoint assurance
licenses and the number that are
currently in use.
Total Number of
Advanced
Assurance
Endpoints
Enter the total number of advanced assurance

Prime Collaboration Advanced. Default is 0.

Status displays the total number of
endpoint assurance licenses and the
Provisioning
Total Number of Enter the total number of endpoints that will be
Advanced
provisioned using Advanced Prime Collaboration
Provisioning
Provisioning.
Endpoints

Management. The Provisioning
License Status displays the number of
endpoint provisioning licenses and the
Analytics
Total Number of Enter the total number of analytics endpoints that
Analytics
may be administered using Prime Collaboration
Endpoints
Advanced. The total number of Prime Collaboration
Analytics scale licenses obtained must be greater
than or equal to the total number of scale licenses
you have for Prime Collaboration Assurance. For
example, if you are managing 1000 endpoints in
Prime Collaboration Assurance, you must have Prime
Collaboration Analytics license for 1000 or more
endpoints. Default is 0.
9/15/2015
Page 109 of 118
Prime CollaborationOutput
The following table describes the function of each field on the Prime Collaboration - Output section of the Management page.
Field
Description
Prime Collaboration Assurance and Analytics Server

Assurance with Analytics: 10K phones
Prime Collaboration Provisioning Application Server
Provisioning: 80K phones (Application)
Prime Collaboration Provisioning Database Server
Provisioning: 80K phones (Database)
Total VM Resources
Gateways Page
Cisco IOS gateways can be sized as part of a System Release Sizing or Compatible Components Sizing scenario as discussed
in Describe Gateways Implemented in Sizing Solution. For these scenarios, using the tables provided in Gateways.
z
Gateways
Gateways
This page lets you identify the gateways to be included in the solution. Gateways are identified in one or more groups and this
page provides options that allow you to define multiple gateway groups.
Enter the characteristics of the gateways for all the groups that you define. This section displays the total load that needs to be
allocated to gateway groups.
This page includes the following sections:
z
Load Allocated to All Gateway Groups
Load Allocated to Remaining Gateway Groups
Gateway Groups Defined
Gateways Group
9/15/2015
Page 110 of 118
Gateway Output
Load Allocated to All Gateway Groups

Field
Description
Total PSTN TDM-IP IPT Load to All

Gateway Groups
Displays the Erlangs of IPT load and the number of phones (agents)
that need to be allocated to all gateway groups.
Total PSTN TDM-IP Unified CC Inbound

Load to All Gateway Groups
Displays the Erlangs of inbound Unified CC load that need to be

allocated to all gateway groups.
Total PSTN TDM-IP Unified CC Outbound

Load to All Gateway Groups
Displays the Erlangs of outbound Unified CC load that need to be

allocated to all gateway groups.
Total VoiceXML Load to All Gateway

Groups
Displays the Erlangs of VoiceXML load that need to be allocated to

all gateway groups.
Total Unified Border Element IP-IP Load to Displays the Erlangs of Cisco Unified Border Element IP-IP load that
All Gateway Groups
need to be allocated to all gateway groups.
Load Allocated to Remaining Gateway Groups

Field
Description
Total PSTN TDM-IP IPT Load to

Remaining Gateway Groups
Displays the Erlangs of PSTN TDM-IPT load and the number of

phones (agents) that need to be allocated to remaining gateway
groups.
Total PSTN TDM-IP Unified CCE Inbound

Load to Remaining Gateway Groups
Displays the Erlangs of inbound Unified CC load that need to be

allocated to remaining gateway groups.
Total PSTN TDM-IP Unified CCE

Outbound Load to Remaining Gateway
Groups
Displays the Erlangs of outbound Unified CC load that need to be

allocated to remaining gateway groups.
Total VoiceXML Load to Remaining

Gateway Groups
Displays the Erlangs of VoiceXML load that need to be allocated to

remaining gateway groups.
Total Unified Border Element IP-IP Load

to Remaining Gateway Groups
Displays the Erlangs of Cisco Unified Border Element IP-IP load that
need to be allocated to remaining gateway groups.
Gateway Groups Defined
9/15/2015
Page 111 of 118
The following table shows the function of each option in the Gateways Groups Defined section of the Gateways page. These
options allow you to describe, edit, and delete gateway groups.
Field
Description
Add GW Group
Click this option to define a new gateway group.
Edit an Existing
GW Group
Use this option to specify values for an existing gateway group. Select the gateway group
you wish to edit from among those listed in the drop-down list.
Delete an Existing
GW Group
Use this option to remove a gateway group and its associated information. Select the
gateway group you wish to delete from among those listed in the drop-down list.
Gateways Group
The Gateway group sections let you define the characteristics of the gateway group or groups that you have identified. To
define a new group, click Add GW group. To edit an existing group, specify one from among those available in the Edit an
Existing GW Group drop-down list, and enter values in the input fields as required.
The following tables describes the function of the fields available for the defined gateway groups. The availability of fields in the
gateway sections may depend on the particular configuration of the other solution components.
Gateway Group
Field
Description
Input Source
Percentage of PSTN TDMIP IPT Load to Gateway

Group
Enter the percentage of IPT load that should

be assigned to this gateway group. Default is
50%. Range is 0 - 100%.
Track through RTMT and thirdparty gateway tools. This is

gateway-specific, refer to the
operating manual.
Percentage of PSTN TDMIP Unified CCE Inbound

Load to Gateway Group
Enter the percentage of inbound Unified CCE

load that should be assigned to this gateway
group. Default is 0%. Range is 0 - 100%.

operating manual.
Percentage of PSTN TDMIP Unified CCX Inbound

Enter the percentage of inbound Unified CCX

load that should be assigned to this gateway

operating manual.
Percentage of PSTN TDMIP Unified CCE Outbound

Enter the percentage of outbound Unified CCE Track through RTMT and thirdload that should be assigned to this gateway
party gateway tools. This is
operating manual.
Percentage of VoiceXML
Enter the percentage of VoiceXML load that

should be assigned to this gateway group.

operating manual.
Border Element IP-IP Load
to Gateway Group
Enter the percentage of Cisco Unified Border

Element IP-IP load that should be assigned to
this gateway group. Default is 0%. Range is 0 100%.

operating manual.
Gateway Input
9/15/2015
Page 112 of 118
Field
Description
Input Source
Gateway
Platform
Select the voice gateway platform used by gateways

in this gateway group. Default is Cisco 4451-X.

Administration go to Device >
Gateway. The Voice Gateway Platform
is listed under the Device Type column.
IOS Release
Select the IOS software release used by gateways in

this gateway group.
For existing deployments, Telnet to a

gateway in the group and type show
version.
Gateway Type
Select whether the Gateways in this group are

Standalone, that is, they are dedicated for voice
functions or whether they are used for data as well as
voice. Default is Dedicated Voice Gateway.
Analyze the role of the gateway in the

network.
Blocking
Probability
Enter the highest acceptable probability as a

percentage that a call will be blocked. Default is 1%.
Range is 0.01 - 10%.
This is per user preference regarding

quality. A value of 1% is generally
accepted in the industry.
Physical
Locations
Enter the number of physical locations where

gateways of this gateway group will be located.
Default is 1. Range is 0 to the value entered in the
Locations/Branches field on the Deployment Model
page of the Unified Communications Manager
component.
For existing deployments, examine the

locations attribute of gateways; in
Unified CM Administration go to Device
> Gateway.
GW Used as
Select Yes if this gateway group is used for SRST or
Unified SRST CME. Default is No.
or Unified CME

information on the gateway; in Unified
Gateway and in Unified CM
Administration > System > SRST.
Gateways PSTN TDM-IP Options

Field
Description
Input Source
Gateway
Select the security option used by
Voice Security gateways in this gateway group.
Default is No encryption.
For existing deployments, check whether IPSec has been

enabled in the network infrastructure between the Unified
CM and gateways in this gateway group.
TDM-PSTN
Integration
For existing deployments, in Unified CM Administration go

to Device > Gateway. PSTN integration can be found in
the modules used in various slots in the gateways.
Select the link type used for

integration with the PSTN for this
gateway group. Default is T1.
Gateway VoiceXML Options

Field
Description
Input Source
Local Router
Input
Select the local router input as DTMF or

ASR/TTS. Default is DTMF.
This parameter applies to where caller input is

recognized: locally on the gateway itself (DTMF
only), or DTMF and speech input using an
ASR/TTS server.
VoiceXML
Control
Specify where the VoiceXML application This parameter allows specification of where the
is attached on the gateway by selecting
VoiceXML script is attached on the gateway, on
IP-Side or PSTN-Side. Default is IP-Side. the POTS or VoIP dial-peer. If the application is
attached in the POTS dial-peer then select PSTNSide. If the application is attached on the VOIP
dial-peer, then select IP-Side.
9/15/2015
Secure HTTP
&/or JavascriptIntensive
Applications
Page 113 of 118
Select the appropriate option based on

what the gateway is going to perform.
The available options are HTTP & CU
Call Studio, HTTPS & CU Call Studio,
and HTTP & Javascript. Default is HTTP
& CU Call Studio.
If you intend on deploying the VoiceXML gateway

using HTTP and executing non-Javascript
intensive VoiceXML scripts written in Cisco
Unified Call Studio, then select HTTP & CU Call
Studio.
If the VoiceXML gateway uses Secure HTTP
(HTTPS) and executes non-Javascript intensive
VoiceXML scripts written in Cisco Unified Call
Studio, then select HTTPS & CU Call Studio.
If the VoiceXML gateway uses HTTP and
executes VoiceXML scripts that are javascript
intensive, then select the third option, HTTP &
Javascript.
Gateway Unified Border Element IP-IP Options

Field
Description
Input Source
Signaling
Interworking
Select the incoming or outgoing trunk types (IP protocol on

Unified CM and non Unified CM side). The available options
are: H.323-H.323 and H.323- SIP in case there are no SIP
trunks on the Unified CM side; SIP- H.323 and SIP-SIP in case
there are no H.323 trunks on the Unified CM side; H.323/SIPH.323 and H.323/SIP- SIP in case there are both H.323 and
SIP trunks on the Unified CM side. Default is always the first
option.
Analyze the configuration on the

Unified CM and Cisco Unified
Border Element to determine the
types of IP signaling protocols
being used towards the Unified
CM and the remote side.
Gateway Output
The following table describes the function of each field on the Output section of the Gateways page.
GatewayOutput
Field
Description
Gateways Group [n] Needed
Displays the suggested total number of gateways required for

this group.
DS0s per Gateway Group [n] Needed
Displays the suggested number of DS0s per gateway required

for this group.
T1s/E1s per Gateway Group [n] Needed
Displays the suggested number of T1/E1s per gateway

required for this group.
Gateway Group [n] DS0 Utilization
Displays the expected DS0 utilization of each gateway for this

group.
Gateway Group [n] Resource Capacity

Utilization
Displays the expected resource capacity utilization of each

gateway for this group.
9/15/2015
Page 114 of 118
Solution Sizing Summary

The Solution Sizing Summary page displays the sizing recommendations for each component included in the solution. The
Sizing summary displays the suggested type and suggested quantity of each server that is required for each component. The
sizing recommendations are grouped in sections corresponding to the components that you chose for the solution. The
recommendations are displayed to the right of each component.
The following equipment groupings may be included in the sizing summary; the sections that do appear and are populated with
information in the summary depend on the components you that specify and size for the solution.
z
Unified Contact Center Enterprise Equipment
Unified Contact Center Enterprise Agent and Supervisor
CVP Equipment
IP-IVR Equipment
MediaSense Equipment
Unified CM Equipment
Capacity Utilization Call Processing Server
CER Equipment
Gateways
Unity Connection Equipment
Voice Messaging Equipment
Minimal Meeting Place Equipment Required
Conferencing Equipment
CUP Equipment
IME System Equipment
Unified CCX System Equipment
Unified Computing Resources
Network Management Suite Equipment
Note
You can download and save the solution sizing summary report as a PDF file. See Generate Solution Sizing Summary
Report for instructions.
Unified CCE Components
Generate Solution Sizing Summary Report
Unified CCE Components

This sizing summary displays the recommended number of servers for the Unified CCE components within the proposed
solution. The following terms may appear in the Unified CCE summary information:
z
Progger - A single server running the Peripheral Gateway, Router, and Logger modules
Logger - A database server that stores contact center configuration and reporting data
Router - Call router, which makes all routing decisions about how to route a call or customer contact
9/15/2015
Page 115 of 118
Rogger - A single server running the Router and Logger modules
HDS - Historical Data Server, which is the database used for longer-term data storage and reporting.
WebView - WebView Server, which provides browser-based reporting
HDS/WV - A single server running HDS and WebView
Agent PG - Agent Peripheral Gateway, a server that runs the Cisco Unified CM PIM, the CTI Server, the CTI OS, and
the Unified IP IVR PIMs
Generate Solution Sizing Summary Report

Solution Sizing Summary Report
Option
Description
Export to Click the Export to PDF option on the upper right of the Solution Sizing Summary page to generate a
PDF
PDF report of your solution summary information. The solution sizing summary report is automatically
saved as a PDF file to the MySavedSolutions folder in which the sizing tool application (.exe) file
resides (the default installation folder for the sizing tool is: C:\Program Files\Cisco Systems\Sizing
Tool\<toolname>).
Export to Click the Export to VMPT option on the upper right of the Solution Sizing Summary page to use the
VMPT
Virtual Machine Placement tool (VMPT) at tools.cisco.com/ucs. With VMPT, you can determine the
number of UCS servers needed by importing your VM requirements. Import the saved file into VMPT.
All recommended VMs will be listed on the CST tab.
Create Bill of Materials

The Create Bill of Materials page and Bill of Materials page will only be available for solutions based on Unified CM 10.0(1), with
Voice Messaging specified as either (None, Unity Connection 10.0(1), or 3rd Party). If your solution meets these requirements,
the Create Bill of Materials page will appear at the bottom of the navigation list (at the right side of the page) after you click the
Solution Sizing Summary option.
The Create Bill of Materials page provides fields in which you can specify information for the software licenses that are required
for the described solution. The user can enter license information in the following sections:
Unified Communications Manager: License Type In this section, enter the required quantities for the license types listed,
based on your solution requirements. The maximum values displayed in this section are determined by the user license
requirements specified for each product, and the product and bundle license types specified within this section.
UC Clients and Soft PhonesUse the fields in this section to describe the licensing requirements for mobile, clients and
softphones. You must first enter a quantity of Unified Workspace Licenses before you can add values in the UC Clients and
Softphones section.
When specifying license information, it is important to correctly describe the licence requirements for the system users (Unified
Communications Manager: License Requirements section). This information helps to determine the most appropriate set of
licenses for the solution. The license information that appears on the bill of materials (BOM) page is derived (in part) from the
information that you enter on the Create Bill of Materials page.
If you do not specify any information on the Create Bill of Materials page, the Bill of Materials page will describe only the
hardware requirements of the solution.
z
License Type
UC Clients and Softphones
9/15/2015
Page 116 of 118
UC on UCS Servers
License Type
The following table describes the function of each field on the License Type Inputs section of the Create Bill of Materials page.
License TypeInput
Field
Description
Unified Workspace License

Professional
The number of users who will use Cisco Unified Workspace Licensing Pro
licensing that includes Cisco Unified Communications Manager, Cisco
Unity Connection, Conferencing, Contact Center Express and Clients.
Unified Workspace License

Standard
The number of users who will use Cisco Unified Workspace Licensing
Standard licensing that includes Cisco Unified Communications Manager,
Cisco Unity Connection and Clients.
User Connect License Advanced
The number of Cisco Unified Communications Manager User Connect

licenses for users using two enhanced devices/clients.
User Connect License Enhanced

licenses for users using one enhanced device/client.
User Connect License Basic

licenses for users using one basic device/client.
User Connect License Essential

licenses for users using one essential device/client.
Unity Connection user licenses
Total quantity of Unity Connection user licenses, in addition to those

included with Cisco Unified Workspace licenses.
Contact Center Express Agent +

Supervisor licenses
Total quantity of Contact Center Express licenses, in addition to those

included with Cisco Unified Workspace licenses.
MeetingPlace Audio user licenses
Total quantity of conference user licenses, in addition to those included

with Cisco Unified Workspace licenses.
WebEx Meetings Center schedulers Total quantity of conference user licenses, in addition to those included
with Cisco Unified Workspace licenses.
WebEx Social Users
Total quantity of WebEx Social licenses, in addition to those included with

Cisco Unified Workspace licenses.
UC Clients and Softphones

The following table describes the function of each field on the UC Clients and Softphones Inputs section of the Create Bill of
Materials page:
UC Clients and SoftphonesInput
9/15/2015
Page 117 of 118
Field
Description
Input Source
Presence Option
Users get a choice of either Cisco

UnifiedPresence on Premise or Cloud IM. If
users entered any quantity of Unified
Personal Communicator on the
CUCM:Endpoints page, Cisco Unified
Presence on Premise is required and,
therefore, the only option available.
Enter the quantity of Cisco Unified

Workspace Licensing and Cisco Unity
Connection licenses you wish to order. This
information is used for generating your
custom Bill of Materials (BOM).
IP Communicator
The number of licenses for IP

Communicator.
Enter the quantity of IP Communicator

licenses you wish to order. This information
is used for generating your custom BOM.
Cisco Jabber for

Desktop
The number of licenses for Cisco Jabber for Enter the quantity of Cisco Jabber for
Desktop.
Desktop licenses you wish to order. This
custom BOM.
Cisco Jabber for Mac The number of licenses for Cisco Jabber for Enter the quantity of Cisco Jabber for Mac
Mac.
Cisco Jabber for
SDK
The number of licenses for Jabber for SDK.
Enter the quantity of Cisco Jabber for SDK

Unified Personal
Communicator
The number of licenses for Unified Personal Enter the quantity of Unified Personal
Communicator.
Communicator licenses you wish to order.
This information is used for generating your
custom BOM.
Cisco UC Integration The number of licenses for Cisco UC

for Microsoft Lync
Integration for Microsoft Lyc.
Enter the quantity of Cisco UC Integration

for Microsoft Lyc licenses you wish to order.
custom BOM.
Cisco UC Integration The number of licenses for Cisco UC

for WebEx Connect Integration for WebEx Connect.
Enter the quantity of Cisco UC Integration

for WebEx Connect licenses you wish to
order. This information is used for
generating your custom BOM.
Cisco Web
Communicator
The number of licenses for Cisco Web

Communicator.
Enter the quantity of Cisco Web

Communicator licenses you wish to order.
custom BOM.
Cisco Mobile for

iPhone Licenses
The number of licenses for Cisco Mobile for

iPhone Licenses. This field is displayed if
you have entered mobile users on the Cisco
Unified Communications Manager (CUCM)Endpoints page.
Enter the quantity of Cisco Mobile for

iPhone licenses you wish to order. This
custom BOM.
Cisco Jabber for

Android
The number of licenses for Cisco Jabber for

Android. This field is displayed if you have
entered mobile users on the CUCMEndpoints page.
Enter the quantity of Cisco Jabber for

Android licenses you wish to order. This
custom BOM.
Cisco Jabber for

iPad
The number of licenses for Cisco Jabber for Enter the quantity of Cisco Jabber for iPad
iPad.
9/15/2015
Page 118 of 118
UC on UCS Servers
Click the Export to VMPT option on the upper right of the Solution Sizing Summary page to use the Virtual Machine Placement
tool (VMPT) at tools.cisco.com/ucs. With VMPT, you can determine the number of UCS servers needed by importing your VM
requirements. Import the saved file into VMPT. All recommended VMs will be listed on the CST tab.
9/15/2015

Collaboration Sizing Tool Field Reference

Hochgeladen von

Dokumentinformationen

Copyright

Verfügbare Formate

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Copyright:

Verfügbare Formate

Collaboration Sizing Tool Field Reference

Hochgeladen von

Copyright:

Verfügbare Formate

Collaboration Sizing Tool Field Reference