Craig
OpenMCU only supports basic H.245 notifications of entry and exit. The H.230 standard interface (which is really made up of H.230/H.243/T.124) extends that so the member can request and retrieve the full list of members inside the conference as well as all the conference controls mentioned below. Since it is all standard H.323 (or generic extensions) it can be deployed mixed and matched with existing H.323 equipment. There is a standard conferenceControl capability which is negotiated on connection so if the endpoint supports conference controls then it can utilise these controls, if not then the endpoint can still participate in the conference but does not receive any notifications and operates like an existing OpenMCU member. So really it's an interoperable functional upgrade of OpenMCU. Giving it far greater functionality without losing any of it existing deployments or code base.
Woomera a completely new animal, its a fantastic proprietry add-on solution and it does solve very important and varied issues way way beyond OpenMCU.
I guess what I'm saying is that the OpenMCU development is incremental and standard (in the most part) while Woomera is new and proprietry (in the most part).
Not saying either is better just they are different. :)
Simon
-----Original Message----- From: Craig Southeren [mailto:craigs@postincrement.com] Sent: Wednesday, 7 November 2007 5:34 PM To: Simon Horne Cc: bxg; h323plus@lists.packetizer.com; Opalvoip-devel@lists.sourceforge.net Subject: Re: [h323plus] OpalCall Concept Question
Simon Horne wrote:
Craig
As you are probably aware we will be taking the existing openMCU in a slightly different direction. Having the conference controlled from within the conference itself. Using the recently added H.230 conference control support in h323plus to be able to use H.245 generic messages to assign a chair who can invite/eject users, transfer chair controls to others.
Member
lists can be seen by everyone. A member can be assigned the floor who has limited control like being able to takeover the MCU display and switch the video input from the primary video to the secondary app share input for presentations. Since this developed with the existing openMCU, implementations should be able to migrate/upgrade to include these new features.
Not sure why you think it is different. OpenMCU already has low level support for some of the H.245 conference control messages to implement these functions
And I'm already implementing these kinds of functions in the Woomera-based MCU
Craig
----------------------------------------------------------------------- Craig Southeren Post Increment �C VoIP Consulting and Software craigs@postincrement.com.au www.postincrement.com.au
Phone: +61 243654666 ICQ: #86852844 Fax: +61 243656905 MSN: craig_southeren@hotmail.com Mobile: +61 417231046 Jabber: craigs@jabber.org
"Science is the poetry of reality." Richard Dawkins