[jitsi-dev] custom configs break standard SIP settings?

Archive
#1

I'm using lib/jitsi-defaults.properties to introduce a small number of
custom settings:

# 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 use 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

When I do that, I can see the properties have been accepted, but I
notice that SIP no longer works reliably and it starts logging
exceptions like this:

Warning: ERROR|IA|Missing resource for key: net.java.sip.communicator.SIP_PREFERRED_CLEAR_PORT |
  at java.util.logging.Logger.log(Unknown Source)
  at java.util.logging.Logger.doLog(Unknown Source)
  at java.util.logging.Logger.log(Unknown Source)
  at java.util.logging.Logger.warning(Unknown Source)
  at net.java.sip.communicator.util.Logger.warn(Unknown Source)
  at net.java.sip.communicator.service.resources.AbstractResourcesService.getSettingsInt(AbstractResourcesService.java:588)
  at net.java.sip.communicator.impl.protocol.sip.SipStackSharing.getPreferredClearPort(SipStackSharing.java:494)
  at net.java.sip.communicator.impl.protocol.sip.SipStackSharing.startListening(SipStackSharing.java:243)
  at net.java.sip.communicator.impl.protocol.sip.SipStackSharing.addSipListener(SipStackSharing.java:162)
  at net.java.sip.communicator.impl.protocol.sip.ProtocolProviderServiceSipImpl.register(ProtocolProviderServiceSipImpl.java:329)
  at net.java.sip.communicator.util.account.LoginManager$RegisterProvider.run(LoginManager.java:426)

net.java.sip.communicator.SIP_PREFERRED_CLEAR_PORT is not one of the properties I am overriding myself.

If I specify custom properties, does that mean I have to repeat all the
SIP-related properties, even those where I am happy with the defaults?
Or is this some unrelated issue?

#2

I'm using lib/jitsi-defaults.properties to introduce a small number of
custom settings:

[some props]

When I do that, I can see the properties have been accepted, but I
notice that SIP no longer works reliably and it starts logging
exceptions like this:

Warning: ERROR|IA|Missing resource for key:
net.java.sip.communicator.SIP_PREFERRED_CLEAR_PORT
[stacktrace]

net.java.sip.communicator.SIP_PREFERRED_CLEAR_PORT is not one of the
properties I am overriding myself.

This is just a too noisy warning that even gets reported in the stable
builds. We should get rid of it.

If I specify custom properties, does that mean I have to repeat all the
SIP-related properties, even those where I am happy with the defaults?

No, you don't need to repeat them.

Or is this some unrelated issue?

It seems unrelated. If your SIP account doesn't work anymore it's either one
of the properties you specifically set or some other (hopefully logged)
error. But it's for sure not related to the exception you posted.

Info

···

On 2014-07-30 19:41, Daniel Pocock wrote: