The one feature I really like with Openmeetings is the "Remote Desktop control"...which is the ability to remotely control the desktop of meeting participant.
BBB does not have this feature. You can share your desktop, but you can not control someone else...this was the case when we looked into this 6 months ago. We ended up going with Openmeetings integration for that reason. -M >>> Tony Graziano <[email protected]> 01/14/11 3:52 PM >>> I found the AUDIO function in BBB to be somewhat problematic. * MUTE function on FS in BBB uses twice CPU per user as non-muted. * Uploaded documents do not scale beyond desktop size, making them hard to read. * AUDIO and VIDEO sync is poor. When Audio is removed, and a normal call is in place to take its place, video is MUCH better sync'ed. * Usability, for the end user is not nearly as polished. * Based on RAM/CPU, this needs to be a standalone server for this one process. 5-6% of CPU for muted calls (per user) and up to 100MB per call (audio) via browser, due to encode/decode processes, is a bit high. * It would be nice to remove AUDIO completely and have a paddle/user shown only code they can use when entering conference (lua script) to associate audio with user, moving AUDIO controls into FLEX on BBB for centralized control. The API would have to be utilized for all user/room access controls. This approach might be feasible for other projects... * BBB has some things in place to start accessing the camera from a DROID, making a handheld cam in the field able to transmit into a meeting. At the same time, Openmeeting looks to have the desktop scaling and other items associated solved, and can record the sessions, whereas BBB cannot as of yet. OM also has the ability to join "just" audio or video. The user tools are more plentiful. OM would need some changes (not use port 5080 to connect), I have an OM system up, but am building a downloadable VM based on Centos 5.5 for further testing. I already have a BBB VM running (they readily supply one). I have to dig into it and see what to do to get the system to respond on a different port. /t </[email protected]>
_______________________________________________ sipx-users mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-users/
