I have a question regarding CUP Inter-clustering. I have two Presence servers set up, both attached to different Call Manager clusters, and I am trying to integrate Presence status indicators and contacts between the two. Both Call Manager clusters/Presence instances have the same LDAP root in Active Directory. Each Presence server (and Presence client) works independently, but I'm having issues with Presence status indicators / contacts between the two Presence servers. I should be able to accomplish this by using Inter-clustering, right? Or is there another way (or any way) to do this? When I look at the Sync Agent troubleshooter, the only error I see is this:
I only see this on one Presence server, the other one is fine. Is this the cause of my problems? What specifically is happening is that I can add contacts to the CUP client from the same CUP server, but I can't add contacts to the CUP client from the other CUP server. It just shows that it is waiting for approval, and the other client never sees anything. Am I misunderstanding how this should work, or is something broken? If I am misunderstanding, is there a different way I can accomplish this?
The users WERE licensed on the old cluster/presence server. Their License Capabilities have been removed, and they are now licensed on the new cluster/presence server. Here is what Presence Viewer shows for one of the users on the old presence server:
I've exactly same issue as yours , running CUPS version 8.6.2, everythinh is OK with CUPS troubleshooting tools . I've not the same mail ID my user have different UserID and are defined only on one cluster .
IntroductionCUCM Routing RulesDial String implementation PolicyCUCM Routing LogicSIP URI Call Routing Analysis+++ Case Study: 1 ++++++ Case Study: 2 +++Conclusion
Over the last few months, I have had the privilege of working on SI...
Are you getting this error “Installer User Interface Mode Not Supported. The installer cannot run in this UI mode. To specify the interface mode, use the -i command-line option, followed by the UI mode identifier. The value UI mode identifiers...