Distributed conferencing works

The Work in Progress version of our platform is available in the project download page, with these new features
implemented so far:  

  • implementation of a new, more flexible, focus discovery and presence manager component;
  • support for the new functionality and messages of the Scheduling Protocol; 
  • remote user invite to a conference; 
  • implementation of a Dispatcher which is in charge to dialog with the (new created in CONFIANCE) Gateway componet;
  • forwarding of Conference Control and BFCP messages to the rigth remote destination by means of an XMPP encapsulation and of a label switching mechanism.

From this moment DCON really works!!!If a user belonging to a focus wants to join a conference hosted by a remote focus he/she simply calls the selected conference number as well as if it were a local conference. The centralized focus understands the conference isn't local and triggers the exchange of a set of messages needed to setup an RTP channel (only for audio) between the involved foci and to add the remote user to the conference. From this moment all messages related to natively centralized protocols (e.g. BFCP)
are appropriately routed and dispatched through the s2s channel. In such way the management of floors is performed by the FCS on the focus hosting the conference. Media flows instead are locally mixed on each cascaded focus and then sent through the RTP channel to the hosting focus. The hosting focus will mix all its local users' media with the incoming flow from all the cascaded foci, and send them back the final mix. Some slides explaining how DCON works are available in the documentation section.

Submitted by tcastaldi on Wed, 07/11/2007 - 16:38.