Does this mean that it is possible to get access to the XMPP
client object to send messages to specific users? If so, are
there any examples or pointers for doing so?
Do you mean from the JS side? Using our iframe API? Or a generic
I was imagining that within the JS API, there'd be an XMPP client
that's performing the MUC send/receive, and that such a client might
be able to send/receive other arbitrary XMPP commands (like
We actually have two mechanisms that can be used for sending messages between endpoints. One is XMPP, where currently we only use the MUC. It should be possible to modify lib-jitsi-meet to support sending XMPP messages from one client to another (rather than to the whole MUC).
The other way is to use the data channel to the bridge (which itself runs either on top of sctp or web sockets). It already supports sending messages to a specific endpoint only, see the API here. It also already supports sending JSON natively, e.g. on the receiving side you should see an event like this with the payload already parsed.
With both approaches the contents of the message will be readable by the server (prosody in the first case, jitsi-videobridge in the second).
>>> Additionally, I'd like to try setting up an additional data
>>> channel between specific users for arbitrary data streaming on a
>>> per-user basis, but the API only appears to allow for new
>>> channels to be opened to the room as a whole. Is there something
>>> I'm missing, or is data always related by the videobridge server
>>> and never by STUN/TURN?
It shouldn't be too hard to extend the p2p code to have a data channel (or does it already do this?) if you only care about the case of 2 participants. For 3 and more we don't have any direct channels, and adding them would be non-trivial.
On 17/08/2017 12:08, Nick Poole wrote: