Skip to content

Support TURN only or STUN only mode for examples/turn-server #283

Description

@danjenkins

Currently if someone wants to only support STUN... they can't disable the TURN server being available. The module should allow you to configure this behaviour in server setup.

Activity

  1. changed the title [-]Support TURN inly or STUN only modes[/-] [+]Support TURN only or STUN only modes[/+] on Jan 20, 2023
  2. changed the title [-]Support TURN only or STUN only modes[/-] [+]Support TURN only or STUN only mode for examples/turn-server[/+] on Jan 20, 2023
  3. stv0g commented on Jan 20, 2023

    @stv0g
    Member

    I assume you are referring to examples/turn-server?

  4. danjenkins commented on Jan 20, 2023

    @danjenkins
    Author

    From what I could see in the code... there's no way to use the module in a STUN only way?

  5. stv0g commented on Jan 21, 2023

    @stv0g
    Member

    No, turn.Server currently does not support filtering which messages are supported.

    If we would add support for it, I would propose to add support for a message handler which would check whether a given message class is supported. Just like we already have handlers for validating permissions and authentication requests.

  6. Sean-Der commented on Jan 11, 2026

    @Sean-Der
    Member

    Cool idea!

    @adrianosela @rg0now What do you think of adding a OnMessage handler? Users could just return false if a message should be dropped and that would allow us to filter all non stun.MethodBinding messages?

    Also unlocks users that want to do custom filtering/logging!

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

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions