BRKUCC-1683 Deploying Unified CM Business Edition For Simple Voice Messaging and Basic Dial Tone

Deploying Unified CM, Business Edition for
Simple Voice Messaging and Basic Dial Tone

BRKUCC-1683
Agenda
 Unified CM, Business Edition

Overview
Deployment Models
SRST/Gateway Protocol Selection
Unified CM Applications
Roadmap + Demo
 Rapid Deployment Method

Overview
Architecture and Design
RDM Deployment A to Z
RDM Demo
BRKUCC-1683_c1 © 2010 Cisco and/or its affiliates. All rights reserved. Cisco Public 2
Unified CM, Business Edition Overview
MCS 7828 Specifications
 MCS 7828 appliance required for Cisco Unified CM, BE
 Rack-mountable 1RU form factor
 Intel XEON QUAD-CORE Q9400 1333 MHz
 8GB SDRAM (4x2GB)
 Two 250GB Cold Swap SATA drives for higher reliability
 Pre-loaded OS and software suite
 SW-Only is not available for this offering
 MCS Model only, no HP or IBM equivalents
Right Balance of: Availability / Affordability / Cost of Ownership

Cisco Unified Communications
Manager Business Edition (CMBE)
 Same as Unified Communications

Manager 8.0
Same version, same image (Unified CM,
Unified CM, BE or Unity Connection)
Unity
Unified
Pre-loaded on MCS-7828 servers CM
Connection Mobility
Manager
Released in lock step with CUCM
 Common Platform Services

RTMT: diagnostics, macro and micro
traces, port status monitor
DRS: backup and restore (replaces DRT)
Patch management: same process as
UCM, patch OS and application together
ServM: start, stop and monitor processes
Dual Partition Upgrades Unified CM,
No longer requires Unity TSP BE
Migration
 CMBE is targeted at Greenfield customers and is

for new installations only
 Migration to CMBE from Stand-alone CUCM or
CUC is not currently supported but can be achieved
 Methods
Re-purpose
Use Bulk Administration Tool
Migrate Licenses
 Migration from CMBE to stand-alone CUCM
or CUC
HW can be re-purposed for CUCM or CUC
stand-alone deployment
Matching Solution to Customer Needs
 Customer has fewer than 100 employees

Cisco Unified Communications Manager Express OR Unified 500
Series likely the best fit
 Customer has between 150–500 employees
Is customer price sensitive?
Yes—Cisco Unified Communications Manager Business Edition
… but, wants higher level of Availability
Include Cisco Unified SRST
Nope—Customer wants highest level of availability and is not
price sensitive
Offer redundant Cisco Unified Communications Manager
Customer has more than 300 employees and is likely to grow
beyond 500 employees in 2–3 years?
Yes—Offer Unified Communications Manager
No—Offer Unified Communications Manager Business Edition
LDAP Directories
Directory Synchronization
User Data
Synchronization DirSync
CUCM CUC
DB Dir DB
Authentication User
Corporate Lookup
Directory IMS
(Microsoft AD, CMBE
Netscape/iPlanet) WWW CM 7.X Server
Authentication User
DirSync tool pulls Lookup
main user attributes
from directory into
DB
User passwords are
NOT sync’ed “directories”
button
CUCM User Options,

Extension Mobility, IP Phone
CUCM Administrators
Unified CM, BE: Limitations
 No Redundancy
Single appliance solution only
No VM redundancy
No CUCM redundancy (no Publisher/subscriber model)
SRST supported for all sites (the hub and the spoke)
 Migration possible with caveats

Must buy as CMBE appliance
License and Hardware migration
No data migration to multi-appliance/server (standalone)
solution; can leverage Bulk Admin Tool and COBRAS to
migrate data!
Deployment Models
Cisco Unified CM, Business Edition
Single Site
The single-site model:

Application
Server  Consists of Cisco
(optional)
Unified CM and Cisco
Cisco Unity Connection on
Unified CM, the same hardware
Business Edition platform, 7828I4,
located at a single site
SRST-Enabled
Voice Gateway
or campus, with no
telephony services
provided over an
PSTN IP WAN
Multi-Site Centralized Call Processing
Application
Server
SRST-Enabled
(optional)
Voice Gateway
PSTN
Cisco Unified
CM, Business
Edition
IP WAN Remote Site 1

SRST-Enabled
Voice Gateway
SRST-Enabled
Voice Gateway
Headquarters
Remote Site 2
Tele-worker
…
Up to 20 Total Sites
Distributed Call Processing
CMBE to CMBE Application
Server
(optional)
AS Site 1 Cisco Unified
CM, Business
Application Server Edition
(optional)
PSTN SRST-Enabled
Cisco Unified Voice Gateway
CM, Business
Edition
AS Site 2
IP WAN
SRST-Enabled AS Site 3
Voice Gateway
Application
Server
(optional)
Cisco Unified
CM, Business
Edition
Up to 20
Interconnected Sites SRST-Enabled
Voice
Consistent w/ 20 max gw Gateway
Unified CM to CMBE Application
Server
(optional)
Cisco Unified
CM, Business
Applications Edition
(VMail, IPCC, MP…)
CUCM PSTN SRST-Enabled

Cluster Voice Gateway
AS Site 1
IP WAN
Application
Server
(optional)
Headquarters Cisco Unified
CM, Business
Edition
Up to 20
Interconnected Sites SRST-Enabled
Voice
Consistent w/ 20 max gw Gateway
BRKUCC-1683_c1 © 2010 Cisco and/or its affiliates. All rights reserved. AS Site 2
Cisco Public 18
CMBE to CUCME
Headquarters
CUCME
Application Server
(optional)
PSTN
Cisco Unified
CM, Business
Edition
Remote Site 1
IP WAN
SRST-Enabled
Voice Gateway
CUCME
Up to 20
Interconnected Sites
Consistent w/ 20 max gw
BRKUCC-1683_c1 © 2010 Cisco and/or its affiliates. All rights reserved. Remote Site 2
Cisco Public 19
Autonomous System (AS)
 AS should comply with the follow guidelines

 Operates independently from other AS
 No centralized applications for other AS devices,
endpoints or clients
 Interworks via trunking consistent with maximum
gateways (20)
ICT/SIP to CMBE or Unified CM
H.323/SIP to Unified CME
 Do not surpass system BHCA limitation 3600
Design Characteristics and Considerations
 Supports a max of 500 users and up to 575 SCCP or SIP IP phones or video endpoints
Note: There is a firm configuration maximum of 700 devices (including all configurable phone types,
CTI ports, and H.323 clients)
 Supports a max of 20 SIP, MGCP, or H323 devices (gateways, MCUs, trunks,

and clients)
 Unified CMBE supports a maximum of 500 mailboxes and 24 SCCP voicemail ports; the
24 ports can be provisioned for Automated Speech Recognition (ASR), Text-to-Speech
(TTS) or as simple voicemail ports, as needed and licensed
 Unified CMBE supports a maximum of 500 concurrent sessions of any mix of the
following client access options:
Cisco Unified Personal Communicator
Internet Message Access Protocol (IMAP)
Cisco Unity Connection Inbox clients
Cisco Unity Inbox RSS Feeds
 Max 3600 System BHCA/BHCC

 Stay within the limits specified above, and be attentive not to oversubscribe the system;
when planning your system, if you reach those limits or surpass them, consider deploying
standalone Cisco Unified CM and Cisco Unity Connection solutions instead
 Digital signal processor (DSP) resources for conferencing, transcoding, and media
termination point (MTP)
 500 active CTI connections (ex: Remote Call Control, UCCx, etc.)
System Capacity: Key Takeaways
Attribute Capacity
Maximum total devices 575 / 700
500 Mailboxes and 24 ports
Mailboxes and voicemail ports Updated from 16 (SCCP)
Total number of sites (SRST) 20
Gateways (clients) 20
Max BHCA 3600
Call processing and voicemail

Feature limitations redundancy
Survivable Remote Site Telephony
SRST/Gateway Protocol Selection
Survivable Remote Site
Telephony (SRST)
Guidelines When Using SRST with Unified CMBE
 When choosing a gateway call control protocol,
observe the following recommendation:
If you are not using SRST, use Media Gateway Control
Protocol (MGCP) gateways for the PSTN if you do not
require H.323 or SIP functionality; this practice simplifies
the dial plan configuration and administration
Gateways
H.323
TDM IP
PRI Layer 3
PSTN
Layer 2 H.225
Framing
Cisco Unified CM
 All PSTN signaling terminates on gateway

 H.225 communication between gateway and Cisco Unified CM
 H.323 is a “peer-to-peer” protocol: each side can make decisions
Gateways
SIP
TDM IP
PRI Layer 3
PSTN
Layer 2 SIP over UDP/TCP/TLS

Framing
Cisco Unified CM
 All PSTN signaling terminates on gateway

 SIP communication between gateway and Cisco Unified CM
 SIP is a “peer-to-peer” protocol: each side can make decisions
Gateways
MGCP: Q.931 Backhaul
TDM IP
PRI Layer 3 Q.931 Backhaul over TCP

PSTN
Layer 2
Framing MGCP over UDP
Call Signaling Cisco Unified CM
 Framing and layer 2 signaling terminates at the gateway

 Layer 3 signaling is backhauled to the Cisco Unified CM
 MGCP is a “client-server” protocol: all call-related decision making
is done by the server.
 MGCP 0.1 with Cisco Unified CM only
Voice Gateway Failover
H.323/SIP MGCP
SIP Proxy GW Switches to
H.323/SIP/POTS Dial-Peers
POTS Dial-Peer VoIP Dial-Peers During MGCP Fallback
4 1
PSTN
2
3
X IP GK
CUCM PSTN
X IP
MGCP Registration,
Keepalives and Backhaul
CUCM
 MGCP requires “failover” features  H.323/SIP intrinsically resilient

No special “failover” features, just dial-
 When call agent is out of peer configuration
contact, MGCP GW fails over
to local control  Successive VoIP/POTS dial-
H.323, SIP or POTS dial-peers peers (by preference) attempted
ISDN D-channel is reset to gain control
on failure
of call state
 Each call setup attempt is treated
 Flapping IP links interfere independently
significantly with call setup Same sequence of dial-peers
Call agent registration and state
are affected  Flapping IP links do not interfere
significantly with call setup operation
Survivable Remote Site
Telephony (SRST)
Recommendation: Gateway Call Control Protocol
 Stateless vs. Stateful: H.323/SIP vs. MGCP; MGCP is a
state-full, master/slave gateway call control protocol that is
robust and easy to configure, but it has the following
drawbacks when deployed with SRST:
1. MGCP gateway fallback transitions to a default H.323 or SIP
session application; therefore, an H.323 or SIP configuration is still
required for external calls in SRST mode
2. There is no call preservation when MGCP fallback occurs for T1
and E1 PRI or BRI (only for MGCP analog and T1 CAS)—all
active calls are dropped when MGCP fallback occurs for PRI; with
H.323 and SIP, you can achieve call preservation on T1 and E1
PRI with failover to SRST mode—phones in SRST mode can dial
out to the PSTN, and previously active calls are still preserved
3. Conversely, the same process occurs when connectivity to
Unified CMBE becomes available; the MGCP PRI re-homes
(called switchback) to Unified CM, and all active calls on the PRI
are dropped—with SIP and H.323, call preservation is maintained
MGCP Gateway Fallback
CUCMBE
Backhaul PSTN
D-Channel
L3/Q931
L2/L3
L2/Q921
WAN
Outage
HQ Signaling
MGCP
Fallback
Media
Site A
Signaling
MGCP Gateway Failback/Switchover
CUCMBE
Backhaul PSTN
D-channel
L3/Q931
STOP L2/L3
L2/Q921
WAN
Outage
HQ Signaling
MGCP
Fallback
Media Still registered

in SRST Mode
Switchback: Site A
Immediate
Signaling
MGCP Gateway Failback/Switchover
CUCMBE STOP
PSTN
L2/L3
WAN
Outage
HQ Signaling
MGCP
Fallback
Media Registered to
CMBE
Switchback: Site A
Graceful
Signaling
Unified CM Apps
CUCM Apps
Cisco Extension Mobility (EM)

Supports 26 sequential logins and/or logouts per minute.
 Cisco Unified Communications Manager Assistant

(Unified CM Assistant)
Maximum of 10 assistants can be configured per manager
Maximum of 10 managers can be configured for a single assistant
(if each manager has one line controlled by Unified CM Assistant)
Maximum of 10 assistants and 10 managers can be configured per
Unified CMBE system
 The Unified CM Assistant application interacts with the CTIManager

for line monitoring and phone control—each line on an assistant or
manager phone generates a connection to the CTIManager; in
addition, each Unified CM Assistant route point generates a
connection to the CTIManager
 When configuring Unified CM Assistant, you must consider the
number of required CTI connections with regard to the overall limit for
CTI connections (300 CTI connections for Cisco Unified CMBE); if
additional CTI connections are required for other applications, they
can limit the capacity of Unified CM Assistant
CUCM Apps
Cisco Unified Communications Manager Attendant Console (AC)

 The native AC application no longer supported in 8.x
 Cisco Unified Business Attendant Console and Cisco Unified Department
Attendant Console:
Maximum of two attendants
Same Limits apply for Pilot points and AC devices
 Max of 50 AC devices:
The AC device capacity numbers can be divided among pilot points and pilot point hunt group members; for
example, the maximum number of AC devices is 50—this capacity can be allocated in a number of ways, such
as one pilot point with 50 members or 10 pilot points with five members in each pilot point hunt group
 The Cisco AC application interacts with the CTIManager for line monitoring and phone
control—each line on an Attendant phone generates a connection to the CTIManager;
in addition, each AC pilot point generates a connection to the CTIManager
 When you configure the AC application, the number of required CTI connections
must be considered with regard to the overall limit for CTI connections (300 CTI
connections for Unified CMBE); if additional CTI connections are required for other
applications, they can limit the capacity of the AC application
CUCM Apps
Cisco WebDialer
 The WebDialer service runs on Unified CM and can support
up to the maximum BHCA capacity for Unified CMBE (one call
per second, or 3,600 calls per hour)
 To calculate the total BHCA for WebDialer, use the
following formula:
Total WebDialer BHCA = (Number of users) * (BHCA per user)
The result will typically be the same as the total user BHCA for
Unified CMBE; whether users dial from the phone itself or the
WebDialer application, the expected BHCA should not change
CUCM Apps
Cisco Unified Mobility

 Mobile Connect, commonly called Single Number Reach (SNR), gives users the ability to
redirect incoming IP calls from Unified CM to as many as four different designated client
devices such as cellular phones or IP phones
 The capacity for Unified Mobility users in Unified CMBE depends on the BHCA of the
phones to which SNR is associated—thus, the number of remote destinations supported
depends directly on the BHCA of those phones; the guidelines are as follows:
A maximum of 4 remote destinations can be configured per Device Profile
 Each remote destination has an associated cost to it that affects BHCA—for every
remote destination, one additional call leg is used; because each call generally consists
of two call legs, one remote destination ring is equal to half (0.5) of a call—therefore, you
can use the following formula to calculate the remote destination BHCA:
Remote destination BHCA = 0.5 * (Number of users) * (User or phone BHCA)
 Assuming a system of 300 users at five BHCA each, with each user having one remote
destination (total of 300 remote destinations), the BHCA calculation for the remote
destinations would be:
Remote destination BHCA = 0.5 * 300 * 5 = 750 BHCA
 Total user BHCA in this example is 300*5 = 1500, and the remote destination BHCA is
750; therefore, the total system BHCA for this example would be 1500+750 = 2250 if
these were the only two BHCA variables in the deployment
Key Takeaways
The Key Takeaways of this section are:

 Max 500 CTI Connections
 All users can be EM enabled as long as 26 EM login/logout
per minute are not exceeded
 CUCMA 10 asst/10 mgr
 WebDialer bound to system BHCA
 Mobile Connect (SNR) increases BHCA for associated
phones by 0.5
SMB Roadmap
Roadmap slides
 1-2 slides on roadmap

 Small Demo
RDM Overview
UC Rapid Deployment Method (RDM)
What Are We Trying to Solve?
 Deploy a base configuration of Unified CM and
Unity Connection
for basic dial-tone and simple voice messaging
 Guiding Principles
Simplify configuration effort
Reduce complexity
Reduce time to deploy
Reduce operational expenses
Leverage features currently shipping in products
 Where to Start: Phase out the approach
Start with SMB market and work up
Determine relevance in the field
 Potential Next Steps (Need field input)
UC Rapid Deployment Method (RDM)
Deploying Unified CM and Unity Connection for
Basic Dial-Tone and Simple Voice Messaging:
Simplify, Reduce Time, Complexity and
Operation Expenses RDM
Method
 Streamlined Multi-Site Deployment Process for up to 1000 Users
 Easy to follow Procedure to Install, Configure, Provision and Deploy “User and Phones”
 Wizard Driven Customization Tool to Ease User and Phone Provisioning and Deployment
 Ship Phones to Site (no bar code scanning necessary)
Benefits
 Reduced time to Deploy by up to 50% (Tested)
 Reduced Skill Level Requirements (Equivalent to CCNA)
 Reduced Partner Logistical Costs (Phone scan, etc.)
 Reduced Partner Total Cost of Operations
 Validated Reference Architecture based on UC SRND
 Automated and Validated Deployment Process = Less Error Prone
UC Rapid Deployment Method
What Does RDM Comprise?
 Architecture Guide
 Deployment Guide
 RDM Customization Tool
Wizard Driven Tool (EXE + zip DLL)
BAT TAR File (Preconfigured Template)
Produces BAT Files (TAR, CSV, TXT)
(Customized Templates)
RDM is FREE! No special licenses required!
Provisioning Phones
The Manual Way: Bulk Administration
 Scan Barcode from

Each Phone’s Box
into a Spreadsheet
 Configure Site and User

Specific Details for Each
Phone in the Spreadsheet
 Label Each Box and

Ensure Shipment to the
Correct Site and Person
Provisioning Phones
The “RDM” Way
 Configure Site Info and RDM

User Device Profiles
Using the “RDM” Procedure
 Ship Correct Models

and Quantity of Phones
to Sites
Correct Phone Model
on User’s Desk
 User Logs in to
Associate Phone
IP Address of Phone
Defines Site Profile
Architecture and Design
Reference Architecture #1
Unified Communications Manager and Unity Connection
Unity Connection
Voice Messaging
PSTN
Unified CM
2 Node Cluster
SRST
IP WAN
Site1
…
HQ
 Unified CM (2 Nodes-Redundant) at HQ
 Unity Connection Voice Messaging at HQ
 Up to 20 Remote Sites
SRST
 SRST at Remote Sites
Site20
 Up to 1,000 Users supported
Reference Architecture #2
Unified Communications Manager Business Edition (CMBE)
Not Included in SBA
PSTN
Cisco
Unified CM,
Business Edition
SRST
IP WAN
SRST
Site1
…
HQ
 Cisco Unified CM and Unity Connection
on a single platform located at HQ
 Up to 19 Remote Sites
 SRST at both HQ and Remote SRST
Site locations
Site19
 Up to 500 Users supported
DN: 51234
LDAP
FOUNDATION
Voice Messaging DB
Ext Mobility AD Sync
2.2.2.0/24
INITIAL 1.1.1.0/24
Dial Tone
BRKUCC-1683_c1 DIAL PLAN
© 2010 Cisco and/or its affiliates. All rights reserved. Device Mobility
Cisco Public 50
Auto-Registration and Device Mobility
Central Site Remote Site

PDX EUG
IP Subnet
IP Subnet
2.2.2.X
1.1.1.X
Device Mobility
Central Site Remote Site

PDX EUG
IP Subnet
IP Subnet
2.2.2.X
1.1.1.X
 Use Local Gateway

 Use Local Media Resources (MRGL)
 CAC Aware (Location/Region)
 Local SRST Reference
Device’s subnets that are not recognized by UCM will default

to the Central Site (HG) DMI; ensure correct subnet
configuration when filling out subnet information in RDM
Extension Mobility
Extension Mobility Login

jsmith
Device Profile 62796

62796
62798
Home
Sue Mobile
RDM: How It Works
Deploy Phones
DB
Bulk Admin
CCM BAT
WWW
Install/Provision
Enable EM
CCMADMIN  System  Unified CM  Select Server:

SECURITY
Toggle Auto-Registration On/Off
Perform On Each Server
Rapid Deployment Method
Call Admission Control: Locations Design
HQ
<Hub_None>
Location
PSTN IP WAN
Remote
Sites
Site1
... Site20
Location 1 Location 20
Max BW = 48 kbps Max BW = 48 kbps
Class of Service
Calling Search Space Route Partition 1 Route Partition 2 Route Partition 3

CSS_Base PAR_Base
CSS_LocalPSTN PAR_PSTN_Local
CSS_NationalPSTN PAR_PSTN_Local PAR_PSTN_National
CSS_InternationalPSTN PAR_PSTN_Local PAR_PSTN_National PAR_PSTN_Intl
ROUTE PATTERN ROUTE PARTITION

9.911 PAR_Base
Emergency Dialing
911 PAR_Base
9.[2-9]XXXXXX# PAR_PSTN_Local
Local Dialing
9.[2-9]XXXXXX PAR_PSTN_Local
9.1[2-9]XX[2-9]XXXXXX PAR_PSTN_National
National Dialing
9.1[2-9]XX[2-9]XXXXXX# PAR_PSTN_National
9.011! PAR_PSTN_Intl
International Dialing
9.011!# BRKUCC-1683_c1 ©PAR_PSTN_Intl
2010 Cisco and/or its affiliates. All rights reserved. Cisco Public 56
Dial Plan: Call Routing
Calling Search Partitions Route Route

Spaces (CSS)(Containing Route Patterns) Lists Groups Devices
Internal
All IP Phones
CSS_Base
911
Device 9.911 PSTN
All Phones Assigned
the CSS_Base Calling
Local Local HQ Gateway
Search Space 9.[2-9]XXXXXX
Route Local
National Route PSTN
List Group
National 9.1 [2-9]XX
Site 1 Gateway
[2-9]XXXXXX
UDP Line International PSTN

Lines Assigned International 9.011!
Additional Site 2 Gateway
9.011!#
Classes of Service
RDM Deployment
A to Z
UC RDM
Deployment Phases
 Prerequisites
 Server Installation (Unified CM/Unity Connection)
 Server and Site Provisioning
 User and Device Profile Configuration
 Unity Connection Installation/Configuration
 Phone Deployment
RDM: How It Works
Prerequisites
 DNS
 License Files (Unified CM/Unity Connection)
 Unified CM 7.1.3 FCS DVD
 Microsoft’s Active Directory (Optional)
Manager Distinguished Name (Read Access required)
Password
User Search Base (cn=users,dc=cisco,dc=com)
Host Name or IP Address and port number
 Spreadsheet S/W installed on the PC used

for administration if Active Directory is
not available
 DHCP
Option 150 for TFTP
Option 6 for DNS
RDM: How It Works
Install the Servers
 Installs can be done in parallel

 Post Install
a) Activate Services
b) Upload Licenses
RDM: How It Works
RDM-CT: Server and Site Provisioning
 Run RDM-CT: Server and Site

 Choose Architecture (CMBE or UCM)
 Configure Servers and Sites (Quantity,
Names, Voice Subnets, SIP GW IP)
 LDAP Directory (Active Directory)
 Dial Plan (Auto-Reg Ext, VM

Ports, VM Pilot, MWI)
 Confirm Configuration
 BAT TAR File Created
RDM: How It Works
RDM-CT: Server and Site Provisioning
 Import BAT File

 Update LDAP Passwords
RDM: How It Works
User and Device Profile Configuration: User Data
Cisco Unified
User Data CM 8.X Server
Synchronization DirSync
DB
LDAP(S)  First Name
 Last Name
Corporate  UserID
Directory BAT  Tel Number
(Microsoft AD,
Netscape/iPlanet)
WWW {optional}
Export Users
Admin Exports
User Data
RDM: How It Works
User and Device Profile Configuration: UDP Template
Cisco Unified
CM 8.X Server
DB
BAT
WWW
Create UDP
Templates
RDM: How It Works
RDM-CT: User and Device Profile Configuration
 Run RDM-CT: User and Device Profile
 Add User DN ranges per Site
 Import User Data into RDM-CT
(From Previous BAT User Export)
 Populate UDP Grid with User Data

 DN (From: AD, Ranges, Manual)
 External Phone Number Mask
 Class of Service (CSS)
 Set Line Display Text
 Alerting and Calling Name
(Automatic)
 BAT Files Created
RDM: How It Works
RDM-CT: User and Device Profile Configuration
DB
Bulk Admin
CCMAdmin BAT
WWW
RDM: How It Works
Unity Connection Configuration
 Install CUC (If Not Already Done)

 Activate Services
 Upload Licenses
 Configure Phone System
 Configure LDAP
 BAT: Import Users
(Associate with VM Template)
RDM: How It Works
Deploy Phones
DB
Bulk Admin
CCM BAT
WWW
Enable EM
On
Phones
CCMADMIN  System  Unified CM  Select Server:
Toggle Auto-Registration On/Off

Perform On Each Server
RDM: How It Works
Deploy Phones
Users Simply Login To Phones

Avoid User/Phone Association
BRKUCC-1683_c1 © 2010 Cisco and/or its affiliates. All rights reserved. Cisco Public
User Device Profile 70
Appendices
 User PIN Change: Procedure to Change PIN

after first login
 Integration without LDAP: Add Users to CUCM
in case of unavailability of LDAP/Active Directory
 Integration without LDAP: Add Users to Unity
Connection in case of unavailability of LDAP/
Active Directory
 Dial-Plan: Procedure to remove the current
dial plan
 Dial-Plan: Procedure to add and change User
and Networks Locales
Partner Pilot Validation
 54 Partners Signed up for the RDM Pilot

 15 Partners have sent written feedback
 “Would this RDM save you time over the approach
that you currently use?”
“Definitely YES! The RDM tool automation saves time”
“This method reduced my time to half; if deployment
would take four days with regular approach then this
would reduce time to one or two days”
 “Did the RDM experience meet the objectives of
reducing time, cost and skill to deploy UC system’s
(250–1000 users): Yes, No?”
15 of 15 partners/testers responded “yes”
Benefits
 Validated Reference Architecture based on UC

SRND (Simplified UC Planning, Design and
Deployment)
 Reduce Skill level requirements (Equivalent
to CCNA)
 Reduced time to deploy (Up to 50%)
 Reduced Partner logistical costs (Phone scan, etc.)
 Automated less error prone (Day 0–2 Ops)
 Reduced Partner Total Cost of Operations
 Improve the products and solution
RDM Demo
Tips and Tricks
Tips and Tricks
 Managing Extension Mobility

 Removing Extension Mobility from Device Profiles
Managing Extension Mobility Phones: 1
 “Actively Logged In Device Report”: Allows

CCMAdmin to manage phones with Extension
Mobility
 Device > Phones > “Related Links” in the right hand
side of the CCMAdmin Page called “Actively
Logged In Device Report”:
 Selecting this will allow you to view which users are

logged into which devices
 Or view the phone device itself to verify the

currently logged on User
 On the Phone Device > Extension Mobility
subsection > view the current logged on User:
Resources
 Rapid Deployment Method Landing Page:

http://www.cisco.com/en/US/partner/products/sw/voicesw/p
s556/products_partner_resources_list.html
 Link to Cisco Community Central

https://www.myciscocommunity.com/index.jspa
 Login/Register with CCO ID and go to

RDM Community:
https://www.myciscocommunity.com/community/partner/coll
aboration/uc/rdm
Complete Your Online
Session Evaluation
 Give us your feedback and you

could win fabulous prizes.
Winners announced daily.
 Receive 20 Cisco Preferred
Access points for each session
evaluation you complete.
 Complete your session
evaluation online now (open a
browser through our wireless
network to access our portal)
or visit one of the Internet Don’t forget to activate your
stations throughout the Cisco Live and Networkers Virtual
Convention Center. account for access to all session
materials, communities, and on-demand
and live activities throughout the year.
Activate your account at any internet
station or visit www.ciscolivevirtual.com.
Enter to Win a 12-Book Library
of Your Choice from Cisco Press
Visit the Cisco Store in the

World of Solutions, where
you will be asked to enter
this Session ID code
Check the Recommended Reading brochure for

suggested products available at the Cisco Store
Appendix
Capacity Planning
and Scaling the System
Capacity Planning
and Scaling the System
 What is BHCA?
The BHCA is the average number of calls per hour per device during
the busy hour. (For example, the busy hour for many systems is from
10:00 AM to 11:00 AM or from 2:00 PM to 3:00 PM.)
 How does BHCA affect performance?

Many types of devices can register with Unified CM (for example, IP
phones, voicemail ports, CTI devices, gateways, and DSP resources
such as transcoding and conferencing). Each of these devices
requires resources that can include memory, processor usage, and
disk I/O. Each device then consumes additional system resources
during transactions, which are normally in the form of calls. For
example, a device that makes only 6 calls per hour consumes fewer
resources than a device making 12 calls per hour
 What other than devices effects BHCA?

Shared Lines, Call Distribution Broadcast algorithm, SNR
Capacity Planning:
Rules and Guidelines
 Ensure that you are within the 3,600 BHCA maximum

 Create groups of devices with common usage characteristics based on BHCA
 Add the BHCA for each device group to get the total BHCA for the system
 Calculate half calls (single call legs):
 Shared Lines:
A call to a shared line will be calculated as one call leg per line instance, thus 0.5 of a call or
Shared line BHCA = 0.5 * (Number of Shared lines) * (line BHCA)
 Single Number Reach (SNR):

Remote destination BHCA = 0.5 * (Number of users) * (User or phone BHCA)
 Call Distribution algorithm of broadcast:

Max 3 members per line group and Max 3 line groups that have a distribution algorithm of
broadcast
 CTI Ports handling calls
Capacity Planning:
Contact Center Example
 The required specification is for 15 contact center agents with a

maximum of 30 calls per hour during the busiest hour
15 contact center agents at 30 BHCA = 450 BHCACA
 There are 96 non-agent users with average usage of 6 BHCA, and each user
has the ability to configure one remote destination for Single Number Reach
with Cisco Unified Mobility
96 average-usage users at 6 BHCA = 576 BHCA
SNR BHCA = 0.5 * 96 * 6 = 288 BHCA96 * 6 = 288 BHCA
 There are 36 non-agent users with heavy usage of 15 BHCA, and each also
has the ability to configure one remote destination for Single Number Reach
36 heavy-usage users at 15 BHCA = 540 BHCA
SNR BHCA = 0.5 * 36 * 15 = 270 BHCA = 0.5 * 36 * 15 = 270 BHCA
 There are 20 extra shared lines, 10 of which are shared across 10 users from
the average usage pool and 10 in the heavy usage pool
10 shared lines in the 6 BHCA group = 30 BHCA
Capacity Planning:
 What about BHCA on CTI ports?

From the system perspective it takes two calls legs to
equal one call (remember SNR example); the total impact
of 450 BHCA for 15 agent phones will be shared across the
CTI ports
Therefore 450 calls will come in and be transferred out to
the agents—this accounts for 1 call leg per call; thus the
cost of 450 BHCA on those CTI ports would be 225 extra
call legs (the same as SNR calculation):
CTI Port BHCA = 0.5 * (Number of agents) * (Agent BHCA)
CTI Port BHCA = 0.5 * 15 * 30 = 225
Capacity Planning:
15 contact center agents at 30 BHCA = 450 BHCA

96 average-usage users at 6 BHCA = 576 BHCA
SNR BHCA = 0.5 * 96 * 6 = 288 BHCA
36 heavy-usage users at 15 BHCA = 540 BHCA
SNR BHCA = 0.5 * 36 * 15 = 270 BHCA
CTI Port BHCA = 0.5 * 15 * 30 = 225 BHCA
Total system BHCA = 2,454 BHCA
Groups of devices with common

usage characteristics based on
BHCA
Capacity Planning:
 System Max of 500 CTI Connections

 CTI connections in Contact Center Example:
15 contact center agents = 15 CTI connections
2 Applications (2 CTI Route Points) = 2 CTI connections
10 CTI ports allocated = 10 CTI connections
 Total CTI Connections = 15 + 2 + 10 = 27
If you plan to use any other Cisco Unified Communications applications

with Unified CMBE, such as Cisco Unified Presence or Cisco Unified
MeetingPlace Express on separate servers, remember to factor in their
impact on Unified CMBE performance and capacity. (See the chapters on
Cisco Unified Presence, and Cisco Unified MeetingPlace Express) Factors
such as BHCA and CTI ports are just a few of the components to be
considered.
Key Takeaways
The Key Takeaways of this section are:

 Calculate BHCA based on device groups
 500 total system CTI connections
 3600 total system BHCA
 Important Factors: CTI, Shared lines, Call Distribution
Algorithm, SNR, CUCM Apps

BRKUCC-1683 Deploying Unified CM Business Edition For Simple Voice Messaging and Basic Dial Tone

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

BRKUCC-1683 Deploying Unified CM Business Edition For Simple Voice Messaging and Basic Dial Tone

Uploaded by

Copyright:

Available Formats

Deploying Unified CM, Business Edition for

Simple Voice Messaging and Basic Dial Tone

 Unified CM, Business Edition

 Rapid Deployment Method

 MCS 7828 appliance required for Cisco Unified CM, BE

 Rack-mountable 1RU form factor

 Intel XEON QUAD-CORE Q9400 1333 MHz

 8GB SDRAM (4x2GB)

 Two 250GB Cold Swap SATA drives for higher reliability

 Pre-loaded OS and software suite

 SW-Only is not available for this offering

 MCS Model only, no HP or IBM equivalents

Right Balance of: Availability / Affordability / Cost of Ownership

 Same as Unified Communications

 Common Platform Services

 CMBE is targeted at Greenfield customers and is

 Customer has fewer than 100 employees

CUCM User Options,

 Migration possible with caveats

The single-site model:

IP WAN Remote Site 1

CUCM PSTN SRST-Enabled

 AS should comply with the follow guidelines

 Do not surpass system BHCA limitation 3600

 Supports a max of 20 SIP, MGCP, or H323 devices (gateways, MCUs, trunks,

 Max 3600 System BHCA/BHCC

Total number of sites (SRST) 20

Call processing and voicemail

 All PSTN signaling terminates on gateway

Layer 2 SIP over UDP/TCP/TLS

 All PSTN signaling terminates on gateway

PRI Layer 3 Q.931 Backhaul over TCP

Call Signaling Cisco Unified CM

 Framing and layer 2 signaling terminates at the gateway

 MGCP requires “failover” features  H.323/SIP intrinsically resilient

Media Still registered

Cisco Extension Mobility (EM)

 Cisco Unified Communications Manager Assistant

 The Unified CM Assistant application interacts with the CTIManager

Cisco Unified Communications Manager Attendant Console (AC)

Cisco Unified Mobility

The Key Takeaways of this section are:

 1-2 slides on roadmap

 Ship Phones to Site (no bar code scanning necessary)

 Reduced Skill Level Requirements (Equivalent to CCNA)

 Reduced Partner Logistical Costs (Phone scan, etc.)

 Reduced Partner Total Cost of Operations

 Validated Reference Architecture based on UC SRND

 Automated and Validated Deployment Process = Less Error Prone

RDM is FREE! No special licenses required!

 Scan Barcode from

 Configure Site and User

 Label Each Box and

 Configure Site Info and RDM

 Ship Correct Models

Central Site Remote Site

Central Site Remote Site

 Use Local Gateway

Device’s subnets that are not recognized by UCM will default

Extension Mobility Login

Device Profile 62796

CCMADMIN  System  Unified CM  Select Server:

Calling Search Space Route Partition 1 Route Partition 2 Route Partition 3