I've been trying to create a custom UI for a WebRTC app using the Jitsi
Meet API but I've been having some issues with the time it takes for the
second user to receive the stream.
My setup is the following
- Dev machine: MacBook Pro
- VirtualBox running Ubuntu with jitsi-meet installed.
- Default jitsi-meet configuration plus change in the Prosody config file
to enable CORS. Jitsi Meet is accessible from the host machine at
- My custom app is running locally at https://local-dev.agilityfeat.com, it
is a nodejs app that uses React+Redux. The Redux actions are heavily based
on the https://github.com/jitsi/jitsi-meet-react project.
- Custom app uses lib-jitsi-meet npm module and strophe 1.2.4 from CDNjs.
User A accesses it https://local-meet.agilityfeat.com/mycoolroom
User B joins the conference through the custom app (
User B receives the CONFERENCE_JOINED event
About 15 seconds have to pass after User B had CONFERENCE_JOINED for the
stream to be visible by User A.
Note: I already tried using the custom app on both the ends and the issue
remains. Jitsi Meet works just fine when used on both ends.
*The expected behavior:*
User A should be able to see User B stream way sooner (~3 seconds) like it
happens when using Jitsi Meet on both ends.
I've enabled the debug logs in Prosody and captured the logs for a session.
The user in the custom app joined first. You can find them attached.
I also saved the console logs in both the custom app and the jitsi meet
app. In the custom app the log that takes forever to appear is
<Object.onJingle>: on jingle session-initiate...*
I'm also attaching the file that contains all the Redux actions.
Any clues on why this is happening? Would it had to do with the fact that
the request is coming from a different subdomain (remember I enabled CORS
for prosody)?. Please let me know if I can provide any additional info.
Sorry I'm causing some spam guys, I tried sending the email before with the
attachments included but didn't see the thread in