Account Manager and Channel Dispatcher based on telepathy-glib
Clone or download
Fetching latest commit…
Cannot retrieve the latest commit at this time.
Type Name Latest commit message Commit time
Failed to load latest commit information.


telepathy-mission-control 5

Telepathy Mission Control 5 is an account manager and channel dispatcher for
the Telepathy framework, allowing user interfaces and other clients
to share connections to real-time communication services without conflicting.
It implements the AccountManager and ChannelDispatcher D-Bus APIs as described
by telepathy-spec.

The account manager part stores real time communication account details,
connects to the stored accounts on request, and sets the accounts' presence,
nickname and avatar according to requests from Telepathy user interfaces and
other components.

The channel dispatcher part responds to incoming communication channels
(message streams, voice/video calls, file transfers etc.) by dispatching
them to suitable user interfaces, and requests outgoing communication
channels according to requests from a Telepathy UI.

Telepathy is a D-Bus framework for unifying real time communication,
including instant messaging, voice calls and video calls. It abstracts
differences between protocols to provide a unified interface for


Building Mission Control requires:
  GLib, GObject <>
  libdbus <>
  The D-Bus GLib bindings <>
  telepathy-glib <>

  GNU make <>
  pkg-config <>
  libxslt, xsltproc <>
  Python <>

and can also make use of:
  gtkdoc <>

See for full details, including versions required.
Of the packages listed above, only GLib, GObject, libdbus, dbus-glib and
telepathy-glib are required at runtime.

Building from git also requires the GNU build system (Autoconf, Automake,

Bugs, feature requests and to-do list

Report all bugs, feature requests and "to-do" items here:

D-Bus API stability

Interfaces described as stable in the Telepathy Specification
<> are considered stable and will not
generally have incompatible changes.

All other interfaces (including draft interfaces and Nokia-specific
extensions) are subject to change.

C API stability

The mission-control-plugins library introduced in Mission Control 5.5.0
contains a C API for plugins. All plugins should be compiled and linked
against this library by using the CFLAGS and LIBS from
mission-control-plugins.pc, and installed in the directory given by this
pkg-config query:

    pkg-config --variable=plugindir mission-control-plugins

Incompatible changes in this library's public API/ABI will be avoided whenever
possible. The API and ABI versions can be retrieved with these pkg-config

    pkg-config --variable=MCP_API_VERSION mission-control-plugins
    pkg-config --variable=MCP_ABI_VERSION mission-control-plugins

The older libmcclient and libmissioncontrol-server have no API or ABI
guarantees, and should not generally be used at all. Since version 5.5.0,
their headers are not installed by default.


Mission Control follows the same Linux-style odd/even minor versioning policy
as most other Telepathy components: for instance, the 5.1.x series were
development releases leading to the 5.2.x stable branch.

Intermediate versions built from the git repository have a "+" suffix on the
version number, so version "5.1.0+" could be any snapshot taken between 5.1.0
and 5.1.1.

Contact info

Mission Control was originally written by Nokia Corporation for the Maemo
platform, but it is now maintained by the Telepathy project:


The current development version of MC is available from the
'master' branch in the git repository:
  <> (gitweb)

Stable branches will be made available from branches with names like
'telepathy-mission-control-5.2' in the same repository.

Contributions for review should be attached to bugs in
Bugzilla, with the "patch" tag. If there's no relevant bug, open one:

MC does not yet follow <>. Please
follow the style used in the current code.