Jitsi room

Jitsi to offer conference calls in rooms, with an experimental Element Call implementation in the works.A set of defaults are applied, pointing at our Jitsi and Element Call instances, to ensure conference calling works, however youcan point Element at your own if you prefer.More information about the Jitsi setup can be found here.The VoIP and Jitsi options are:jitsi: Optional configuration for how to start Jitsi conferences. Currently can only contain a single preferred_domainvalue which points at the domain of the Jitsi instance. Defaults to meet.element.io. This is not used if the Jitsi widgetwas created by an integration manager, or if the homeserver provides Jitsi information in /.well-known/matrix/client. Forexample:{ "jitsi": { "preferred_domain": "meet.jit.si" }}jitsi_widget: Optional configuration for the built-in Jitsi widget. Currently can only contain a single skip_built_in_welcome_screenvalue, denoting whether the "Join Conference" button should be shown. When true (default false), Jitsi calls will skip tothe call instead of having a screen with a single button on it. This is most useful if the Jitsi instance being used alreadyhas a landing page for users to test audio and video before joining the call, otherwise users will automatically join the call.For example:{ "jitsi_widget": { "skip_built_in_welcome_screen": true }}voip: Optional configuration for various VoIP features. Currently can only contain a single obey_asserted_identity value tosend MSC3086-style asserted identity messages during VoIP calls in the room corresponding to the asserted identity. This mustonly be set in trusted environments. The option defaults to false. For example:{ "voip": { "obey_asserted_identity": false }}widget_build_url: Optional URL to have Element make a request to when a user presses the voice/video call buttons in the app,if a call would normally be started by the action. The URL will be called with a roomId query parameter to identify the roombeing called in. The URL must respond with a JSON object similar to the following:{ "widget_id": "$arbitrary_string", "widget": { "creatorUserId": "@user:example.org", "id": "$the_same_widget_id", "type": "m.custom", "waitForIframeLoad": true, "name": "My Widget Name Here", "avatar_url": "mxc://example.org/abc123", "url": " "data": { "title": "Subtitle goes here" } }, "layout": { "container": "top", "index": 0, "width": 65, "height": 50 }}The widget is the content of a normal widget state event. The layout is the layout specifier for the widget being created,as defined by the io.element.widgets.layout state event. By default this applies to all rooms, but the behaviour can be skipped for2-person rooms, causing Element to fall back to 1:1 VoIP, by setting the option widget_build_url_ignore_dm to true.audio_stream_url: Optional URL to pass to Jitsi to enable live streaming. This option is considered experimental and may be removedat any time without notice.element_call: Optional configuration for native group calls using Element Call, with the following subkeys:url: The URL of the Element Call instance to use for native group calls. This option is considered experimentaland may be removed at any time without notice. Defaults to A boolean specifying whether Element Call should be used exclusively as the only VoIP stack inthe app, removing the ability to start legacy 1:1 calls or Jitsi calls. Defaults to false.participant_limit: The maximum number of users who can

Description:I have changed some property about videoQuality in Config.js, but the actual videoQuality is always about 1440x810, can not reach 1080P. So how to let the videoQuality settings work?Steps to reproduce:Edit the config.js file in '/root/.jitsi-meet-cfg/web/config.js'.Make below changes:`// Koala addedconfig.videoQuality.minHeightForQualityLvl = { 1080: 'low'} ;config.resolution = 1080;config.constraints.video.height = { ideal: 1080, max: 1080, min: 1080 };config.constraints.video.width = { ideal: 1920, max: 1920, min: 1920};config.desktopSharingFrameRate = { min: 30, max: 60 };`4. run the command 'chattr +i /root/.jitsi-meet-cfg/web/config.js' and restart the container 'docker-jitsi-meet-stable-8044-1-web-1'.5. Enter the container 'docker-jitsi-meet-stable-8044-1-web-1' and check the file in path: /config/config.js to confirm the changes.6. Re-create a new meeting room and check the frame rate of SharingScreen but the number is always 5.7. Change the frame rate to 30 and starting SharingScreen.8. Check the status of sharingscreen and saw the resolution is '1440x810' and frame rate never over 30.Expected behavior:The actual resolution and frame rate are same as the one I set in config.js .Actual behavior:The actual resolution and frame rate never reached the one I set in config.js .Server information:Jitsi Meet version: stable-8044-1Operating System: Alibaba Cloud Linux 3Running Time: Docker with your official docker imageBandwidth of Server: 200Mbps with DCDN and original server.Client information:Browser / app version: Chrome Version 108.0.5359.94 (Official Build) (arm64)Operating System: MacOS 13.0.1 (22A400)Bandwidth: 200Mbps

Description:We are self-hosting Jitsi Meet and we often get a bug where someone will enable their camera and nobody else will see it. (To others it appears as if the user does not have their camera enabled.)I think it started to happen when we upgraded from 2.0.8719-1 to 2.0.8922-1 (or at least it was not this frequent before).Steps to reproduce:Say you have a room with 2 users.User A enables their camera.User B does not see it.This has been confirmed by several of our users.(I tried to reproduce on but got a different bug: as soon as I enabled my camera, audio and video froze for both me and the other user.)Expected behavior:When an user enables their camera, the other users should see it.Actual behavior:Very often, other users don't see the camera.Server information:Jitsi Meet version: 2.0.8922-1Operating System: Debian GNU/Linux 11 (bullseye)Client information:Browser / app version: Firefox 118.0.1Operating System: Linux Mint 21Additional information:Here is a browser log from the user enabling their camera (Firefox on Linux):Jitsi-camera-sender-logs.txtAnd from the other user (Firefox on Linux):Jitsi-camera-receiver-logs.txt