Jabber Persistent Chat across multiple clusters ??
I am building a sandbox to test persistent chat for my region. I see that a postgres db is needed per node however I don't see details on what that allots me. Does that mean that only the users assigned to that cluster can access that node(s) persistent chat rooms? Or does that mean that I can house a persistent chat room on that cluster and users from all regional clusters can then join them?
That's an interesting question. Since no one has answered this in nearly two weeks, I'll take a generic XMPP stab; however, be aware I haven't tested this specifically with Jabber/IM&P across a multi-cluster environment.
The generic answer is that each node has a text conferencing server alias which is used as the right-hand-side of an XMPP URI unique to each chat room. You can see this under IM&P Administration > Messaging > Group Chat Server Alias Mapping. For example, the chat room may be firstname.lastname@example.org. Just as a user has an XMPP URI, so does an ad-hoc or persistent chat room. This is controlled by the Cisco UP XCP Text Conference Manager service. So, each node needs a PostgreSQL database to cache the relevant details about the rooms it is hosting. Users homed on other nodes simply interact with the URI and the XCP fabric takes care of routing the message.
That leaves the question: what about other clusters (inter-cluster peered or not). Well, when doing inter-domain federation, it states that you need SRV records for the Chat Server Aliases. But there are two other scenarios that I don't have a ready answer for:
multiple clusters with inter-cluster peers.
multiple clusters in the same domain relying only on the XMPP fabric.
I actually have a setup in my lab with a 10.5(2) and an 11.0 system with inter-cluster between IM&P and ILS/GDPR between CUCM, and I can access the persistent chat rooms configured on 10.5(2) using clients registered to 11.x
I just wanted to circle back to this topic. I have been running 5 clusters with only one node in one cluster hosting all of my persistent chat rooms successfully. I understand from the documentation that each node wants to host rooms but it made zero sense for us to present rooms this way. We didn't want to have to 'balance' hosted rooms as we have one chat room admin that controls room creation for all 5 regions. We use one Postgres db for all of our hosted rooms. Intercluster takes care of any communications from other regions. Granted this is one point of failure but there is nothing showing us how to cluster the database if one of the hosting nodes fail anyway. Its not in the CUPs functionality to cluster dbs across nodes so we went forward with one db/one node for all.
Even in the one cluster that hosts persistent chat our PUB is connected to the Postgres db and the SUB is not connected to any db (left blank).
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...