[jitsi-users] OSS jabber server for Jitsi


#1

Hi all

I find Jitsi a really promising client. Thanks for the effort.

But I'd like to know if there are any open-source jabber servers
supporting Jingle Nodes in a way compatible with Jitsi?
I've tried OpenFire with JabberNodes plugin with no luck. Moreover
plugin seems to be abandoned.

BR,
Denis


#2

Hi Denis,

But I'd like to know if there are any open-source jabber servers
supporting Jingle Nodes in a way compatible with Jitsi?
I've tried OpenFire with JabberNodes plugin with no luck. Moreover
plugin seems to be abandoned.

I'd be interested in that too! Whether or not abandoned, i've tried to
get JingleNodes to work together with ejabberd in Debian/Stable, which
turned out as a problem since JingleNodes needed a newer erlang version
than ejabberd, thus i couldn't upgrade erlang on my stable server.

The temporary solution i've come up now is to use the "reTurn" server
from the resiprocate project and manually enter a '[X]Turn Capable'
STUN-Server in Jitsi. While this works, a JingleNodes solution would be
much more appreciated from me too!

Also, i've got a problem with Jitsi/SIP ... it doesn't seem to support
TURN?!? But this is probably a different, new topic on this ML. Will
write soon ;P.

Regards
- Dario

···

On 08/06/2012 02:03 PM, Denis Golovan wrote:


#3

Hi Dario

Thanks for the quick answer!

I'd be interested in that too! Whether or not abandoned, i've tried to
get JingleNodes to work together with ejabberd in Debian/Stable, which
turned out as a problem since JingleNodes needed a newer erlang version
than ejabberd, thus i couldn't upgrade erlang on my stable server.

Yeap. That beast looks to be able to support everything, but not
everybody can make it do that :slight_smile:

The temporary solution i've come up now is to use the "reTurn" server
from the resiprocate project and manually enter a '[X]Turn Capable'
STUN-Server in Jitsi. While this works, a JingleNodes solution would be
much more appreciated from me too!

Well. That's a really interesting information. I'll try to use that TURN server.

Also, i've got a problem with Jitsi/SIP ... it doesn't seem to support
TURN?!? But this is probably a different, new topic on this ML. Will
write soon ;P.

SIP. So much trouble in one small word :slight_smile:

@Developers
Is it possible to promise some kind of a bounty for someone willing to
implement a decent plugin for OpenFire, Prosody or any OSS jabber
server (server for human beings). I am willing to offer some bucks for
the job. I reckon some other folks will support this as well.

BR,
Denis


#4

I forgot to comment on this one:

Also, i've got a problem with Jitsi/SIP ... it doesn't seem to support
TURN?!? But this is probably a different, new topic on this ML. Will
write soon ;P.

We do support TURN. By default we will try to discover the default
TURN server for the domain of the server you are using, and then we
will try to login using the credentials for your XMPP server. You can
add other servers and credentials in the account wizard.

Hope this helps,
Emil
.

···

On Mon, Aug 6, 2012 at 2:41 PM, Dario Ernst <daddel9@kanojo.de> wrote:


#5

Hey folks,

We've been using Openfire's JingleNodes plugin on a number of
occasions, including jit.si, and we never had any issues with it.

I wouldn't say that it's abandoned. It's just that it does what it needs to.

Hope this helps,
Emil

···

On Mon, Aug 6, 2012 at 2:55 PM, Denis Golovan <denis.golovan@gmail.com> wrote:

Hi Dario

Thanks for the quick answer!

I'd be interested in that too! Whether or not abandoned, i've tried to
get JingleNodes to work together with ejabberd in Debian/Stable, which
turned out as a problem since JingleNodes needed a newer erlang version
than ejabberd, thus i couldn't upgrade erlang on my stable server.

Yeap. That beast looks to be able to support everything, but not
everybody can make it do that :slight_smile:

The temporary solution i've come up now is to use the "reTurn" server
from the resiprocate project and manually enter a '[X]Turn Capable'
STUN-Server in Jitsi. While this works, a JingleNodes solution would be
much more appreciated from me too!

Well. That's a really interesting information. I'll try to use that TURN server.

Also, i've got a problem with Jitsi/SIP ... it doesn't seem to support
TURN?!? But this is probably a different, new topic on this ML. Will
write soon ;P.

SIP. So much trouble in one small word :slight_smile:

@Developers
Is it possible to promise some kind of a bounty for someone willing to
implement a decent plugin for OpenFire, Prosody or any OSS jabber
server (server for human beings). I am willing to offer some bucks for
the job. I reckon some other folks will support this as well.

BR,
Denis

--
Emil Ivov, Ph.D. 67000 Strasbourg,
Project Lead France
Jitsi
emcho@jitsi.org PHONE: +33.1.77.62.43.30
http://jitsi.org FAX: +33.1.77.62.47.31


#6

Hi Emil

···

2012/8/6 Emil Ivov <emcho@jitsi.org>:

Hey folks,

We've been using Openfire's JingleNodes plugin on a number of
occasions, including jit.si, and we never had any issues with it.

I wouldn't say that it's abandoned. It's just that it does what it needs to.

Could you provide details for OpenFire Jingle nodes plug-in and Jitsi
settings? I assume you had used Jabber account in Jitsi, right?
I've tried various settings, but with no success.

The problem is that JingleNodes plugin documentation lacks those very details.

BR,
Denis


#7

Hey Denis,

···

On Tue, Aug 7, 2012 at 10:13 AM, Denis Golovan <denis.golovan@gmail.com> wrote:

Hi Emil

2012/8/6 Emil Ivov <emcho@jitsi.org>:

Hey folks,

We've been using Openfire's JingleNodes plugin on a number of
occasions, including jit.si, and we never had any issues with it.

I wouldn't say that it's abandoned. It's just that it does what it needs to.

Could you provide details for OpenFire Jingle nodes plug-in and Jitsi
settings? I assume you had used Jabber account in Jitsi, right?
I've tried various settings, but with no success.

The problem is that JingleNodes plugin documentation lacks those very details.

Well, as long as the JingleNodes plugin on OpenFire is enabled then it
should pretty much "just work". What are you experiencing? Can you try
with the latest nightly?

Cheers,
Emil


#8

Hello Emil,

thank you for the reply for my email and sorry for disturbing - I
mistakenly sent it to you directly, not to the list.

So currently after a week of shaman dances I somehow managed things to
work. But I'm still in doubt what was the reason for previous faults.
Probably the reason was a bug within Jitsi settings which I will
explain below.

Here is what I did to make it work:

1) Freshly installed OpenFire server with Jingle Nodes plugin activated
(on the Jingle Nodes settings tab the IP address was verified and has a
green checkmark).

2) Activated my own OpenFire-STUN server with additional IP address (as
required).

3) Activated Media Proxy on OpenFire (though not sure if it was
required - it is not in use when a call is in progress).

4) In Jitsi settings I disabled all other accounts (I suppose it is
important that all XMPP-type accounts in Jitsi have the same
ICE/STUN/Jingle settings, probably that was another reason for previous
faults).

5) In Jitsi XMPP account configuration -> ICE Configuration tab, I
activated only the following settings (All other checkboxes are OFF):

- Use ICE
- Use Jingle Nodes
- Auto discover Jingle Nodes relays

For Additional STUN servers I added IP address of my OpenFire-STUN
server.

The same settings applied on all endpoints. I'm testing voice between
different Windows and MacOS servers and now it works well. On the
OpenFire server console in the Jingle Nodes tab I can see a number of
active sessions and all traffic properly relays through my OpenFire
server.

Now for the bugs.

While playing with Jitsi settings I found another bug which prevented
JingleNodes from working:

while experimenting with different settings I put my server IP address
into Additional Jingle Nodes section. Probably this parameter should
have another syntax, but Jitsi failed to establish correct Jingle Nodes
session all the time after that. The problem is that I can not delete
this wrong entry from the GUI - Jitsi shows that it is deleted, but
actually it is not. After restart of Jitsi this setting appears there
again. I had to manually remove the parameter from
sip-communicator.properties file.

This bug is confirmed for both Windows and Mac versions of Jitsi.

But although it is working now, I still have little understanding of
the underlying technology and requirements.

Emil, would you be so kind please to comment my investigations and also
answer on the following questions (from my previous email):

1) Jitsi XMPP account configuration, ICE Configuration tab:

a) should I really have "Use ICE" and "Use Google's Jingle/ICE"
checkboxes set ON? Is Jinglenodes functionality somehow related to ICE?

b) the same for STUN/TURN settings - should it all be enabled (i.e. is
it required for Jinglenodes to work)?

c) do I have to manually add my own OpenFire-STUN server there?

2) Additional Jingle Nodes setting:

a) do I have to manually add my OpenFire server there or it should find
and discover it automagically?

b) does it rely on some DNS SRV records for the domain or uses current
server connection and XMPP protocol for Auto discovery of jingle nodes?

c) last very important question - if I want to manually add Additional
Jingle Nodes (i.e. my OpenFire server), should I put there just a
server IP? The field asks for "JID Address" which supposed to be
something@myserver.org, is it? I have no idea what would be the JID of
the Jingle Nodes plugin on my Open Fire server.

Thank you very much in advance,
in the lack of JN documentation your comments would be highly
appreciated!

Best Regards,
Dmitry
.


#9

Hey Dmitry,

Hello Emil,

thank you for the reply for my email and sorry for disturbing - I
mistakenly sent it to you directly, not to the list.

No problem. Thanks for resending it here.

So currently after a week of shaman dances I somehow managed things to
work. But I'm still in doubt what was the reason for previous faults.
Probably the reason was a bug within Jitsi settings which I will
explain below.

Here is what I did to make it work:

1) Freshly installed OpenFire server with Jingle Nodes plugin activated
(on the Jingle Nodes settings tab the IP address was verified and has a
green checkmark).

Right. You need to watch out for that one. Sometimes, on multihomed
machines or IPv4/IPv6 double stacks you'd get the wrong address in
there.

2) Activated my own OpenFire-STUN server with additional IP address (as
required).

Not necessary. I am not sure we even use it the STUN server we learn
from XMPP. (Would need to check though)

3) Activated Media Proxy on OpenFire (though not sure if it was
required - it is not in use when a call is in progress).

I wouldn't do that. I think it may only work on raw udp, but it can
only screw up ICE so best leave it off.

4) In Jitsi settings I disabled all other accounts (I suppose it is
important that all XMPP-type accounts in Jitsi have the same
ICE/STUN/Jingle settings, probably that was another reason for previous
faults).

This shouldn't be a problem. Accounts and their ICE settings are
completely independent.

5) In Jitsi XMPP account configuration -> ICE Configuration tab, I
activated only the following settings (All other checkboxes are OFF):

- Use ICE
- Use Jingle Nodes
- Auto discover Jingle Nodes relays

For Additional STUN servers I added IP address of my OpenFire-STUN
server.

Ah OK. I see now. We use stun.jitsi.net if you don't set one.

Either way, that would only matter for finding a direct route, other
than Jingle Nodes.

The same settings applied on all endpoints. I'm testing voice between
different Windows and MacOS servers and now it works well. On the
OpenFire server console in the Jingle Nodes tab I can see a number of
active sessions and all traffic properly relays through my OpenFire
server.

Through the JingleNodes plugin?

Now for the bugs.

While playing with Jitsi settings I found another bug which prevented
JingleNodes from working:

while experimenting with different settings I put my server IP address
into Additional Jingle Nodes section. Probably this parameter should
have another syntax, but Jitsi failed to establish correct Jingle Nodes
session all the time after that. The problem is that I can not delete
this wrong entry from the GUI - Jitsi shows that it is deleted, but
actually it is not. After restart of Jitsi this setting appears there
again. I had to manually remove the parameter from
sip-communicator.properties file.

This bug is confirmed for both Windows and Mac versions of Jitsi.

Oh. Could you please open an issue for that?

But although it is working now, I still have little understanding of
the underlying technology and requirements.

Emil, would you be so kind please to comment my investigations and also
answer on the following questions (from my previous email):

1) Jitsi XMPP account configuration, ICE Configuration tab:

a) should I really have "Use ICE"

Yes!

and "Use Google's Jingle/ICE"

No, not necessarily. Unless you want to call Google Talk users.

checkboxes set ON? Is Jinglenodes functionality somehow related to ICE?

It is. ICE is about gathering all your potentially usable addresses
(Candidates), sending them to your contact, retrieving theirs and
trying to check every one of them before settling on one that you have
confirmed to work.

This allows you to only use relay technologies, such as JingleNodes,
only in cases when there's no other way of communicating.

b) the same for STUN/TURN settings - should it all be enabled (i.e. is
it required for Jinglenodes to work)?

TURN is pretty much the same as Jingle nodes. It just has a different
protocol for allocating relay channels.

STUN is different. It gives you a possibility to connect to people
that are outside your network without using a relay. It wouldn't work
with all NATs though, which is why you need ICE. With it, you can fall
back to TURN or Jingle nodes if the addresses your learned from your
STUN server did not work.

c) do I have to manually add my own OpenFire-STUN server there?

Not necessarily. You can just use Jitsi's (i.e. if you don't uncheck
the "Use Jitsi's Stun server" box)

2) Additional Jingle Nodes setting:

a) do I have to manually add my OpenFire server there or it should find
and discover it automagically?

It will be discovered automatically. You only need to add relays there
if your server doesn't have one, or in case you want to have an extra
option.

b) does it rely on some DNS SRV records for the domain or uses current
server connection and XMPP protocol for Auto discovery of jingle nodes?

We learn about JingleNode relays from the XMPP server. No SRVs are
involved their. We do however use DNS SRV when discovering domain STUN
and TURN servers. That's what the corresponding checkbox is about.

c) last very important question - if I want to manually add Additional
Jingle Nodes (i.e. my OpenFire server), should I put there just a
server IP? The field asks for "JID Address" which supposed to be
something@myserver.org, is it? I have no idea what would be the JID of
the Jingle Nodes plugin on my Open Fire server.

It should be the name of the component that your Jingle Nodes relay is
registered with. I think OpenFire's plugin uses "relay" by default,
which would give you "relay.example.com" for your server. We have
"relay.jit.si" for the jit.si service.

Note that "relay" is not an actual domain name. It's just an XMPP
component name.

Thank you very much in advance,
in the lack of JN documentation your comments would be highly
appreciated!

Well, hope it helps. Please let me know if you have other questions.

Cheers,
Emil

···

On Thu, Aug 9, 2012 at 3:55 PM, <dmit2k@gmail.com> wrote:


#10

Hi guys

Sorry for late answer.
It's summer now :slight_smile:

1) Freshly installed OpenFire server with Jingle Nodes plugin activated
(on the Jingle Nodes settings tab the IP address was verified and has a
green checkmark).

I am a multi-homed server, so I cannot make plugin show green checkmark though.
I assume Override IP option with correct ip entered will do the trick. Right?

Not necessary. I am not sure we even use it the STUN server we learn
from XMPP. (Would need to check though)

Could you investigate this?
Even though I have multi-homed internet server, I have only one white
ip present.
Others internet interfaces are routed through other servers. I guess I
cannot use STUN in this situation.
Is it correct? It looks like STUN needs two public/white ips present.

Unfortunately, for some reason windows version of Jitsi (both latest
versions 1.0 and 1.1) do not see my partner's audio device.
Other applications do not have any troubles. Some Java bug here?
So I cannot test audio calls properly for now.

@dmit2k@gmail.com
Please let me know if it is possible to test my server configuration
with your help.
And yes I am Russian, and I speak Russian :slight_smile:
And thanks for letting me know about results.

BR,
Denis


#11

(it seems like my last mail never arived so im resending it now)
I am on Ubuntu 12.04 running jitsi 1.1, updated to the newest version.
jitsi fails to detect my webcam while other applications like cheese or pidgin do detect it properly.
I am also able to do video-calls in pidgin.
Whenever I open the Video-settings it says "<No Device>" (it actualy says <Kein Ger�t> but that's German)

The webcam is called Trust Webcam Live WB-1300N.
there is also a support-URL: http://www.trust.com./15278

and some info, you said too much is better then too less:
lsusb:
Bus 006 Device 004: ID 145f:013a Trust

v4l-info:

### v4l2 device info [/dev/video0] ###
general info
VIDIOC_QUERYCAP
driver : "pac207"
card : " "
bus_info : "usb-0000:00:1a.2-1"
version : 3.2.21
capabilities : 0x5000001 [VIDEO_CAPTURE,READWRITE,STREAMING]

standards

inputs
VIDIOC_ENUMINPUT(0)
index : 0
name : "pac207"
type : CAMERA
audioset : 0
tuner : 0
std : 0x0 []
status : 0x0 []

video capture
VIDIOC_ENUM_FMT(0,VIDEO_CAPTURE)
index : 0
type : VIDEO_CAPTURE
flags : 0
description : "P207"
pixelformat : 0x37303250 [P207]
VIDIOC_G_FMT(VIDEO_CAPTURE)
type : VIDEO_CAPTURE
fmt.pix.width : 352
fmt.pix.height : 288
fmt.pix.pixelformat : 0x37303250 [P207]
fmt.pix.field : NONE
fmt.pix.bytesperline : 352
fmt.pix.sizeimage : 101952
fmt.pix.colorspace : SRGB
fmt.pix.priv : 0

controls
VIDIOC_QUERYCTRL(BASE+0)
id : 9963776
type : INTEGER
name : "Brightness"
minimum : 0
maximum : 255
step : 1
default_value : 46
flags : 0
VIDIOC_QUERYCTRL(BASE+17)
id : 9963793
type : INTEGER
name : "Exposure"
minimum : 3
maximum : 26
step : 1
default_value : 5
flags : 0
VIDIOC_QUERYCTRL(BASE+18)
id : 9963794
type : BOOLEAN
name : "Auto Gain"
minimum : 0
maximum : 1
step : 1
default_value : 1
flags : 0
VIDIOC_QUERYCTRL(BASE+19)
id : 9963795
type : INTEGER
name : "Gain"
minimum : 0
maximum : 31
step : 1
default_value : 9
flags : 0

jitsi's logfile:13:42:23.324 INFO: plugin.defaultresourcepack.DefaultResourcePackActivator.start().93 Default resources ... [REGISTERED]
13:42:23.403 INFO: org.jitsi.impl.configuration.ConfigurationServiceImpl.info() java.runtime.name=OpenJDK Runtime Environment
13:42:23.404 INFO: org.jitsi.impl.configuration.ConfigurationServiceImpl.info() felix.config.properties=file:/usr/lib/jitsi/lib/felix.client.run.properties
13:42:23.404 INFO: org.jitsi.impl.configuration.ConfigurationServiceImpl.info() sun.boot.library.path=/usr/lib/jvm/java-6-openjdk-amd64/jre/lib/amd64
13:42:23.404 INFO: org.jitsi.impl.configuration.ConfigurationServiceImpl.info() java.vm.version=20.0-b12
13:42:23.404 INFO: org.jitsi.impl.configuration.ConfigurationServiceImpl.info() java.vm.vendor=Sun Microsystems Inc.
13:42:23.404 INFO: org.jitsi.impl.configuration.ConfigurationServiceImpl.info() java.vendor.url=http://java.sun.com/
13:42:23.405 INFO: org.jitsi.impl.configuration.ConfigurationServiceImpl.info() path.separator=:
13:42:23.405 INFO: org.jitsi.impl.configuration.ConfigurationServiceImpl.info() java.util.logging.config.file=/usr/lib/jitsi/lib/logging.properties
13:42:23.405 INFO: org.jitsi.impl.configuration.ConfigurationServiceImpl.info() java.vm.name=OpenJDK 64-Bit Server VM
13:42:23.405 INFO: org.jitsi.impl.configuration.ConfigurationServiceImpl.info() file.encoding.pkg=sun.io
13:42:23.405 INFO: org.jitsi.impl.configuration.ConfigurationServiceImpl.info() sun.java.launcher=SUN_STANDARD
13:42:23.406 INFO: org.jitsi.impl.configuration.ConfigurationServiceImpl.info() user.country=DE
13:42:23.406 INFO: org.jitsi.impl.configuration.ConfigurationServiceImpl.info() sun.os.patch.level=unknown
13:42:23.406 INFO: org.jitsi.impl.configuration.ConfigurationServiceImpl.info() java.vm.specification.name=Java Virtual Machine Specification
13:42:23.406 INFO: org.jitsi.impl.configuration.ConfigurationServiceImpl.info() user.dir=/usr/lib/jitsi
13:42:23.406 INFO: org.jitsi.impl.configuration.ConfigurationServiceImpl.info() java.runtime.version=1.6.0_24-b24
13:42:23.406 INFO: org.jitsi.impl.configuration.ConfigurationServiceImpl.info() java.awt.graphicsenv=sun.awt.X11GraphicsEnvironment
13:42:23.407 INFO: org.jitsi.impl.configuration.ConfigurationServiceImpl.info() java.endorsed.dirs=/usr/lib/jvm/java-6-openjdk-amd64/jre/lib/endorsed
13:42:23.407 INFO: org.jitsi.impl.configuration.ConfigurationServiceImpl.info() os.arch=amd64
13:42:23.407 INFO: org.jitsi.impl.configuration.ConfigurationServiceImpl.info() java.io.tmpdir=/tmp
13:42:23.407 INFO: org.jitsi.impl.configuration.ConfigurationServiceImpl.info() line.separator=

13:42:23.407 INFO: org.jitsi.impl.configuration.ConfigurationServiceImpl.info() java.vm.specification.vendor=Sun Microsystems Inc.
13:42:23.408 INFO: org.jitsi.impl.configuration.ConfigurationServiceImpl.info() os.name=Linux
13:42:23.408 INFO: org.jitsi.impl.configuration.ConfigurationServiceImpl.info() sun.jnu.encoding=UTF-8
13:42:23.408 INFO: org.jitsi.impl.configuration.ConfigurationServiceImpl.info() java.library.path=/usr/lib/jvm/java-6-openjdk-amd64/jre/lib/amd64/server:/usr/lib/jvm/java-6-openjdk-amd64/jre/lib/amd64:/usr/lib/jvm/java-6-openjdk-amd64/jre/../lib/amd64::/usr/lib/jitsi/lib/native:/usr/java/packages/lib/amd64:/usr/lib/x86_64-linux-gnu/jni:/lib/x86_64-linux-gnu:/usr/lib/x86_64-linux-gnu:/usr/lib/jni:/lib:/usr/lib

13:42:23.408 INFO: org.jitsi.impl.configuration.ConfigurationServiceImpl.info() java.specification.name=Java Platform API Specification
13:42:23.408 INFO: org.jitsi.impl.configuration.ConfigurationServiceImpl.info() java.class.version=50.0
13:42:23.409 INFO: org.jitsi.impl.configuration.ConfigurationServiceImpl.info() org.jitsi.service.audionotifier.AudioNotifierService=org.jitsi.impl.neomedia.notify.AudioNotifierServiceImpl
13:42:23.409 INFO: org.jitsi.impl.configuration.ConfigurationServiceImpl.info() sun.management.compiler=HotSpot 64-Bit Tiered Compilers
13:42:23.409 INFO: org.jitsi.impl.configuration.ConfigurationServiceImpl.info() os.version=3.2.0-27-generic
13:42:23.409 INFO: org.jitsi.impl.configuration.ConfigurationServiceImpl.info() user.home=/home/user
13:42:23.409 INFO: org.jitsi.impl.configuration.ConfigurationServiceImpl.info() user.timezone=Europe/Berlin
13:42:23.410 INFO: org.jitsi.impl.configuration.ConfigurationServiceImpl.info() java.awt.printerjob=sun.print.PSPrinterJob
13:42:23.410 INFO: org.jitsi.impl.configuration.ConfigurationServiceImpl.info() file.encoding=UTF-8
13:42:23.410 INFO: org.jitsi.impl.configuration.ConfigurationServiceImpl.info() java.specification.version=1.6
13:42:23.410 INFO: org.jitsi.impl.configuration.ConfigurationServiceImpl.info() jna.library.path=/usr/lib/jitsi/lib/native
13:42:23.410 INFO: org.jitsi.impl.configuration.ConfigurationServiceImpl.info() java.class.path=/usr/lib/jitsi/lib/jdic_stub.jar:/usr/lib/jitsi/lib/jdic-all.jar:/usr/lib/jitsi/lib/felix.jar:/usr/lib/jitsi/lib/bcprovider.jar:/usr/lib/jitsi/sc-bundles/sc-launcher.jar:/usr/lib/jitsi/sc-bundles/util.jar
13:42:23.410 INFO: org.jitsi.impl.configuration.ConfigurationServiceImpl.info() user.name=user
13:42:23.411 INFO: org.jitsi.impl.configuration.ConfigurationServiceImpl.info() java.vm.specification.version=1.0
13:42:23.411 INFO: org.jitsi.impl.configuration.ConfigurationServiceImpl.info() sun.java.command=net.java.sip.communicator.launcher.SIPCommunicator
13:42:23.411 INFO: org.jitsi.impl.configuration.ConfigurationServiceImpl.info() java.home=/usr/lib/jvm/java-6-openjdk-amd64/jre
13:42:23.411 INFO: org.jitsi.impl.configuration.ConfigurationServiceImpl.info() sun.arch.data.model=64
13:42:23.411 INFO: org.jitsi.impl.configuration.ConfigurationServiceImpl.info() user.language=de
13:42:23.412 INFO: org.jitsi.impl.configuration.ConfigurationServiceImpl.info() java.specification.vendor=Sun Microsystems Inc.
13:42:23.412 INFO: org.jitsi.impl.configuration.ConfigurationServiceImpl.info() java.vm.info=mixed mode
13:42:23.412 INFO: org.jitsi.impl.configuration.ConfigurationServiceImpl.info() java.version=1.6.0_24
13:42:23.412 INFO: org.jitsi.impl.configuration.ConfigurationServiceImpl.info() java.ext.dirs=/usr/lib/jvm/java-6-openjdk-amd64/jre/lib/ext:/usr/java/packages/lib/ext
13:42:23.412 INFO: org.jitsi.impl.configuration.ConfigurationServiceImpl.info() sun.boot.class.path=/usr/lib/jvm/java-6-openjdk-amd64/jre/lib/resources.jar:/usr/lib/jvm/java-6-openjdk-amd64/jre/lib/rt.jar:/usr/lib/jvm/java-6-openjdk-amd64/jre/lib/sunrsasign.jar:/usr/lib/jvm/java-6-openjdk-amd64/jre/lib/jsse.jar:/usr/lib/jvm/java-6-openjdk-amd64/jre/lib/jce.jar:/usr/lib/jvm/java-6-openjdk-amd64/jre/lib/charsets.jar:/usr/lib/jvm/java-6-openjdk-amd64/jre/lib/netx.jar:/usr/lib/jvm/java-6-openjdk-amd64/jre/lib/plugin.jar:/usr/lib/jvm/java-6-openjdk-amd64/jre/lib/rhino.jar:/usr/lib/jvm/java-6-openjdk-amd64/jre/lib/modules/jdk.boot.jar:/usr/lib/jvm/java-6-openjdk-amd64/jre/classes
13:42:23.413 INFO: org.jitsi.impl.configuration.ConfigurationServiceImpl.info() net.java.sip.communicator.SC_HOME_DIR_LOCATION=/home/user
13:42:23.413 INFO: org.jitsi.impl.configuration.ConfigurationServiceImpl.info() java.vendor=Sun Microsystems Inc.
13:42:23.413 INFO: org.jitsi.impl.configuration.ConfigurationServiceImpl.info() file.separator=/
13:42:23.413 INFO: org.jitsi.impl.configuration.ConfigurationServiceImpl.info() net.java.sip.communicator.SC_HOME_DIR_NAME=.jitsi
13:42:23.413 INFO: org.jitsi.impl.configuration.ConfigurationServiceImpl.info() java.vendor.url.bug=http://java.sun.com/cgi-bin/bugreport.cgi
13:42:23.414 INFO: org.jitsi.impl.configuration.ConfigurationServiceImpl.info() sun.io.unicode.encoding=UnicodeLittle
13:42:23.414 INFO: org.jitsi.impl.configuration.ConfigurationServiceImpl.info() sun.cpu.endian=little
13:42:23.414 INFO: org.jitsi.impl.configuration.ConfigurationServiceImpl.info() sun.desktop=gnome
13:42:23.414 INFO: org.jitsi.impl.configuration.ConfigurationServiceImpl.info() sun.cpu.isalist=
13:42:23.542 INFO: impl.resources.ResourceManagementActivator.start().43 Resource manager ... [REGISTERED]
13:42:23.543 INFO: service.notification.NotificationServiceActivator.start().37 Notification Service...[ STARTED ]
13:42:23.561 INFO: service.notification.NotificationServiceActivator.start().44 Notification Service ...[REGISTERED]
13:42:23.695 INFO: impl.netaddr.NetworkAddressManagerServiceImpl.start().81 Network Address Manager ...[ STARTED ]
13:42:23.695 INFO: impl.netaddr.NetworkAddressManagerServiceImpl.start().87 Network Address Manager Service ...[REGISTERED]
13:42:23.878 INFO: impl.browserlauncher.BrowserLauncherActivator.start().45 Browser Launcher Service STARTED
13:42:23.879 INFO: impl.browserlauncher.BrowserLauncherActivator.start().54 Browser Launcher Service REGISTERED
13:42:23.905 INFO: impl.packetlogging.PacketLoggingActivator.start().78 Packet Logging Service ...[REGISTERED]
13:42:23.927 INFO: impl.version.VersionActivator.start() Jitsi Version: Jitsi 1.1-nightly.build.4145
13:42:24.637 INFO: plugin.globalproxyconfig.GlobalProxyPluginActivator.start().79 GLOBAL PROXY CONFIGURATION PLUGIN... [REGISTERED]
13:42:24.687 INFO: org.jitsi.impl.neomedia.device.DeviceSystem.info() Initializing audio devices
13:42:24.976 INFO: org.jitsi.impl.neomedia.device.DeviceSystem.info() Initializing video devices
13:42:24.984 INFO: org.jitsi.impl.neomedia.device.DeviceConfiguration.info() Looking for configured audio devices.
13:42:24.985 INFO: org.jitsi.impl.neomedia.device.DeviceConfiguration.info() Scanning for configured Video Devices.
13:42:24.985 INFO: org.jitsi.impl.neomedia.device.DeviceConfiguration.info() Found Desktop Streaming 0 as a AVFRAME, class org.jitsi.impl.neomedia.codec.video.AVFrame, pixFmt= -1 video capture device.
13:42:25.420 INFO: fmj.commit() Wrote registry file: /home/user/.jitsi/.fmj.registry
13:42:25.483 INFO: impl.neomedia.NeomediaActivator.start().277 Audio Notifier Service ...[REGISTERED]
13:42:25.574 INFO: impl.netaddr.NetworkConfigurationWatcher.checkNetworkInterfaces().444 Currently Active wlan0:[/192.168.2.4]
13:42:25.845 INFO: impl.msghistory.MessageHistoryActivator.start().73 Message History Service ...[REGISTERED]
13:42:25.861 INFO: impl.callhistory.CallHistoryActivator.start().93 Call History Service ...[REGISTERED]
13:42:25.879 INFO: impl.filehistory.FileHistoryActivator.start().64 File History Service ...[REGISTERED]
13:42:25.887 INFO: impl.metahistory.MetaHistoryActivator.start().56 Meta History Service ...[REGISTERED]
13:42:26.130 INFO: impl.gui.GuiActivator.start().127 GlobalStatus Service ...[REGISTERED]
13:42:27.507 INFO: org.jitsi.impl.neomedia.ZrtpFortunaEntropyGatherer.info() GatherEntropy got: 128000 bytes
13:42:30.534 INFO: impl.gui.GuiActivator.start().138 UI Service...[ STARTED ]
13:42:30.703 INFO: impl.gui.GuiActivator.start().144 UI Service ...[REGISTERED]
13:42:30.713 INFO: impl.gui.UIServiceImpl.serviceChanged().1054 Handling registration of a new Plugin Component.
13:42:30.722 INFO: plugin.branding.BrandingActivator.registerMenuEntryNonMacOSX().228 ABOUT WINDOW ... [REGISTERED]
13:42:30.725 INFO: impl.gui.UIServiceImpl.serviceChanged().1054 Handling registration of a new Plugin Component.
13:42:30.728 INFO: plugin.branding.BrandingActivator.registerMenuEntryNonMacOSX().242 CHAT ABOUT WINDOW ... [REGISTERED]
13:42:30.748 INFO: impl.swingnotification.SwingNotificationActivator.start().52 Swing Notification ...[ STARTING ]
13:42:30.752 INFO: impl.swingnotification.SwingNotificationActivator.start().67 Swing Notification ...[REGISTERED]
13:42:31.057 INFO: impl.osdependent.jdic.SystrayServiceJdicImpl.initSystray().380 added the following popup handler : freedesktop.org Desktop-Benachrichtigungen
13:42:31.058 INFO: impl.osdependent.jdic.SystrayServiceJdicImpl.setActivePopupMessageHandler().582 setting the following popup handler as active: freedesktop.org Desktop-Benachrichtigungen
13:42:31.059 INFO: impl.osdependent.jdic.SystrayServiceJdicImpl.initSystray().380 added the following popup handler : Jitsi Pop-Ups
13:42:31.282 INFO: impl.osdependent.OsDependentActivator.start().76 Systray Service...[ STARTED ]
13:42:31.285 INFO: impl.osdependent.OsDependentActivator.start().84 Systray Service ...[REGISTERED]
13:42:31.294 INFO: impl.osdependent.OsDependentActivator.start().90 Desktop Service...[ STARTED ]
13:42:31.296 INFO: impl.osdependent.OsDependentActivator.start().98 Desktop Service ...[REGISTERED]
13:42:31.428 INFO: impl.gui.main.account.AccountRegWizardContainerImpl.serviceChanged().311 Handling registration of a new Account Wizard.
13:42:31.436 INFO: impl.gui.main.account.AccountRegWizardContainerImpl.serviceChanged().311 Handling registration of a new Account Wizard.
13:42:31.449 INFO: impl.gui.main.account.AccountRegWizardContainerImpl.serviceChanged().311 Handling registration of a new Account Wizard.
13:42:31.459 INFO: impl.gui.main.account.AccountRegWizardContainerImpl.serviceChanged().311 Handling registration of a new Account Wizard.
13:42:31.477 INFO: impl.gui.main.account.AccountRegWizardContainerImpl.serviceChanged().311 Handling registration of a new Account Wizard.
13:42:31.485 INFO: impl.gui.main.account.AccountRegWizardContainerImpl.serviceChanged().311 Handling registration of a new Account Wizard.
13:42:31.492 INFO: impl.gui.main.account.AccountRegWizardContainerImpl.serviceChanged().311 Handling registration of a new Account Wizard.
13:42:31.504 INFO: impl.gui.UIServiceImpl.serviceChanged().1054 Handling registration of a new Plugin Component.
13:42:31.506 INFO: plugin.contactinfo.ContactInfoActivator.start().45 CONTACT INFO... [REGISTERED]
13:42:31.536 INFO: plugin.generalconfig.GeneralConfigPluginActivator.start().178 PREFERENCES PLUGIN... [REGISTERED]
13:42:31.549 INFO: impl.gui.UIServiceImpl.serviceChanged().1054 Handling registration of a new Plugin Component.
13:42:31.555 INFO: impl.gui.UIServiceImpl.serviceChanged().1054 Handling registration of a new Plugin Component.
13:42:31.558 INFO: impl.gui.UIServiceImpl.serviceChanged().1054 Handling registration of a new Plugin Component.
13:42:31.566 INFO: plugin.facebookaccregwizz.FacebookAccRegWizzActivator.start().68 Loading facebook account wizard.
13:42:31.567 INFO: impl.gui.main.account.AccountRegWizardContainerImpl.serviceChanged().311 Handling registration of a new Account Wizard.
13:42:31.568 INFO: plugin.facebookaccregwizz.FacebookAccRegWizzActivator.start().95 Facebook account registration wizard [STARTED].
13:42:31.626 WARNUNG: plugin.spellcheck.Parameters.<clinit>().89 Unrecognized category: #text
13:42:31.627 WARNUNG: plugin.spellcheck.Parameters.<clinit>().89 Unrecognized category: #text
13:42:31.635 WARNUNG: plugin.spellcheck.Parameters.<clinit>().89 Unrecognized category: #text
13:42:31.640 INFO: impl.resources.ResourceManagementServiceImpl.getImageURL().544 Missing resource for key: blankFlag
13:42:31.856 INFO: plugin.spellcheck.SpellChecker.start().161 Spell Checker loaded.
13:42:31.858 INFO: impl.gui.UIServiceImpl.serviceChanged().1054 Handling registration of a new Plugin Component.
13:42:31.889 INFO: plugin.advancedconfig.AdvancedConfigActivator.start().88 ADVANCED CONFIG PLUGIN... [REGISTERED]
13:42:31.912 INFO: plugin.advancedconfig.AdvancedConfigurationPanel.serviceChanged().161 Handling registration of a new Configuration Form.
13:42:31.952 INFO: plugin.advancedconfig.AdvancedConfigurationPanel.serviceChanged().161 Handling registration of a new Configuration Form.
13:42:31.967 INFO: impl.replacement.youtube.YoutubeActivator.start().56 Youtube source implementation [STARTED].
13:42:31.979 INFO: impl.replacement.dailymotion.DailymotionActivator.start().56 Dailymotion source implementation [STARTED].
13:42:31.988 INFO: impl.replacement.smiley.SmileyActivator.start().76 Smiley source implementation [STARTED].
13:42:31.995 INFO: impl.replacement.vimeo.VimeoActivator.start().56 Vimeo source implementation [STARTED].
13:42:32.001 INFO: impl.replacement.vbox7.Vbox7Activator.start().57 Vbox7 source implementation [STARTED].
13:42:32.007 INFO: impl.replacement.metacafe.MetacafeActivator.start().57 Metacafe source implementation [STARTED].
13:42:32.013 INFO: impl.replacement.flickr.FlickrActivator.start().57 Flickr source implementation [STARTED].
13:42:32.020 INFO: impl.replacement.hulu.HuluActivator.start().56 HULU source implementation [STARTED].
13:42:32.025 INFO: impl.replacement.twitpic.TwitpicActivator.start().57 Twitpic source implementation [STARTED].
13:42:32.030 INFO: impl.replacement.directimage.DirectImageActivator.start().57 Direct Image Link source implementation [STARTED].
13:42:32.054 INFO: impl.replacement.bliptv.BliptvActivator.start().57 Blip.TV source implementation [STARTED].
13:42:32.060 INFO: impl.replacement.viddler.ViddlerActivator.start().58 Viddler source implementation [STARTED].
13:42:32.084 INFO: plugin.advancedconfig.AdvancedConfigurationPanel.serviceChanged().161 Handling registration of a new Configuration Form.
13:42:32.092 INFO: plugin.advancedconfig.AdvancedConfigurationPanel.serviceChanged().161 Handling registration of a new Configuration Form.
13:42:32.097 INFO: impl.notification.NotificationActivator.start().45 Notification handler Service...[ STARTED ]
13:42:32.100 INFO: impl.notification.NotificationActivator.start().65 Notification handler Service ...[REGISTERED]
13:42:32.104 INFO: plugin.notificationwiring.NotificationWiringActivator.start().42 Notification wiring plugin...[ STARTED ]
13:42:32.232 INFO: impl.protocol.jabber.OperationSetBasicTelephonyJabberImpl.registrationStateChanged().112 Jingle : ON
13:42:32.245 INFO: plugin.notificationwiring.NotificationWiringActivator.start().54 Notification wiring plugin ...[REGISTERED]
13:42:32.600 INFO: impl.gui.main.account.AccountRegWizardContainerImpl.serviceChanged().311 Handling registration of a new Account Wizard.
13:42:32.607 INFO: impl.gui.main.account.AccountRegWizardContainerImpl.serviceChanged().311 Handling registration of a new Account Wizard.
13:42:32.612 INFO: plugin.simpleaccreg.SimpleAccountRegistrationActivator.start().88 SIMPLE ACCOUNT REGISTRATION ...[STARTED]
13:42:32.932 INFO: impl.protocol.jabber.JingleNodesServiceDiscovery.run().95 Start Jingle Nodes discovery!
13:42:45.405 INFO: impl.protocol.jabber.JingleNodesServiceDiscovery.run().128 Jingle Nodes discovery terminated!

felix.client.run.properties (7.07 KB)

···

--
Yannik


#12

Hey Denis,

Hi guys

Sorry for late answer.
It's summer now :slight_smile:

1) Freshly installed OpenFire server with Jingle Nodes plugin activated
(on the Jingle Nodes settings tab the IP address was verified and has a
green checkmark).

I am a multi-homed server, so I cannot make plugin show green checkmark though.
I assume Override IP option with correct ip entered will do the trick. Right?

Only one way to know.

Not necessary. I am not sure we even use it the STUN server we learn
from XMPP. (Would need to check though)

Could you investigate this?

I did check yesterday, and no we don't retrieve STUN information from
Openfire. We use:

1. The servers provided by the user.
2. STUN servers in the SRV records of the XMPP server domain.
3. The Jitsi STUN server.

Even though I have multi-homed internet server, I have only one white
ip present.

What's a white IP?

Others internet interfaces are routed through other servers. I guess I
cannot use STUN in this situation.
Is it correct? It looks like STUN needs two public/white ips present.

The second IP address is part of the legacy STUN discovery procedures.
We don't use those in Jitsi and we only need one IP address per STUN server.

Unfortunately, for some reason windows version of Jitsi (both latest
versions 1.0 and 1.1) do not see my partner's audio device.
Other applications do not have any troubles. Some Java bug here?

Unlikely. We don't use java for audio capture. You may want to send some
logs over.

Cheers,
Emil

···

On 10.08.12, 12:15, Denis Golovan wrote:


#13

Why is my mail sorted into this thread? I am confused

···

--
Yannik


#14

Your mail contains the following header:

  References: <sympa.1344520501.15806.464@jitsi.java.net>

Did you start by replying to "OSS jabber server for Jitsi" and then
change the subject?

Emil

···

On 10.08.12, 13:41, Yannik Völker wrote:

Why is my mail sorted into this thread? I am confused