Difference between revisions of "Telepathy Connection Manager"

From reSIProcate
Jump to navigation Jump to search
 
(6 intermediate revisions by the same user not shown)
Line 13: Line 13:
 
* create a package of this code, potentially called telepathy-resiprocate, for the Linux distributions
 
* create a package of this code, potentially called telepathy-resiprocate, for the Linux distributions
  
To maximize the usefulness of this project, it would first be desirable to adapt ReCon to use [https://developers.google.com/talk/libjingle/developer_guide?hl=en libjingle] instead of sipXtapi, for compatibility with WebRTC clients and all the latest codecs, SRTP, AVPF and other features.
+
To maximize the usefulness of this project, it would first be desirable to adapt ReCon to use [https://developers.google.com/talk/libjingle/developer_guide?hl=en libjingle] instead of sipXtapi, for compatibility with WebRTC clients and all the latest codecs, SRTP, AVPF and other features.  Use of libjingle is tracked in [https://www.resiprocate.org/bugzilla/show_bug.cgi?id=93 Bug #93].
 +
 
 +
== Project status ==
 +
 
 +
A proof of concept has been developed (in the repository under apps/telepathy) and [http://list.resiprocate.org/archive/resiprocate-devel/msg08972.html announced on the reSIProcate and Telepathy mailing lists].
  
 
== License validation ==
 
== License validation ==
Line 24: Line 28:
  
 
* [https://www.resiprocate.org/bugzilla/show_bug.cgi?id=92 Bug #92] for tracking this work
 
* [https://www.resiprocate.org/bugzilla/show_bug.cgi?id=92 Bug #92] for tracking this work
 +
* [http://lists.freedesktop.org/archives/telepathy/2015-August/006699.html Discussion on Telepathy mailing list]
 +
** Seems to conclude that TelepathyQt is the API to use (under active development, supported, C++)
 +
*** mentions API breakage in TelepathyQt releases
 +
*** mentions static linking
 +
*** I notice Debian has 0.9.4 while newer distributions have 0.9.6
 
* [http://telepathy.freedesktop.org/doc/book/ Telepathy API documentation]
 
* [http://telepathy.freedesktop.org/doc/book/ Telepathy API documentation]
 
* [http://telepathy.freedesktop.org/doc/telepathy-glib/ telepathy-glib API documentation]
 
* [http://telepathy.freedesktop.org/doc/telepathy-glib/ telepathy-glib API documentation]
* [https://github.com/TelepathyQt/telepathy-morse telepathy-morse component], a connection manager developed in C++
+
* [http://telepathy.freedesktop.org/doc/telepathy-qt/ telepathy-qt API documentation]
 +
** [https://github.com/TelepathyQt/telepathy-qt telepathy-qt on Github]
 +
** [https://github.com/TelepathyQt/telepathy-morse telepathy-morse component], a connection manager developed in C++ using telepathy-qt
 +
* [http://telepathy.freedesktop.org/wiki/Components/ list of many telepathy components including connection managers]
 +
* [http://maemo.org/development/documentation/manuals/4-0-x/implementing_custom_connection_managers/ Maemo document about implementing a connection manager for Telepathy]

Latest revision as of 00:36, 16 October 2015

Telepathy is the communication framework of the Free Desktop project, commonly used as part of GNOME and KDE desktops on GNU/Linux distributions. Telepathy works with back-ends (connection managers) and front-ends such as the GNOME Empathy application for voice, webcam and IM chat.

There is currently a SIP connection manager for Telepathy called telepathy-rakia based on Sofia SIP. Sofia SIP is no longer actively maintained (last release 2011) and has fewer capabilities than reSIProcate.

Creating a reSIProcate-based connection manager for Telepathy is now viable because reSIProcate packages are available on the major GNU/Linux distributions.

The reSIProcate ReCon API is a high-level API that conveniently supports the API calls for a Telepathy Connection Manager.

It is necessary to

  • develop and test glue-code for mapping the Telepathy API calls for voice/video calling to ReCon API calls
  • develop and test glue-code for mapping the Telapathy API calls for IM (presence, messaging) to Dialog Usage Manager API calls.
  • create a package of this code, potentially called telepathy-resiprocate, for the Linux distributions

To maximize the usefulness of this project, it would first be desirable to adapt ReCon to use libjingle instead of sipXtapi, for compatibility with WebRTC clients and all the latest codecs, SRTP, AVPF and other features. Use of libjingle is tracked in Bug #93.

Project status[edit]

A proof of concept has been developed (in the repository under apps/telepathy) and announced on the reSIProcate and Telepathy mailing lists.

License validation[edit]

  • The libjingle license is BSD
  • The reSIProcate license is Vovida (not GPL compatible)
  • The Telepathy and Telepathy-glib licenses are LGPL, this is compatible with the reSIProcate and libjingle licenses.

Reference material[edit]