[jitsi-dev] fresh install of iOS app and black screen


#1

Hi,

I just did a fresh git clone and compiled the iOS app as I had done a few
months ago.
Testing with meet.jit.si seems to work fine, but when I try on my freshly
built jitsi meet installation (debian testing installed yesterday) I don't
seem to get audio and video flowing at all (black screen and frozen video).

What version is currently being deployed at meet.jit.si (stable or
testing)? I think I might go back to stable since my current installation
seems fairly buggy. Thoughts?

What versions are most people on that are stable enough for daily use?

Cheers,
Peter


#2

OK, I decided to upgrade to today's nightly and now I have some more
insight into what's going on.

It seems to work fine when only 2 participants are in the room (including
freshly compiled mobile app that now seems to allow p2p too - well done!)
Although the iOS app is still pretty buggy - sometimes clicking the join
button does nothing, and if you keep clicking you get a black screen, and
I've also had it crash a couple of times when starting, even after a reboot
of my iPhone 7 running 10.3.2 - I'll try to get debug logs for the app
tomorrow.

But as soon as a 3rd person enters it stops working (I believe) because of
turn options recently added.

In fact I see this in Chrome's console:

[modules/xmpp/strophe.jingle.js] <>: getting turn credentials failed <iq
xmlns=​"jabber:​client" type=​"error"

[modules/xmpp/strophe.jingle.js] <>: is mod_turncredentials or similar
installed?

This confuses me somewhat since I thought that the bridge itself was
already working as a pseudo-turn server, so not sure why we need to use an
external Turn server with creds, etc Am I missing something in this new
config option?

Cheers,
Peter

P.S. I also see this in the console which would explain why Chrome's audio
output is forced through the system speakers on my ubuntu machine instead
of through the headset:

[modules/settings/Settings.js] <>: Failed to set audio output device from
local storage. Default audio output device will be usedinstead.
DOMException: Requested device not found

Finally, I see a bunch of errors related to a certain select2.png and
select2-spinner.gif files that it tries to get but seem to be missing:

select2.png:1 GET https://jitsi.my.domain/libs/select2.png 404 (Not Found)

jquery.min.js:4 GET https://jitsi.my.domain/libs/select2-spinner.gif 404
(Not Found)

I hope all this detailed feedback helps. I'm a big fan and have been
playing around since it was just still sip communicator, and it keeps
getting better and better.

Cheers,
Peter

···

On Thu, Jul 6, 2017 at 4:19 PM, Peter Villeneuve <petervnv1@gmail.com> wrote:

Hi,

I just did a fresh git clone and compiled the iOS app as I had done a few
months ago.
Testing with meet.jit.si seems to work fine, but when I try on my freshly
built jitsi meet installation (debian testing installed yesterday) I don't
seem to get audio and video flowing at all (black screen and frozen video).

What version is currently being deployed at meet.jit.si (stable or
testing)? I think I might go back to stable since my current installation
seems fairly buggy. Thoughts?

What versions are most people on that are stable enough for daily use?

Cheers,
Peter


#3

Can someone explain the new turn config options in nightly?

On a fresh install If I don't uncomment the

useStunTurn: true, // use XEP-0215 to fetch STUN and TURN server

setting in config.js then the bridge doesn't show any video at all. If
I do set that setting, then p2p works fine but then I get the ICE
error mentioned above (related to turn I believe) when a 3rd person
joins.

Should I open an ticket on github?

Cheers,

Peter

···

On Thu, Jul 6, 2017 at 6:48 PM, Peter Villeneuve <petervnv1@gmail.com> wrote:

OK, I decided to upgrade to today's nightly and now I have some more
insight into what's going on.

It seems to work fine when only 2 participants are in the room (including
freshly compiled mobile app that now seems to allow p2p too - well done!)
Although the iOS app is still pretty buggy - sometimes clicking the join
button does nothing, and if you keep clicking you get a black screen, and
I've also had it crash a couple of times when starting, even after a reboot
of my iPhone 7 running 10.3.2 - I'll try to get debug logs for the app
tomorrow.

But as soon as a 3rd person enters it stops working (I believe) because of
turn options recently added.

In fact I see this in Chrome's console:

[modules/xmpp/strophe.jingle.js] <>: getting turn credentials failed <iq
xmlns=​"jabber:​client" type=​"error"

[modules/xmpp/strophe.jingle.js] <>: is mod_turncredentials or similar
installed?

This confuses me somewhat since I thought that the bridge itself was
already working as a pseudo-turn server, so not sure why we need to use an
external Turn server with creds, etc Am I missing something in this new
config option?

Cheers,
Peter

P.S. I also see this in the console which would explain why Chrome's audio
output is forced through the system speakers on my ubuntu machine instead
of through the headset:

[modules/settings/Settings.js] <>: Failed to set audio output device from
local storage. Default audio output device will be usedinstead.
DOMException: Requested device not found

Finally, I see a bunch of errors related to a certain select2.png and
select2-spinner.gif files that it tries to get but seem to be missing:

select2.png:1 GET https://jitsi.my.domain/libs/select2.png 404 (Not Found)

jquery.min.js:4 GET https://jitsi.my.domain/libs/select2-spinner.gif 404
(Not Found)

I hope all this detailed feedback helps. I'm a big fan and have been
playing around since it was just still sip communicator, and it keeps
getting better and better.

Cheers,
Peter

On Thu, Jul 6, 2017 at 4:19 PM, Peter Villeneuve <petervnv1@gmail.com> > wrote:

Hi,

I just did a fresh git clone and compiled the iOS app as I had done a few
months ago.
Testing with meet.jit.si seems to work fine, but when I try on my
freshly built jitsi meet installation (debian testing installed yesterday)
I don't seem to get audio and video flowing at all (black screen and frozen
video).

What version is currently being deployed at meet.jit.si (stable or
testing)? I think I might go back to stable since my current installation
seems fairly buggy. Thoughts?

What versions are most people on that are stable enough for daily use?

Cheers,
Peter


#4

Can someone explain the new turn config options in nightly?

On a fresh install If I don't uncomment the
useStunTurn: true, // use XEP-0215 to fetch STUN and TURN server

setting in config.js then the bridge doesn't show any video at all. If I do set that setting, then p2p works fine but then I get the ICE error mentioned above (related to turn I believe) when a 3rd person joins.

Should I open an ticket on github?

Can you pull again? That should be fixed now.

···

On Jul 7, 2017, at 13:19, Peter Villeneuve <petervnv1@gmail.com> wrote:

Cheers,
Peter

On Thu, Jul 6, 2017 at 6:48 PM, Peter Villeneuve <petervnv1@gmail.com> wrote:
OK, I decided to upgrade to today's nightly and now I have some more insight into what's going on.

It seems to work fine when only 2 participants are in the room (including freshly compiled mobile app that now seems to allow p2p too - well done!)
Although the iOS app is still pretty buggy - sometimes clicking the join button does nothing, and if you keep clicking you get a black screen, and I've also had it crash a couple of times when starting, even after a reboot of my iPhone 7 running 10.3.2 - I'll try to get debug logs for the app tomorrow.

But as soon as a 3rd person enters it stops working (I believe) because of turn options recently added.

In fact I see this in Chrome's console:

[modules/xmpp/strophe.jingle.js] <>: getting turn credentials failed <iq xmlns=​"jabber:​client" type=​"error"

[modules/xmpp/strophe.jingle.js] <>: is mod_turncredentials or similar installed?

This confuses me somewhat since I thought that the bridge itself was already working as a pseudo-turn server, so not sure why we need to use an external Turn server with creds, etc Am I missing something in this new config option?

Cheers,
Peter

P.S. I also see this in the console which would explain why Chrome's audio output is forced through the system speakers on my ubuntu machine instead of through the headset:

[modules/settings/Settings.js] <>: Failed to set audio output device from local storage. Default audio output device will be usedinstead. DOMException: Requested device not found

Finally, I see a bunch of errors related to a certain select2.png and select2-spinner.gif files that it tries to get but seem to be missing:

select2.png:1 GET https://jitsi.my.domain/libs/select2.png 404 (Not Found)

jquery.min.js:4 GET https://jitsi.my.domain/libs/select2-spinner.gif 404 (Not Found)

I hope all this detailed feedback helps. I'm a big fan and have been playing around since it was just still sip communicator, and it keeps getting better and better.

Cheers,
Peter

On Thu, Jul 6, 2017 at 4:19 PM, Peter Villeneuve <petervnv1@gmail.com> wrote:
Hi,

I just did a fresh git clone and compiled the iOS app as I had done a few months ago.
Testing with meet.jit.si seems to work fine, but when I try on my freshly built jitsi meet installation (debian testing installed yesterday) I don't seem to get audio and video flowing at all (black screen and frozen video).

What version is currently being deployed at meet.jit.si (stable or testing)? I think I might go back to stable since my current installation seems fairly buggy. Thoughts?

What versions are most people on that are stable enough for daily use?

Cheers,
Peter

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

--
Saúl


#5

OK, gracias Saúl.

I'll pull and try again after lunch.

I assume this is the commit that fixes it?
https://github.com/jitsi/lib-jitsi-meet/commit/97d2e3452cfca80487fd73910d6d05e9110791f2

So I should leave "useStunTurn: true" commented out and it should work fine
again?

Still confused why we need turn functionality at all when jvb already acts
as a relay. Can someone explain the thinking behind this?

Cheers

···

On Fri, Jul 7, 2017 at 12:35 PM, Saúl Ibarra Corretgé < scorretge@atlassian.com> wrote:

> On Jul 7, 2017, at 13:19, Peter Villeneuve <petervnv1@gmail.com> wrote:
>
> Can someone explain the new turn config options in nightly?
>
> On a fresh install If I don't uncomment the
> useStunTurn: true, // use XEP-0215 to fetch STUN and TURN server
>
> setting in config.js then the bridge doesn't show any video at all. If I
do set that setting, then p2p works fine but then I get the ICE error
mentioned above (related to turn I believe) when a 3rd person joins.
>
> Should I open an ticket on github?
>

Can you pull again? That should be fixed now.

> Cheers,
> Peter
>
> On Thu, Jul 6, 2017 at 6:48 PM, Peter Villeneuve <petervnv1@gmail.com> > wrote:
> OK, I decided to upgrade to today's nightly and now I have some more
insight into what's going on.
>
> It seems to work fine when only 2 participants are in the room
(including freshly compiled mobile app that now seems to allow p2p too -
well done!)
> Although the iOS app is still pretty buggy - sometimes clicking the join
button does nothing, and if you keep clicking you get a black screen, and
I've also had it crash a couple of times when starting, even after a reboot
of my iPhone 7 running 10.3.2 - I'll try to get debug logs for the app
tomorrow.
>
> But as soon as a 3rd person enters it stops working (I believe) because
of turn options recently added.
>
> In fact I see this in Chrome's console:
>
> [modules/xmpp/strophe.jingle.js] <>: getting turn credentials failed
<iq xmlns=​"jabber:​client" type=​"error"
>
> [modules/xmpp/strophe.jingle.js] <>: is mod_turncredentials or similar
installed?
>
> This confuses me somewhat since I thought that the bridge itself was
already working as a pseudo-turn server, so not sure why we need to use an
external Turn server with creds, etc Am I missing something in this new
config option?
>
> Cheers,
> Peter
>
> P.S. I also see this in the console which would explain why Chrome's
audio output is forced through the system speakers on my ubuntu machine
instead of through the headset:
>
> [modules/settings/Settings.js] <>: Failed to set audio output device
from local storage. Default audio output device will be usedinstead.
DOMException: Requested device not found
>
>
> Finally, I see a bunch of errors related to a certain select2.png and
select2-spinner.gif files that it tries to get but seem to be missing:
>
> select2.png:1 GET https://jitsi.my.domain/libs/select2.png 404 (Not
Found)
>
> jquery.min.js:4 GET https://jitsi.my.domain/libs/select2-spinner.gif
404 (Not Found)
>
>
> I hope all this detailed feedback helps. I'm a big fan and have been
playing around since it was just still sip communicator, and it keeps
getting better and better.
>
> Cheers,
> Peter
>
>
>
> On Thu, Jul 6, 2017 at 4:19 PM, Peter Villeneuve <petervnv1@gmail.com> > wrote:
> Hi,
>
> I just did a fresh git clone and compiled the iOS app as I had done a
few months ago.
> Testing with meet.jit.si seems to work fine, but when I try on my
freshly built jitsi meet installation (debian testing installed yesterday)
I don't seem to get audio and video flowing at all (black screen and frozen
video).
>
>
> What version is currently being deployed at meet.jit.si (stable or
testing)? I think I might go back to stable since my current installation
seems fairly buggy. Thoughts?
>
> What versions are most people on that are stable enough for daily use?
>
> Cheers,
> Peter
>
>
> _______________________________________________
> dev mailing list
> dev@jitsi.org
> Unsubscribe instructions and other list options:
> http://lists.jitsi.org/mailman/listinfo/dev

--
Saúl

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


#6

OK, gracias Saúl.

I'll pull and try again after lunch.

I assume this is the commit that fixes it? https://github.com/jitsi/lib-jitsi-meet/commit/97d2e3452cfca80487fd73910d6d05e9110791f2

Correct.

So I should leave "useStunTurn: true" commented out and it should work fine again?

Yes.

Still confused why we need turn functionality at all when jvb already acts as a relay. Can someone explain the thinking behind this?

Sure. When making 1-to-1 calls, there is no need to use all the advanced video routing features (like simulcast for example) in the JVB. The easiest way for disabling everything is not use the JVB in the first place for those calls. A while ago we added a “P2P mode”, which means we’ll start a second peer connection and try to connect directly, only if there are 2 participants.

All in all, 1-to-1 calls are a very used scenario which is worth optimizing. This is one such optimization.

Cheers,

···

On Jul 7, 2017, at 14:02, Peter Villeneuve <petervnv1@gmail.com> wrote:

Cheers

On Fri, Jul 7, 2017 at 12:35 PM, Saúl Ibarra Corretgé <scorretge@atlassian.com> wrote:

> On Jul 7, 2017, at 13:19, Peter Villeneuve <petervnv1@gmail.com> wrote:
>
> Can someone explain the new turn config options in nightly?
>
> On a fresh install If I don't uncomment the
> useStunTurn: true, // use XEP-0215 to fetch STUN and TURN server
>
> setting in config.js then the bridge doesn't show any video at all. If I do set that setting, then p2p works fine but then I get the ICE error mentioned above (related to turn I believe) when a 3rd person joins.
>
> Should I open an ticket on github?
>

Can you pull again? That should be fixed now.

> Cheers,
> Peter
>
> On Thu, Jul 6, 2017 at 6:48 PM, Peter Villeneuve <petervnv1@gmail.com> wrote:
> OK, I decided to upgrade to today's nightly and now I have some more insight into what's going on.
>
> It seems to work fine when only 2 participants are in the room (including freshly compiled mobile app that now seems to allow p2p too - well done!)
> Although the iOS app is still pretty buggy - sometimes clicking the join button does nothing, and if you keep clicking you get a black screen, and I've also had it crash a couple of times when starting, even after a reboot of my iPhone 7 running 10.3.2 - I'll try to get debug logs for the app tomorrow.
>
> But as soon as a 3rd person enters it stops working (I believe) because of turn options recently added.
>
> In fact I see this in Chrome's console:
>
> [modules/xmpp/strophe.jingle.js] <>: getting turn credentials failed <iq xmlns=​"jabber:​client" type=​"error"
>
> [modules/xmpp/strophe.jingle.js] <>: is mod_turncredentials or similar installed?
>
> This confuses me somewhat since I thought that the bridge itself was already working as a pseudo-turn server, so not sure why we need to use an external Turn server with creds, etc Am I missing something in this new config option?
>
> Cheers,
> Peter
>
> P.S. I also see this in the console which would explain why Chrome's audio output is forced through the system speakers on my ubuntu machine instead of through the headset:
>
> [modules/settings/Settings.js] <>: Failed to set audio output device from local storage. Default audio output device will be usedinstead. DOMException: Requested device not found
>
>
> Finally, I see a bunch of errors related to a certain select2.png and select2-spinner.gif files that it tries to get but seem to be missing:
>
> select2.png:1 GET https://jitsi.my.domain/libs/select2.png 404 (Not Found)
>
> jquery.min.js:4 GET https://jitsi.my.domain/libs/select2-spinner.gif 404 (Not Found)
>
>
> I hope all this detailed feedback helps. I'm a big fan and have been playing around since it was just still sip communicator, and it keeps getting better and better.
>
> Cheers,
> Peter
>
>
>
> On Thu, Jul 6, 2017 at 4:19 PM, Peter Villeneuve <petervnv1@gmail.com> wrote:
> Hi,
>
> I just did a fresh git clone and compiled the iOS app as I had done a few months ago.
> Testing with meet.jit.si seems to work fine, but when I try on my freshly built jitsi meet installation (debian testing installed yesterday) I don't seem to get audio and video flowing at all (black screen and frozen video).
>
>
> What version is currently being deployed at meet.jit.si (stable or testing)? I think I might go back to stable since my current installation seems fairly buggy. Thoughts?
>
> What versions are most people on that are stable enough for daily use?
>
> Cheers,
> Peter
>
>
> _______________________________________________
> dev mailing list
> dev@jitsi.org
> Unsubscribe instructions and other list options:
> http://lists.jitsi.org/mailman/listinfo/dev

--
Saúl

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

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

--
Saúl


#7

Thanks for the explanation Saúl.

I first updated using apt-get and got a black screen when the 2nd person
joined. I then did a purge and reinstalled everything from scratch again
(unstable repo) and I'm still getting black screen when the 2nd person
joins (from behind the same LAN where p2p was working fine yesterday)

Firefox console:

XML Parsing Error: not well-formed
Location:
Line Number 1, Column 168:

and specially

ICE failed, add a STUN server and see about:webrtc for more details
(unknown)
[modules/xmpp/JingleSessionPC.js]
<value/this.peerconnection.oniceconnectionstatechange>: (TIME) ICE failed
P2P? false: 52667.535 lib-jitsi-meet.min.js:2:161499
[conference.js] <value>: CONFERENCE FAILED: conference.setup_failed Error:
ICE fail
Stack trace:
value/this.peerconnection.oniceconnectionstatechange@
https://jitsi.my.domain/libs/lib-jitsi-meet.min.js?v=2087:2:489934
r/this.peerconnection.oniceconnectionstatechange@
https://jitsi.my.domain/libs/lib-jitsi-meet.min.js?v=2087:2:321633
  app.bundle.min.js:2:442688

This is on a default install without changing any configuration settings at
all...

···

On Fri, Jul 7, 2017 at 2:59 PM, Saúl Ibarra Corretgé < scorretge@atlassian.com> wrote:

> On Jul 7, 2017, at 14:02, Peter Villeneuve <petervnv1@gmail.com> wrote:
>
> OK, gracias Saúl.
>
> I'll pull and try again after lunch.
>
> I assume this is the commit that fixes it? https://github.com/jitsi/lib-
jitsi-meet/commit/97d2e3452cfca80487fd73910d6d05e9110791f2
>

Correct.

> So I should leave "useStunTurn: true" commented out and it should work
fine again?
>

Yes.

> Still confused why we need turn functionality at all when jvb already
acts as a relay. Can someone explain the thinking behind this?
>

Sure. When making 1-to-1 calls, there is no need to use all the advanced
video routing features (like simulcast for example) in the JVB. The easiest
way for disabling everything is not use the JVB in the first place for
those calls. A while ago we added a “P2P mode”, which means we’ll start a
second peer connection and try to connect directly, only if there are 2
participants.

All in all, 1-to-1 calls are a very used scenario which is worth
optimizing. This is one such optimization.

Cheers,

> Cheers
>
> On Fri, Jul 7, 2017 at 12:35 PM, Saúl Ibarra Corretgé < > scorretge@atlassian.com> wrote:
>
> > On Jul 7, 2017, at 13:19, Peter Villeneuve <petervnv1@gmail.com> > wrote:
> >
> > Can someone explain the new turn config options in nightly?
> >
> > On a fresh install If I don't uncomment the
> > useStunTurn: true, // use XEP-0215 to fetch STUN and TURN server
> >
> > setting in config.js then the bridge doesn't show any video at all. If
I do set that setting, then p2p works fine but then I get the ICE error
mentioned above (related to turn I believe) when a 3rd person joins.
> >
> > Should I open an ticket on github?
> >
>
> Can you pull again? That should be fixed now.
>
> > Cheers,
> > Peter
> >
> > On Thu, Jul 6, 2017 at 6:48 PM, Peter Villeneuve <petervnv1@gmail.com> > wrote:
> > OK, I decided to upgrade to today's nightly and now I have some more
insight into what's going on.
> >
> > It seems to work fine when only 2 participants are in the room
(including freshly compiled mobile app that now seems to allow p2p too -
well done!)
> > Although the iOS app is still pretty buggy - sometimes clicking the
join button does nothing, and if you keep clicking you get a black screen,
and I've also had it crash a couple of times when starting, even after a
reboot of my iPhone 7 running 10.3.2 - I'll try to get debug logs for the
app tomorrow.
> >
> > But as soon as a 3rd person enters it stops working (I believe)
because of turn options recently added.
> >
> > In fact I see this in Chrome's console:
> >
> > [modules/xmpp/strophe.jingle.js] <>: getting turn credentials failed
<iq xmlns=​"jabber:​client" type=​"error"
> >
> > [modules/xmpp/strophe.jingle.js] <>: is mod_turncredentials or
similar installed?
> >
> > This confuses me somewhat since I thought that the bridge itself was
already working as a pseudo-turn server, so not sure why we need to use an
external Turn server with creds, etc Am I missing something in this new
config option?
> >
> > Cheers,
> > Peter
> >
> > P.S. I also see this in the console which would explain why Chrome's
audio output is forced through the system speakers on my ubuntu machine
instead of through the headset:
> >
> > [modules/settings/Settings.js] <>: Failed to set audio output device
from local storage. Default audio output device will be usedinstead.
DOMException: Requested device not found
> >
> >
> > Finally, I see a bunch of errors related to a certain select2.png and
select2-spinner.gif files that it tries to get but seem to be missing:
> >
> > select2.png:1 GET https://jitsi.my.domain/libs/select2.png 404 (Not
Found)
> >
> > jquery.min.js:4 GET https://jitsi.my.domain/libs/select2-spinner.gif
404 (Not Found)
> >
> >
> > I hope all this detailed feedback helps. I'm a big fan and have been
playing around since it was just still sip communicator, and it keeps
getting better and better.
> >
> > Cheers,
> > Peter
> >
> >
> >
> > On Thu, Jul 6, 2017 at 4:19 PM, Peter Villeneuve <petervnv1@gmail.com> > wrote:
> > Hi,
> >
> > I just did a fresh git clone and compiled the iOS app as I had done a
few months ago.
> > Testing with meet.jit.si seems to work fine, but when I try on my
freshly built jitsi meet installation (debian testing installed yesterday)
I don't seem to get audio and video flowing at all (black screen and frozen
video).
> >
> >
> > What version is currently being deployed at meet.jit.si (stable or
testing)? I think I might go back to stable since my current installation
seems fairly buggy. Thoughts?
> >
> > What versions are most people on that are stable enough for daily use?
> >
> > Cheers,
> > Peter
> >
> >
> > _______________________________________________
> > dev mailing list
> > dev@jitsi.org
> > Unsubscribe instructions and other list options:
> > http://lists.jitsi.org/mailman/listinfo/dev
>
> --
> Saúl
>
>
> _______________________________________________
> dev mailing list
> dev@jitsi.org
> Unsubscribe instructions and other list options:
> http://lists.jitsi.org/mailman/listinfo/dev
>
> _______________________________________________
> dev mailing list
> dev@jitsi.org
> Unsubscribe instructions and other list options:
> http://lists.jitsi.org/mailman/listinfo/dev

--
Saúl

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


#8

I'm going to reinstall debian from scratch and try again with the unstable
repo to see if there was some leftover file or setting that's messing
things up.

···

On Fri, Jul 7, 2017 at 4:21 PM, Peter Villeneuve <petervnv1@gmail.com> wrote:

Thanks for the explanation Saúl.

I first updated using apt-get and got a black screen when the 2nd person
joined. I then did a purge and reinstalled everything from scratch again
(unstable repo) and I'm still getting black screen when the 2nd person
joins (from behind the same LAN where p2p was working fine yesterday)

Firefox console:

XML Parsing Error: not well-formed
Location:
Line Number 1, Column 168:

and specially

ICE failed, add a STUN server and see about:webrtc for more details
(unknown)
[modules/xmpp/JingleSessionPC.js] <value/this.peerconnection.oniceconnectionstatechange>:
(TIME) ICE failed P2P? false: 52667.535 lib-jitsi-meet.min.js:2:161499
[conference.js] <value>: CONFERENCE FAILED: conference.setup_failed
Error: ICE fail
Stack trace:
value/this.peerconnection.oniceconnectionstatechange@htt
ps://jitsi.my.domain/libs/lib-jitsi-meet.min.js?v=2087:2:489934
r/this.peerconnection.oniceconnectionstatechange@htt
ps://jitsi.my.domain/libs/lib-jitsi-meet.min.js?v=2087:2:321633
  app.bundle.min.js:2:442688

This is on a default install without changing any configuration settings
at all...

On Fri, Jul 7, 2017 at 2:59 PM, Saúl Ibarra Corretgé < > scorretge@atlassian.com> wrote:

> On Jul 7, 2017, at 14:02, Peter Villeneuve <petervnv1@gmail.com> wrote:
>
> OK, gracias Saúl.
>
> I'll pull and try again after lunch.
>
> I assume this is the commit that fixes it?
https://github.com/jitsi/lib-jitsi-meet/commit/97d2e3452cfca
80487fd73910d6d05e9110791f2
>

Correct.

> So I should leave "useStunTurn: true" commented out and it should work
fine again?
>

Yes.

> Still confused why we need turn functionality at all when jvb already
acts as a relay. Can someone explain the thinking behind this?
>

Sure. When making 1-to-1 calls, there is no need to use all the advanced
video routing features (like simulcast for example) in the JVB. The easiest
way for disabling everything is not use the JVB in the first place for
those calls. A while ago we added a “P2P mode”, which means we’ll start a
second peer connection and try to connect directly, only if there are 2
participants.

All in all, 1-to-1 calls are a very used scenario which is worth
optimizing. This is one such optimization.

Cheers,

> Cheers
>
> On Fri, Jul 7, 2017 at 12:35 PM, Saúl Ibarra Corretgé < >> scorretge@atlassian.com> wrote:
>
> > On Jul 7, 2017, at 13:19, Peter Villeneuve <petervnv1@gmail.com> >> wrote:
> >
> > Can someone explain the new turn config options in nightly?
> >
> > On a fresh install If I don't uncomment the
> > useStunTurn: true, // use XEP-0215 to fetch STUN and TURN server
> >
> > setting in config.js then the bridge doesn't show any video at all.
If I do set that setting, then p2p works fine but then I get the ICE error
mentioned above (related to turn I believe) when a 3rd person joins.
> >
> > Should I open an ticket on github?
> >
>
> Can you pull again? That should be fixed now.
>
> > Cheers,
> > Peter
> >
> > On Thu, Jul 6, 2017 at 6:48 PM, Peter Villeneuve <petervnv1@gmail.com> >> wrote:
> > OK, I decided to upgrade to today's nightly and now I have some more
insight into what's going on.
> >
> > It seems to work fine when only 2 participants are in the room
(including freshly compiled mobile app that now seems to allow p2p too -
well done!)
> > Although the iOS app is still pretty buggy - sometimes clicking the
join button does nothing, and if you keep clicking you get a black screen,
and I've also had it crash a couple of times when starting, even after a
reboot of my iPhone 7 running 10.3.2 - I'll try to get debug logs for the
app tomorrow.
> >
> > But as soon as a 3rd person enters it stops working (I believe)
because of turn options recently added.
> >
> > In fact I see this in Chrome's console:
> >
> > [modules/xmpp/strophe.jingle.js] <>: getting turn credentials
failed <iq xmlns=​"jabber:​client" type=​"error"
> >
> > [modules/xmpp/strophe.jingle.js] <>: is mod_turncredentials or
similar installed?
> >
> > This confuses me somewhat since I thought that the bridge itself was
already working as a pseudo-turn server, so not sure why we need to use an
external Turn server with creds, etc Am I missing something in this new
config option?
> >
> > Cheers,
> > Peter
> >
> > P.S. I also see this in the console which would explain why Chrome's
audio output is forced through the system speakers on my ubuntu machine
instead of through the headset:
> >
> > [modules/settings/Settings.js] <>: Failed to set audio output device
from local storage. Default audio output device will be usedinstead.
DOMException: Requested device not found
> >
> >
> > Finally, I see a bunch of errors related to a certain select2.png and
select2-spinner.gif files that it tries to get but seem to be missing:
> >
> > select2.png:1 GET https://jitsi.my.domain/libs/select2.png 404 (Not
Found)
> >
> > jquery.min.js:4 GET https://jitsi.my.domain/libs/select2-spinner.gif
404 (Not Found)
> >
> >
> > I hope all this detailed feedback helps. I'm a big fan and have been
playing around since it was just still sip communicator, and it keeps
getting better and better.
> >
> > Cheers,
> > Peter
> >
> >
> >
> > On Thu, Jul 6, 2017 at 4:19 PM, Peter Villeneuve <petervnv1@gmail.com> >> wrote:
> > Hi,
> >
> > I just did a fresh git clone and compiled the iOS app as I had done a
few months ago.
> > Testing with meet.jit.si seems to work fine, but when I try on my
freshly built jitsi meet installation (debian testing installed yesterday)
I don't seem to get audio and video flowing at all (black screen and frozen
video).
> >
> >
> > What version is currently being deployed at meet.jit.si (stable or
testing)? I think I might go back to stable since my current installation
seems fairly buggy. Thoughts?
> >
> > What versions are most people on that are stable enough for daily use?
> >
> > Cheers,
> > Peter
> >
> >
> > _______________________________________________
> > dev mailing list
> > dev@jitsi.org
> > Unsubscribe instructions and other list options:
> > http://lists.jitsi.org/mailman/listinfo/dev
>
> --
> Saúl
>
>
> _______________________________________________
> dev mailing list
> dev@jitsi.org
> Unsubscribe instructions and other list options:
> http://lists.jitsi.org/mailman/listinfo/dev
>
> _______________________________________________
> dev mailing list
> dev@jitsi.org
> Unsubscribe instructions and other list options:
> http://lists.jitsi.org/mailman/listinfo/dev

--
Saúl

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


#9

Some dependencies are broken when I install the unstable package:

This is on a newly built debian 8 machine with all packages up to date

apt-get -y install jitsi-meet
Reading package lists... Done
Building dependency tree
Reading state information... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
jitsi-meet : Depends: jitsi-meet-web-config (= 1.0.2087-1) but it is not
going to be installed
E: Unable to correct problems, you have held broken packages.

···

On Fri, Jul 7, 2017 at 4:23 PM, Peter Villeneuve <petervnv1@gmail.com> wrote:

I'm going to reinstall debian from scratch and try again with the unstable
repo to see if there was some leftover file or setting that's messing
things up.

On Fri, Jul 7, 2017 at 4:21 PM, Peter Villeneuve <petervnv1@gmail.com> > wrote:

Thanks for the explanation Saúl.

I first updated using apt-get and got a black screen when the 2nd person
joined. I then did a purge and reinstalled everything from scratch again
(unstable repo) and I'm still getting black screen when the 2nd person
joins (from behind the same LAN where p2p was working fine yesterday)

Firefox console:

XML Parsing Error: not well-formed
Location:
Line Number 1, Column 168:

and specially

ICE failed, add a STUN server and see about:webrtc for more details
(unknown)
[modules/xmpp/JingleSessionPC.js] <value/this.peerconnection.oniceconnectionstatechange>:
(TIME) ICE failed P2P? false: 52667.535 lib-jitsi-meet.min.js:2:161499
[conference.js] <value>: CONFERENCE FAILED: conference.setup_failed
Error: ICE fail
Stack trace:
value/this.peerconnection.oniceconnectionstatechange@https:/
/jitsi.my.domain/libs/lib-jitsi-meet.min.js?v=2087:2:489934
r/this.peerconnection.oniceconnectionstatechange@https://
jitsi.my.domain/libs/lib-jitsi-meet.min.js?v=2087:2:321633
  app.bundle.min.js:2:442688

This is on a default install without changing any configuration settings
at all...

On Fri, Jul 7, 2017 at 2:59 PM, Saúl Ibarra Corretgé < >> scorretge@atlassian.com> wrote:

> On Jul 7, 2017, at 14:02, Peter Villeneuve <petervnv1@gmail.com> >>> wrote:
>
> OK, gracias Saúl.
>
> I'll pull and try again after lunch.
>
> I assume this is the commit that fixes it?
https://github.com/jitsi/lib-jitsi-meet/commit/97d2e3452cfca
80487fd73910d6d05e9110791f2
>

Correct.

> So I should leave "useStunTurn: true" commented out and it should work
fine again?
>

Yes.

> Still confused why we need turn functionality at all when jvb already
acts as a relay. Can someone explain the thinking behind this?
>

Sure. When making 1-to-1 calls, there is no need to use all the advanced
video routing features (like simulcast for example) in the JVB. The easiest
way for disabling everything is not use the JVB in the first place for
those calls. A while ago we added a “P2P mode”, which means we’ll start a
second peer connection and try to connect directly, only if there are 2
participants.

All in all, 1-to-1 calls are a very used scenario which is worth
optimizing. This is one such optimization.

Cheers,

> Cheers
>
> On Fri, Jul 7, 2017 at 12:35 PM, Saúl Ibarra Corretgé < >>> scorretge@atlassian.com> wrote:
>
> > On Jul 7, 2017, at 13:19, Peter Villeneuve <petervnv1@gmail.com> >>> wrote:
> >
> > Can someone explain the new turn config options in nightly?
> >
> > On a fresh install If I don't uncomment the
> > useStunTurn: true, // use XEP-0215 to fetch STUN and TURN server
> >
> > setting in config.js then the bridge doesn't show any video at all.
If I do set that setting, then p2p works fine but then I get the ICE error
mentioned above (related to turn I believe) when a 3rd person joins.
> >
> > Should I open an ticket on github?
> >
>
> Can you pull again? That should be fixed now.
>
> > Cheers,
> > Peter
> >
> > On Thu, Jul 6, 2017 at 6:48 PM, Peter Villeneuve < >>> petervnv1@gmail.com> wrote:
> > OK, I decided to upgrade to today's nightly and now I have some more
insight into what's going on.
> >
> > It seems to work fine when only 2 participants are in the room
(including freshly compiled mobile app that now seems to allow p2p too -
well done!)
> > Although the iOS app is still pretty buggy - sometimes clicking the
join button does nothing, and if you keep clicking you get a black screen,
and I've also had it crash a couple of times when starting, even after a
reboot of my iPhone 7 running 10.3.2 - I'll try to get debug logs for the
app tomorrow.
> >
> > But as soon as a 3rd person enters it stops working (I believe)
because of turn options recently added.
> >
> > In fact I see this in Chrome's console:
> >
> > [modules/xmpp/strophe.jingle.js] <>: getting turn credentials
failed <iq xmlns=​"jabber:​client" type=​"error"
> >
> > [modules/xmpp/strophe.jingle.js] <>: is mod_turncredentials or
similar installed?
> >
> > This confuses me somewhat since I thought that the bridge itself was
already working as a pseudo-turn server, so not sure why we need to use an
external Turn server with creds, etc Am I missing something in this new
config option?
> >
> > Cheers,
> > Peter
> >
> > P.S. I also see this in the console which would explain why Chrome's
audio output is forced through the system speakers on my ubuntu machine
instead of through the headset:
> >
> > [modules/settings/Settings.js] <>: Failed to set audio output
device from local storage. Default audio output device will be usedinstead.
DOMException: Requested device not found
> >
> >
> > Finally, I see a bunch of errors related to a certain select2.png
and select2-spinner.gif files that it tries to get but seem to be missing:
> >
> > select2.png:1 GET https://jitsi.my.domain/libs/select2.png 404 (Not
Found)
> >
> > jquery.min.js:4 GET https://jitsi.my.domain/libs/select2-spinner.gif
404 (Not Found)
> >
> >
> > I hope all this detailed feedback helps. I'm a big fan and have been
playing around since it was just still sip communicator, and it keeps
getting better and better.
> >
> > Cheers,
> > Peter
> >
> >
> >
> > On Thu, Jul 6, 2017 at 4:19 PM, Peter Villeneuve < >>> petervnv1@gmail.com> wrote:
> > Hi,
> >
> > I just did a fresh git clone and compiled the iOS app as I had done
a few months ago.
> > Testing with meet.jit.si seems to work fine, but when I try on my
freshly built jitsi meet installation (debian testing installed yesterday)
I don't seem to get audio and video flowing at all (black screen and frozen
video).
> >
> >
> > What version is currently being deployed at meet.jit.si (stable or
testing)? I think I might go back to stable since my current installation
seems fairly buggy. Thoughts?
> >
> > What versions are most people on that are stable enough for daily
use?
> >
> > Cheers,
> > Peter
> >
> >
> > _______________________________________________
> > dev mailing list
> > dev@jitsi.org
> > Unsubscribe instructions and other list options:
> > http://lists.jitsi.org/mailman/listinfo/dev
>
> --
> Saúl
>
>
> _______________________________________________
> dev mailing list
> dev@jitsi.org
> Unsubscribe instructions and other list options:
> http://lists.jitsi.org/mailman/listinfo/dev
>
> _______________________________________________
> dev mailing list
> dev@jitsi.org
> Unsubscribe instructions and other list options:
> http://lists.jitsi.org/mailman/listinfo/dev

--
Saúl

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


#10

That is strange, the only explanation I have is hitting the server in
the moment that version was uploading. Can you try again?
apt-get udpate
apt-get install jitsi-meet

···

On Fri, Jul 7, 2017 at 11:18 AM, Peter Villeneuve <petervnv1@gmail.com> wrote:

Some dependencies are broken when I install the unstable package:

This is on a newly built debian 8 machine with all packages up to date

apt-get -y install jitsi-meet
Reading package lists... Done
Building dependency tree
Reading state information... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
jitsi-meet : Depends: jitsi-meet-web-config (= 1.0.2087-1) but it is not
going to be installed
E: Unable to correct problems, you have held broken packages.

On Fri, Jul 7, 2017 at 4:23 PM, Peter Villeneuve <petervnv1@gmail.com> > wrote:

I'm going to reinstall debian from scratch and try again with the unstable
repo to see if there was some leftover file or setting that's messing things
up.

On Fri, Jul 7, 2017 at 4:21 PM, Peter Villeneuve <petervnv1@gmail.com> >> wrote:

Thanks for the explanation Saúl.

I first updated using apt-get and got a black screen when the 2nd person
joined. I then did a purge and reinstalled everything from scratch again
(unstable repo) and I'm still getting black screen when the 2nd person joins
(from behind the same LAN where p2p was working fine yesterday)

Firefox console:

XML Parsing Error: not well-formed
Location:
Line Number 1, Column 168:

and specially

ICE failed, add a STUN server and see about:webrtc for more details
(unknown)
[modules/xmpp/JingleSessionPC.js]
<value/this.peerconnection.oniceconnectionstatechange>: (TIME) ICE failed
P2P? false: 52667.535 lib-jitsi-meet.min.js:2:161499
[conference.js] <value>: CONFERENCE FAILED: conference.setup_failed
Error: ICE fail
Stack trace:

value/this.peerconnection.oniceconnectionstatechange@https://jitsi.my.domain/libs/lib-jitsi-meet.min.js?v=2087:2:489934

r/this.peerconnection.oniceconnectionstatechange@https://jitsi.my.domain/libs/lib-jitsi-meet.min.js?v=2087:2:321633
  app.bundle.min.js:2:442688

This is on a default install without changing any configuration settings
at all...

On Fri, Jul 7, 2017 at 2:59 PM, Saúl Ibarra Corretgé >>> <scorretge@atlassian.com> wrote:

> On Jul 7, 2017, at 14:02, Peter Villeneuve <petervnv1@gmail.com> >>>> > wrote:
>
> OK, gracias Saúl.
>
> I'll pull and try again after lunch.
>
> I assume this is the commit that fixes it?
> https://github.com/jitsi/lib-jitsi-meet/commit/97d2e3452cfca80487fd73910d6d05e9110791f2
>

Correct.

> So I should leave "useStunTurn: true" commented out and it should work
> fine again?
>

Yes.

> Still confused why we need turn functionality at all when jvb already
> acts as a relay. Can someone explain the thinking behind this?
>

Sure. When making 1-to-1 calls, there is no need to use all the advanced
video routing features (like simulcast for example) in the JVB. The easiest
way for disabling everything is not use the JVB in the first place for those
calls. A while ago we added a “P2P mode”, which means we’ll start a second
peer connection and try to connect directly, only if there are 2
participants.

All in all, 1-to-1 calls are a very used scenario which is worth
optimizing. This is one such optimization.

Cheers,

> Cheers
>
> On Fri, Jul 7, 2017 at 12:35 PM, Saúl Ibarra Corretgé >>>> > <scorretge@atlassian.com> wrote:
>
> > On Jul 7, 2017, at 13:19, Peter Villeneuve <petervnv1@gmail.com> >>>> > > wrote:
> >
> > Can someone explain the new turn config options in nightly?
> >
> > On a fresh install If I don't uncomment the
> > useStunTurn: true, // use XEP-0215 to fetch STUN and TURN server
> >
> > setting in config.js then the bridge doesn't show any video at all.
> > If I do set that setting, then p2p works fine but then I get the ICE error
> > mentioned above (related to turn I believe) when a 3rd person joins.
> >
> > Should I open an ticket on github?
> >
>
> Can you pull again? That should be fixed now.
>
> > Cheers,
> > Peter
> >
> > On Thu, Jul 6, 2017 at 6:48 PM, Peter Villeneuve >>>> > > <petervnv1@gmail.com> wrote:
> > OK, I decided to upgrade to today's nightly and now I have some more
> > insight into what's going on.
> >
> > It seems to work fine when only 2 participants are in the room
> > (including freshly compiled mobile app that now seems to allow p2p too -
> > well done!)
> > Although the iOS app is still pretty buggy - sometimes clicking the
> > join button does nothing, and if you keep clicking you get a black screen,
> > and I've also had it crash a couple of times when starting, even after a
> > reboot of my iPhone 7 running 10.3.2 - I'll try to get debug logs for the
> > app tomorrow.
> >
> > But as soon as a 3rd person enters it stops working (I believe)
> > because of turn options recently added.
> >
> > In fact I see this in Chrome's console:
> >
> > [modules/xmpp/strophe.jingle.js] <>: getting turn credentials
> > failed <iq xmlns="jabber:client" type="error"
> >
> > [modules/xmpp/strophe.jingle.js] <>: is mod_turncredentials or
> > similar installed?
> >
> > This confuses me somewhat since I thought that the bridge itself was
> > already working as a pseudo-turn server, so not sure why we need to use an
> > external Turn server with creds, etc Am I missing something in this new
> > config option?
> >
> > Cheers,
> > Peter
> >
> > P.S. I also see this in the console which would explain why Chrome's
> > audio output is forced through the system speakers on my ubuntu machine
> > instead of through the headset:
> >
> > [modules/settings/Settings.js] <>: Failed to set audio output
> > device from local storage. Default audio output device will be usedinstead.
> > DOMException: Requested device not found
> >
> >
> > Finally, I see a bunch of errors related to a certain select2.png
> > and select2-spinner.gif files that it tries to get but seem to be missing:
> >
> > select2.png:1 GET https://jitsi.my.domain/libs/select2.png 404 (Not
> > Found)
> >
> > jquery.min.js:4 GET https://jitsi.my.domain/libs/select2-spinner.gif
> > 404 (Not Found)
> >
> >
> > I hope all this detailed feedback helps. I'm a big fan and have been
> > playing around since it was just still sip communicator, and it keeps
> > getting better and better.
> >
> > Cheers,
> > Peter
> >
> >
> >
> > On Thu, Jul 6, 2017 at 4:19 PM, Peter Villeneuve >>>> > > <petervnv1@gmail.com> wrote:
> > Hi,
> >
> > I just did a fresh git clone and compiled the iOS app as I had done
> > a few months ago.
> > Testing with meet.jit.si seems to work fine, but when I try on my
> > freshly built jitsi meet installation (debian testing installed yesterday) I
> > don't seem to get audio and video flowing at all (black screen and frozen
> > video).
> >
> >
> > What version is currently being deployed at meet.jit.si (stable or
> > testing)? I think I might go back to stable since my current installation
> > seems fairly buggy. Thoughts?
> >
> > What versions are most people on that are stable enough for daily
> > use?
> >
> > Cheers,
> > Peter
> >
> >
> > _______________________________________________
> > dev mailing list
> > dev@jitsi.org
> > Unsubscribe instructions and other list options:
> > http://lists.jitsi.org/mailman/listinfo/dev
>
> --
> Saúl
>
>
> _______________________________________________
> dev mailing list
> dev@jitsi.org
> Unsubscribe instructions and other list options:
> http://lists.jitsi.org/mailman/listinfo/dev
>
> _______________________________________________
> dev mailing list
> dev@jitsi.org
> Unsubscribe instructions and other list options:
> http://lists.jitsi.org/mailman/listinfo/dev

--
Saúl

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

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