asterisk users - Aug 2005 - [Announce] Pending update to Web-MeetMe

[What it is]
	Web-MeetMe is a collection of PHP pages to allow for database
driven scheduling of conference resources.

[Current features]
	Schedule new conferences
		1.  Control start and end times
		2.  Set conference pin #
			a.  Generate one if the requester leaves it
blank
			b.  Identify pin # conflicts (another conference
with
				the same pin is scheduled at the same
time)
		3.  Set Admin and User passwords
			a.  Generate a user password if an Admin pw is
set
				but the User pw is blank
		4.  Email the details for a successfully scheduled
conference
		5.  Separate views for Current, Past and Future
conferences
		6.  Ability to modify the end time of a running
conference
			a.  Can also reschedule a past or future
conference.
		7.  Monitor realtime conference activity
			a.  Mute/Kick participants

[What's new]
	I've had a number of folks submit enhancements or make requests
for 
improvements.  Specifically with how people should be limited to viewing
other
parties conferences.  So-

		1.  Optional authentication
			a.  Currently Active Directory or LDAP based
			b.  Authentication is abstracted so
unix/PAM/DB/RADIUS
				support could be easily added (but
outside of my
				interest to do so (patches welcome))
		2.  Users can only monitor, update or delete their
conferences
		3.  Verified administrators can monitor, update or
delete any
			conferences.
		4.  Updated to CVS-Head (a couple weeks ago, will target
1.2 soon)
			a.  Changes to the Manager interface may have
caused
				support for 1.0.X to slip, I cannot test
that)

[Maybe]
	A recent list post about Marked callers and Admins prompted me
to think
that perhaps the conference flags should be stored in the database, so
the scheduler
could pick the conference options that they want.  While I don't see
this as too hard
to add, I think that the interface would be a bit busy with even a
subset of the 22
flags available in recent MeetMe versions.  So this is a call for
feedback, if anyone
even wants such a feature-
	
	1.  Does anyone want it?
	2.  What options should be available?	
		a.  For Users?
		b.  For  Admins?
		c.  Any that should be considered default and not
optional?
	3.  Should I consider the current features a release point, or
is there
		something I missed that should be added before packaging
it?

I appreciate the feedback I have received since the last announcement,
and 
apologize that I allowed work to get in the way of development.

Thanks and enjoy,
Dan
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
http://lists.digium.com/pipermail/asterisk-users/attachments/20050826/021ebe7e/attachment.htm

Dan Austin wrote:
>
>         3.  Should I consider the current features a release point, or 
> is there
>                 something I missed that should be added before 
> packaging it?
>
> I appreciate the feedback I have received since the last announcement, 
> and
> apologize that I allowed work to get in the way of development.
>
> Thanks and enjoy,
> Dan
>
Storing the conference parameters in the database could be useful. I'd
suggest c,i,M,q,r,s,w,x. Some parameters could be grouped together
as alternatives in the user interface:
c / i / q / none

Although I've never used them, I think the m (monitor) ,t (talk) parameters
should not apply to the whole conference, but to specific users.

Also, the parameters a (admin mode) and A (marked mode) are not the
easiest way to identify admins and marked users. Transferring them to
the database would not help either.

What I think would be more useful is a way of identifying a marked user
through a separate password as can be done for admin users.

John