[cisco-voip] moving jabber client between clusters for support?

[Lelio Fulgenzi]

That’s definitely another way!

From: cisco-voip <cisco-voip-bounces at puck.nether.net> On Behalf Of UC Penguin
Sent: Wednesday, April 28, 2021 10:42 AM
Cc: cisco-voip <cisco-voip at puck.nether.net>
Subject: Re: [cisco-voip] moving jabber client between clusters for support?

CAUTION: This email originated from outside of the University of Guelph. Do not click links or open attachments unless you recognize the sender and know the content is safe. If in doubt, forward suspicious emails to IThelp at uoguelph.ca<mailto:IThelp at uoguelph.ca>

The quick and dirty way is to setup your own DNS server using the same domain as production with SRV records that point to your dev environment.

Switch the DNS servers set on your client PC and toggle back and forth as needed.


On Apr 28, 2021, at 09:28, Lelio Fulgenzi <lelio at uoguelph.ca<mailto:lelio at uoguelph.ca>> wrote:

I may not understand exactly what you’re trying to do, but, I think that will come out during discussion.

I have a production cluster and a development cluster.

To switch between the clusters (and to switch users) I have had to do two things:


  *   Create a new service discovery domain with the appropriate servers listed (including development expressway cluster)
  *   Ensure I use the UDS disabled switch when installing Jabber (this allows for different userIDs to be used)

I know there are a few parameters out there that allow you to push the domain out, but I’m not 100% sure how that works to be honest. Especially because it sounded like they were meant to be done at install time. And still required a domain to be set.

Let the games begin!




From: cisco-voip <cisco-voip-bounces at puck.nether.net<mailto:cisco-voip-bounces at puck.nether.net>> On Behalf Of Nick Barnett
Sent: Wednesday, April 28, 2021 10:16 AM
To: cisco-voip <cisco-voip at puck.nether.net<mailto:cisco-voip at puck.nether.net>>
Subject: [cisco-voip] moving jabber client between clusters for support?

CAUTION: This email originated from outside of the University of Guelph. Do not click links or open attachments unless you recognize the sender and know the content is safe. If in doubt, forward suspicious emails to IThelp at uoguelph.ca<mailto:IThelp at uoguelph.ca>

Up until now, I've just been using CIPC as it does everything I needed it to do... for the most part. Starting this year, I have to jump through way too many hoops to keep using CIPC as it is EOL and our security team doesn't like that.

I'm trying to figure out how to configure my Jabber client to register to a specific non-prod cluster, but I'm not having much luck.

Our prod has 2 clusters with ILS. the internal SRV record for discovery contains all nodes for both clusters. This works just fine in production and relies on the HOME CLUSTER checkbox for the user to be logged into the correct cluster.

My problem comes because I work on non-prod systems as well as prod. The only way I've been able to figure out how to get my jabber to jump to non-prod system is to create a NEW srv record that only contains the nodes of the cluster I want to work with and then change the entry in the bootstrap file.

Is there some way to override discovery and hard code a TFTP or subscriber so that Jabber goes to the intended cluster?  Or, maybe there's a way to do this without a custom SRV record for each non-prod cluster using registry like we could in Cucilync? Some other trick?  I'm hopeful there is some combination of bootstrap settings that I need to figure out, but all of those fields can be a nightmare to get correct without unintentionally breaking something else.

Thanks,
Nick

_______________________________________________
cisco-voip mailing list
cisco-voip at puck.nether.net<mailto:cisco-voip at puck.nether.net>
https://puck.nether.net/mailman/listinfo/cisco-voip
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20210428/0c7b55a6/attachment.htm>