Nice!
Sent from my iPhone
On Apr 28, 2021, at 6:04 PM, Michael Nickolich
wrote:
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
Nick,
This is what I have done to register between test and prod clusters for
J4W. I reset my Jabber client and then kill off that process.
Browse to C:\ProgramData\Cisco Systems\Cisco Jabber. Use Notepad++ or some
other editor.
Example Bootstrap
You can modify the file, but each position is
A different user is another good idea.
Be careful with the bootstrap file though. You will need
upnDiscoveryEnabled: FALSE
and you can only change this by deleting the directories (I think)
C:\ProgramData\Cisco Systems\Cisco Jabber
or by re-installing with a CLEAR=1 and the
Creating a uniquely named user account marked as home cluster on each cluster
would appear to be the simplest. This assumes you have ILS setup between all
clusters and you don’t have a large number of clusters that would chew through
licensing.
> On Apr 28, 2021, at 11:03, Nick Barnett wrote:
Thanks, let me try and clarify a bit.
We have a support team that needs to log their Jabber device into multiple
clusters. Using the "home cluster" setting is too cumbersome and requires CUCM
access. Our testers do not have CUCM access, but they can modify their own
local config files.
Hello Reto,
This looks like every RTP packet is duplicated.
This could be an artifact of how the packet capture was taken. Was a SPAN or
similar feature used that might duplicate packets? Are the packets truly
duplicates? Sometimes this IP ID field is useful
Otherwise, this could be a
That’s definitely another way!
From: cisco-voip On Behalf Of UC Penguin
Sent: Wednesday, April 28, 2021 10:42 AM
Cc: cisco-voip
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
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 wrote:
>
>
> I may
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
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
10 matches
Mail list logo
