[jitsi-users] Viable for deployment - advice


#1

Hello Jitsi user base!

I've been spending the last week looking at various XMPP servers and
clients, and I've spent some time reading parts of the OReilly book on
XMPP.

I'm potentially looking to deploy as an alternative to MS Lync in a UK
company of around 200 persons.

I have come up with a lot of questions, mostly around getting the majority
of features working in Jitsi.

At the moment I've been basicly guessing which components might work the
best with Jitsi based off my own research and guesswork with regards to
comments I've seen throughout the website. And any advise for a complete
stack of components that should work well would be great advice.

Now I have an ejabberd server (I've also tried out Openfire and
Prosody) running on a personal server not related to the company I work
for, this is to serve as my own personal experimentation before (if) I
present XMPP and Jisti as a possible solution.

I've set up and have connected the Jitsi Video bridge, and maybe its
working (I havn't had much success). I also have setup and connected the
Jingle Nodes extension, and maybe its working (I dont even know how to
tell).

I have the STUN module of ejabberd enabled. The server is public on the
internet (registration disabled).

So on to my problems...

So far the majority of video/voice calls seem to fail to connect with an
ICE failure, except if both devices are on the same network, and then it
sometimes works. I presume I need to setup a TURN server? and I am
uncertain of what ICE actually is (I guess I should read the RFC) in
addition to the STUN/TURN setup.

The Jitsi bridge is running and connected to ejabberd, and the option is
now enabled in the Jitsi client, however I continually get ICE failures
regardless of the locality of the clients when i try to use the video
bridge.

Presuming that my problems stem from NAT traversal (or lack there of). I
was wondering if there was any advice in regard to using a TURN server (and
whatever the rest of the ICE stack is), with ejabberd or whichever XMPP
server the community would recommend.

Apart from selecting an external TURN server, part of my problem in
understand the TURN server is how a client would authenticate with the
server based on service auto discovery (via DNS?), after an IRC
conversation it was suggested that XEP-0215 might be used to provide user
credentials, another option is that when deployed the client settings for
TURN could be provided via auto provisioning services.

After seeing your jitsi meet demonstrations on youtube, I was excited to
use it to present my proposal to use Jitsi and XMPP to people at work,
(hoping to provide a wow factor as well as being just damn useful) however
I had very little success when trying it at home between my desktop and my
laptop using https://meet.jit.si both clients using the latest version of
chrome, although they both manage to connect and work for a while, I found
that my laptop would continually loose the video stream and i couldnt seem
toget audio out from the laptop either, it was pretty much unworkable,
restarting one or the other clients would resolve the video issue for a
little while. I understand its very much a work in progress, but do you
expect it to be more stable than this?

Finally, the Jitsi client doesnt seem to want to detect my camera (either
the current nightly or the stable of the windows x64 build), is there a
limited support for cameras at the moment?

Sorry for bundling many subjects and questions into one post, and thanks you
in advance for help you can provide, and to those who develop Jitsi, XMPP,
XMPP servers and components.

Paul Grove


#2

Hey Paul,

Hello Jitsi user base!

I've been spending the last week looking at various XMPP servers and
clients, and I've spent some time reading parts of the OReilly book on
XMPP.

Way to go!

I'm potentially looking to deploy as an alternative to MS Lync in a UK
company of around 200 persons.

Depending on what you'd like to have at the end XMPP may be enough or you may want to have a combination of XMPP and SIP (CUSAX) as described here:

http://tools.ietf.org/html/rfc7081
https://jitsi.org/cusax

I have come up with a lot of questions, mostly around getting the majority
of features working in Jitsi.

At the moment I've been basicly guessing which components might work the
best with Jitsi based off my own research and guesswork with regards to
comments I've seen throughout the website. And any advise for a complete
stack of components that should work well would be great advice.

We often use Jitsi with Openfire and Asterisk or FreeSWITCH.

Now I have an ejabberd server (I've also tried out Openfire and
Prosody) running on a personal server not related to the company I work
for, this is to serve as my own personal experimentation before (if) I
present XMPP and Jisti as a possible solution.

I've set up and have connected the Jitsi Video bridge, and maybe its
working (I havn't had much success).

We currently recommender using Jitsi Videobridge primarily within the context of Jitsi Meet ( https://jitsi.org/meet )

I also have setup and connected the
Jingle Nodes extension, and maybe its working (I dont even know how to
tell).

Personally, I don't have any experience running Jingle Nodes on ejabberd with Jitsi. The Openfire plugin on the other hand runs quite nicely.

I have the STUN module of ejabberd enabled. The server is public on the
internet (registration disabled).

So on to my problems...

So far the majority of video/voice calls seem to fail to connect with an
ICE failure, except if both devices are on the same network, and then it
sometimes works. I presume I need to setup a TURN server?

No, the role of a Jingle Node relay is exactly the same.

and I am
uncertain of what ICE actually is (I guess I should read the RFC) in
addition to the STUN/TURN setup.

The RFC is indeed very readable (especially the intro parts) but the idea behind ICE is to basically attempt connecting using all possibilities (local addresses, public ones obtained from STUN, UPnP ones, Jingle Nodes, TURN servers, etc.). If none of these work, ICE is considered to have failed.

The Jitsi bridge is running and connected to ejabberd, and the option is
now enabled in the Jitsi client, however I continually get ICE failures
regardless of the locality of the clients when i try to use the video
bridge.

Your clients have to be capable to freely exchange UDP with addresses outside your network. Can you verify this?

Presuming that my problems stem from NAT traversal (or lack there of). I
was wondering if there was any advice in regard to using a TURN server (and
whatever the rest of the ICE stack is), with ejabberd or whichever XMPP
server the community would recommend.

I'd recommend that you try using Openfire with the integrated Jingle Node relay.

Apart from selecting an external TURN server, part of my problem in
understand the TURN server is how a client would authenticate with the
server based on service auto discovery (via DNS?),

If we discover a TURN server through DNS we try to authenticate using the same credentials as the ones you connected to your XMPP server with. You can also explicitly configure them in the account config.

after an IRC
conversation it was suggested that XEP-0215 might be used to provide user
credentials, another option is that when deployed the client settings for
TURN could be provided via auto provisioning services.

This is something that Jitsi Meet supports but that the Jitsi client does NOT.

After seeing your jitsi meet demonstrations on youtube, I was excited to
use it to present my proposal to use Jitsi and XMPP to people at work,
(hoping to provide a wow factor as well as being just damn useful) however
I had very little success when trying it at home between my desktop and my
laptop using https://meet.jit.si both clients using the latest version of
chrome, although they both manage to connect and work for a while, I found
that my laptop would continually loose the video stream and i couldnt seem
toget audio out from the laptop either, it was pretty much unworkable,
restarting one or the other clients would resolve the video issue for a
little while. I understand its very much a work in progress, but do you
expect it to be more stable than this?

It's actually very stable now and issues like this one are rare. Could you please tell us more about your deployment? OS, network?

The video problem above is indeed something we see every now and then but we are not yet sure if it's a Chrome or a Jitsi issue.

I suspect that the audio problem is more related to Chrome not picking up the right audio device to use. Try looking in that direction.

Finally, the Jitsi client doesnt seem to want to detect my camera (either
the current nightly or the stable of the windows x64 build), is there a
limited support for cameras at the moment?

Quite rarely but it's not impossible. What kind of web cam are you using?

Emil

···

On 17.04.14, 00:04, Paul Grove wrote:

Sorry for bundling many subjects and questions into one post, and thanks
you
in advance for help you can provide, and to those who develop Jitsi, XMPP,
XMPP servers and components.

Paul Grove

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

--
https://jitsi.org


#3

Thanks for the great reply,

We will look into using SIP in Jitsi
as well, we already have Asterisk.

I will try out Openfire more
thoroughly. My choice of ejabberd was purely based on a perceived
popularity.

I have read the introduction (second 2) in the RFC for
ICE, and your right - its very clear.

I'll stick to Jingle Nodes for
now, and not worry about a STUN/TURN service.

Although I'm a bit of a
Linux guy, I've been testing the jitsi client in x64 windows 7 as that's
the company policy.

I have a VM in the office, but mostly my
experiments were at home, behind a simple nat with all traffic allowed
outbound through the firewall.

I havn't currently deployed Jitsi Meet,
I was just using https://meet.jit.si to play with it. The laptop that
experienced the majority of problems with Jitsi Meet was on Wifi, but it
was in good range, and although unmeasured, seemed to be accomplishing a
decent bandwidth (I downloaded the Jitsi Client over wifi very quickly).

The video (works at first, then stops) issue seemed to happen
frequently, and easy to reproduce (at least is was last night), if I can
continue to reproduce it, would I be able to help in any way?

I tried
Jitsi Meet in the office today, and it worked very well, so perhaps its
related to my home network somehow - I can look in to it.

As for the
webcam (which was undetected in the Jitsi), it was admittedly a bit of
an odd one, I was using a Playstation Eye using these drivers:
http://codelaboratories.com/products/eye/driver/

I have 4 of them, I
bought them for 2 quid each a while back, and they usually work well
enough, so I've never bought a better webcam, they are detected in
Chrome (therefore jitsi meet works with it), and in other applications -
such as skype.

Thank again Emil, I have plenty to work on now.

Regards,

Paul

Hey

Paul,

Hello Jitsi user

base! I've been spending the last week looking at various XMPP servers
and clients, and I've spent some time reading parts of the OReilly book
on XMPP.

Way to go!

I'm potentially looking to deploy as an

alternative to MS Lync in a UK company of around 200 persons.

Depending on what you'd like to have at the end XMPP may be enough or

you may want to have a combination of XMPP and SIP (CUSAX) as described

here:

http://tools.ietf.org/html/rfc7081 [3]

https://jitsi.org/cusax [4]

Now I have an ejabberd server (I've also

tried out Openfire and Prosody) running on a personal server n

nt

XMPP and Jisti as a possible solution. I've set up and have connected
the Jitsi Video bridge, and maybe its working (I havn't had much
success).

We currently recommender using Jitsi Videobridge

primarily within the

context of Jitsi Meet ( https://jitsi.org/meet

[1])

ft:5px; border-left:#1010ff 2px solid; margin-left:5px;

width:100%">I also have setup and connected the Jingle Nodes extension,
and maybe its working (I dont even know how to tell).

Personally,

I don't have any experience running Jingle Nodes on ejabberd

with

Jitsi. The Openfire plugin on> f 2px solid; margin-left:5px;
width:100%">I have the STUN module of ejabberd enabled. The server is
public on the

gistration disabled). So on to my problems... So far the

majority of video/voice calls seem to fail to connect with an ICE
failure, except if both devices are on the same network, and then it
sometimes works. I presume I need to setup a TURN server?

No, the

role of a Jingle Node relay is exactly the same.

I am uncertain of

what ICE actually is (I guess I should read the RFC) in addition to the
STUN/TURN setup.

The RFC is indeed very readable (especially the

intro parts) but the idea behind ICE is to basically attempt connecting
using all possibilities (local addresses, public ones obtained from
STUN, UPnP o

odes, TURN servers, etc.). If none of these work, ICE is

considered to have failed. my camera (either the current nightly or the
stable of the windows x64 build), is there a limited support for cameras
at the moment?

Quite rarely but it's not impossible. What kind

of web cam are you using?

Emil
Sorry for bundling many

subjects and questions into one post, and thanks you in advance for help
you can provide, and to those who develop Jitsi, XMPP, XMPP servers and
components. Paul Grove _______________________________________________
users mailing list users@jitsi.org [2] Unsubscribe instructions and
other list options: http://lists.jitsi.org/mailman/listin

/blockquote>

Links:

···

On 17-04-2014 14:04, Emil Ivov wrote:

On 17.04.14, 00:04, Paul Grove wrote:

------
[1]
https://jitsi.org/meet
[2] mailto:users@jitsi.org
[3]
http://tools.ietf.org/html/rfc7081
[4] https://jitsi.org/cusax