On Mon, 2010-06-07 at 14:36 -0500, David Swardstrom wrote: > One feature that many conferences have is classes of users. There is the > Host/Moderator, speakers, and Guests/participants. In such conferences, the > Host may have the ability to Mute all non-speaking Conferees. Currently this > requires a separate flag for each user indicating the user class. To toggle > conference level mute, the application will need to get a conference list and > run through it. For each conferee in the list, the current mute status and > user class must be determined. > > I would like to propose introducing a new member flag: speaker. > This indicates that the member is a speaker and should not be automatically > muted. This would be provided as a “speaker” flag as part of the status on a > list. >
would it not be better to have a profile set for each member instead of for the conference as a whole? This could mean that you can have some muted, some not, some with extra dtmf events some with less, etc. One thing that I ran into was if you set sounds, dtmf events, etc its for everyone and if you change it for the 2nd person entering you lose that. In this way it would allow you to use different pins for a moderator, speaker and listener like some other conferences I have seen elsewhere. _______________________________________________ FreeSWITCH-dev mailing list FreeSWITCH-dev@lists.freeswitch.org http://lists.freeswitch.org/mailman/listinfo/freeswitch-dev UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-dev http://www.freeswitch.org
