Are you running the latest stable?
It looks like the latest Jitsi we have is already supporting this when going straight to the room creation screen and making calls.
We, however are using the jitsi lib with custom front-end.
The Jitsi lib is imported with the @lyno npm, which just wraps the standard sdk. Not sure if that package is maintained by someone internal to the jitsi project?
No, it is not maintained by us, no idea about it. It is advised you source lib-jitsi-meet from your deployment so you make sure you are updating the version with the rest of the components otherwise you can face unpredictable problems.
@damencho I extended the origin trial on google chrome for my domain temporary (till I upgrade to latest jitsi meet). Any idea, where/how can I configure that token on haproxy/nginx server? Thanks!
In here jitsi-meet/head.html at master · jitsi/jitsi-meet · GitHub
You can add
<meta http-equiv="origin-trial" content="....
Thanks, Damian, will do👍
I’ve upgraded to jitsi-meet 6726 and unified plan doesn’t seem to be active as Chrome reports the issue with plan B. In addition to the latest stable, is there changes to the configuration to make to enable it?
What version of Chrome are you running?
It’s Chrome 96, current latest
We have a custom UI using the the lib-jitsi-meet Jitsi APIs and everything was stable.
We encountered the Plan B error on chrome, so have upgraded jitsi components so they are on the Unified plan
The jitsi-meet install on our server now works fine with the upgrade so the upgrade has been successful, but our custom UI is facing issues now. The first authorised user see’s themselves only (local track), and then the subsequent users only see 2 tracks themselves (local track) and the authorised user , and do not see any other users.
So to summarise everyone sees the first authorised users remote track, but do not see any other remote tracks.
I am not sure if this has been caused by the unified update or not, but I see you mentioned there was changes made on the Jitsi-meet implementation, so could you advise of what changes we would need to do on the Custom GUI to enable unified or if you think this is possibly caused by something else, if you could suggest what it could be that would be great.
Unified plan changes are all internal to lib-jitsi-meet and should not affect the UI implementation. The change is only how the remote tracks are represented in the session description passed to the browser but the track events are the same irrespective of the mode that the browser is running in. It would be hard to tell what is going wrong with your implementation without looking at the logs.
Thanks for your reply which makes total sense
The Audio tracks for all participants were being added to the remote track object, but not the video
We have further check our implementation and it seems the creation local tracks is not in the order as described by the jitsi example use of the API and seems possible that the upgrade to the latest version of lib-jitsi-meet has tightened its logic around addition of the video track to the conference object.
We are in the process of reconfiguring order for it to match the jitsi documentation and hopefully this will resolve the issue.
Yep it was indeed that we called the API to create the local tracks too early, and earlier versions of lib-jitsi-meet was handling this but the updated ones are not.
Good to share in case anyone else comes across this issue whilst upgrading
Hi, I am getting this error while connecting to jitsi call and am not being audible on the call
I have got a token from developers chrome. I just
wanted to ask what exactly needs to be done after fetching the token… as the info is spread across different posts
Hi, I am facing an issue where in I connect the same call for two different users one on web and one on android device but the audio and video is not working
Also the meet is not connecting to audio and video when using ms edge in my pc and android chrome browser
Can you point me to Jitsi Github MRs where the changes were made to switch to unified plan for chrome? (Following the Deprecation of Plan B SDP)
These are multiple PRs around may- june last year. Just follow the commits around that period …