[jitsi-users] screen sharing "does not work"


#1

Hi

Sorry for the bad title, but I've been trying to get Jitsy working
properly for a while and not getting farther enough. So I'd like to know
I'm on the right track.

I started off with using the Git version of Jitsi. Is that a bad idea? I
ended up staying on tag 4904 rather than master due to the regression
with user accounts I reported before.

My basic goal is to get chat, voice and desktop sharing working with one
specific peer. So far I managed to get chat working easily, video with
no audio occasionally and never desktop sharing.

On my side I have a Debian Stable amd64 laptop. Java is:

java version "1.6.0_27"
OpenJDK Runtime Environment (IcedTea6 1.12.6) (6b27-1.12.6-1~deb7u1)
OpenJDK 64-Bit Server VM (build 20.0-b12, mixed mode)

The remote side is a Windows 7 system with JRE 7 with the latest release
downloaded from the site. I have a very limited access to that system.

I also occasionally test with my N900 phone and some other devices I can
lay my hands on. From what I recall (I didn't see this in the FAQ)
desktop sharing (but not remote control) should work with any SIP / XMPP
video chat. Is that correct?

I tried to minimize the accounts I ask my peer to register to. So at
first we tried using the xmpp support of Google Talk. Seems to work (but
only after I removed any sort of ICE support) - but we get a video chat
with no audio.

Then I tried registering with iptel.org . I could not get any call
through - I keep getting "server error".

I considered ippi.com but the required way too many details for a casual
registration, so I gave up.

Next thing to try was to run my own SIP server. With repro I could not
get a call from one SIP client to another. With Asterisk I managed to do
that and Jitsi immediatly crashed as soon as the video started.

I have no idea to what sort of "support" to expect. I noticed a clear
regression. As I'm not familiar with the software and generally with
Java I followed the recommended procedure and reported it here. Sadly I
got no followups. There are also some recommendations in the site to use
the IRC channel. But nobody seems to answer useful answers on that
channel.

Any recommended path of least resistance for getting the required calls
working would be appreciated.

One last question: I'm trying to understand why the IRC plugin is not
used. As a sanity check I see that it is part of the tree and that it
was built:

$ git show HEAD:src/net/java/sip/communicator/plugin/ircaccregwizz/
tree HEAD:src/net/java/sip/communicator/plugin/ircaccregwizz/

FirstWizardPage.java
IrcAccRegWizzActivator.java
IrcAccountRegistration.java
IrcAccountRegistrationWizard.java
Resources.java
ircaccregwizz.manifest.mf

$ ls classes/net/java/sip/communicator/plugin/ircaccregwizz/
FirstWizardPage.class IrcAccRegWizzActivator.class
IrcAccountRegistration.class Resources.class
IrcAccountRegistrationWizard.class

But I don't see it in Options => Advanced => Plug-ins.

I see a long list of plug-ins. Most of them are "system plug ins" (are
not listed when I uncheck "show system plugins". The only non-system
ones I see are:

* Certificate Configuration plugin 0.0.1
* Common Logging 1.1.2
* Java Mork 1.0.5.SNAPSHOT
* Microsoft Office Communicator 0.0.1
* Spell Checker 0.0.1
* bccontrib 0.0.1
* bcprov 1.49
* thunderbird 0.0.1

Where are the system plugins loaded from? If I run jitsi with 'ant run',
will it identify the existing plugins? If not, how do I point it to the
path for the plugins (hopefully without needing to install them to
anywhere outside my home directory)?

···

--
Tzafrir Cohen | tzafrir@jabber.org | VIM is
http://tzafrir.org.il | | a Mutt's
tzafrir@cohens.org.il | | best
tzafrir@debian.org | | friend


#2

Hi

Sorry for the bad title, but I've been trying to get Jitsy working
properly for a while and not getting farther enough. So I'd like to know
I'm on the right track.

I started off with using the Git version of Jitsi. Is that a bad idea?

This is generally equal to the nightly builds so I wouldn't call it a
bad idea, but there would be no reason to do it unless you are
changing the source code.

I
ended up staying on tag 4904 rather than master due to the regression
with user accounts I reported before.

You might want to try again.

My basic goal is to get chat, voice and desktop sharing working with one
specific peer. So far I managed to get chat working easily, video with
no audio occasionally and never desktop sharing.

On my side I have a Debian Stable amd64 laptop. Java is:

java version "1.6.0_27"
OpenJDK Runtime Environment (IcedTea6 1.12.6) (6b27-1.12.6-1~deb7u1)
OpenJDK 64-Bit Server VM (build 20.0-b12, mixed mode)

The remote side is a Windows 7 system with JRE 7 with the latest release
downloaded from the site. I have a very limited access to that system.

I also occasionally test with my N900 phone and some other devices I can
lay my hands on.

Now that you mention the N900 this makes me thing: are all the tests
above with Jitsi on both ends? You should start there.

From what I recall (I didn't see this in the FAQ)
desktop sharing (but not remote control) should work with any SIP / XMPP
video chat. Is that correct?

Both desktop streaming and sharing (i.e. remote control) work with
both SIP and XMPP. Some SIP and XMPP servers however may have a
limitation on the signalling traffic so sharing may be shaky in such
cases.

I tried to minimize the accounts I ask my peer to register to. So at
first we tried using the xmpp support of Google Talk. Seems to work (but
only after I removed any sort of ICE support) - but we get a video chat
with no audio.

Disabling ICE is a BAD idea. Don't do it unless you are certain that
all your conversations are going to be automatically relayed by the
server (which is rarely, if ever, the case for XMPP) or you are only
going to talk to people on the same LAN as yourself.

Then I tried registering with iptel.org . I could not get any call
through - I keep getting "server error".

I considered ippi.com but the required way too many details for a casual
registration, so I gave up.

They are pretty reliable so, if you are looking for SIP, you may want
to reconsider.

Next thing to try was to run my own SIP server. With repro I could not
get a call from one SIP client to another.

That's commendable, but it is also a bold step. Properly setting up a
SIP server is a tricky business so you may want to validate Jitsi as
running with an existing one before that.

You can, for example, try creating an account and using http://jit.si

With Asterisk I managed to do
that and Jitsi immediatly crashed as soon as the video started.

Did you give up after a single crash? Crashes do happen every now and
then for various reasons. They don't automatically invalidate all your
network setup. More often than not they are actually unrelated.

I have no idea to what sort of "support" to expect. I noticed a clear
regression. As I'm not familiar with the software and generally with
Java I followed the recommended procedure and reported it here. Sadly I
got no followups. There are also some recommendations in the site to use
the IRC channel. But nobody seems to answer useful answers on that
channel.

Yup. Sorry about that. We are thinking of setting up a jitsi channel
on jit.si and using that as our default discussion venue.

Any recommended path of least resistance for getting the required calls
working would be appreciated.

Try using ippi.com and/or http://jit.si

One last question: I'm trying to understand why the IRC plugin is not
used.

Two reasons: a) inappropriate licensing, b) it wasn't maintained. We
are hoping to get a new implementation at some point.

As a sanity check I see that it is part of the tree and that it
was built:

$ git show HEAD:src/net/java/sip/communicator/plugin/ircaccregwizz/
tree HEAD:src/net/java/sip/communicator/plugin/ircaccregwizz/

FirstWizardPage.java
IrcAccRegWizzActivator.java
IrcAccountRegistration.java
IrcAccountRegistrationWizard.java
Resources.java
ircaccregwizz.manifest.mf

$ ls classes/net/java/sip/communicator/plugin/ircaccregwizz/
FirstWizardPage.class IrcAccRegWizzActivator.class
IrcAccountRegistration.class Resources.class
IrcAccountRegistrationWizard.class

But I don't see it in Options => Advanced => Plug-ins.

I see a long list of plug-ins. Most of them are "system plug ins" (are
not listed when I uncheck "show system plugins". The only non-system
ones I see are:

* Certificate Configuration plugin 0.0.1
* Common Logging 1.1.2
* Java Mork 1.0.5.SNAPSHOT
* Microsoft Office Communicator 0.0.1
* Spell Checker 0.0.1
* bccontrib 0.0.1
* bcprov 1.49
* thunderbird 0.0.1

Where are the system plugins loaded from?

System plugins are those that we ship with Jitsi, which, unless you
manually add plugins, means everything. The ones that you see when you
uncheck "show system plugins" are simply bundles where we forgot to
add set the system flag in the bundle manifest.

Hope this helps,
Emil

···

On Thu, Nov 21, 2013 at 7:57 AM, Tzafrir Cohen <tzafrir@cohens.org.il> wrote:

If I run jitsi with 'ant run',
will it identify the existing plugins? If not, how do I point it to the
path for the plugins (hopefully without needing to install them to
anywhere outside my home directory)?

--
Tzafrir Cohen | tzafrir@jabber.org | VIM is
http://tzafrir.org.il | | a Mutt's
tzafrir@cohens.org.il | | best
tzafrir@debian.org | | friend

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

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


#3

Hi,

Thanks for the quick reply.

Anwering some things:

> Hi
>
> Sorry for the bad title, but I've been trying to get Jitsy working
> properly for a while and not getting farther enough. So I'd like to know
> I'm on the right track.
>
> I started off with using the Git version of Jitsi. Is that a bad idea?

This is generally equal to the nightly builds so I wouldn't call it a
bad idea, but there would be no reason to do it unless you are
changing the source code.

> I
> ended up staying on tag 4904 rather than master due to the regression
> with user accounts I reported before.

You might want to try again.

I tried a few hours ago (with rev. 4916) and had the same issue.

To upgrade I use:

  git pull
  ant rebuild
  ant run

> My basic goal is to get chat, voice and desktop sharing working with one
> specific peer. So far I managed to get chat working easily, video with
> no audio occasionally and never desktop sharing.
>
> On my side I have a Debian Stable amd64 laptop. Java is:
>
> java version "1.6.0_27"
> OpenJDK Runtime Environment (IcedTea6 1.12.6) (6b27-1.12.6-1~deb7u1)
> OpenJDK 64-Bit Server VM (build 20.0-b12, mixed mode)
>
> The remote side is a Windows 7 system with JRE 7 with the latest release
> downloaded from the site. I have a very limited access to that system.
>
> I also occasionally test with my N900 phone and some other devices I can
> lay my hands on.

Now that you mention the N900 this makes me thing: are all the tests
above with Jitsi on both ends? You should start there.

See below.

> From what I recall (I didn't see this in the FAQ)
> desktop sharing (but not remote control) should work with any SIP / XMPP
> video chat. Is that correct?

Both desktop streaming and sharing (i.e. remote control) work with
both SIP and XMPP. Some SIP and XMPP servers however may have a
limitation on the signalling traffic so sharing may be shaky in such
cases.

> I tried to minimize the accounts I ask my peer to register to. So at
> first we tried using the xmpp support of Google Talk. Seems to work (but
> only after I removed any sort of ICE support) - but we get a video chat
> with no audio.

In this case, both sides are Jitsi.

Disabling ICE is a BAD idea. Don't do it unless you are certain that
all your conversations are going to be automatically relayed by the
server (which is rarely, if ever, the case for XMPP) or you are only
going to talk to people on the same LAN as yourself.

ICE worked well as long as we were on the same LAN. When I connected
from a different network I got an ICE error. Only way around it was to
disable both forms of ICE.

> Then I tried registering with iptel.org . I could not get any call
> through - I keep getting "server error".
>
> I considered ippi.com but the required way too many details for a casual
> registration, so I gave up.

They are pretty reliable so, if you are looking for SIP, you may want
to reconsider.

> Next thing to try was to run my own SIP server. With repro I could not
> get a call from one SIP client to another.

In this case the other side was my N900.

That's commendable, but it is also a bold step. Properly setting up a
SIP server is a tricky business so you may want to validate Jitsi as
running with an existing one before that.

You can, for example, try creating an account and using http://jit.si

> With Asterisk I managed to do
> that and Jitsi immediatly crashed as soon as the video started.

Did you give up after a single crash? Crashes do happen every now and
then for various reasons. They don't automatically invalidate all your
network setup. More often than not they are actually unrelated.

Crash was consistent. I tried different video codecs and it didn't help.

···

On Thu, Nov 21, 2013 at 09:33:40AM +0100, Emil Ivov wrote:

On Thu, Nov 21, 2013 at 7:57 AM, Tzafrir Cohen <tzafrir@cohens.org.il> wrote:

--
Tzafrir Cohen | tzafrir@jabber.org | VIM is
http://tzafrir.org.il | | a Mutt's
tzafrir@cohens.org.il | | best
tzafrir@debian.org | | friend


#4

Hi,

Thanks for the quick reply.

Anwering some things:

> Hi
>
> Sorry for the bad title, but I've been trying to get Jitsy working
> properly for a while and not getting farther enough. So I'd like to know
> I'm on the right track.
>
> I started off with using the Git version of Jitsi. Is that a bad idea?

This is generally equal to the nightly builds so I wouldn't call it a
bad idea, but there would be no reason to do it unless you are
changing the source code.

> I
> ended up staying on tag 4904 rather than master due to the regression
> with user accounts I reported before.

You might want to try again.

I tried a few hours ago (with rev. 4916) and had the same issue.

To upgrade I use:

  git pull
  ant rebuild
  ant run

Can you try with the latest build? (as opposed to compiling and
running it yourself). The NoClassDefFound exception you pasted earlier
looks like an indication that some files did not get updated properly.

> My basic goal is to get chat, voice and desktop sharing working with one
> specific peer. So far I managed to get chat working easily, video with
> no audio occasionally and never desktop sharing.
>
> On my side I have a Debian Stable amd64 laptop. Java is:
>
> java version "1.6.0_27"
> OpenJDK Runtime Environment (IcedTea6 1.12.6) (6b27-1.12.6-1~deb7u1)
> OpenJDK 64-Bit Server VM (build 20.0-b12, mixed mode)
>
> The remote side is a Windows 7 system with JRE 7 with the latest release
> downloaded from the site. I have a very limited access to that system.
>
> I also occasionally test with my N900 phone and some other devices I can
> lay my hands on.

Now that you mention the N900 this makes me thing: are all the tests
above with Jitsi on both ends? You should start there.

See below.

> From what I recall (I didn't see this in the FAQ)
> desktop sharing (but not remote control) should work with any SIP / XMPP
> video chat. Is that correct?

Both desktop streaming and sharing (i.e. remote control) work with
both SIP and XMPP. Some SIP and XMPP servers however may have a
limitation on the signalling traffic so sharing may be shaky in such
cases.

> I tried to minimize the accounts I ask my peer to register to. So at
> first we tried using the xmpp support of Google Talk. Seems to work (but
> only after I removed any sort of ICE support) - but we get a video chat
> with no audio.

In this case, both sides are Jitsi.

Disabling ICE is a BAD idea. Don't do it unless you are certain that
all your conversations are going to be automatically relayed by the
server (which is rarely, if ever, the case for XMPP) or you are only
going to talk to people on the same LAN as yourself.

ICE worked well as long as we were on the same LAN. When I connected
from a different network I got an ICE error. Only way around it was to
disable both forms of ICE.

Non-use of ICE can only work when there is direct connectivity between
both IPs. That is, only when they can both ping each other.

OR

In case the the provide changes the IP addresses and provides hosted
NAT traversal. I don't know which case you happened to fall into but
my point is that if things worked it was because you caught a lucky
break.

Use of ICE on the other hand can fail for cases where the provider
does not have a relaying mechanism. This is why I suggested you use
jit.si (with ICE) because it has a Jingle Nodes relay.

> Then I tried registering with iptel.org . I could not get any call
> through - I keep getting "server error".
>
> I considered ippi.com but the required way too many details for a casual
> registration, so I gave up.

They are pretty reliable so, if you are looking for SIP, you may want
to reconsider.

> Next thing to try was to run my own SIP server. With repro I could not
> get a call from one SIP client to another.

In this case the other side was my N900.

That's commendable, but it is also a bold step. Properly setting up a
SIP server is a tricky business so you may want to validate Jitsi as
running with an existing one before that.

You can, for example, try creating an account and using http://jit.si

> With Asterisk I managed to do
> that and Jitsi immediatly crashed as soon as the video started.

Did you give up after a single crash? Crashes do happen every now and
then for various reasons. They don't automatically invalidate all your
network setup. More often than not they are actually unrelated.

Crash was consistent. I tried different video codecs and it didn't help.

H.263 might currently be crashing, so make sure you keep it disabled.
It is by default. If using H.264, you have to explicitly configure
that in Asterisk.

I would still advise that you try existing services such as ippi or
jit.si before going down that road. Adding your own server is a great
thing to do eventually but right now it's just one more point of
uncertainty.

Hope this helps,
Emil

···

On Thu, Nov 21, 2013 at 9:37 AM, Tzafrir Cohen <tzafrir@cohens.org.il> wrote:

On Thu, Nov 21, 2013 at 09:33:40AM +0100, Emil Ivov wrote:

On Thu, Nov 21, 2013 at 7:57 AM, Tzafrir Cohen <tzafrir@cohens.org.il> wrote:

--
Tzafrir Cohen | tzafrir@jabber.org | VIM is
http://tzafrir.org.il | | a Mutt's
tzafrir@cohens.org.il | | best
tzafrir@debian.org | | friend

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

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