Jingle (Jabber)

See also: Jingle

Jingle is an extension of protocol XMPP/Jabber intended for initialization, the follow-up and the termination of sessions Multimédia P2P between customers XMPP/Jabber. Jingle allows the audio sessions (VoIP) and should, in the long term, not only allow videos, but also any type of application based on sessions multi-media.

The various elements of this protocol, under development, are documented in various XEP (“  XMPP Proposal  Extension; ”) that one can distribute in three categories. Initially, the XEP 166 constitutes building block of the protocol, it defines only the semantics of a session. Then, for each method of data transmission recognized, there exists a dedicated XEP. Lastly, for each format of data recognized, there exist the same a dedicated XEP.

History

CHOCKS, defined in the JEP 111 ( Jabber Enhancement Proposals , famous since in XMPP Extensions Proposals ) and since retracted with the profit of Jingle, was the first attempt at extension of protocol to allow the multi-media establishment of sessions between two customers XMPP/Jabber. This not very practical and effective solution proving with use, its originators, Joe Hildebrand and Peter Saint-Andrew, then decided to resume their work with zero and to define very an other protocol for this use.

After the publication of a first draft, Scott Ludwig, of the team of developers of Google Talk, contacted them to announce to them that this draft was very resembling in the spirit and even in syntax the protocol of VoIP developped at the point for their software. Peter Saint-Andrew and Scott Ludwig agreed to join their efforts for a joint definition of protocol. They were largely helped in this task by Joe Beda which also appears in the list of the contributors.

Thus, on October 6th, 2005, the JEP 166 (Jingle) were published and 167 (Jingle Audio). It is only in the month of March 2006 that any reference to a method of transport was withdrawn from the JEP 166 and was moved for a clear division of the definition of Jingle between the various JEP (semantic of a session, transport, formats of data).

Implementation

Side of the implementation of this protocol, after to have promised it a few months before, Google will have placed at the disposal, on December 14th, 2005, in the form of a library of free programming (libjingle), the part of its software implementing this protocol.

The customers Jabber Spark, Coccinella, Pidgin, Jabbin (fork of Psi), Kopete and Psi, the framework Tapioca, as well as the IPBX Asterisk prepares the integration of Jingle by using this library. The free library libDingaLing was also published by FreeSwitch.

External bonds

Protocols

The semantics of a session:
  • XEP-0166: Jingle Signalling
Methods of data transmission:
  • XEP-0176: Jingle RTP-ICE Transport
  • XEP-0177: Jingle Raw UDP Transport
  • XEP-0179: Jingle IAX Transport Method
Formats of data:
  • XEP-0167: Audio Jingle
  • XEP-0180: Video Jingle Media Description Format

Implementations

Libraries: Jabber customers:
  • Coccinella 0.95.12
  • the version of development with Jingle of Kopete
  • Jabbin 2.0
  • the version of development with Jingle of Psi
  • the framework Tapioca

Random links:Sulgen (Thurgovie) | Actinorhytis calapparia | Subduction ante-collision | Jean Lebeuf | 4th stage of the Turn of Catalonia 2007

| Daphne_(usine)