-
Notifications
You must be signed in to change notification settings - Fork 49
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
documentation questions #5
Comments
9000 is for the default TURN is not a requirement, but recommended for better connection. I'm not familiar with container configurations, sorry. |
I guess kraken is listening on some UDP port for the webrtc connection or how is the audio transmitted? |
If you don't use turn, then you should open as many UDP ports as possible |
I use turn server so that I could only open one port to the public, the the turn server connect with kraken via vpc |
I cannot forward all 65535 UDP ports to kraken. With other voip software you usually can configure a range of UDP ports. It's not clear which port range is used by kraken. |
I will try to add some configurations for port range. |
Thanks for the port range configuration commit. I'm still not sure how to use kraken and kraken.fm without a turn server. I'm running kraken in an LXC container on a local IP, ports are forwarded from the public IP to the local IP. What should I put in TURNSERVER in kraken.fm/index.js or should I comment out iceServers and iceTransportPolicy? I also don't know what the error message means:
|
Hi, I am facing same issue while running the server and client on local.
Were you able to solve the issue? |
To run the client and server in local, please do this modification in index.js const configuration = {
- iceServers: [{
- urls: TURNSERVER,
- username: "webrtc",
- credential: "turnpassword"
- }],
- iceTransportPolicy: 'relay',
+ iceTransportPolicy: 'all', |
it's still not working for me. I wonder if it has to do with the non-public IP that kraken is using. Is there a way to configure/set the public IP? |
Maybe change the interface name in the configuration? I'm not familiar with container, maybe you could try something without container at first? |
The interface name is correct (eth0). I just tested it without a container and it seems to work fine. I guess all it needs to work inside a container is a configuration option to set the IP address. I'm running a webrtc proxy for Mumble and it works fine insider a container with NAT. |
Please try the new configuration. |
looks good :). no errors in the log and audio works between mobile and desktop browser. |
I have some questions that are not covered by the documentation:
Is port 9000 used for anything? (it shows up in netstat)
Do I need coturn or does kraken also work without a turnserver?
https://github.com/MixinNetwork/kraken#quick-start doesn't mention a turnserver,
but https://vec.io/posts/deploy-a-group-audio-conferencing-service does.
I'm running kraken inside a container with a local IP and and a reverse proxy on the public IP. Do I have to configure any additional port forwards? (UDP ports?)
The text was updated successfully, but these errors were encountered: