cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
606
Views
0
Helpful
0
Replies

Persistent Group Chat Location & Federation

Hi!

 

We have multiple CUCM/IM&P (about 30) clusters that cannot be interconnected via Intercluster Peers, just because it's a high number of clusters and IC peering would mean a fully meshed setup and thereof significant increase of bandwidth over satellite connection. 

 

When we began to setup XMPP Federation via Expressway we also discovered that for some clusters we can see the conference aliases under Location in Jabber being listed, for some others they are not. Is there any limitation how many locations will be listed in Jabber under Locations when creating a Chat Room?

Are there any other requirements that needs to be fulfilled to make this work? Documentation states that group chat aliases needs to be setup in DNS, but so far I haven't found any reference for Cisco Jabber how which kind this setup needs to be? Prosody XMPP server documentation says a MUC conference needs to be referenced as _xmpp-server._tcp.conference-2-clusterid.example.com SRV RR, but this doesn't seem to work with Jabber. Setting up a CNAME that points to that IM&P doesn't work either. 

 

Are there any other caveats or tips&tricks that would help in setting this up?

The basic idea would be to have different clusters with their own chat rooms locally, but being able to join the remote rooms on a different cluster. 

Imagine a fleet of cruise ships and a shore side HQ. The crew on board is organised in departments, each department should have their own chat room, and shore side manager for those departments that may also need to join the ship side chats.

Additionally there also would be a shore side chat room for all department heads of all ships. 

0 Replies 0