Cisco Cisco Prime Collaboration Assurance 11.5 백서

다운로드
페이지 33
 
 
© 2015 Cisco and/or its affiliates. All rights reserved. This document is Cisco Public Information. 
Page 28 of 33 
● 
If 
you can’t see the phones and lines under some user records, it is because, by default, services are 
assigned to users and displayed under the user record only if there are matching service-area settings. For 
phones, Cisco Prime Collaboration Provisioning matches the following attributes: device pool, common 
device configuration, location, and partition. For lines, Cisco Prime Collaboration Provisioning matches the 
following attributes: device pool of the phone, common device configuration of the phone, route partition of 
the line, and the location of the phone. Make sure you add the corresponding service areas and redo the 
domain sync. 
Tips for Using Cisco Prime Collaboration Provisioning 
Why Doesn’t the Extension Mobility Service Show Up in the User Record? 
Please check the following: 
● 
Make sure you have Extension Mobility Service subscribed for the user. 
● 
Make sure the service name defined in Cisco Prime Collaboration Provisioning is the name of the Extension 
Mobility Service configured on a call processor. 
● 
Make sure the service URL defined in Cisco Prime Collaboration Provisioning 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. 
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 within a service area. 
If directory numbers can be random within the entire domain, the directory-number pool can be added to each 
service area. The directory-number allocation in Cisco Prime Collaboration Provisioning checks to see if the 
directory number it would pick out of a block has been used, so the first service area to pick a directory number 
gets it and the other service area then skips it to get the next one. In this design, users get the next available 
number in the pool. 
You may also allocate directory-number blocks based on the calling search spaces setup or how many users are 
expected within a service area. In this case, some network planning is necessary to decide how to allocate 
directory numbers. This option may be useful if each service area is to use certain ranges of directory numbers. 
For example, building 1 is in SA1 and has extensions with 1xxxx, and building 2 is in SA2 and has extensions with 
2xxxx. 
In either case, you can have multiple directory-number blocks per service area to fine-tune how the numbers get 
allocated. 
Working with TAPS 
The Tool for Auto-Registered Phone Support (TAPS) feature is supported on Cisco Unified Communications 
Manager. So far we suggest that you use it in conjunction with the Bulk Administration Tool (BAT) to provide two 
features: 
● 
Update MAC addresses and download predefined configuration for new phones 
● 
Reload configuration for replacement phones