| 8 Apr 2024 |
 Martin Dougiamas | The client could surely detect a long connection time and offer some debugging help | 14:18:19 |
| Martin Dougiamas | Anyway thanks for your help! | 14:18:40 |
 td | In reply to @daedric:aguiarvieira.pt
Do you have turn servers ? s/turn/livekit these days afaik, maybe someone who has already setup ec can confirm though :D | 14:20:12 |
 Ricardo Duarte | In reply to @td:technodisaster.com
s/turn/livekit these days afaik, maybe someone who has already setup ec can confirm though :D I have livekit... but even then... eturnal gets movement on calls... 🙂 | 14:20:56 |
| Martin Dougiamas | So what's the recommended (most working) way to do this? | 14:23:03 |
| Ricardo Duarte | In reply to @martin:moodle.com
So what's the recommended (most working) way to do this? I come from the Jitsi era... so Turn was configured ... and remained as so 🙂 | 14:23:38 |
| Ricardo Duarte | I have livekit configured as well | 14:23:44 |
| Martin Dougiamas | I've heard about livekit ... is that what Element Call is based on? | 14:24:20 |
 ninchuka | for the SFU I belive | 14:25:53 |
| ninchuka | * for the SFU I believe | 14:26:03 |
| Ricardo Duarte | In reply to @martin:moodle.com
I've heard about livekit ... is that what Element Call is based on? Consider this docker compose and it's individual services | 14:28:54 |
| Ricardo Duarte | https://github.com/element-hq/element-call/blob/livekit/backend-docker-compose.yml | 14:28:55 |
| td | In reply to @martin:moodle.com
So what's the recommended (most working) way to do this? well ideally your element clients would just use the call.element.io backend and not have to do anything afaik, maybe you could poke around the timeline (with hidden events enabled) and look at what state events (org.matrix.msc3401.member) are being sent.
(maybe element desktop just doesn't support this though? Have you tried it on element web? Have you turned on the new group call experience toggle in settings > labs?)
| 14:31:05 |
| Martin Dougiamas | In reply to @td:technodisaster.com
well ideally your element clients would just use the call.element.io backend and not have to do anything afaik, maybe you could poke around the timeline (with hidden events enabled) and look at what state events (org.matrix.msc3401.member) are being sent.
(maybe element desktop just doesn't support this though? Have you tried it on element web? Have you turned on the new group call experience toggle in settings > labs?)
oh, really? yes we all have those labs features on for the Element desktop client | 14:32:37 |
| Martin Dougiamas | In reply to @martin:moodle.com
oh, really? yes we all have those labs features on for the Element desktop client er, Element Nightly, that is. Seems that Element doesn't have those settings at all. Interestingly I notice that Element seems to fall back to turn.matrix.org even for Jitsi, I guess ... I'm also told by my team that we had a TURN server installed already. Anyway, we'll chase this rabbit down the hole a bit. | 14:44:12 |
| Martin Dougiamas | In reply to @martin:moodle.com
oh, really? yes we all have those labs features on for the Element desktop client * er, Element Nightly, that is. Seems that Element doesn't have those settings for Element Call at all. Interestingly I notice that Element seems to fall back to turn.matrix.org even for Jitsi, I guess ... I'm also told by my team that we had a TURN server installed already. Anyway, we'll chase this rabbit down the hole a bit. | 14:44:28 |
| Ricardo Duarte | In reply to @martin:moodle.com
er, Element Nightly, that is. Seems that Element doesn't have those settings for Element Call at all. Interestingly I notice that Element seems to fall back to turn.matrix.org even for Jitsi, I guess ... I'm also told by my team that we had a TURN server installed already. Anyway, we'll chase this rabbit down the hole a bit. The turn server must be configured in the Matrix server | 14:45:37 |
| Ricardo Duarte | REgarding falling back to turn.matrix.org: | 14:46:20 |
| Ricardo Duarte | 
Download image.png | 14:46:22 |
 Florian Heese // away | element call (using livekit) does NOT user turn.matrix.org | 14:49:37 |
| Florian Heese // away | * element call (using livekit) does NOT use turn.matrix.org | 14:49:43 |
| Florian Heese // away | since the SFU is publicly exposed you can directly connect to the SFU | 14:49:57 |
| Martin Dougiamas | In reply to @daedric:aguiarvieira.pt
sent an image. yes that's the one I mean. That's in old element, when they only had Jitsi | 14:50:25 |
| Martin Dougiamas | In reply to @daedric:aguiarvieira.pt
sent an image. * yes that's the one I mean. That's in old Element, when they only had Jitsi | 14:50:34 |
| Ricardo Duarte | It still remains i think... | 14:53:45 |
| Martin Dougiamas | Indeed, it's in Element Nightly, but it appears not to be used by Element Call ... | 15:16:01 |
| Florian Heese // away | In reply to @daedric:aguiarvieira.pt
It still remains i think... even if the setting is part of element dev or nightly it is not consumed by embedded element call | 15:17:04 |
| Martin Dougiamas | Not consumed by anything apparently ... | 15:18:32 |
| Martin Dougiamas | In reply to @fheese:element.io
since the SFU is publicly exposed you can directly connect to the SFU What is SFU? | 15:19:26 |
| Florian Heese // away | In reply to @martin:moodle.com
What is SFU? Selective Forwarding Unit. Its the central place to distribute the media streams to all participants. also jitsi uses an SFU
https://bloggeek.me/webrtcglossary/sfu/ for an intro
| 15:22:00 |
