Cisco Cisco Unified Provisioning Manager 8.5 White Paper
Deployment Guide
© 2010 Cisco and/or its affiliates. All rights reserved. This document is Cisco Public Information.
Page 29 of 53
How-To Examples
Taking Over an Existing Cisco Unified Communications Network
This section follows the exploits of a fictitious company as it deploys Cisco Unified Provisioning Manager to simplify
the Cisco Unified Communications deployment.
Network Descriptions
With operations in multiple countries, a fictional France-based utility firm is in the process of deploying Cisco Unified
Provisioning Manager to simplify moves, adds, changes, and deletes (MACD). Customer already has an operational
Cisco Unified Communications network so Cisco Unified Provisioning Manager will mainly be used for day 2
operations to speed up MACD.
Collecting Information for Cisco Unified Provisioning Manager Design and Configuration
The following information is collected to determine how to design and configure Cisco Unified Provisioning Manager:
●
Sites
◦
100 physical branch offices in total.
◦
10,000 IP phones.
●
Call processors
◦
Three Communications Manager clusters.
◦
For each of the three Communications Manager publishers:
Release 6.1(1).
Lightweight Directory Access Protocol synchronization and authentication.
Extension mobility.
●
Messages processors
◦
Three Cisco Unity Version 5.
●
Administrative partitioning
◦
Based on delegation requirements, users are partitioned into eight administrative sites.
●
Subscriber services provisioning requirement
◦
Most users have phone, line, voicemail, and email.
◦
Some users are provisioned with extension mobility (device profile and line) and voicemail.
●
Dial plan information
◦
There is one device calling search space per branch office.
◦
There are four line calling search spaces per branch office.
◦
There is one location code per branch office.
◦
There is one device pool per branch office.
◦
There are two common device configurations for all sites.
◦
Only Skinny Client Control Protocol (SCCP) is used for phones.
◦
Only one voicemail template is used per branch office
◦
Only one route partition is used for all sites.
Preparing End Systems
●
Create a SQL Server user and password that can be used by Provisioning Manager to access the SQL
Server database on Cisco Unity. The SQL Server user requires access to both the Cisco Unity and master