[jitsi-users] A demo video: WebRTC, Jitsi Videobridge and COLIBRI


#1

Hey all,

A few of use have just created a sample video showing Jitsi Videobridge and WebRTC in action. You can check it out here:

For those of you who haven't had the chance to learn about the bridge yet, it acts as a video relay or, more preciesely, a Selective Forwarding Unit (SFU), that mixes audio but keeps video streams separated when forwarding them to all participants in a conference call.

This allows for a great scalability potential contrary to other approaches like full mesh conferences or content/composite mixing.

The reason you are seeing a burst of Jitsi Videobridge related posts lately is because we have recently made it compatible with WebRTC by adding to it DTLS and ICE support (kudos to Lyubomir Marinov). This means that it can now be used to build video conferences in a web page like the video above shows.

The actual JavaScript application in the video (which we will make publicly available very soon) is built by Philipp Hancke from Estos. It uses the COLIBRI XMPP protocol extension ( https://jitsi.org/colibri ) to control the Jitsi Videobridge. It also uses XMPP Multi-User Chats (MUCs) to keep track of and control participants.

All in all this makes for a very neat project and a completely open alternative to Google Hangouts.

You will very likely be hearing more about this in the following days and weeks.

Cheers,
Emil

···

--
https://jitsi.org


#2

Cool! It certainly removes a bunch of barriers to entry:
* Users access via web browser (often already installed)
* Users do not even need to register an account to the website

Any plans to support Firefox and other browsers? It looks like it is
Chrome only at the moment.

Also, any plans to migrate away from the ajax.googleapis.com (for privacy).

David

···

On 12/8/2013 4:22 AM, Emil Ivov wrote:

Hey all,

A few of use have just created a sample video showing Jitsi
Videobridge and WebRTC in action. You can check it out here:

http://goo.gl/nS1b7H


#3

I really, really like the progress this has made and maybe the VUC will
start using this soon!

One thing that google hangouts also has is the ability to make phone calls
out. If not already possible, will it be integrated to make a phone call
out on a particular SIP account?


#4

Currently I get a 404 Not Found error on browsers other than Chrome.
On Firefox it redirects to: https://meet.jit.si/chromeonly.html
On Internet Explorer it redirects to:
https://meet.jit.si/webrtcrequired.html

Could you add a simple HTML page that says, "meet.jit.si currently works
with ..." (with links to browsers that work, maybe Chrome, Chronium?,
Opera?)

David

···

On 12/8/2013 4:22 AM, Emil Ivov wrote:

A few of use have just created a sample video showing Jitsi
Videobridge and WebRTC in action. You can check it out here:

http://goo.gl/nS1b7H


#5

This is a great presentation !
Thank you for the update.

I'm sure after having the JS application shared, we will see further
improvement (Such as half full screen if 2 videos peers, quarter a screen
if 4 ppl, etc...)

In term of encryption, any post related to, for me to learn more?

Thank you

···

On 8 December 2013 18:22, Emil Ivov <emcho@jitsi.org> wrote:

Hey all,

A few of use have just created a sample video showing Jitsi Videobridge
and WebRTC in action. You can check it out here:

http://goo.gl/nS1b7H

For those of you who haven't had the chance to learn about the bridge yet,
it acts as a video relay or, more preciesely, a Selective Forwarding Unit
(SFU), that mixes audio but keeps video streams separated when forwarding
them to all participants in a conference call.

This allows for a great scalability potential contrary to other approaches
like full mesh conferences or content/composite mixing.

The reason you are seeing a burst of Jitsi Videobridge related posts
lately is because we have recently made it compatible with WebRTC by adding
to it DTLS and ICE support (kudos to Lyubomir Marinov). This means that it
can now be used to build video conferences in a web page like the video
above shows.

The actual JavaScript application in the video (which we will make
publicly available very soon) is built by Philipp Hancke from Estos. It
uses the COLIBRI XMPP protocol extension ( https://jitsi.org/colibri ) to
control the Jitsi Videobridge. It also uses XMPP Multi-User Chats (MUCs) to
keep track of and control participants.

All in all this makes for a very neat project and a completely open
alternative to Google Hangouts.

You will very likely be hearing more about this in the following days and
weeks.

Cheers,
Emil

--
https://jitsi.org

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


#6

Hi Emil,

One extremely odd thing to report...

Replication steps:

0. open chrome on your internet browser chrome
1. go to meet.jit.si
2. copy meeting ID
3. send to android phone via push button so you don't have to type 16
character room ID
4. once link is received on phone, open up link in chrome internet browser
5. do you have one or twe video streams?

I would expect there to be two video streams on both the android phone and
the website on the desktop.

Can anyone else replicate this?

Thanks,
Jungle

···

On 8 December 2013 02:22, Emil Ivov <emcho@jitsi.org> wrote:

Hey all,

A few of use have just created a sample video showing Jitsi Videobridge
and WebRTC in action. You can check it out here:

http://goo.gl/nS1b7H

For those of you who haven't had the chance to learn about the bridge yet,
it acts as a video relay or, more preciesely, a Selective Forwarding Unit
(SFU), that mixes audio but keeps video streams separated when forwarding
them to all participants in a conference call.

This allows for a great scalability potential contrary to other approaches
like full mesh conferences or content/composite mixing.

The reason you are seeing a burst of Jitsi Videobridge related posts
lately is because we have recently made it compatible with WebRTC by adding
to it DTLS and ICE support (kudos to Lyubomir Marinov). This means that it
can now be used to build video conferences in a web page like the video
above shows.

The actual JavaScript application in the video (which we will make
publicly available very soon) is built by Philipp Hancke from Estos. It
uses the COLIBRI XMPP protocol extension ( https://jitsi.org/colibri ) to
control the Jitsi Videobridge. It also uses XMPP Multi-User Chats (MUCs) to
keep track of and control participants.

All in all this makes for a very neat project and a completely open
alternative to Google Hangouts.

You will very likely be hearing more about this in the following days and
weeks.

Cheers,
Emil

--
https://jitsi.org

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

--
-------
inum: 883510009902611
sip: jungleboogie@sip2sip.info
xmpp: jungle-boogie@jit.si


#7

Folks

I have tried meet.jit.si. Sometimes the video bridge works, sometimes
not. For example, I just tried it on Chrome from Linux to Windows--the
other party could hear me, see me, and we could chat. But his video
didn't work. I couldn't see him.

When I tried it between three computers on the same network, two
connections worked, the third one did not.

Suggestions?

Paul

···

El dom, 08-12-2013 a las 11:22 +0100, Emil Ivov escribió:

Hey all,

A few of use have just created a sample video showing Jitsi Videobridge
and WebRTC in action. You can check it out here:

http://goo.gl/nS1b7H

For those of you who haven't had the chance to learn about the bridge
yet, it acts as a video relay or, more preciesely, a Selective
Forwarding Unit (SFU), that mixes audio but keeps video streams
separated when forwarding them to all participants in a conference call.

This allows for a great scalability potential contrary to other
approaches like full mesh conferences or content/composite mixing.

The reason you are seeing a burst of Jitsi Videobridge related posts
lately is because we have recently made it compatible with WebRTC by
adding to it DTLS and ICE support (kudos to Lyubomir Marinov). This
means that it can now be used to build video conferences in a web page
like the video above shows.

The actual JavaScript application in the video (which we will make
publicly available very soon) is built by Philipp Hancke from Estos. It
uses the COLIBRI XMPP protocol extension ( https://jitsi.org/colibri )
to control the Jitsi Videobridge. It also uses XMPP Multi-User Chats
(MUCs) to keep track of and control participants.

All in all this makes for a very neat project and a completely open
alternative to Google Hangouts.

You will very likely be hearing more about this in the following days
and weeks.

Cheers,
Emil


#8

This is a great presentation !
Thank you for the update.

I'm sure after having the JS application shared, we will see further
improvement (Such as half full screen if 2 videos peers, quarter a screen
if 4 ppl, etc...)

The basic client code was committed yesterday in
https://github.com/ESTOS/strophe.jingle/commit/f50911516801ec3d7c3645c369e0a8a8d08f3379
and also in
https://github.com/legastero/jingle-interop-demos
I am pretty sure that Lance Stout will soon follow with stanza.io.

What is still missing is the actual colibri implementation in Javascript. I'm cleaning that up currently, watch https://github.com/ESTOS/colibri.js closely.
The way I currently implemented this is a participating focus. However, I would note that you don't need the colibri implementation in Javascript because this could easily be implemented as a bot inside a Multi-User Chatroom or even part of the chatroom itself.

I think it's still possible to hide all those gritty xmppish details under a nice API such as simplewebrtc.com. I already replaced the non-standard signalling of simplewebrtc with standard jingle for https://gowebrtc.me so I am pretty sure the same can be done for the colibri stuff.

In term of encryption, any post related to, for me to learn more?

DTLS-SRTP. Actually, the DTLS session is always between client and bridge, so make sure you trust the bridge :wink:

···

Am 08.12.2013 13:34, schrieb Dudumomo:


#9

Hey all,

A few of use have just created a sample video showing Jitsi
Videobridge and WebRTC in action. You can check it out here:

http://goo.gl/nS1b7H

Cool! It certainly removes a bunch of barriers to entry:
* Users access via web browser (often already installed)
* Users do not even need to register an account to the website

Any plans to support Firefox and other browsers? It looks like it is
Chrome only at the moment.

It is but that question is best asked to Firefox and other browsers. While Firefox have basic support for WebRTC they are still unable to handle multiple streams.

They should be working on that because, they were quite active while advocating for a specific approach to multi-stream handling on the IETF.

Other browsers have yet to officially announce their exact policies concerning WebRTC support.

Also, any plans to migrate away from the ajax.googleapis.com (for privacy).

You mean: would we use a different copy of jquery? I suppose we could, if need be. Although if you are really worried about privacy, you should just use Jitsi (and we'll have a number of very important modifications coming there as well, so the barriers wouldn't be that different)

Emil

···

On 09.12.13, 00:44, David Bolton wrote:

On 12/8/2013 4:22 AM, Emil Ivov wrote:

--
https://jitsi.org


#10

I really, really like the progress this has made and maybe the VUC will
start using this soon!

One thing that google hangouts also has is the ability to make phone
calls out. If not already possible, will it be integrated to make a
phone call out on a particular SIP account?

Definitely some day. Not an immediate goal though. Priorities priorities :slight_smile:

Emil

···

On 09.12.13, 02:44, jungleboogie0 wrote:

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

--
https://jitsi.org


#11

Hey Jungle,

We haven't yet had the time to look into Android support. So far it seems that Chrome for Android might be lacking some aspects of WebRTC support.

Emil

···

On 09.12.13, 22:32, jungleboogie0 wrote:

Hi Emil,

One extremely odd thing to report...

Replication steps:

0. open chrome on your internet browser chrome
1. go to meet.jit.si <http://meet.jit.si>
2. copy meeting ID
3. send to android phone via push button so you don't have to type 16
character room ID
4. once link is received on phone, open up link in chrome internet browser
5. do you have one or twe video streams?

I would expect there to be two video streams on both the android phone
and the website on the desktop.

Can anyone else replicate this?

Thanks,
Jungle

On 8 December 2013 02:22, Emil Ivov <emcho@jitsi.org > <mailto:emcho@jitsi.org>> wrote:

    Hey all,

    A few of use have just created a sample video showing Jitsi
    Videobridge and WebRTC in action. You can check it out here:

    http://goo.gl/nS1b7H

    For those of you who haven't had the chance to learn about the
    bridge yet, it acts as a video relay or, more preciesely, a
    Selective Forwarding Unit (SFU), that mixes audio but keeps video
    streams separated when forwarding them to all participants in a
    conference call.

    This allows for a great scalability potential contrary to other
    approaches like full mesh conferences or content/composite mixing.

    The reason you are seeing a burst of Jitsi Videobridge related posts
    lately is because we have recently made it compatible with WebRTC by
    adding to it DTLS and ICE support (kudos to Lyubomir Marinov). This
    means that it can now be used to build video conferences in a web
    page like the video above shows.

    The actual JavaScript application in the video (which we will make
    publicly available very soon) is built by Philipp Hancke from Estos.
    It uses the COLIBRI XMPP protocol extension (
    https://jitsi.org/colibri ) to control the Jitsi Videobridge. It
    also uses XMPP Multi-User Chats (MUCs) to keep track of and control
    participants.

    All in all this makes for a very neat project and a completely open
    alternative to Google Hangouts.

    You will very likely be hearing more about this in the following
    days and weeks.

    Cheers,
    Emil

    --
    https://jitsi.org

    _________________________________________________
    users mailing list
    users@jitsi.org <mailto:users@jitsi.org>
    Unsubscribe instructions and other list options:
    http://lists.jitsi.org/__mailman/listinfo/users
    <http://lists.jitsi.org/mailman/listinfo/users>

--
-------
inum: 883510009902611
sip: jungleboogie@sip2sip.info <mailto:jungleboogie@sip2sip.info>
xmpp: jungle-boogie@jit.si <mailto:jungle-boogie@jit.si>

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

--
https://jitsi.org


#12

I've been having problems on linux for a while (amazingly not on windows). I think I just fixed that with
https://github.com/ESTOS/meet/commit/db7bb50d2841011f832d37cdd0bedfe3c140e397
Yana: can you merge and deploy that?

This seems to be a bug in chrome 31 with respect to DTLS roles... apparently to be fixed in canary, so I'm still looking for the respective ticket.

I hope that increases the success rate :-/

···

Am 01.01.2014 00:27, schrieb Carola y Pablo:

Folks

I have tried meet.jit.si. Sometimes the video bridge works, sometimes
not. For example, I just tried it on Chrome from Linux to Windows--the
other party could hear me, see me, and we could chat. But his video
didn't work. I couldn't see him.


#13

[...]

It is but that question is best asked to Firefox and other browsers.
While Firefox have basic support for WebRTC they are still unable to
handle multiple streams.

Yep, I suppose we can make mixed audio work nonetheless and check that 1-1 relayed via the bridge works.

[...]

Also, any plans to migrate away from the ajax.googleapis.com (for
privacy).

You mean: would we use a different copy of jquery? I suppose we could,
if need be. Although if you are really worried about privacy, you should
just use Jitsi (and we'll have a number of very important modifications
coming there as well, so the barriers wouldn't be that different)

Oh, you can run your own instance soon. It's using jquery from a CDN just for ease of deployment.


#14

Dear Jitsi community,

This is a huge development.

Congratulations to all people involved in making this happen.

So, I couldn't resist and did a few trials.

The first observation is that the setup is entirely hassle-free,
which beats Hangout and its plugin from hell, or anything else.

Now, here are my findings based on a single attempt at each configuration.

1/ Start a conference at meet.jit.si from Chrome on a Public IP computer
    Join from Chrome on a computer behind NAT
    Result: Audio works both ways, but only local video is showing, on both
sides

2/ Start a conference at meet.jit.si from Chrome on a computer behind NAT
    Join from Chrome on a Public IP computer
    Result: Audio and Video work both ways

3/ Trying to join an existing conference from Chrome on iPhone doesn't
work, as I was expecting.
    The browser is redirected to
https://meet.jit.si/webrtcrequired.html(which triggers a 404)

I did not confirm the Chrome version number on the iPhone, but on the
computers it was the most recent one.

Also, on the Public IP computer there is an impressive 3 seconds lag in the
local video (although it's smooth),
whereas the local video is pretty responsive and smooth on the laptop.
Should I blame Chrome, or even hardware ?

Looking forward to all the upcoming new developments in and around Jitsi !

Jean

···

On Tue, Dec 10, 2013 at 6:47 AM, Emil Ivov <emcho@jitsi.org> wrote:

Hey Jungle,

We haven't yet had the time to look into Android support. So far it seems
that Chrome for Android might be lacking some aspects of WebRTC support.

Emil

On 09.12.13, 22:32, jungleboogie0 wrote:

Hi Emil,

One extremely odd thing to report...

Replication steps:

0. open chrome on your internet browser chrome
1. go to meet.jit.si <http://meet.jit.si>

2. copy meeting ID
3. send to android phone via push button so you don't have to type 16
character room ID
4. once link is received on phone, open up link in chrome internet browser
5. do you have one or twe video streams?

I would expect there to be two video streams on both the android phone
and the website on the desktop.

Can anyone else replicate this?

Thanks,
Jungle

On 8 December 2013 02:22, Emil Ivov <emcho@jitsi.org >> <mailto:emcho@jitsi.org>> wrote:

    Hey all,

    A few of use have just created a sample video showing Jitsi
    Videobridge and WebRTC in action. You can check it out here:

    http://goo.gl/nS1b7H

    For those of you who haven't had the chance to learn about the
    bridge yet, it acts as a video relay or, more preciesely, a
    Selective Forwarding Unit (SFU), that mixes audio but keeps video
    streams separated when forwarding them to all participants in a
    conference call.

    This allows for a great scalability potential contrary to other
    approaches like full mesh conferences or content/composite mixing.

    The reason you are seeing a burst of Jitsi Videobridge related posts
    lately is because we have recently made it compatible with WebRTC by
    adding to it DTLS and ICE support (kudos to Lyubomir Marinov). This
    means that it can now be used to build video conferences in a web
    page like the video above shows.

    The actual JavaScript application in the video (which we will make
    publicly available very soon) is built by Philipp Hancke from Estos.
    It uses the COLIBRI XMPP protocol extension (
    https://jitsi.org/colibri ) to control the Jitsi Videobridge. It
    also uses XMPP Multi-User Chats (MUCs) to keep track of and control
    participants.

    All in all this makes for a very neat project and a completely open
    alternative to Google Hangouts.

    You will very likely be hearing more about this in the following
    days and weeks.

    Cheers,
    Emil

    --
    https://jitsi.org

    _________________________________________________
    users mailing list
    users@jitsi.org <mailto:users@jitsi.org>

    Unsubscribe instructions and other list options:
    http://lists.jitsi.org/__mailman/listinfo/users

    <http://lists.jitsi.org/mailman/listinfo/users>

--
-------
inum: 883510009902611
sip: jungleboogie@sip2sip.info <mailto:jungleboogie@sip2sip.info>
xmpp: jungle-boogie@jit.si <mailto:jungle-boogie@jit.si>

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

--
https://jitsi.org

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


#15

Dear Jitsi community,

This is a huge development.

Congratulations to all people involved in making this happen.

So, I couldn't resist and did a few trials.

The first observation is that the setup is entirely hassle-free,
which beats Hangout and its plugin from hell, or anything else.

Now, here are my findings based on a single attempt at each configuration.

1/ Start a conference at meet.jit.si <http://meet.jit.si> from Chrome on
a Public IP computer
     Join from Chrome on a computer behind NAT
     Result: Audio works both ways, but only local video is showing, on
both sides

2/ Start a conference at meet.jit.si <http://meet.jit.si> from Chrome on
a computer behind NAT
     Join from Chrome on a Public IP computer
     Result: Audio and Video work both ways

Are one and two consistently reproducible? The NAT shouldn't matter here especially if audio is going through. All conference control happens in the JS though so it is more likely that this failed in on of the cases.

Were both Chromes updated versions on a Desktop OS?

3/ Trying to join an existing conference from Chrome on iPhone doesn't
work, as I was expecting.
     The browser is redirected to
https://meet.jit.si/webrtcrequired.html (which triggers a 404)

Yeah. This requires WebRTC to work. Support is not yet everywhere.

I did not confirm the Chrome version number on the iPhone, but on the
computers it was the most recent one.

Hmmm ... that's interesting. Next time you reproduce the issue, could you please "Download the PeerConnection and stats data" under "Create Dump" in chrome://webrtc-internals ?

Also, on the Public IP computer there is an impressive 3 seconds lag in
the local video (although it's smooth),
whereas the local video is pretty responsive and smooth on the laptop.
Should I blame Chrome, or even hardware ?

Maybe ... the bridge is in France though and all video goes through there. If you are doing the test from say ... Japan? then you could be experiencing some issues due to this.

Looking forward to all the upcoming new developments in and around Jitsi !

So are we!

Cheers,
Emil

···

On 10.12.13, 04:43, Jean Lorchat wrote:

On Tue, Dec 10, 2013 at 6:47 AM, Emil Ivov <emcho@jitsi.org > <mailto:emcho@jitsi.org>> wrote:

    Hey Jungle,

    We haven't yet had the time to look into Android support. So far it
    seems that Chrome for Android might be lacking some aspects of
    WebRTC support.

    Emil

    On 09.12.13, 22:32, jungleboogie0 wrote:

        Hi Emil,

        One extremely odd thing to report...

        Replication steps:

        0. open chrome on your internet browser chrome
        1. go to meet.jit.si <http://meet.jit.si> <http://meet.jit.si>

        2. copy meeting ID
        3. send to android phone via push button so you don't have to
        type 16
        character room ID
        4. once link is received on phone, open up link in chrome
        internet browser
        5. do you have one or twe video streams?

        I would expect there to be two video streams on both the android
        phone
        and the website on the desktop.

        Can anyone else replicate this?

        Thanks,
        Jungle

        On 8 December 2013 02:22, Emil Ivov <emcho@jitsi.org > <mailto:emcho@jitsi.org> > <mailto:emcho@jitsi.org <mailto:emcho@jitsi.org>>> wrote:

             Hey all,

             A few of use have just created a sample video showing Jitsi
             Videobridge and WebRTC in action. You can check it out here:

        http://goo.gl/nS1b7H

             For those of you who haven't had the chance to learn about the
             bridge yet, it acts as a video relay or, more preciesely, a
             Selective Forwarding Unit (SFU), that mixes audio but keeps
        video
             streams separated when forwarding them to all participants in a
             conference call.

             This allows for a great scalability potential contrary to other
             approaches like full mesh conferences or content/composite
        mixing.

             The reason you are seeing a burst of Jitsi Videobridge
        related posts
             lately is because we have recently made it compatible with
        WebRTC by
             adding to it DTLS and ICE support (kudos to Lyubomir
        Marinov). This
             means that it can now be used to build video conferences in
        a web
             page like the video above shows.

             The actual JavaScript application in the video (which we
        will make
             publicly available very soon) is built by Philipp Hancke
        from Estos.
             It uses the COLIBRI XMPP protocol extension (
        https://jitsi.org/colibri ) to control the Jitsi Videobridge. It
             also uses XMPP Multi-User Chats (MUCs) to keep track of and
        control
             participants.

             All in all this makes for a very neat project and a
        completely open
             alternative to Google Hangouts.

             You will very likely be hearing more about this in the
        following
             days and weeks.

             Cheers,
             Emil

             --
        https://jitsi.org

             ___________________________________________________
             users mailing list
        users@jitsi.org <mailto:users@jitsi.org> <mailto:users@jitsi.org
        <mailto:users@jitsi.org>>

             Unsubscribe instructions and other list options:
        http://lists.jitsi.org/____mailman/listinfo/users
        <http://lists.jitsi.org/__mailman/listinfo/users>

             <http://lists.jitsi.org/__mailman/listinfo/users
        <http://lists.jitsi.org/mailman/listinfo/users>>

        --
        -------
        inum: 883510009902611
        sip: jungleboogie@sip2sip.info
        <mailto:jungleboogie@sip2sip.info>
        <mailto:jungleboogie@sip2sip.__info
        <mailto:jungleboogie@sip2sip.info>>
        xmpp: jungle-boogie@jit.si <mailto:jungle-boogie@jit.si>
        <mailto:jungle-boogie@jit.si <mailto:jungle-boogie@jit.si>>

        _________________________________________________
        dev mailing list
        dev@jitsi.org <mailto:dev@jitsi.org>
        Unsubscribe instructions and other list options:
        http://lists.jitsi.org/__mailman/listinfo/dev
        <http://lists.jitsi.org/mailman/listinfo/dev>

    --
    https://jitsi.org

    _________________________________________________
    dev mailing list
    dev@jitsi.org <mailto:dev@jitsi.org>
    Unsubscribe instructions and other list options:
    http://lists.jitsi.org/__mailman/listinfo/dev
    <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

--
https://jitsi.org