So, what’s so good about Dokeos videoconference?
I’m often faced (locally) to the question about our videoconference tool…
Although sadly DHTML doesn’t manage video streams, at least OpenLaszlo offered a possible future choice, so we went on with that.
It so happened that we weren’t completely satisfied with the work of Sebastian, and there was a lot of misunderstanding, and we finally decided to end our collaboration and start to code on top of what Sebastian had built. Arnaud Ligot and myself worked a lot to clean the code and make it more extensible, while Sebastian went his own way with the same original code to build a project called OpenMeeting, which should still be alive today (I haven’t checked for a while).
Instead of adding more features to the tool, we decided to remove some of them and to build on the reliability of the tool, which has now brought us to a solution that is very stable, uses the Red5 streaming much more efficiently and is easier to work on.
So, what are these things that make the Dokeos videoconference so special? Well, I can certainly list a few:
- linked to course contents (you can add images/slides in your normal Dokeos course and then use it inside the videoconference)
- 2 conference types: conference (1 speaker, many listeners) and virtual meeting (4 people together as speakers and listeners)
- each course has one videoconference room and one virtual meeting room
- written chat
- slides are writable (you can add text or marks to the slide on screen)
- controllable access to the streaming server (by portal)
- totally free if you decide to install it and manage it yourself
- totally open-source (resources, code, compiled versions)
- the *only* thing you need to use the tool is a recent browser with the Flash plugin, and pretty much any desktop system has that
- you can use a special mode to make the signal go through port 80, avoiding most problems related to firewalls
Apart from that, there are many features that we might need to add in the future, if our clients would like to finance/contribute to that, like:
- sharing the voice/video with a member of the public for a limited time
- web browsing
- recording of the whole videoconference sequence
- download of slides by the public
Some of these features were actually available in the first videoconference tool, but we had to remove them for lack of support (and so lack of stability).
So if you ask me now, what’s so good about the Dokeos videoconference tool, I’m pretty much going to tell you:
- you can use it with whichever system is more practical for you
- it is reliable and it looks good
- you can do most of what you would like to do with a videoconference tool
- it can go through your company’s firewall
- its link to a Dokeos course is smart