Ian Knowles

Using the extra notification "hack" the call signalling (after I click Join Call from my laptop) also takes no more than 2s (but as you're aware due the RTC Session...

Oh yes - sorry - you has commented in the other Issue (https://github.com/element-hq/element-call/issues/3257) but were not having such problems although I noticed that you stated "Not element-call but widget mode"...

> You might be using old jitsi-call in element-desktop. I am using Livekit - this is a redacted portion of the log relevant to a call that ended with an...

I have been experiencing the exact same problem (and submitted a couple of rage shake reports) - it happens using either the Apple or Android versions of Element X and...

I am wondering if the livekit-jwt service has something to do with this as I see the following (redacted) lines in its log: ``` May 10 17:09:54 lk-jwt-service[32152]: 2025/05/10 17:09:54...

> If is referring to the same in the following both lines that is indeed wrong. I'm not sure that *wrong* is accurate as it does work that way (i.e....

This is some typical (redacted) log lines from the "livekit-sfu" service when starting an Element-Calll (the one that was working for ten minutes before I got the RTCSession Error): ```...

> I am pretty sure it does matter, otherwise the clients won't be able to see each other. If the clients can't see each other then how did I manage...

Just to follow up - I enabled TURN for Livekit and it made no difference at all (call connected then died after a minute with the familiar RTC_Session Error). >...

As stated I am just using a single hostname (with reverse proxies to be more clear) and I have shown that both livekit-jwt and livekit-sfu are working (including adding Livekit's...