wiki:FAQ

[TracNav?(Index)]]

QuteCom FAQ

Here is a list of common questions regarding QuteCom with their answers. Please, look at this list before asking for help on IRC or on the QuteCom mailing list.

General Questions

Can QuteCom be used with any SIP provider?

Yes.

Is there any chance to see other instant messaging protocols supported?

We only plan to support MSN, Yahoo!, AIM, ICQ, SIP/SIMPLE and Jabber for the 2.x series. However, depending on users needs and feedback, we may add support for other instant messaging protocols, possibly under the form of plugins.

Are there binary GNU/Linux packages?

fixme

Are there universal binaries available for Mac?

Not yet. It is a bit tedious to do, but not that complicated. Universal binaries should come in the short to mid-term future.

Sound on GNU/Linux is chopy, it seems like there's a sampling rate issue as well as some jitter, what should I do?

fixme

Is QuteCom able to place audio and/or video calls through Google Talk network?

Not yet. It is technically possible, we would welcome any contribution on this.

Is QuteCom capable of doing video-conference on MSN and Yahoo! instant messaging networks?

Not yet. It is technically possible, we would welcome any contribution on this.

Is there any embedded version being developed?

Although we plan to support as much embedded platforms as possible, this work has not started yet.

How can I customize QuteCom and ship it to one or several business clients?

Please, e-mail customization at mbdsys dot com and we'll be glad to help you delivering a customized version of QuteCom.

Does QuteCom support encryption of communications?

fixme

Why does the QuteCom community fork all these cool open source libs ?

The community does its best not to fork libs.

Most of the time, the original code is commited as is only for the sake of the automatic builder. This is annoying for some people under certain circumstances and we try to do our best to change this situation in the future.

Sometimes, the code is commited as is but with a very light patch. This allows the community to patch bugs that are not yet accepted upstream but that are critical to the quality of the QuteCom a page is dedicated to following the status of the external libraries?

Compiling FAQ

Which compilers can i use to build QuteCom?

On Windows, you should use Visual Studio 2003. On GNU/Linux and MacOS X, you should use GCC 4.X. We plan to support MinGW on all platforms as well as Visual Studio 2005 Free Edition. Any patch, test or other contribution on this subject would be greatly appreciated.

I see that there is a GTK frontend being developed, and i don't want to install the new Qt version, what should i do?

The Qt frontend is the one that get the most attention today. However, as the design of QuteCom is modular, it should be straightforward to implement a GTK frontend for it. An initial implementation has been done, but has not been updated for the 2.x releases.

While Qt has proven very robust and featureful, we'd love to have a GTK frontend too. A featureful and sucessful GTK frontend would also validate our design decisions, so feel free to scratch your itch on this ;-).

GCC complains about boost's visit_each symbol missing, what should I do?

If you get an error message from GCC similar to the following:

/usr/include/boost/bind.hpp:1208: error: no matching function for call to ‘visit_each(boost::signals::detail::bound_objects_visitor&, QtConfigPanel* const&, int)’

it probably means that you're building QuteCom with GCC 4.1.x. One solution is to use a GCC version not later than GCC 4.0.x. Another would be to use Boost from CVS, or a pretty recent snapshot.

Running and Testing FAQ

I can't hear anything when placing a call, what should i do?

It probably means that you are using the null audio driver. Please, try to use the portaudio audio driver by setting the PH_FORCE_AUDIO_DEVICE environment variable to "pa:" using the following command line :

export PH_FORCE_AUDIO_DEVICE="pa:" 

debuging

Some tools to help debugging if you need it:

Run on the command line. Warnings & errors are enabled by default, you should see some sound card related messages.

strace will show you all system calls made by the application.

Change the debug level: set the environment variable OWLOGGER_DEFAULT to "debug" to get lots more messages when running from the command line.

You can debug just the audio component by unsetting OWLOGGER_DEFAULT and just setting OWLOGGER_SOUND to "debug" should debug sound more heavily than the other components.

Just after QuteCom starts, there is an assertion failure about _BLOCK_TYPE_IS_VALID(...), what should I do?

You're probably mixing libraries linked in debug or release mode with binaries or libraries built in the other mode. Please, try to build everything in either debug or release mode, and restart QuteCom.

MacOS X specific FAQ

When calling, I get no sound or a lot of weird squeaky noises out of my speakers, what should I do?

Set your PH_FORCE_AUDIO_DEVICE environment variable to 'ca:' using the following command line:

export PH_FORCE_AUDIO_DEVICE="ca:"

I get a "illegal reference to symbol" error between libstdc++.a and libstdc++.6.dylib when linking. What should I do?

This error can occur when compiling the WengoPhone NG? on MacOS X 10.3.9 with XCode 1.5. See this mailing list for more details.

To correct this problem you have to downgrade Quicktime to version 7.0.3. Use the downgrader provided by Apple on this website then go here to update to 7.0.3. The linkage should work then.

When using precompiled version of Qt 4.2.2 from Trolltech, I got the following error: "'QtValidLicenseForCoreModule?' does not name a type"

Trolltech forgot to set the QT_EDITION variable in the package. Edit /Library/Frameworks/QtCore?.framework/Versions/4/Headers/qconfig.h and change line 5:

# define QT_EDITION QT_EDITION_UNKNOWN

to

# define QT_EDITION QT_EDITION_OPENSOURCE

GNU/Linux specific FAQ

When I start the QuteCom under Gnome I get a SIGCHILD in the console, and it takes a long time to start

This is probably caused by the Cleanlooks widget style. Try starting the application with the Plastique style, like this:

wengophone -style plastique
Last modified 17 months ago Last modified on 05/19/2013 03:01:18 PM