You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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:
As I said. The server ignores the request. There are no replies. I guess there is some sort of pre-auth in the connection to the Jitsi Videobridge. And yes, it's all the same destination port (443).
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: