[jitsi-dev] forcing a conference stop


#1

Hey guys,

I'm looking for a way to stop a running conference from outside. More
precisely to stop it on focus leaving.

I can't use authentication and I can't use a reservation system -- so
when the focus leaves the room, another participant takes the turn
(as normally expected).

Is there a way to prevent this focus changing and to force conference
room expiration on focus leaving? Or on command? I tried deleting the
xmpp room, to no avail.

···

--

Yasen Pramatarov
Lindeas Ltd. https://lindeas.com
'working on GNU/Linux ideas'
Professional Jitsi Meet services


#2

Hey Yasen,

Just to be clear, you mean "moderator" right? The participant with the star?

Now that we have Jicofo, participants no longer take the role of a focus.

As for killing an existing conference without authentication, this
sounds tricky. I mean, you could easily kick everyone out of the room
but what stops them from coming back? How do you expect this to work?

Emil

···

On Fri, Nov 27, 2015 at 10:01 AM, Yasen Pramatarov <yasen@lindeas.com> wrote:

Hey guys,

I'm looking for a way to stop a running conference from outside. More
precisely to stop it on focus leaving.

I can't use authentication and I can't use a reservation system -- so
when the focus leaves the room, another participant takes the turn
(as normally expected).

Is there a way to prevent this focus changing and to force conference
room expiration on focus leaving? Or on command? I tried deleting the
xmpp room, to no avail.

--
> Yasen Pramatarov
> Lindeas Ltd. https://lindeas.com
> 'working on GNU/Linux ideas'
> Professional Jitsi Meet services

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

--
https://jitsi.org


#3

Just to be clear, you mean "moderator" right? The participant with the
star?

Correct -- moderator, my bad. :slight_smile:

As for killing an existing conference without authentication, this
sounds tricky.

You are right Emil, it seems tricky as I look at it again...

The reason was to get more control over rooms -- the scenario is where
each user is billed for conference usage of "his" room, so one has to
be sure only the inviting peer gets billed, not the others that may
remain after that in the room.

I mean, you could easily kick everyone out of the room but what stops
them from coming back? How do you expect this to work?

I managed to restrict the loading of the conference to specific users
-- one that has the room assigned to and the ones that he has
"invited" with a special link with parameter... It's a custom Meet
integration in a web portal...

What I can't control is whether the invited peers stay in the room or
not after the inviting party has left.

If they get kicked (or the conference stops), I can make sure they
don't get in again uninvited, but otherwise they can remain in the
room indefinitely.

I was considering the reservation system[0] of jicofo to make somehow
this, but I am not sure it will fit the scenario. Do you think I
should get back to jicofo registration? I would surely prefer to rely
on officially supported functionality rather than hacks.

So I thought that if there is some simple way to automatically "kick
out" everyone upon exiting of the one that invited them, the first
with moderator rights, it would be best. Same with the force conf stop.

P.S.: I know my question is very specific and maybe such functionality
is not in the Jitsi Meet project's scope -- in that case please ignore
it and sorry for the noise, I'll see if I can make use if the
reservation system.

[0] https://github.com/jitsi/jicofo/blob/master/doc/reservation.md

···

On Fri, 27 Nov 2015 10:43:51 -0600 Emil Ivov wrote:

--

Yasen Pramatarov
Lindeas Ltd. https://lindeas.com
'working on GNU/Linux ideas'
Professional Jitsi Meet services