Cisco Cisco Unified Provisioning Manager 8.5 白書

Page 55 of 71

Why Am I Not Able to See the Phones and Line Under Some Subscriber Records?

By default, services are assigned to subscribers and displayed under the subscriber record only if there are

matching service area settings. For phones, Cisco Unified Provisioning Manager matches the following attributes:

Device Pool, Common Device Configuration, Calling Search Space of Phone, Location, and Protocol. For lines,

Cisco Unified Provisioning Manager matches the following attributes: Device Pool of Phone, Common Device

Configuration of Phone, Route Partition of Line, Calling Search Space of Line, Location of Phone. Make sure you

add the corresponding service areas and redo the domain sync.

Note:

Direct Inward Dialing (DID) blocks assigned to the service area are not used for synchronization.

Enabling Non-RestrictedDomainSync to Reduce the Number of Service Areas

By default, services are assigned to subscribers and displayed under the subscriber record only if there are

matching service area settings. The number of service areas required might be a lot based on permutations and

combinations of different service area attributes. To reduce the number of service areas needed, you can enable

Non-RestrictedDomainSync rule with one default service area per call processor to make sure services for all the

existing users are manageable in Cisco Unified Provisioning Manager. Then you can create the new service areas

to serve as service templates for UPM to manage all the new users.

Notes:

●

The Non-RestrictedDomainSync always picks up the first service area from the list of service areas in the

data field of the Non-RestrictedDomainSync rule and adds the service under that service area. Therefore if

you have only one Communications Manager cluster, adding more than one service area to the data field

will not have any effect. Only the first one will be used.

●

Be aware that if you run a domain synchronization and then change the configured domain rule to Non-

RestrictedDomainSync and then run another domain synchronization, any services that were not previously

synchronized will be placed in a service area based on the Non-RestrictedDomainSync rule. This could

result in services for a subscriber showing up in multiple service areas.

Why Did Some Subscriber Services Show Up in Multiple Locations (Service Areas)?

The services were probably already categorized under different service areas based on regular sync rules before

the Non-RestrictedDomainSync rule was enabled. After the rule was enabled, it would have picked up the services

that either could not be added to any customer record during previous syncs since matching service area was not

found, or services that were added to the Communications Manager after the rule was enabled.

Those are the only reasons services might show up under different service areas. The only option is to delete the

domain (not the call processors or Unified Message processors) and re-create the domains/service areas and

then do a synchronization.

Why Doesn’t the Extension Mobility Service Show Up in the Subscriber Record?

Please check the following:

●

Make sure you have Extension Mobility Service subscribed for the subscriber.

●

Make sure the service name defined in Provisioning Manager is the name of the Extension Mobility Service

configured on a call processor.