I'm having a trying time debugging a fairly straight forward app I've built
using lib-jitsi-meet in an attempt to build something different from
It's setup is similar to lib-jitsi-meet/doc/example/example.js, and I'm
using websockets by specifying bosh: "wss:// ... /xmpp-websocket", have
prosody configured to use websockets, and nginx to pass it through. All of
that seems to work fine, and a multi-party conference is coming up fine.
The reason I want to use websockets is to have better visibility in the
chrome debugger, where I can see the XMPP messages in Chrome's WS network
So everything is going well until I try to use sendEndpointMessage when it
throws a "Channel support is disabled" exception. The app works fine with
straight bosh, however it does not seem to work when using websockets. As
in the example.js, I am passing in the option "openBridgeChannel: true",
and I have changed that to "openBridgeChannel: 'websocket'".
I'm not altogether clear what "openBridgeChannel" is connecting to though,
so I don't know where to look -- is it establishing a channel with Prosody,
or jitsi-videobridge to be able to pass messages between participants?
Should I expect it to work when using websockets for the XMPP?
My ultimate goal is to be able to have one participant be able to send
data/event messages to another participant via XMPP, and ideally via
websockets so that I can see what is going on in the Chrome debugger along
with the rest of the XMPP messages. Maybe I'm going about it all wrong? Is
there perhaps a better way to be passing these messages?