I've been using and developing on Jitsi (high level UI tweaking/baked in
configuration and such: if I do anything interesting I'll contribute it
back) and I've noticed that my sip-communicator.properties file has a
fair few entries of the pattern
My issue is that I am trying to provision to users a given configuration
for STUN/TURN/Multimedia support, and these keys seem to be the relevant
ones. But interestingly they do not seem to be getting wiped. I have
been using both Stock Jitsi and "Smith Chat" (my fork) and they are
running off the same .properties file (as intended: my changes are
I have attached these entries and the bizarre thing is that they refer
to both `Jitsi2.2.4603.9615` (my current version) and `SmithChat1.0.0`,
`SmithChat1.0.2` and `SmithChat1.0.3`. I am only using a single XMPP
account to connect, so shouldn't these replace each other as I move
between versions? And where exactly does the hash come from?
I apologise if this is a known and often-asked question about Jitsi
provisioning, but I've scoured the internet and couldn't find any
details beyond the DISCO specification, which explains what the messages
are. I guess I just need to be aware of how that SHA1 hash is generated
and whether or not it's possible to provision users with the correct
configs. I should be fine composing the body of the XML myself, but I am
unclear on how to make sure my exact config remains the one that is used.
Additionally if this accumulation of CAPS messages is not desired
behaviour, I guess I am reporting it as a possible bug. It seems like
it's just not wiping the old ones, which kind of makes sense.
Thanks as always for your help.
DISCO_entries.properties (16.7 KB)
Smith Electric Vehicles