The RoomWidgetClient (embedded) is calling `/rtc/transports` without authentication

[BillCarsonFr]

The base _unstable_getRTCTransports is calling authedRequest for /rtc/transports.

When using the RoomWidgetClient (widget client), this will always result to a 401 Missing access token.

If we want widgets to support _unstable_getRTCTransports we need to introduce a new widget API action to forward to the host client, similar to other calls

[kherb27]

Is there any timeline when this will be fixed or will it remain for the forseeable future that Element Desktop cannot be used for VoIP using Element X? Is there any temporary fix?

[networkException]

Advertising transports via .well-known should work as a fallback

[kherb27]

Thank you very much! Yes, I thought I currently do this:

{
    "cc.etke.ketesa": {
        "asManagedUsers": [
            "^@hookshot:example\\.org$",
            "^@_github_[a-zA-Z0-9]+:example\\.org$",
            "^@_gitlab_[a-zA-Z0-9]+:example\\.org$",
            "^@_jira_[a-zA-Z0-9]+:example\\.org$",
            "^@_webhooks_[a-zA-Z0-9]+:example\\.org$"
        ],
        "corsCredentials": "same-origin",
        "externalAuthProvider": false,
        "menu": [],
        "restrictBaseUrl": "https://matrix.example.org"
    },
    "m.homeserver": {
        "base_url": "https://matrix.example.org"
    },
    "im.vector.riot.e2ee": {
        "default": true
    },
    "io.element.e2ee": {
        "default": true,
        "secure_backup_required": false,
        "secure_backup_setup_methods": []
    },
    "org.matrix.msc4143.rtc_foci": [
        {
            "livekit_service_url": "https://matrix.example.org/livekit-jwt-service",
            "type": "livekit"
        }
    ]
}

Element in the browser works nicely with Element X on the phone. However, Element Desktop fails ("Error Code: MISSING_MATRIX_RTC_TRANSPORT")