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 22 of 53
During fresh installations of Cisco Unified Provisioning Manager 2.1, users should select the image (K9) license file
when prompted. Add-on license files must be copied to <install dir>/license when install completes.
During upgrades from 1.3.1 to 2.0 (to get to 2.1), old 1.3.1 licenses, image licenses, and upgrade licenses should be
put in a temporary directory, which UPM will ask for during installation. The installer will display license entitlement
based on licenses in the temporary directory. UPM will then copy all licenses into the license directory.
Total phone licenses are calculated as follows:
2.x image license must be present + new add-on phone licenses + ((1.x base licenses + total 1.x add-on licenses)
∩
total 2.x add-on upgrade licenses)) = total phone licenses.
At least one image license must be present. Feature counts within the image licenses are cumulative. These may be
phones, call processors, and message processors.
A “B” in the license PID means this license is good for the 2.x family of releases.
Basic Task Flow
●
Set up devices
◦
Add call processors (Cisco Unified Communications Manager publishers only, when using Cisco Unified
Communications Manager clusters) and message processors to Cisco Unified Provisioning Manager as
devices with capabilities assigned
◦
Configure call processors and message processors
◦
Perform infrastructure synchronization
◦
Perform subscriber synchronization
●
Set up domain deployment
◦
Create domains and assign call processors and message processors
◦
Create service areas
◦
Configure rules
◦
Perform domain synchronization
◦
For preexisting call processors and message processors
Verify that subscribers get created
●
Provision network
◦
Create and push templates to configure Cisco Unified Communications Manager
◦
Or sync current provisioning configurations from existing deployment
●
Set up deployment
◦
Create new service areas, as needed, for each domain, typically one per class of service
◦
Assign subscriber types to each service area
●
Admin
◦
Add subscriber types
◦
Modify products available to subscriber types
◦
Create administrative users for each domain
◦
Configure business rules
Set ordering workflow
●
Order, update, or change subscriber services