[jitsi-dev] jitsi videobridge REST interface

Archive
#1

Hi,

The REST interface of the jitsi videobridge does not expose all the
features available trough the "standard" XMPP interface which effectively
makes it unusable in certain application. Some of the problems encountered
with the REST interface are:

1. Impossible to specify RTCP-FB and RTP_HDREXT details like in the
following COLIBRI snippet which is sent to the videobridge as part of the
participant invitation process:

<content name="video">

<channel channel-bundle-id="2547f93d" initiator="true" last-n="-1"
endpoint="2547f93d">

<payload-type id="100" name="VP8" clockrate="90000">

<rtcp-fb xmlns="urn:xmpp:jingle:apps:rtp:rtcp-fb:0" type="ccm"
subtype="fir" />

<rtcp-fb xmlns="urn:xmpp:jingle:apps:rtp:rtcp-fb:0" type="nack" />

<rtcp-fb xmlns="urn:xmpp:jingle:apps:rtp:rtcp-fb:0" type="nack"
subtype="pli" />

<rtcp-fb xmlns="urn:xmpp:jingle:apps:rtp:rtcp-fb:0" type="goog-remb" />

</payload-type>

<payload-type id="116" name="red" clockrate="90000" />

<payload-type id="117" name="ulpfec" clockrate="90000" />

  <rtp-hdrext id="2" uri="urn:ietf:params:rtp-hdrext:toffset" />

  <rtp-hdrext id="3" uri="
http://www.webrtc.org/experiments/rtp-hdrext/abs-send-time" />

</channel>

</content>

2. While with the XMPP interface the source element (see below) can have
some parameters inside - such parameters are ignored when using the REST
interface i.e. they are not deserialized at all:

<content name="audio">

<channel id="bac6f7272b63da1e">

<source xmlns="urn:xmpp:jingle:apps:rtp:ssma:0" ssrc="3307295683">

<parameter value="syt30/FuV8xkh8yw" name="cname" />

<parameter value="c7cc0dbb-d1c0-470f-88bf-2f2a7d1d9310
f58832d2-d420-4e0a-9a2d-00cd698242ba" name="msid" />

<parameter value="c7cc0dbb-d1c0-470f-88bf-2f2a7d1d9310" name="mslabel" />

<parameter value="f58832d2-d420-4e0a-9a2d-00cd698242ba" name="label" />

</source>

<ssrc-group xmlns="urn:xmpp:jingle:apps:rtp:ssma:0" semantics="SIM" />

</channel>

</content>

Appreciate if someone can confirm, elaborate or provide any feedback that
helps to sort this out!

Thanks.
Mihail

#2

The REST interface of the jitsi videobridge does not expose all the features
available trough the "standard" XMPP interface which effectively makes it
unusable in certain application.

Thank you for the feedback!

Appreciate if someone can confirm, elaborate or provide any feedback that
helps to sort this out!

I confirm. The REST API (serialization/deserialization) is maintained
manually i.e. it does not update automatically as changes to the
COLIBRI protocol are made in the XMPP API. Looking at the repository
logs, it appears that at least some of the modifications to the XMPP
API were introduced soon after the last (manual) update of the REST
API.

···

2015-05-26 23:35 GMT+03:00 Mihail Bratoev <mbratoev@gmail.com>:

#3

Thanks for the prompt response!

Can you please provide an approximate date for the next update of the REST
interface?

···

On Wed, May 27, 2015 at 12:00 AM, Lyubomir Marinov < lyubomir.marinov@jitsi.org> wrote:

2015-05-26 23:35 GMT+03:00 Mihail Bratoev <mbratoev@gmail.com>:
> The REST interface of the jitsi videobridge does not expose all the
features
> available trough the "standard" XMPP interface which effectively makes it
> unusable in certain application.

Thank you for the feedback!

> Appreciate if someone can confirm, elaborate or provide any feedback that
> helps to sort this out!

I confirm. The REST API (serialization/deserialization) is maintained
manually i.e. it does not update automatically as changes to the
COLIBRI protocol are made in the XMPP API. Looking at the repository
logs, it appears that at least some of the modifications to the XMPP
API were introduced soon after the last (manual) update of the REST
API.

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