Bug 124130 - Support for Tapioca-VoIP, Jingle and SIP,
Summary: Support for Tapioca-VoIP, Jingle and SIP,
Status: RESOLVED FIXED
Alias: None
Product: kopete
Classification: Applications
Component: New plugin wishes (show other bugs)
Version: unspecified
Platform: Compiled Sources Linux
: NOR wishlist
Target Milestone: ---
Assignee: Kopete Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-03-23 13:51 UTC by Gustavo Sverzut Barbieri
Modified: 2023-07-27 13:17 UTC (History)
11 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Gustavo Sverzut Barbieri 2006-03-23 13:51:32 UTC
Version:            (using KDE Devel)
Installed from:    Compiled sources

Tapioca-VoIP (http://tapioca-voip.sourceforge.net/) is a modular VoIP system that consists of a core/server that does SIP and other kind of session initialization and then handles sound exchange using GStreamer. User interfaces can comunicate with core using DBus directly or tapioca-lib, which uses DBus internally.

By using Tapioca-VoIP, Kopete would win for free every procotol and codec it supports, at the moment it do Jingle, H.323, Speex and other supported by GStreamer (however their GUI is still hardcoded for Google Talk).
Comment 1 Thiago Macieira 2006-03-27 22:17:17 UTC
If they use libdbus internally, it'll work. If they use libdbus-glib internally, it WILL NOT work.
Comment 2 Gustavo Sverzut Barbieri 2006-03-27 22:26:37 UTC
You may use raw dbus to talk to core.

If you wish to use libtapioca, which is a helper to easy development and avoid dbus directly, they use libdbus-glib (AFAIK).

But this is not required, just a way to make things easier (or harder in kde sense).
Comment 3 Thiago Macieira 2006-03-27 22:56:50 UTC
well, hopefully, the QtDBus code I'm writing will make the libtapioca completely useless :-)
Comment 4 Aldoo 2006-05-03 18:01:05 UTC
*** This bug has been confirmed by popular vote. ***
Comment 5 Will Stephenson 2006-06-08 11:46:22 UTC
Thiago: could you explain your comment #1?
Comment 6 Thiago Macieira 2006-06-13 23:21:40 UTC
If you try to use any library that links to libdbus-glib-1 in a KDE application, the application will not work, or the library will not.

KDE applications may only link to libdbus-1 (pure) applications. Also note that, for an external application (including any eventual server), the library and the KDE application will appear as two separate connections.
Comment 7 Will Stephenson 2006-11-05 23:07:11 UTC
I'm working on it - no ETA though.
Comment 8 Michaël Larouche 2006-11-05 23:32:03 UTC
Hey Will you are not alone on this task ;)
Comment 9 Matt Rogers 2006-11-08 14:36:47 UTC
Assign back to kopete-devel. This will most likely be done as part of the tapioca/decibel integration work for KDE 4 (if we decide to go that route, it's not real clear yet to me)
Comment 10 Javier Jardon 2008-11-11 18:06:39 UTC
Any progress in this bug? I think that this bug is very important for KDE Desktop
Comment 11 Abner Silva 2008-11-11 19:02:25 UTC
(In reply to comment #10)
> Any progress in this bug? I think that this bug is very important for KDE
> Desktop
> 

Javier,
To be honest I don't know the real status of Decibel, but I know that it still using tapioca-qt for voip/im stuff. So, I think it's just need someone to keep working on it. You can ask decibel related things at irc: #decibel @ freenode

I'll try to get more infos about it and then report here.
Comment 12 Pablo Montepagano 2009-04-28 14:31:27 UTC
Is Decibel a dead project? KDE users will have to use Pidgin/Empathy?
Comment 13 matt 2009-09-27 15:40:06 UTC
would be really great to have decibel/jingle support as in empathy so kde got an own solution for that.
Comment 14 Marcel Partap 2009-10-22 20:36:04 UTC
So the great semantic desktop still has no VOIP client available, what a shame.. ;-/
Comment 15 Mathieu Jobin 2010-03-25 13:18:48 UTC
please !
Comment 16 Heiko Becker 2023-07-27 13:17:29 UTC
It seems this never happened and Tapioca-VoIP is marked as inactive nowadays, so I'll close this.