Cisco Cisco Unified Provisioning Manager 8.5 White Paper
© 2011 Cisco and/or its affiliates. All rights reserved. This document is Cisco Public Information.
Page 56 of 71
●
Make sure the service URL defined in Provisioning Manager is the Extension Mobility Service configured
on the call processor: http://<IPAddress>/emapp/EMAppServlet?device=#DEVICENAME#
Where <IPAddress> is the name or the IP address of the server where Extension Mobility is installed.
How to Batch-Create Service Areas
Bulk service area management allows you to create multiple service areas in one batch action. In the
/sep/ipt/config/sample/batchProvisioning folder, there is a sample file called AddServiceArea.txt. Users can modify
that sample file and load it into UPM through batch provisioning to create multiple service areas in one shot.
Note:
In UPM 2.x, the support for batch service area configuration only covers the attributes that you see in the
first screen of the service area UI configuration page, which does not include (1) the directory number block
configuration and (2) the provisioning attributes configuration that you see in the UI. Due to usability and
navigation issues, no more than five phones per user are recommended.
Moving Users Between Domains or Services Between Service Areas
Once a subscriber is added to a domain in Cisco UPM, subsequent syncs do not move subscribers from one
domain to the other even if changes are made to the key properties that dictate to which domain the subscriber
should be added. Cisco Unified Provisioning Manager 1.3 introduced a new batch action file column for deleting
users: OnlyFromCUPM. If this column is enabled (set to Y), any services on the subscriber record for the user will
be moved to the Global Resources namespace, and the subscribers or their services on the actual device (the call
processors or message processor device) will not be removed. If this column is not enabled, the user will be
removed from both Provisioning Manager and the device.
This provides you with a way to move users between domains or move subscriber services across service areas.
To move users between domains, a batch action file for deleting users can be created as shown in Table 10.
Table 10.
A Batch Action File for Deleting Users
Order Type
User ID
Product Name
Domain
Only From CUPM
Service Area
deleteUser
tsmith
*
westcoast
Y
*
*
Leave these fields empty (even if something is entered, it will be ignored).
After the batch project is executed, another batch action file for adding users can be created as shown in Table
11.
Table 11.
A Batch Action File for Adding Users.
Order Type
User ID
First Name
Last Name
Domain
Product Name
Service Area
addUser
tsmith
Tom
Smith
eastcoast
*
*
*
Leave these fields empty (even if something is entered, it will be ignored).
Lastly, enable AssociateOnlyExistingUsers for the desired domain and perform a domain synchronization.
Note:
Removing a subscriber only from Cisco UPM can be also done through the Cisco UPM 2.0 UI. If there
are services associating with the subscriber, Cisco UPM will first give you a warning; if you wish to proceed, it will
remove the subscriber only from Cisco UPM.
Handling Common Directory Number Mapping Across Multiple Service Areas
There are multiple ways to deploy, depending on whether the directory numbers need to have some significance
within a domain or significance within a service area.