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
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.
The text was updated successfully, but these errors were encountered:
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.
The text was updated successfully, but these errors were encountered: