Projects tigase _server tigase-http-api Issues #141
Add A/V (coturn) option to setup features (#141)
Wojciech Kapcia (Tigase) opened 2 years ago

In order to have quite complete server it would be good to add option to enable A/V support, which would basically enable TURN/STUN server ext-disco items.

For the simplicity sake by default we could use current/configured VHost as default host and tigase as username and password of coturn. If possible we could add section to customise those items (akin to database root password section).

The option should have also a NOTE/WARNING that it requires configured CoTURN (or any other) server.

  • Wojciech Kapcia (Tigase) batch edited 2 years ago
    Name Previous Value Current Value
    Iterations
    empty
    tigase-server-8.4.0
  • Wojciech Kapcia (Tigase) batch edited 2 years ago
    Name Previous Value Current Value
    Iterations
    tigase-server-8.4.0
    tigase-server-8.5.0
    Version
    tigase-server-8.4.0
    tigase-server-8.5.0
  • Andrzej Wójcik (Tigase) changed state to 'In Progress' 1 year ago
    Previous Value Current Value
    Open
    In Progress
  • Andrzej Wójcik (Tigase) commented 1 year ago

    I've added class to store data and page to collect them, but not connected that to setup flow.

  • Andrzej Wójcik (Tigase) changed state to 'In QA' 3 weeks ago
    Previous Value Current Value
    In Progress
    In QA
  • Andrzej Wójcik (Tigase) changed fields 3 weeks ago
    Name Previous Value Current Value
    Assignee
    andrzej.wojcik
    wojtek
  • Wojciech Kapcia (Tigase) commented 3 weeks ago

    Does it only support configuring TURN(S)? Should we care about STUN @andrzej.wojcik ?

  • Andrzej Wójcik (Tigase) commented 3 weeks ago

    I think it supports both? You just select type (stun or turn) and then the settings are the same. Or is there something else that should be added?

  • Wojciech Kapcia (Tigase) commented 3 weeks ago

    Hmm… assuming one only wants to configure only either TURN or STUN it should be OK I guess. Though shouldn't be allow using both tcp and udp? maybe add option "both"? or use checkboxes? or is it not needed?

  • Andrzej Wójcik (Tigase) commented 3 weeks ago

    If UDP and TCP would be offered then most likely it would be 2 separate entries if I recall correctly. We are offering to configure one in setup. I think this is OK, as WebRTC for calls usually only accepts/uses UDP anyway.

  • Wojciech Kapcia (Tigase) commented 3 weeks ago

    I think that for "bootstrap sake" this is more than enough.

  • Wojciech Kapcia (Tigase) changed state to 'Closed' 3 weeks ago
    Previous Value Current Value
    In QA
    Closed
issue 1 of 1
Type
New Feature
Priority
Normal
Assignee
Version
tigase-server-8.5.0
Target Release
1.0
Sprints
n/a
Customer
n/a
Iterations
Issue Votes (0)
Watchers (3)
Reference
tigase/_server/tigase-http-api#141
Please wait...
Page is in error, reload to recover