Looking for some help

[prescottc4]

Over the past week i have found myself trying to get this to work but to no luck. looking over the documentations i do think there should be a more detailed guide, im sure someone with more experience could figure this out but im not the brightest. that being said i have had issues with including the turn server into my homeserver.yaml. using the local docker url for synapse to call for the turn server url so any matrix app would actually accept a turn server. but it appears that regardless of what i do, even though i get a response from _matrix/client/r0/voip/turnServer giving me a password it shows the internal urls again and there is no output from matrix-turnify (even with debug mode on). in my mind it should be working like this
Client -> traefik -> matrix-turnify -> credientials -> end user | but this is clearly not the case since there is no way for a client to know if a valid turn server is available. i am most likely overlooking something simple but regardless i cant figure it out. (any help is much appreciated)

[bpbradley]

Over the past week i have found myself trying to get this to work but to no luck. looking over the documentations i do think there should be a more detailed guide, im sure someone with more experience could figure this out but im not the brightest. that being said i have had issues with including the turn server into my homeserver.yaml. using the local docker url for synapse to call for the turn server url so any matrix app would actually accept a turn server. but it appears that regardless of what i do, even though i get a response from _matrix/client/r0/voip/turnServer giving me a password it shows the internal urls again and there is no output from matrix-turnify (even with debug mode on). in my mind it should be working like this
Client -> traefik -> matrix-turnify -> credientials -> end user | but this is clearly not the case since there is no way for a client to know if a valid turn server is available. i am most likely overlooking something simple but regardless i cant figure it out. (any help is much appreciated)

Sure,

I'll have some time tomorrow to try to help you out.

But the first thing I'll mention that I need to make clear, I originally implemented this back before Element X was stable or commonly used. Now that has changed. To my knowledge, I don't think there's a way to make this work with Element X, because this uses the "legacy" calling interface.

I thought there was, but I took a look recently and I don't think there is. They use a completely different mechanism for connecting clients.

I do plan to revisit this project in the near future. I've been occupied with another project I'm working on. So I definitely need to get back to this to at least update documentation like you said.

But if you are using Element Classic and still experiencing issues, let me know and I will definitely try to help you and then figure out where I need to improve docs.

Thanks for trying out the project!

[prescottc4]

One thing i forgot to mention in my initial message is that we are not using elementX but fluffy chat, (fluffy chat appears to have its own way of identifying real TURN servers) its most likely a simple fix but any help is appreciated.

[bpbradley]

One thing i forgot to mention in my initial message is that we are not using elementX but fluffy chat, (fluffy chat appears to have its own way of identifying real TURN servers) its most likely a simple fix but any help is appreciated.

Gotcha.. I don't use FluffyChat but I've been browsing their code for a bit trying to figure out how it handles calling.

From what I can tell, they support multiple different backends for voip. One of them is the livekit backend, which is what won't work. It just won't request credentials from the home server. But it does have a mesh backend that appears to use the legacy call interface.

It's not super clear to me when one is triggered vs the other without testing myself which I don't have time for right this second unfortunately.

But from what I can tell, the inviteToCall function will call getIceServers which should be hitting the endpoint for turnify.

What I'm not super sure on is what actually triggers that (I'm not really experienced in dart / flutter). I think it might do that when the call is initiated directly to another user, rather than a room. But it could be the other way around, or something else entirely.

Some things to try

1. Try calling a room vs a user and seeing if there is any difference in behavior.
2. While doing this, observe your logs. Turnify logs, synapse logs, and probably best is traefik access logs. This will show you what routes were actually being requested by the client to figure out if the expected route for turnify was hit.
3. Try to make the curl request listed in the documentation for testing using an authorized bearer token to see if you get a response from turnify with credentials.

curl --header "Authorization: Bearer TOKEN_FROM_AUTHORIZED_MATRIX_USER" \
  -X GET https://matrix.example.com/_matrix/client/v3/voip/turnServer

You should get cloudflare calls credentials and see the request in turnify logs.

4. If able, see if you can test with Element Classic / web UI to see if that works, to narrow down the client.

[prescottc4]

While looking into calls using element x i have been able to get it to accept meetings (jitsi) but not direct calls. it returns a "The server is not configured to work with Element Call. Please contact your server admin whenever"
there is no output in matrix-turnify but it whenever i send a request to the server from another device it does return credentials but with no logs. any possible causes would be very helpful ❤️

[lunarr341]

Sorry for such the late response but while trying the things you suggested i have now just noticed that matrix-turnify is not actually binding to any ports, states its listening on 0.0.0.0:4499 however checking docker ps or netstat shows no ports with :4499 open. nothing is using the port.

also important to add but turnify is running with dockers qemu emulation to (aarch64)

questions

• how should turn urls be included in synapse, like "turn:admin-matrix-turnify-1:4499?transport=udp" or should it link cloudflares turn server.

any input on what might be causing this is very much appreciated <3

[bpbradley]

Sorry for such the late response but while trying the things you suggested i have now just noticed that matrix-turnify is not actually binding to any ports, states its listening on 0.0.0.0:4499 however checking docker ps or netstat shows no ports with :4499 open. nothing is using the port.

also important to add but turnify is running with dockers qemu emulation to (aarch64)

questions

• how should turn urls be included in synapse, like "turn:admin-matrix-turnify-1:4499?transport=udp" or should it link cloudflares turn server.

any input on what might be causing this is very much appreciated <3

Yes it should be. But if you do not expose the ports (i.e. via ports section in docker compose), I don't think netstat would show them. I don't bind the port, because I put turnify on the same internal docker network as traefik in my case, which is handling the route for me (as in my sample compose.yaml in README). If you share your compose that would be helpful.

As for how to configure in synapse, you don't need to. Synapse can think turn servers are completely disabled (I have mine disabled in synapse config). The point of turnify is basically to intercept the request for credentials that the homeserver would normally provide, but instead generate cloudflare credentials automatically.

[bpbradley]

While looking into calls using element x i have been able to get it to accept meetings (jitsi) but not direct calls. it returns a "The server is not configured to work with Element Call. Please contact your server admin whenever" there is no output in matrix-turnify but it whenever i send a request to the server from another device it does return credentials but with no logs. any possible causes would be very helpful ❤️

Sorry for late reply here. Like I mentioned turnify won't work on element X. Turnify is for the legacy calling interface. For Element X, this service isn't needed so much. You should be able to configure Element Call with Livekit, which no longer uses TURN servers at all to my knowledge. This service is needed for Element Classic (the app that was used for a long time before Element X became stable). Many still prefer Element Classic, but the TURN server requirements are annoying, which was why I made turnify.

As for not seeing logs, that is strange. Can you set the log level to debug? Like I said I will be doing an update to turnify soon where I can make sure to improve some of those rough edges.

[lunarr341]

editing me here. I'm low-key kinda stupid. traefik was being bypassed and I never noticed, Im gonna fix it and if it does work I will close the issue.
once I get the server working I would be more then happy to update the documentation :)