Cisco Cisco Unified Provisioning Manager 8.5 White Paper

Page 41 of 71

Note:

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.

When configuring the rules, please follow the below general guidelines:

●

Rules 1-6 determine how subscribers are placed into the domain

●

Rule 7 determines where information for a subscriber comes from

●

Rule 8 determines how services are matched to service areas in a domain

●

Some rules work in conjunction with others, while some rules are set exclusively

●

The rules AssociateUsersByDeptCode, AssociateUsersByDevicePool, and AssociateUsersByLocation can

be used together

●

Once users are assigned to a domain, they cannot be moved to another domain. Users who need to be

deleted need to be deleted for the entire domain

If none of the business rules match your requirements, you can still import the users to domains through LDAP,

UI, or a batch file.

Domain Sync Rules Interoperability

The following are all the rules that determine the call processor users that will be synchronized in a domain sync

(includes the two new rules):

1. AssociateAllUsersinCallProcessor

2. AssociateOnlyExistingUsers

3. AssociateUsersByDeptCode

4. AssociateUsersByDevicePool

5. AssociateUsersByLocation

If the first rule is enabled, the settings of all the other rules are ignored. If the second rule is enabled, the settings

of rules 3, 4, and 5 are ignored. The last three rules are additive in the sense that if two of them enabled, then only

users that satisfy both the constraints are synchronized.

Suppose a domain has three call processors, CCM1, CCM2, and CCM3, and its rules are set like this:

●

AssociateUsersByDeptCode: Enabled with data “Dept1”

●

AssociateUsersByDevicePool: Enabled with data “CCM2:DevicePool2”;”CCM3:DevicePool3”

●

AssociateUsersByLocation: Enabled with data “CCM3:Location3”

When the domain sync is run, these users are synchronized:

●

CCM1: Users with department code “Dept1”

●

CCM2: Users with department code “Dept1” and with phones whose device pool is “DevicePool2”

●

CCM3: Users with the department code “Dept1” and with phones whose device pool is “DevicePool3” and

whose location is “Location3