similar to: [Feedback request] Web-MeetMe authentication

Displaying 20 results from an estimated 20000 matches similar to: "[Feedback request] Web-MeetMe authentication"

2006 Jan 12
5
[Announce] Web-MeetMe v2.0.0
[New Features] 1. Added focus and tab-order to all input fields 2. Dynamic generation of date/month/year listboxes a. It is no longer possible to schedule an invalid date. 3. Added 'Extend' and 'End Now' buttons to the monitor page. 4. Invite button on the monitor page. This greatly simplifies the process of adding callers to a conference. The ./lib/defines
2007 Jan 03
9
[Announce] Web-MeetMe 3.0.0 released
We've been holding back on this release to coincide with the Asterisk 1.4.0 release. This is mostly a compatibility release, but there are a few new features: * No longer requires register_globals in PHP * Separated code from configuration settings in ./lib/defines.php (hopefully this will make future upgrades easier) * Migrated all database interfaces to PEAR::DB which
2005 Aug 29
0
[Announce] Web-MeetMe v1.3.3
Work intrudes again and I will not be able to get to modifying the db and gui to support per-conference flags as soon as I expected. So I have released an update with what I do have available. [Location] http://www.fitawi.com/Asterisk [Features] 1. Schedule new conferences a. Control start and end times b. Set conference pin # i. Generate one if the requester leaves it blank ii.
2006 Mar 03
7
web meetme instructions
This has to be the worst documentation I have ever come acrossed. I have found two or three docs on how to install it, but they are all so different and make huge assumption about what packages you have installed and locations of files. Has anyone seen something better, I want to get this working it is quite a cool app. Jordan Novak Communications Technician Logistics Health Inc. 1319 Saint
2006 Jan 04
2
[Web-MeetM] Seeking Beta testers
I have V2.0.0 about read to roll. There's quite a few new features, clean-ups and bug fixes. I hope this will be the last major update for awhile, and as such I'd like to squash any issues before releasing it. New- ** Dynamic day/date listboxes to prevent invalid date entries ** Textbox focus and tabbing order ** CDR-like view at past conferences to show participants ** Vastly
2005 Aug 26
1
[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
2005 Mar 29
2
MeetMe flags in * 1.0.7
While researching Areski's new Web-MeetMe management gui, I found some odd (from what I expected) behaviour). Using the CLI to set un/mute status works but does not update the flags, or so it appears. Starting with a fresh conference (1 user) *CLI> meetme list 3456 User #: 1 Channel: OH323/R61 Using the CLI to mute the caller (no change in the user status0 *CLI> meetme mute 3456 1
2006 Jan 17
2
MeetMe Listen Only flag (|m)
One of the features that I thought would be popular with the Web-MeetMe suite is the ability to start all non-admin callers in a muted state and selectively unmute them. For example any large conference that is of an announcment nature with a Q&A session. It's probably a feature I should have tested better, but I just discovered that a caller that is joined to a MeetMe with the |m flag
2007 May 03
0
[Announce] Web-MeetMe 3.0.2 and 2.2.2 Released
Basic bug fix releases Both have updates to app_cbmysql to be thread-safe, reconnect to the database in case of timeout and to detect missing/mis-configured conference app/conference participant counting apps. The last one has caused Asterisk to crash. Now If it does not find MeetMe or MeetMeCount (the defaults) it posts a warning and exits back to the dialplan. Web-MeetMe 2.2.2 also has an a
2009 Jul 20
0
[asterisk-dev] MeetMe feature request: bypass pincode
Emrah wrote: >> This is an asterisk-users question, and would have been more appropriate to have >> asked there. >> >> Instead of setting up your conferences in meetme.conf, you could set them up >> dynamically in the dialplan, and then you can control whether the user is >> prompted for a pin or not when joining the conference, based on whatever logic
2013 Aug 15
2
meetme list concise
Hello, Can anyone tell me the format for meetme list concise command, so that I know what field is what (separated by '!'s) Thanks -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.digium.com/pipermail/asterisk-users/attachments/20130815/eba161be/attachment.htm>
2007 Jan 07
0
Re: asterisk-users Digest, Vol 30, Issue 7
On 1/3/07, asterisk-users-request@lists.digium.com < asterisk-users-request@lists.digium.com> wrote: > > ---------- Forwarded message ---------- > From: "Dan Austin" <Dan_Austin@Phoenix.com> > To: "Asterisk Users Mailing List - Non-Commercial Discussion" < > asterisk-users@lists.digium.com> > Date: Wed, 3 Jan 2007 10:33:02 -0800 > Subject:
2008 Jan 30
4
Meetme voice quality problems
Hi, I am using Debian OS kernel 2.6.22-3-amd64 and zaptel driver 1.4 with ztdummy module for meetme application. I use meetme with SIP channels. I have such problem that when one connects to the conference voice is "cut". Each voice sequence is disturbed. Does any one have similar issue and could give me some advice?? my extension.conf for meetme: ;switch =>
2007 Jun 12
1
Realtime Meetme in 1.4
2007 Jun 08
0
Unexpected behaviour shown by "meetme kick confno usernumber"
Hi, I have Asterisk 1.4.4 on my linux box. Whenever i try to kick a participant in conference say "59681446" using following command meetme kick 59681446 1 where "1" is the participant number, following are the actions that asterisk takes * IVR "You have been kicked from this conference" is played. * Participant is taken out from that conference
2004 Oct 05
3
Special Meetme
Hi all, I want to setup a meetme application in the following maner: One operator is connected to a room. The operator hears and can talk to all the participants, but one participant can only hear/talk to the operator, not others. The operator is using one phone. To be more explicit, this means that every new person etering the room has a one2one conversation with the operator only, and the
2006 Mar 16
1
MeetMe - Causes * to crash :/
Anyone ever seen MeetMe cause * to crash? Specifically, it happens consistantly if someone begins to enter a conference and then decides to hangup while Allison is introducing them - like playing back "conf-onlyperson". This has been seen with the MeetMe participant connecting via IAX and SIP (not saying it doesn't happen with Zap, just that I haven't seen it). The box is *
2006 Apr 20
1
MeetMe: lots of buffer overruns/underruns when connecting over IAX
Hello, Situation: I've got two asterisk 1.2.4 servers, connected to each other over the internet with IAX2 with about 20msec delay. One of the servers is hosting MeetMe. It's working fine as long as only SIP phones connected to the meetme server participate in the conference. As soon as a participant using IAX2 is connecting, lots and lots of buffer overruns and underruns are
2005 Mar 22
0
ANNOUNCEMENT : MeetMe - Web-MeetMe (throughmanager)
Cool! I'm still away from the office, but I was starting to work towards syching meetme2 up to the version of meetme in * 1.0.7. It is over a 2000 line diff, ignoring the database integration code, so it was looking like a not too trivial task. One question though, how difficult will it be to extend your latest version with the scheduling features I built on top of you previous version? I
2009 Aug 18
0
Moderator access to meetme allowed despite pin
Hello, all. I've solved my own problem but will post it here in case someone else has the same misunderstanding in the future. We thought we had set up our meetme so that regular users entered the conference without a pin but could not speak to each other until the moderator arrived. We enforced pin entry on the moderator . . . or at least so we thought. If the moderator waited long enough