[Jingle] Join header for Jingle conferences

Dave Cridland dave at cridland.net
Wed Jul 31 21:29:13 UTC 2013


Interesting - I was thinking MUC as well when reading Emil's post, but in a
different way.

Let's assume the pre-existence of a room, such as jingle at muc.xmpp.org.

Your mixer joins the room, including some additional magic in its presence,
like a <mixer xmlns='...'/> element. It becomes, therefore,
jingle at muc.xmpp.org/mixer

Everyone else then sends Jingle negotiation to its room jid. The mixer sees
the caller's room jid as the sender, and can therefore tie it into specific
conference calls. When the caller has connected, it can add a <mixer
xmlns='...' nick='mixer'/> to indicate its chosen mixer and the fact it's
on-call.

The Mixer can even read off the role for access control/voice, allowing it
to distinguish between mere audience and actual speakers.

As with your hinted deployment, the Mixer could be somebody's Jitsi
connected to the MUC, and the MUC could be a temporary room created for a
mutiparty conversation. Or it could be a dedicated service on a persistent
room, or a feature of the server.

No Jingles were harmed in the making of this protocol.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.jabber.org/pipermail/jingle/attachments/20130731/b8395301/attachment.html>


More information about the Jingle mailing list