search

macielbombonato / bigbluebutton

Automatically exported from code.google.com/p/bigbluebutton
0 stars 0 forks source link

Unify the Users and Listeners window #901

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago 
The reason for the Listeners window being separate from the User's window is 
historical: from the beginning BigBlueButton supported dial-in numbers via 
Asterisk (and later FreeSWITCH).  

A user may only dial into the conference and thus have no web presence.  
Separating the Users from the Listeners window allows for unequal numbers of 
users in each.

However, when the number of users in the web and voice conference get large, 
there are usability problems with this approach.

1.  When a user raises her hand, it takes effort for the moderator to find the 
associated user in the Listener's window and unmute them.

2.  It's hard to determine those users that are logged into the web conference, 
but not yet joined the voice conference

For those users that have not joined the web conference, we can indicate so in 
a unified Users window.  Some careful design is needed in such an interface, 
but it should make the moderators job easier for larger number of users.

Original issue reported on code.google.com by ffdixon@gmail.com on 22 Mar 2011 at 12:34

GoogleCodeExporter commented 8 years ago 
add an api parameter on join called CNAM=6134561234,N2,N3 and if the inbound 
caller id matches on the user numbers... link landline call to username in 
viewers window...

Business logic in LMS would keep list of valid telephone numbers for each user 
and pass them as a CNAM=XXX,XXX,XXXXX on join, providing ability to match 
inbound calls to user.

Original comment by 207T...@gmail.com on 7 Apr 2011 at 10:00

GoogleCodeExporter commented 8 years ago

Original comment by ffdixon@gmail.com on 11 Oct 2012 at 5:38

Attachments:

GoogleCodeExporter commented 8 years ago

Original comment by ffdixon@gmail.com on 13 Oct 2012 at 1:34

GoogleCodeExporter commented 8 years ago 
Two more UI mockups.  

For a moderator, they would have the ability to
  - make use presenter
  - Lower all hands

For moderator, they would have the ability to affect audio
  - Mute all 
  - Mute all (except selected)

You'll note that we've removed the lock icons, which was a mechanism to
  (a) mute all (except locked)
  (b) prevent users from unmuting themselves

We're wondering how import it is for (b).  In almost all classes we monitor, 
we've never seen a moderator lock a participate so they couldn't umute 
themselves.  We suspect that while people may like this feature (it's there in 
case I needed it), the presence and functions of the lock icons are not 
self-evident, and most never use them because they don't understand their 
purpose.

Original comment by ffdixon@gmail.com on 13 Oct 2012 at 1:42

Attachments:

GoogleCodeExporter commented 8 years ago 
To match the caller ID with a user in the participants window (which we might 
simply rename to users window), we'll add a parameter 'callerid' to the join 
URL.    For example, 

  &callerid=6135452234

If an incoming voice call has a caller ID that matches the callerid in a 
joinURL, then the audio channel for that voice call will be placed alongside 
the user.

There are some subtle cases as a user might already be joined through the 
build-in VoIP and dial in as well with a matching caller ID.  In that scenario, 
we'd have to mute *both* streams if the user clicks the mute button.

Original comment by ffdixon@gmail.com on 13 Oct 2012 at 1:47

GoogleCodeExporter commented 8 years ago 
Issue 1270 has been merged into this issue.

Original comment by ffdixon@gmail.com on 11 Nov 2012 at 4:48

GoogleCodeExporter commented 8 years ago

Original comment by ffdixon@gmail.com on 8 Feb 2013 at 12:52

GoogleCodeExporter commented 8 years ago 
This feature has been merged into master.

Original comment by ritza...@gmail.com on 15 Mar 2013 at 2:46

GoogleCodeExporter commented 8 years ago 
This issue was about unifying the users and listeners.  Just for clarification, 
the comment about adding callerid was not implemented as part of this.  We'll 
open a separate issue for this.

Original comment by ffdixon@gmail.com on 8 Apr 2013 at 2:38