-
Notifications
You must be signed in to change notification settings - Fork 319
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
TURN-client tcp-alloc example #391
Comments
It seems to at least get until the point to create a TURN allocation successfully. Make sure you set the flags correctly:
I still need to understand what should happen afterwards. Unfortunately, we don't have seem to have docs for this example. Some info can be found in the original PR. |
Thank you for the response. I will also take a look at the PR. However, I believe I configured the flags correctly. I even tried running the command you provided, and I see essentially the same output as you: Instance with signaling=true:
Instance with signaling=false:
This seems to make sense because I can't establish the On the line allocation.DialTCP("TCP", nil, peerAddr), it appears that the error is originating from this block of code (inside the DialTCP function):
|
You're perfectly right, sorry, I forgot how TCP allocation works. It seems you're right: the problem is indeed in Anyway, if you add this to
Unfortunately, I don't have time now to track this further. Did this ever work? Did we break this sometime after the TCP alloc client got merged? The terrible truth is that we cannot test the TCP alloc code until the server part (#315) gets merged so I can certainly imagine we broke this somehow. Feel like submitting a PR? |
Thank you for the feedback! With the changes, it works! I can try to make a PR; I just have to first get comfortable with making PRs since it is my first time :) |
We would love to have you involved! If you need help/have questions we are here :) |
If you are at it: can you please add some documentation here? No need to be super detailed, just the basic command lines for making it work. Also, you don't have to test against a global TURN server, the original PR contains some info on how to make this work with coturn. |
Thank you both, @Sean-Der and @rg0now! I can add some documentation on how to use the example. Just one question, is there any information on how to use these scripts: scripts/lint-commit-message.sh |
Fixed by #394 |
Hello,
I would like to ask if the TCP allocation example for the TURN client works correctly. I am utilizing a TURN server provided by Open Relay: Free WebRTC TURN Server (metered). However, I encounter the following error:
Failed to dial: invalid TURN server address
This error occurs at line 151 in the example, specifically at conn, err := allocation.DialTCP("tcp", nil, peerAddr). I have not made any changes to the code. I run a local instance of the example using the following commands:
go run test.go -host turn_domain -user=user -password=password -signaling true
and then a second instance with:
go run test.go -host turn_domain -user=user -password=password
I am running Windows 10 with Go version go1.21.2 windows/amd64.
Thank you very much for your help and attention.
The text was updated successfully, but these errors were encountered: