[jitsi-dev] Specifications or design documents of the Jitsi protocols


#1

Hi,

I’ve been reading the various Jingle XEPs lately, as well as COIN and
COLIBRI, but it seems that’s not all Jitsi Meet and its companion
components are using.

Do you have any up to date design documents about the whole
architecture I could use in other clients? I’m especially interested
in using the jitsi-videobridge to allow communication between Gstreamer
clients such as Gajim or Pidgin and WebRTC clients like Jitsi Meet or
Movim, which otherwise don’t share a common set of RTP configurations.

I’m also interested (but in a longer timeframe) in allowing other
clients to interoperate with Jitsi Meet, especially for Jingle-in-MUC,
but that’s already covered by COLIBRI.

Thanks for your hard work on this platform, it works like a charm!

···

--
Emmanuel Gil Peyrot


#2

Hi Emmanuel,

Hi,

I’ve been reading the various Jingle XEPs lately, as well as COIN and
COLIBRI, but it seems that’s not all Jitsi Meet and its companion
components are using.

Do you have any up to date design documents about the whole
architecture I could use in other clients? I’m especially interested
in using the jitsi-videobridge to allow communication between Gstreamer
clients such as Gajim or Pidgin and WebRTC clients like Jitsi Meet or
Movim, which otherwise don’t share a common set of RTP configurations.

Jitsi-videobridge doesn't use many extensions, and most of them are specified (XEP-0340, Jingle, etc). So making it work with other clients shouldn't be hard.

Unfortunately for jitsi-meet (and jicofo, jibri, etc) the situation is very different. There are many extensions, most of them defined ad-hoc and not documented. Even if we document them, this wouldn't necessarily open the door for interoperability with other clients, as they keep changing. Lib-jitsi-meet evolves very quickly, and it just isn't designed with the idea of interoperability.

Regards,
Boris

···

On 12/01/2018 17:16, Emmanuel Gil Peyrot wrote: