Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

need kickUser call in API #1276

Open
bigbluebutton-issue-import opened this issue Aug 12, 2015 · 21 comments
Open

need kickUser call in API #1276

bigbluebutton-issue-import opened this issue Aug 12, 2015 · 21 comments

Comments

@bigbluebutton-issue-import

Originally reported on Google Code with ID 521

need to be able to kick a specific user from a conference through the API

it should take the following parameters:
meetingID
password (which must be the moderator password)
userID

this will be dependent on issue #393 being finished - because you should be 
able to specify the userID in the join call.  this userID is what you would 
then use to kick the user

Reported by jeremythomerson on 2010-05-08 02:48:25

@bigbluebutton-issue-import
Copy link
Author

also see issue #327 - this issue was broken out of that one

Reported by jeremythomerson on 2010-05-08 02:49:39

@bigbluebutton-issue-import
Copy link
Author

Yes, I think the moderator needs to be able to kick a user and/or their webcam just
like you can with a voice participant. Why voice but not the others?

Reported by mrmook on 2010-07-06 08:46:48

@bigbluebutton-issue-import
Copy link
Author

In 0.71, there's a new ability for the moderator to kick the participant by clicking
a button in the Viewers Window - similar to the way kicking Listeners is done.

The way it's being done is a bit of a hack though - the Moderator politely asks the
client of the Viewer to log out of the conference. However, if this feature is implemented,
I could refactor the new kicking feature to use the API call instead.

Reported by Me.Snap on 2010-09-29 02:27:29

@bigbluebutton-issue-import
Copy link
Author

Reported by eu.tdj.cc on 2013-10-29 14:59:41

@bigbluebutton-issue-import
Copy link
Author

Is this issue going to be implemented now?
I also think it would be a very important API feature, e.g. for maintenance works.

Reported by Melanie.Treitinger on 2013-11-04 16:10:09

@bigbluebutton-issue-import
Copy link
Author

Hi Melanie,

To understand how we prioritize features requests for each release, see

   https://code.google.com/p/bigbluebutton/wiki/FAQ#When_will_feature_X_be_implemented


Reported by ffdixon on 2013-11-04 20:05:10

@bigbluebutton-issue-import
Copy link
Author

Hi Fred, thank you, I have read the wiki article about implementing features. As I have
seen, this feature is not on the road map.

I posted my question because I have seen that the ownership of this issue changed just
a couple of days ago (the issue was created 3 years ago) - so I thought this might
mean that it will be implemented... 

Reported by Melanie.Treitinger on 2013-11-05 13:00:07

@bigbluebutton-issue-import
Copy link
Author

I'll be working on that, will report when done in this issue.

Reported by eu.tdj.cc on 2013-11-05 18:23:34

@bigbluebutton-issue-import
Copy link
Author

Reported by ffdixon on 2014-01-09 17:43:42

  • Labels added: Milestone-Release0.9.0

@bigbluebutton-issue-import
Copy link
Author

Hi Fred, is this feature implemented now? Is there a patch available?

Reported by Melanie.Treitinger on 2014-01-10 08:51:30

@bigbluebutton-issue-import
Copy link
Author

This feature is not implemented yet.  To receive e-mail updates on this feature and
when it's implemented, make sure you've stared.

Reported by ffdixon on 2014-01-21 08:10:20

@bigbluebutton-issue-import
Copy link
Author

Reported by ritzalam on 2014-06-26 19:28:22

  • Labels removed: Milestone-Release0.9.0

@WojciechRhdt
Copy link

Any news on this feature? I think it would be a very nice API feature for administration.

@Magnusemail
Copy link

Curious as to if this ever made it into road-map, seems useful function

@CeloGomesBR
Copy link

I need it too, so much... :(

@matiasilva
Copy link
Collaborator

Hi @marcelorgomes . Currently, you can ban and remove a user from the conference in the HTML5 client. Is this not sufficient for your purpose?

@CeloGomesBR
Copy link

Hi Matia... no, I need it from API, because we have rules that need to kick de user from conference....

@afsharsafavi
Copy link

Hi
I think kicking a user through API is an essential feature.
Sometimes users join into meeting from different places/devices and without the ability to control it by kicking the last session, we can't handle it.

@b-sass99
Copy link

b-sass99 commented Jan 6, 2021

looking forward to this feature

@mkoursh
Copy link

mkoursh commented Feb 6, 2021

As @afsharsafavi mentioned, kicking a user through API is essential and crucial !!!!

@soheb-somani
Copy link

I am also looking forward to this feature. We desperately need it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

10 participants