We have a multi-cluster environment with multiple CUP servers which are all configured to support Inter-cluster presence/messaging between each other. Whenever a user is migrated from one cluster to another, that user's presence status is shown as "offline" in Jabber for all Jabber users who had the user in their contact list. If the migrated user is not in the contact list, the presence status works just fine. The only solution that we were able to find is to instruct users to remove a "stale" contact of a migrated user from their contact lists and re-add it again. While this workaround is acceptable if we talk about a few isolated cases of migrated users, consider the following scenario:
- A multi-national company with thousands of employees and multiple CUCM clusters have deployed Jabber IM&P for all of their users under Cisco's "Jabber for Everyone" offer by assigning them to a single CUP server on single CUCM cluster.
- After some time and as various CUCM clusters become upgraded to the latest CUCM version and get their own CUP server alongside to support full Phone Services in Jabber, Jabber users are "migrated" from the centralized CUP server to their local CUP server (i.e. the Home Cluster option is disabled for users in the original CUCM cluster, enabled in the new CUCM cluster, and contacts are migrated from original CUP server to the new CUP server).
- All users who have been migrated to the new CUP server now appear as "Offline" to Jabber users who remained on the central CUP server and had those users in their contact lists. Removing the contact from the contact list and looking up and re-adding the same contact back to the contact list resolves the issue, but it is a manual process.
Has anyone dealt with this issue and if so, is there a fix for "stale" records in the contact list (other than resetting Jabber clients on users' workstations)?
Note about versions:
CUCM version 10.5.2 or 11.0
CUP version 10.5.2 or 11.0
Version of Jabber for Windows clients on users' workstations: 10.6(5) or higher
