asterisk users - Jan 2007 - [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 simplifies the code a bit and opens
		up the possibility of using other databases
		to host the scheduling DB (app_cbmysql is
		still only MySQL, but ODBC is planned/hoped for)
	*  The conference monitoring code now uses the
		concise output from "meetme list", improving
		the parsing of participant details.
	*  Minor tweaks to improve the cbEnd.php script that
		enforces the conference duration, plays announcements
		and populates the conferencing CDRs.
	*  Conference CDR records now store participant duration
		in seconds instead of a formatted string, allowing
		for further analysis (the web interface still
		formats the duration for display purposes)
	*  App_cbmysql is updated to work with Asterisk 1.4.0 
	*  App_cbmysql has it's own build environment now, no
		longer requiring a Makefile patch, etc...

The new release can be found at:  
	http://sourceforge.net/projects/web-meetme/

We do have a volunteer developer who will be maintaining the
2.X.X chain for Asterisk 1.2.X compatibility, so bug fixes and
features that are not Asterisk version dependant will still be
made available for older installations.

Thanks,
The Web-MeetMe development team...

Any screenshots available?

I do not want to even test this without having any idea what it is or how it
works.

The brief description on sf.net is not enough.

-- 
-- 
Steven

http://www.glimasoutheast.org



"Dan Austin" <Dan_Austin@Phoenix.com> wrote in message
news:B0CF4196F21DC0448367514774331AB701E37B81@scl-exch2k3.phoenix.com...
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 simplifies the code a bit and opens
up the possibility of using other databases
to host the scheduling DB (app_cbmysql is
still only MySQL, but ODBC is planned/hoped for)
*  The conference monitoring code now uses the
concise output from "meetme list", improving
the parsing of participant details.
*  Minor tweaks to improve the cbEnd.php script that
enforces the conference duration, plays announcements
and populates the conferencing CDRs.
*  Conference CDR records now store participant duration
in seconds instead of a formatted string, allowing
for further analysis (the web interface still
formats the duration for display purposes)
*  App_cbmysql is updated to work with Asterisk 1.4.0
*  App_cbmysql has it's own build environment now, no
longer requiring a Makefile patch, etc...

The new release can be found at:
http://sourceforge.net/projects/web-meetme/

We do have a volunteer developer who will be maintaining the
2.X.X chain for Asterisk 1.2.X compatibility, so bug fixes and
features that are not Asterisk version dependant will still be
made available for older installations.

Thanks,
The Web-MeetMe development team...
_______________________________________________
--Bandwidth and Colocation provided by Easynews.com --

asterisk-users mailing list
To UNSUBSCRIBE or update options visit:
   http://lists.digium.com/mailman/listinfo/asterisk-users

Steven wrote:
> Any screenshots available?
Sorry, not yet.  I've been meaning to get the tools 
together to capture some images, but coding, QA and
paid work have taken priority...
> I do not want to even test this without having any 
> idea what it is or how it works.
It is a suite of tools to permit the scheduling of 
conferences.
> The brief description on sf.net is not enough.
There are four components to the suite:
	1.  A collection of web pages (PHP and javascript)
		that provide the interface to add, update, delete
		conferences.  There is also a page to monitor
		active conferences, with the ability to mute,
		unmute and eject participants, as well as to
		have Asterisk place a call to a participant.
	2.  An Asterisk application that validates the
		conference id, start time, participant count
		and any user/moderator pins
	3.  A small php script that logs the conference 
		participants to a CDR-like database and
		enforces a conference's scheduled endtime.
	4.  A small number of sound files to convey 
		conference events/status.  The files
		were recorded by Alison, so they are a nice
		match for Asterisk's standard sound files.

Key features:
	1.  Enforcable start and end times.
		Optionaly alert callers if they are too
		early.  Also optionally allow callers to
		join a conference if they are too early.  
	2.  Configurable conference id, user and moderator pins.
		Pins are optional.  If a moderator pin is set, then
		the user pin is required.
	3.  Recurring conferences.
		Dialy, weekly and bi-weekly
	4.  Future conferences can be edited.
		The entire series, or one at a time
	5.  A conference endtime can be extended once it has
		started, but this is the only configuration
		setting that can be changed once the conference
		start time has been reached.
	6.  Simple branding.  Reasonably easy to change logos
		and page headings to refect your company (helps
		get past management objections)
	7.  Optional authentication (LDAP or Database) to
		permit users to schedule and manage their own
		conferences.

I'll work on screenshots soon.

Dan

Rob wrote:
> I'm using the latest svn trunk code.  The app_cbmysql builds,
> installs, and loads just fine.  But I don't get any CBMysql 
> application within asterisk.  The only message I get as the 
> module loads is something about finding the configuration file
> (successfully). 
What version of Asterisk?  What does this command return:
*CLI> cb mysql status

> The database & tables are created, though the DDL scripts 
> provided seem to require MySQL 5.  The configuration file 
> (cbmysql.conf) is in place and has been modified to reflect 
> reality (username/pass and socket location). 
I would not expect the scripts to be MySQL 5 dependant, but
they were contributed by another developer, so perhaps they are.

How are you determining that you do not have the application?

What Does this command report:
*CLI> show application CBMySQL

Dan

Steven wrote:
> It sounds very promising, I will have to check it out.
Great.  Let me know how it goes for you.
> Does it edit conf. files?  Or is there just one lead in 
> conference number that flows into your app.?
Flexibility is a key design goal.  The most comon installation
would be a single extension (DID) that calls the cbmysql
application.  The call flow looks like this:
	1.  Answer call
	2.  Lanunch app cbmysql
	3.  App cbmysql requests the conference ID-
		a.  Check the schedule start time against now
		b.  If either Moderator or user pin is set, request
			that the caller enter the pin
	4.  If all conditions are meet, launches app meetme
		with the apprortiate flags (as set from the
		web interface)
>From this point on it is a standard Asterisk meetme conference.
> I am currently using freepbx, and do not want to break anything.
I have never used freepbx, but I don't think there will be major
issues.  The monitoring page im Web-MeetMe uses the Asterisk
Manager interface, which may or may not be an issue for freepbx,
but I don't think it will cause problems.


Dan

Rob wrote:
> What version of Asterisk?  What does this command return:
> *CLI> cb mysql status
> As I said above, latest svn trunk code -- as of yesterday or the day
before. 
> No such command 'cb mysql' (type 'help' for help)
	

>>> The database & tables are created, though the DDL scripts 
>>> provided seem to require MySQL 5.  The configuration file
>>> (cbmysql.conf) is in place and has been modified to reflect
>>> reality (username/pass and socket location).
>> I would not expect the scripts to be MySQL 5 dependant, but 
>> they were contributed by another developer, so perhaps they are.
		
>>How are you determining that you do not have the application?
> An error (I forget specifically) when I try to execute it from the 
> dialplan is what first keyed me in.  But subsequently the 
> command/response below, too. 
	

>> What Does this command report:
>> *CLI> show application CBMySQL
> No such command 'show application CBMySQL' (type 'help' for
help)
	
> But also, and probably more useful:
	
> Your application(s) is (are) not registered
> Command 'core show application CBMySQL' failed. 
	
> However, "module show like cb" does return:
	
> Module                         Description
Use Count 
> app_cbmysql.so                 CBMysql conference scheduling
0          
> 1 modules loaded
	
Can you set verbose and debug levels to 10 and run these commands:
*CLI> module unload app_cbmysql.so
*CLI> module load app_cbmysql.so

I suspect a config file issue, but a log of the module loading will
help peg down the problem.
	

Dan

> *CLI> core set verbose 10
>  Verbosity was 0 and is now 10
> *CLI> module unload app_cbmysql.so
>  Unable to unload resource app_cbmysql.so
>  Command 'module unload app_cbmysql.so' failed. 
> *CLI> [Jan  5 11:09:04] WARNING[30610]: loader.c:465 
> ast_unload_resource:Firm unload failed for app_cbmysql.so
	
> So I added "noload => app_cbmysql.so" to modules.conf, and
load
> manualy after restarting asterisk... 
	
> *CLI> module load app_cbmysql.so
>  == Parsing '/etc/asterisk/cbmysql.conf': Found
> *CLI> 
	
> This *is* with verbosity set to 10, but this is all I was 
> seeing before...
>> I suspect a config file issue, but a log of the module loading will
>> help peg down the problem.
		
> Doesn't look to me like this will be much help, but what do I know...
It actually helps quite a bit, along with me taking the time to
fully accept what version you are running (in one ear and out the
other problem)

Trunk has already moved on and code compatible with 1.4, may have
problems on it.  For a sanity check, I wiped out my test system
and rebuilt it with fresh components for 1.4 (libpri, zaptel, asterisk,
asterisk-addons), and I have no issues with unloading and re-loading
the module, and of course the app does what it claims and works as
intended.

So I can either ask that you try 1.4.0, or I will need to setup
a test against trunk.  I'd prefer to wait a bit before coding against
trunk, since it will break again, and likely before not too long.

Dan

Rob wrote:
> On 1/5/07, Dan Austin <Dan_Austin@phoenix.com> wrote:
	
>> Trunk has already moved on and code compatible with 1.4, may have
>> problems on it.  For a sanity check, I wiped out my test system
>> and rebuilt it with fresh components for 1.4 (libpri, zaptel,
asterisk,
>> asterisk-addons), and I have no issues with unloading and re-loading 
>> the module, and of course the app does what it claims and works as
>> intended.
		
>> So I can either ask that you try 1.4.0, or I will need to setup
>> a test against trunk.  I'd prefer to wait a bit before coding
against
>> trunk, since it will break again, and likely before not too long.
		

> I guess I figured that trunk couldn't have gone far from 1.4 yet, so
I'll
> move to 1.4.  Nothing in particular on trunk I need.  Thanks for your
time,
> but sorry to have wasted it. 
It wasn't a waste though.  I now know to expect more work once I look at
Trunk closely.  A quick review did not show anything exciting that has
changed,
but the APIs to register applications and CLI commands have changed a
small
bit.

Thanks,
Dan

Sorry I forgot to change the subject line in my last posting!

I have been using the Web Meet-Me 2.1.0 on Asterisk 1.2.12.1 for many months
now and I am a big fan and I have been very happy with it. I want to try the
v3.0.0 but I would like to know if there are specific steps I need to carry
out to upgrade to the v3.0.0 on my current Asterisk 1.2.X?

Warm Regards,

Buki

On 1/7/07, Naija Man <voip4naija@gmail.com> wrote:
>
>
>
> 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: [asterisk-users] [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 simplifies the code a bit and opens
> >                up the possibility of using other databases
> >                to host the scheduling DB (app_cbmysql is
> >                still only MySQL, but ODBC is planned/hoped for)
> >        *  The conference monitoring code now uses the
> >                concise output from "meetme list", improving
> >                the parsing of participant details.
> >        *  Minor tweaks to improve the cbEnd.php script that
> >                enforces the conference duration, plays announcements
> >                and populates the conferencing CDRs.
> >        *  Conference CDR records now store participant duration
> >                in seconds instead of a formatted string, allowing
> >                for further analysis (the web interface still
> >                formats the duration for display purposes)
> >        *  App_cbmysql is updated to work with Asterisk 1.4.0
> >        *  App_cbmysql has it's own build environment now, no
> >                longer requiring a Makefile patch, etc...
> >
> > The new release can be found at:
> >        http://sourceforge.net/projects/web-meetme/
> >
> > We do have a volunteer developer who will be maintaining the
> > 2.X.X chain for Asterisk 1.2.X compatibility, so bug fixes and
> > features that are not Asterisk version dependant will still be
> > made available for older installations.
> >
> > Thanks,
> > The Web-MeetMe development team...
> >
> >
> >
> > HI Dan.
>
> I have been using the Web Meet-Me 2.1.0 on Asterisk 1.2.12.1 for many
> months now and I am a big fan and I have been very happy with it. I want to
> try the v3.0.0 but I would like to know if there are specific steps I need
> to carry out to upgrade to the v3.0.0 on my current Asterisk 1.2.X?
>
> Warm Regards,
> Buki
> (Naija Man)
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
http://lists.digium.com/pipermail/asterisk-users/attachments/20070107/488e0f45/attachment.htm

Buki wrote:
> Sorry I forgot to change the subject line in my last posting!
> I have been using the Web Meet-Me 2.1.0 on Asterisk 1.2.12.1 
> for many months now and I am a big fan and I have been very 
> happy with it. 
I'm glad it's working well for you, positive feedback is always
welcome.
> I want to try the v3.0.0 but I would like to know if there are
> specific steps I need to carry out to upgrade to the v3.0.0 on
> my current Asterisk 1.2.X?
There are a couple answers here.  First is that version 3.0.0
is NOT compatible with Asterisk 1.2.X, so there is no way
to test or use it in your installation.  There is a plan to
release version 2.2.0 soon that has the features and bug fixes
from version 3.0.0 that do not have a dependancy on Asterisk's
version.

The second answer is about the upgrade it self.  Since the package
is mostly php pages, there is not an 'upgrade'.  Just rename the
directory where Web-MeetMe is installed and extract the latest package.
With the 3.0.0 and 2.2.0 releases we have further seperated the
configuration settings from the actual code, so future upgrades
should be able to re-use the ./lib/defines.php.  With the 3.0.0 and
2.2.0 release it will be easiest to just edit the new defines.php
to match your settings.  Lastly you may need to add a couple columns
to your database to take advantage of the improved recurring conference
support.  Refer to the sample tables in the ./cbmysql directory for
details.

Dan


current document root and extract the package to