iFolder FAQ

What is Conferencing?

Kablink Conferencing is an open source alternative to expensive commercial offerings for real-time meetings (aka. WebEx). Conferencing provides VOIP conference calling (source code only), chat, desktop sharing, and application sharing. Meeting invitations can be sent via email as calendar requests and include call detail and PIN information.

How is Kablink Conferencing different from Novell Conferencing?

Novell's conferencing product sold with Novell Teaming contains audio capabilities that are not present in the 1.X version of conferencing available from SourceForge. The latest source release of Kablink Conferencing contains an Asterisk server for voice integration. So basically, if you get the older ICEcore binary it doesn't have voice whereas Novell's product does. If you compile the server from source you have essentially all the features.

Can I Participate?

Yes! Conferencing is a work-in-progress that can benefit from active community involvement. Regardless of your skill level or time you have to commit to such a project, you can contribute to the Kablink project. We need help developing, documenting, translating, testing, and evangelizing Conferencing. We invite you to participate in any manner that you feel comfortable with.

Please jump in and help as you can. We appreciate all help that can be given.

What operating systems are supported?

There are 3 client platforms that the Conferencing client is available on ...

• Windows XP
• Novell SLED 10
• openSUSE 10.3 and 11

The server runs only on Linux and has been compiled for SLES and RHEL4.

How do I get the open source version of Kablink Conferencing?

Simple. Start here.

What technologies does Kablink Conferencing use?

Kablink Conferencing uses many open source technologies. For instance, we use VNC for desktop sharing, Jabber for messaging, and wxWidgets for our UI. All the source for Kablink Conferencing is written in C and C++. There is an extensive API for creating and managing meetings that can be accessed via XMLRPC.