[jitsi-dev] compiling with different properties


#1

I've tried rebuilding Jitsi with a modified defaults.properties

Here are the properties I tried to change:

# disable the video codecs so calls will be audio only by default:
net.java.sip.communicator.impl.neomedia.codec.EncodingConfiguration.H264/90000=0
net.java.sip.communicator.impl.neomedia.codec.EncodingConfiguration.H263-1998//90000=0
net.java.sip.communicator.impl.neomedia.codec.EncodingConfiguration.VP8/90000=0
# disable SSLv2 and v3, just TLSv1
gov.nist.javax.sip.TLS_CLIENT_PROTOCOLS=TLSv1
# disable the Windows-ROOT trust store, use Java by default:
net.java.sip.communicator.service.cert.truststore.type=meta:default

I checked that the resulting sc-bundles/defaultresources.jar contains my
changes

However, when I run Jitsi for the first time (after moving ~/.jitsi out
of the way) it creates a new profile without my changes

Is defaults.properties actually used or is there some other way that I
should set things like this if I don't want to use a provisioning server?


#2

Defaults.properties in defaultresources.jar only supports the settings that
are already configured in there (and is therefore deprecated, we just
haven't found the time to replace it entirely). If you want to configure an
arbitrary property, use jitsi-defaults.properties (or
jitsi-default-overrides.properties) in the lib-directory.

(Btw: if you prefix a property in one of those files with an asterisk (*), a
user cannot override it)

Ingo

···

On 2014-07-23 22:52, Daniel Pocock wrote:

I've tried rebuilding Jitsi with a modified defaults.properties

Here are the properties I tried to change:

# disable the video codecs so calls will be audio only by default:
net.java.sip.communicator.impl.neomedia.codec.EncodingConfiguration.H264/9
000 0=0
net.java.sip.communicator.impl.neomedia.codec.EncodingConfiguration.H263-
1998//90000=0
net.java.sip.communicator.impl.neomedia.codec.EncodingConfiguration.VP8/90
000 =0 # disable SSLv2 and v3, just TLSv1
gov.nist.javax.sip.TLS_CLIENT_PROTOCOLS=TLSv1 # disable the Windows-ROOT
trust store, use Java by default:
net.java.sip.communicator.service.cert.truststore.type=meta:default

I checked that the resulting sc-bundles/defaultresources.jar contains my
changes

However, when I run Jitsi for the first time (after moving ~/.jitsi out
of the way) it creates a new profile without my changes

Is defaults.properties actually used or is there some other way that I
should set things like this if I don't want to use a provisioning server?


#3

Great, thanks for that feedback, I'll try that

Can you comment on how I should create SIP account configurations from
my own code, on the client side, without a provisioning server?

E.g. can I create a Properties object with the settings and send it into
the Jitsi config somehow? Would you be able to suggest any examples of
code that does something like that?

···

On 23/07/14 18:10, Ingo Bauersachs wrote:

On 2014-07-23 22:52, Daniel Pocock wrote:

I've tried rebuilding Jitsi with a modified defaults.properties

Here are the properties I tried to change:

# disable the video codecs so calls will be audio only by default:
net.java.sip.communicator.impl.neomedia.codec.EncodingConfiguration.H264/9
000 0=0
net.java.sip.communicator.impl.neomedia.codec.EncodingConfiguration.H263-
1998//90000=0
net.java.sip.communicator.impl.neomedia.codec.EncodingConfiguration.VP8/90
000 =0 # disable SSLv2 and v3, just TLSv1
gov.nist.javax.sip.TLS_CLIENT_PROTOCOLS=TLSv1 # disable the Windows-ROOT
trust store, use Java by default:
net.java.sip.communicator.service.cert.truststore.type=meta:default

I checked that the resulting sc-bundles/defaultresources.jar contains my
changes

However, when I run Jitsi for the first time (after moving ~/.jitsi out
of the way) it creates a new profile without my changes

Is defaults.properties actually used or is there some other way that I
should set things like this if I don't want to use a provisioning server?

Defaults.properties in defaultresources.jar only supports the settings that
are already configured in there (and is therefore deprecated, we just
haven't found the time to replace it entirely). If you want to configure an
arbitrary property, use jitsi-defaults.properties (or
jitsi-default-overrides.properties) in the lib-directory.

(Btw: if you prefix a property in one of those files with an asterisk (*), a
user cannot override it)


#4

I've never done this completely without provisioning.

Quick ideas:
- Set the config as system properties. If I remember correctly, the ConfigService first checks if a property is available as a system (JVM) property. This doesn't work to set a property to empty/null though.

- Use a custom ConfigService implementation that relies on a datasource from your other application

- use a custom provisioning plugin. After all the provisioning plugin is just a bundle that loads early in the startup process and transfers whatever it gets from the webserver to the config service.

Freundliche Grüsse,
Ingo Bauersachs

-- sent from my mobile

···

Le 24.07.2014 à 00:03, "Daniel Pocock" <daniel@pocock.pro> a écrit :

On 23/07/14 18:10, Ingo Bauersachs wrote:

On 2014-07-23 22:52, Daniel Pocock wrote:

I've tried rebuilding Jitsi with a modified defaults.properties

Here are the properties I tried to change:

# disable the video codecs so calls will be audio only by default:
net.java.sip.communicator.impl.neomedia.codec.EncodingConfiguration.H264/9
000 0=0
net.java.sip.communicator.impl.neomedia.codec.EncodingConfiguration.H263-
1998//90000=0
net.java.sip.communicator.impl.neomedia.codec.EncodingConfiguration.VP8/90
000 =0 # disable SSLv2 and v3, just TLSv1
gov.nist.javax.sip.TLS_CLIENT_PROTOCOLS=TLSv1 # disable the Windows-ROOT
trust store, use Java by default:
net.java.sip.communicator.service.cert.truststore.type=meta:default

I checked that the resulting sc-bundles/defaultresources.jar contains my
changes

However, when I run Jitsi for the first time (after moving ~/.jitsi out
of the way) it creates a new profile without my changes

Is defaults.properties actually used or is there some other way that I
should set things like this if I don't want to use a provisioning server?

Defaults.properties in defaultresources.jar only supports the settings that
are already configured in there (and is therefore deprecated, we just
haven't found the time to replace it entirely). If you want to configure an
arbitrary property, use jitsi-defaults.properties (or
jitsi-default-overrides.properties) in the lib-directory.

(Btw: if you prefix a property in one of those files with an asterisk (*), a
user cannot override it)

Great, thanks for that feedback, I'll try that

Can you comment on how I should create SIP account configurations from
my own code, on the client side, without a provisioning server?

E.g. can I create a Properties object with the settings and send it into
the Jitsi config somehow? Would you be able to suggest any examples of
code that does something like that?

_______________________________________________
dev mailing list
dev@jitsi.org
Unsubscribe instructions and other list options:
http://lists.jitsi.org/mailman/listinfo/dev