Version: 0.70.4 (using 4.2.4 (KDE 4.2.4), Gentoo) Compiler: i686-pc-linux-gnu-gcc OS: Linux (i686) release 2.6.29-gentoo-r5 I have Kopete installed from Gentoo with jabber and jingle support enabled. Logging in to "Google Talk" (jabber) works fine and sending instant messages works fine. It is not possible to make voice calls. In the chat window are two buttons "Start audio call", and "Show audio calls", but they are greyed out. I believe the problem could be here (from line 85 kopete/protocols/jabber/jabberchatsession.cpp): JabberResource *bestResource = account()->resourcePool()->bestJabberResource( static_cast<JabberBaseContac if (bestResource) { jingleSessionGui->setEnabled( bestResource->features().canJingle() ); jingleSession->setEnabled( bestResource->features().canJingle() ); } else { jingleSessionGui->setEnabled(false); jingleSession->setEnabled(false); } I can see to resources for a google talk contact - one called "gmail.xyz", the other "Talk.xzy", and there's another one "Automatic (best/default resource)". I assume that the above code is checking if the default resource has jingle capability. If the default resource is the "gmail" one then it probably fails that test and disables making audio calls. This code should probably check if ANY resource can make jingle calls, or something similar.
Yes, it should, thanks for noticing but it would not solve your problem for multiple reasons. First, the Google Talk client still works with the old (Google) version of the Jingle protocol, Kopete works with a pre-version of the new (XMPP) one. Then, Kopete does not implement any NAT and firewall traversal transport. That means that you have to manually enter your public IP and redirect (and open) the necessary ports to your computer. I'm not even sure that the Google client will manage to make a connection like that. And Finally, the sound implementation is really weak (voice will be cut every second) so you won't really ear what your friend is saying. That's the reasons why it will be disabled in kde 4.3 and reactivated when I will have enough time to work on it (actually, it will be as soon as school starts again :-) )
*** This bug has been confirmed by popular vote. ***
The problem with incompatible Google protocol should be solved now. Goggle is swithing to "official" jingle protocol. http://mail.jabber.org/pipermail/jingle/2011-June/001640.html
By the way… how is progress coming along? I am not a C/C++ programmer, and never will be, but if you need some help of any other kind, I’d be willing to assist a bit.
Jingle support in kopete was based on old xmpp jingle draft which is now incompatible with everything. Also jingle support was added to very old xmpp libiris version which has problems with connecting to new xmpp servers. Due to this I removed old jingle support from kopete (which was by default disabled) and updated libiris to new version. Until somebody implement new xmpp xep jingle support I will close this as WONTFIX. Btw Kopete has some code for google libjingle support, but it does not working correctly...