[jitsi-dev] Removing jitsi-videobridge recording from jicofo


#1

Hello,

This is to announce that we are planning to soon remove the functionality from Jicofo which allows a conference to be recorded via jitsi-videobridge. The reasons are that this method of recording has been deprecated, and we don't have the resources to continue to support it while continuing to evolve jicofo.

To clarify:
1. Recording a jitsi-meet/jicofo conference will still be possible through jibri[0], which is what we currently use and recommend.

2. The recording functionality will still exist in jitsi-videobridge, but not in jicofo. The code in jitsi-videobridge will also be removed in the future, but not in this first stage.

Regards,
Boris

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


#2

Hello,

Hi, Boris.

This is to announce that we are planning to soon remove the
functionality from Jicofo which allows a conference to be recorded via
jitsi-videobridge. The reasons are that this method of recording has
been deprecated, and we don't have the resources to continue to support
it while continuing to evolve jicofo.

To clarify:
1. Recording a jitsi-meet/jicofo conference will still be possible
through jibri[0], which is what we currently use and recommend.

2. The recording functionality will still exist in jitsi-videobridge,
but not in jicofo. The code in jitsi-videobridge will also be removed in
the future, but not in this first stage.

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

I thought the support had been removed long ago since I had tried what I
found in the documentation [1] and it did not work. Then I found an
issue where other people had the same problem and Yanas mentioned that
now you are using Jibri.

I was looking at it in the repository but I read that it is still very
experimental so I think it would not yet be ready to run in a production
environment (but it would be better if you confirm it) and the
installation and configuration does not seem trivial.

Kind regards,
Daniel

[1]
https://github.com/jitsi/jitsi-meet/blob/master/doc/manual-install.md#enabling-recording
[2] https://github.com/jitsi/jitsi-meet/issues/656

···

On 16/05/17 16:28, Boris Grozev wrote:


#3

(My emphasis.)

I'd rather you didn't do the second stage. We use JVB standalone (as part
of a larger product), and we use the call recording function.

Martin

···

On 16 May 2017 at 21:28, Boris Grozev <boris@jitsi.org> wrote:

2. The recording functionality will still exist in jitsi-videobridge .... *The
code in jitsi-videobridge will also be removed in the future*, but not in
this first stage.


#4

Hello,

Hi, Boris.

This is to announce that we are planning to soon remove the
functionality from Jicofo which allows a conference to be recorded via
jitsi-videobridge. The reasons are that this method of recording has
been deprecated, and we don't have the resources to continue to support
it while continuing to evolve jicofo.

To clarify:
1. Recording a jitsi-meet/jicofo conference will still be possible
through jibri[0], which is what we currently use and recommend.

2. The recording functionality will still exist in jitsi-videobridge,
but not in jicofo. The code in jitsi-videobridge will also be removed in
the future, but not in this first stage.

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

I thought the support had been removed long ago since I had tried what I
found in the documentation [1] and it did not work. Then I found an
issue where other people had the same problem and Yanas mentioned that
now you are using Jibri.

It has been deprecated for a long time. Honestly, I don't know if it works or not with the current master branches. Now it is being removed.

I was looking at it in the repository but I read that it is still very
experimental so I think it would not yet be ready to run in a production
environment (but it would be better if you confirm it) and the
installation and configuration does not seem trivial.

Yes, the setup is more involved, and unfortunately there is not much documentation.

Regards,
Boris

···

On 16/05/2017 16:15, Daniel Bareiro wrote:

On 16/05/17 16:28, Boris Grozev wrote: