19 Jan 2023 |
Dave | I'm not sure what you mean | 13:37:00 |
V1GR | tcp would be used for a voice call as well as udp, is it? | 13:38:20 |
Dave | if you enable tcp turn then it can fall back to tcp to talk to your turn server | 13:40:07 |
V1GR | Got it, thx | 13:41:29 |
V1GR | BTW is it recommendable to enable tls for turn traffic? | 13:43:49 |
Dave | it can help with really restrictive firewalls | 13:44:23 |
20 Jan 2023 |
| Shane Engelman changed their profile picture. | 17:45:52 |
22 Jan 2023 |
| Spireshield joined the room. | 21:18:47 |
23 Jan 2023 |
| bigtestaccount joined the room. | 00:16:06 |
25 Jan 2023 |
| axel changed their display name from axel to axel - away today. | 09:36:37 |
| @gigantino:matrix.org left the room. | 14:55:37 |
| Dino joined the room. | 22:16:32 |
Dino | hello, is this the right place to ask about Element Call? | 22:19:13 |
26 Jan 2023 |
| Dill joined the room. | 00:24:45 |
Dill | In reply to @dino:serifos.uk hello, is this the right place to ask about Element Call? i believe so, yes | 00:24:59 |
Dino | cool, I just want to ask if, in its current form, Element Call can only be used with homeservers that have open registration without email or token auth at all... because I installed Call on my HS, which has reg disabled, and all I get is 'registration disabled' error | 00:35:07 |
Dino | if I enable registration with email or token, I get 'no authentication flow' (I assume Call still can't handle that) | 00:35:30 |
Robin | If you want to use it on with a homeserver without completely open registration, yes, you'll have to login to an account that already exists | 04:38:58 |
Robin | or are you saying that the 'registration disabled' error is blocking you from even doing that? | 04:40:29 |
Dino | In reply to @robin:robin.town If you want to use it on with a homeserver without completely open registration, yes, you'll have to login to an account that already exists Ah OK thanks! I think this should be added to the readme | 07:22:25 |
Dino | In reply to @robin:robin.town or are you saying that the 'registration disabled' error is blocking you from even doing that? Trying to log in takes ages, I couldn't do it yesterday but maybe I didn't give it enough time? I think I read in last year's blog post that Call can't handle normal rooms so we shouldn't log in to a normal/production HS, is that still the case?
In other words, do we need to have a second, separate HS just for Call to work on its own there? | 07:24:07 |
Dino | ok Element Call cannot login to my HS, I get
fetch failed: NetworkError when attempting to fetch resource.
| 08:40:31 |
| axel changed their display name from axel - away today to axel. | 09:32:33 |
Dave | 'NetworkError' would suggest it's, well, a network error rather than it not liking the HS, although hard to tell with no context | 10:50:56 |
Dino | Element Call is on the same VPS as Synapse, and it is happily communicating with Synapse when it tells me 'registration disabled' or 'no authentication flow'... maybe some timeout happening somewhere | 11:03:46 |
Dino | and suddenly it lets me log in...! After a good while... It also doesn't include verification flow so I can't verify the log in. I guess it's still very early stages for it. | 11:25:00 |
Dino | In the end today it's letting me log in but it's flaky, sometimes takes ages.
I wrote up my findings as additions to the README on github (merged a few minutes ago), hopefully it will help others who try to self host Element Call.
I wonder if there is a road map or plan for when it will be included in Element, as currently it really only runs on homeservers that have open registration enabled without any 3pid or token auth (which means you should run it on a separate hs which is unfederated for now). | 16:56:54 |
27 Jan 2023 |
| manu trivedi joined the room. | 05:46:44 |
| @stffn:matrix.org left the room. | 08:11:32 |
| mf changed their profile picture. | 09:52:20 |