[jitsi-dev] Video bridge - rtcp-mux and Jirecon


#1

Hey all… I’ve been working on getting Jirecon up and running against videobridge and was wondering if anyone’s made any attempt to update Jirecon to support channel bundling/rtcp-mux? As it appears Jirecon is no long being (regularly) maintained, I’ve tried disabling the single port harvester in video bridge via the “org.jitsi.videobridge.SINGLE_PORT_HARVESTER_PORT” as described here: https://github.com/jitsi/jitsi-videobridge/blob/master/doc/single-port.md but it didn’t appear to generate RTCP candidates as I would have expected once that was set to –1… perhaps I’m misinterpreting the intent… in any case the ideal solution would be to have Jirecon support rtcp-muxing so I was curious if anyone’s gone down that route? Any suggestions are appreciated!

Chris.


#2

Hi Chris,

Hey all… I’ve been working on getting Jirecon up and running against
videobridge and was wondering if anyone’s made any attempt to update
Jirecon to support channel bundling/rtcp-mux? As it appears Jirecon is
no long being (regularly) maintained,

This is indeed the case. It takes too much resources just to keep it up to date and we stopped trying to do so after we switched jitsi-meet to use the lib-jitsi-meet library. We switched signalling of SSRCs from presence in the MUC to Jingle and jirecon hasn't been update. So if you are using Jitsi-Meet it will not just work after solving whatever problem you are running into with bundle/rtcp-mux.

I’ve tried disabling the single
port harvester in video bridge via the
“org.jitsi.videobridge.SINGLE_PORT_HARVESTER_PORT” as described here:
https://github.com/jitsi/jitsi-videobridge/blob/master/doc/single-port.md but
it didn’t appear to generate RTCP candidates as I would have expected
once that was set to –1… perhaps I’m misinterpreting the intent…

This should disable the single-port mode, and provide separate candidates for RTP and RTCP, as well as for the different media streams. However, this shouldn't be needed for jirecon (or jigasi) to work. The bridge supports falling back to non-bundle and non-muxed rtcp, this is how it works with jigasi.

in any
case the ideal solution would be to have Jirecon support rtcp-muxing so
I was curious if anyone’s gone down that route? Any suggestions are
appreciated!

Jirecon is unlikely to see any attention from our team. Our efforts are moving towards jibri[0].

Regards,
Boris

[0] https://github.com/jitsi/jibri

···

On 24/03/16 14:41, Higgins, Chris wrote: