Discussion:
~~If the homserver does not promote a service url in the well-known we start searching for one on the other homeservers involved in the room. (check user domains)
The reason for this is, that we currently cannot start nor join a call without knowing a sfu service url since we wont just copy over what others have set in their state event.
Even if taht would be possible we could run into a situation where all members with a set foci_active disconnect and only members without foci active are left which would break the call immediately.
So making it a requirement to have a active foci makes sense.
Hence always loading one via the room member list might be a solution~~
In the current version we have not activated the option to load from other room members.
We add Foci from (in the order listed here)
the current rtc session
the hs well-known
the config
DEACTIVATED from other room members homeserver well known.
Instead of always requireig EC to configure a livekit service url we use the homeserver well-known to aquire the sfu to use.
Relies on: https://github.com/matrix-org/matrix-js-sdk/pull/4195
Discussion: ~~If the homserver does not promote a service url in the well-known we start searching for one on the other homeservers involved in the room. (check user domains) The reason for this is, that we currently cannot start nor join a call without knowing a sfu service url since we wont just copy over what others have set in their state event. Even if taht would be possible we could run into a situation where all members with a set foci_active disconnect and only members without foci active are left which would break the call immediately. So making it a requirement to have a active foci makes sense. Hence always loading one via the room member list might be a solution~~
In the current version we have not activated the option to load from other room members. We add Foci from (in the order listed here)
Signed-off-by: Timo K toger5@hotmail.de