-
-
Notifications
You must be signed in to change notification settings - Fork 42
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
STUN binding request with username attribute #56
Comments
Do you have an example of the replies of the server when running with the |
The server ignores such requests completely. There is no reply. But I don't know it's because of the missing username attribute or anything else. |
Just run with the |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Would it be possible to send the
username
attribute in STUN binding requests? Obviously some STUN servers expect this attribute on binding requests.Does this make sense? I'm not such deep into the STUN protocol but looks like it could be a good addition according to RFC 5389?
I'm currently playing with Jitsi Videobridge (SFU). Wireshark shows that this attribut is set on each initial binding request. Unfortunately, there no corresponding option in
stunner
for that.The text was updated successfully, but these errors were encountered: