Skip to content
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

[Feature Request] Add port information for STUNS/TURNS 5349 #8050

Open
2 tasks done
OdinVex opened this issue Nov 9, 2024 · 0 comments
Open
2 tasks done

[Feature Request] Add port information for STUNS/TURNS 5349 #8050

OdinVex opened this issue Nov 9, 2024 · 0 comments

Comments

@OdinVex
Copy link

OdinVex commented Nov 9, 2024

Important notices

Before you add a new report, we ask you kindly to acknowledge the following:

Is your feature request related to a problem? Please describe.

It isn't related to a problem, just a suggestion for clarity. The UI doesn't show what protocol is assumed for port 5349 traffic like it does for 3478.

Describe the solution you like

Add port information for 5349 as STUNS/TURNS. Perhaps it could be called "STUNS/TURNS".

Describe alternatives you considered

An alias takes up more space in the UI and requires alias-processing.

Additional context

RFC and IANA have 5349 as STUN over (D)TLS/TURN over (D)TLS.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

No branches or pull requests

1 participant