As of September2018[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]
Data Flows
Data Flows for a client CA on XMPP server SA setting a Jingle session to client CB on XMPP server SB
When Client CA is communicating with Client CB in a chat (i.e. one user communicating with another user, on the same of different servers) they client software on both ends uses the Jingle parts of the XMPP specification to establish if they are both Jingle capable. If they can negotiate a way to talk directly, e.g. over RTP (XEP-0167), then they will generally show the user a Telephone or Video icon, enabling them to establish a direct connection to the other client.
Libraries
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.
↑"Use", Kopete, Zugaina, archived from the original on 2013-12-02, retrieved 2013-11-20, Jingle functionality (voice only) can be enabled/disabled in Kopete. The old KDE Wiki statement about it not working is outdated.
This page is based on this Wikipedia article Text is available under the CC BY-SA 4.0 license; additional terms may apply. Images, videos and audio are available under their respective licenses.
