CUCM connection options
Shared user base across several clusters
Mark users without a location in the selected cluster with their home cluster.
In EasyUC: EasyUC Cisco → Administration → CUCM & Provisioning → CUCM Connections → box above the list
What it is for
In environments with several CUCM clusters, all clusters often contain the same end users, for example because they all synchronize from the same LDAP directory. The user list of a cluster then also shows people whose phones are in another cluster. Such users match none of the locations of the selected cluster.
With the All clusters share the same user base setting, EasyUC checks the locations of the other enabled connections for these users. If the user's number falls into a number range of another cluster, or if the attribute value matches for location type Custom Enduser Attribute, EasyUC marks the user in the user list with User of Cluster and the alias of that cluster, plus the location name if there is one.
The setting applies to the entire installation, not to a single connection. It changes nothing on the CUCM.
Prerequisites
- Sign-in as an administrator. Saving requires the permission
ROLE_APP_UPDATE_MULTI_CLUSTER_SETTINGS. - License with the
cucmmodule. - At least two enabled CUCM connections with locations set up. Disabled connections are not taken into account.
- For location type
Normal, the user needs a phone number in the CUCM that falls into a number range of a location.
Step by step
Fields and options
| Field / action | Meaning and use |
|---|---|
| All clusters share the same user base | Switch, default: off. Explanatory text in the interface: “If 'All clusters share the same user base' is active, users that match none of the locations of the selected cluster are marked with the cluster whose locations they belong to.” |
| Save | Saves only this setting. The connections themselves remain unchanged. |
Checking the result and narrowing down errors
- In the user list, users without a location in the selected cluster carry the note User of Cluster with the alias of the other connection.
- If the note is missing, the user matches no location of any other enabled connection. Check the number ranges and attribute values of the locations.
- Users who are assigned to a location in the selected cluster never receive a note.
- If the setting cannot be saved, the signed-in account lacks the permission
ROLE_APP_UPDATE_MULTI_CLUSTER_SETTINGS.