>I don't understand the question. What kinds of "various things"? There
is some documentation in the "doc/" >directory.
Things like what codecs Jitsi can handle, what the various transports
are and their xmpp name.
For audio this depends on the rtp-level-relay-type. For "translator", anything should work. For "mixer", since it requires re-encoding, the only supported codecs are the ones that libjitsi supports. These include opus, G722, G711 and others (see MediaUtils.java for a complete list).
For video, without simulcast, any codec should probably work. For simulcast we are currently limited to VP8, because we need to understand some very small parts of the stream (e.g. is a packet the beginning of a keyframe?). This should be easily extendable to other codecs.
An example of the complete series of data transmitted for a successful
link between the videobridge and chrome.
In light of the question below, I assume this refers to the media path. I would refer to any document which describes this for WebRTC. Short version: first ICE, then DTLS, then media. Keep the ICE consent fresh.
What should go in the various fields in the JSON for the REST interface
- some things are obvious others are not (although I now have the answer
on channel bundle id).
The JSON format used for REST is really just a translation of the XMPP based COLIBRI protocol. So, for documentation of the content and its semantics see here (I think it is slightly outdated now, but nothing major is missing):
The translation to JSON is documented here:
I would be pleased to put this together for the REST interface when I
have got it to work as then I will have had to find quite a bit of this.
What I would probably do for this is to create a transaction that gives
this sort of information by querying the code so it would not end up out
of sync with the videobridge probably as a web page from jetty rather
than json. If you would like me to do this I would be pleased (once I
can get it to work).
I think documentation would be a welcome contribution, but I cannot guarantee that it will be included.
On 14/01/2017 02:29, John Hemming wrote: