Jingle (protocol)

Jingle is an extension to XMPP^[1] (Extensible Messaging and Presence Protocol) which adds peer-to-peer (P2P) session control (signaling) for multimedia interactions such as in Voice over IP (VoIP) or videoconferencing communications. It was designed by Google and the XMPP Standards Foundation. The multimedia streams are delivered using the Real-time Transport Protocol (RTP). If needed, NAT traversal is assisted using Interactive Connectivity Establishment (ICE).

Proposed Jingle logo

As of September 2018^[update], the Jingle specification is a Stable Standard, meaning: " Implementations are encouraged and the protocol is appropriate for deployment in production systems, but some changes to the protocol are possible before it becomes a Final Standard."^[2]

The libjingle library,^[3] used by Google Talk to implement Jingle, has been released to the public under a BSD license. It implements both the current standard protocol and the older, pre-standard version.

Clients supporting Jingle

• Asterisk PBX^{[note 1]}
• Coccinella^{[1][4][5][note 1]}
• Conversations (software)
• Dino (software)
• Empathy^[6] (using Telepathy framework)
• FreeSWITCH
• Gajim
• Google Talk for Gmail, Android,^{[note 2]} Windows^{[note 1][note 2]}
• iChat for Apple OS X
• Jitsi^[7] (multiplatform support using Java)
• KDE Telepathy^[8] (using Telepathy framework)
• Kopete^[9]
• Miranda NG (via JGTalk plugin)^[10]
• Movim
• Pidgin
• Psi^{[note 1]}
• QIP Infium
• Yate/YateClient supports Jingle in both client and server mode, audio and file transfer, also call transfer and DTMF.

Though not an instant messaging client, RemoteVNC uses Jingle as one of the screen sharing means.

Notes

1. Doesn't support video chat.
2. Currently supports only older, pre-standard version.