First of all, Jitsi is spectacular and I’m really grateful for it. It’s covering all my needs out of the box, so that’s phenomenal.
However I’m having trouble with my implementation where events are seemingly never dispatched.
I’ve tried creating a minimal test in JSFiddle and it worked there. In my actual dev environment though it appears as if no events are ever received. This is happening in an Angular 1.5 component controller script: It queries for the div created in the template and instantiates JitsiMeetExternalAPI “by the book”.
I’m on my way reading through the source but from the public API level it seems like the events I am looking for (audioMuteStatusChanged, videoMuteStatusChanged) are expected to be first received by the Transport, and then forwarded to the local API instance’s emit implementation. I made some modifications of the prototype at runtime to observe the behavior and it looks to me like the listener registered with
_transport.on("event", ...) in
_setupListeners never receives any events.
Without having dug deeper, it looks to me like Transport is some kind of low level event bus that also handles remote events, so the actual source of the audio-mute-status-changed event is serverside…?
I realize this is a very general question, but what have you encountered that could cause the transport to fail in my environment? I’ve looked at the verbose logs coming through and I’m not seeing any error messages, so I’m really puzzled right now.
– Andreas R