new join-conference logic for teamspeak 3 plugin

[mfreiholz]

This issue covers two topics:

• how to select server
• how to select correct conference room

  Server selection

Current state There are two options:

• Join now (uses the own private server on the same host machine which runs TS3)
• Join via public server (creates and joins a private conference-room on my public server)

New logic idea (auto-select-server) One single Join option:

• Try to connect to private server on same host and default port (13370)
  • success: well.. use it.
  • error: Tell user about it and offer solutions:
  • join via public server
  • join custom server (by IP)

    Room selection

Current state The room-ID is automatically generated from "TS3-Address"+"TS3-Port"+"TS3-Channel-ID", which is globally unique. The problem here: It only works, if everyone uses the same IP/DNS to join the TS3 server. If someone uses the internal IP like 127.0.0.1 and the other one uses the server's public IP they will join different rooms (see: issue #21)

New logic: Room List

Instead of an automatic room-id generation, the users gets a list of all existing rooms and may be allowed to create a new room (with optional password)

Update 2016-05-31

• Are persistent rooms required or is it enough to keep them as long as there are users?
• What about permissions:
  • Room creator is admin?
  • Do we need roles like "Moderator" and "User"?

In a first approach, I would suggest to keep it simple and implement it like this:

• User clicks "Join"
• TS3VIDEO plugin shows list of available conference rooms
• If there are no rooms, automatically open "Room creation dialog", which allows to set a title and password.

[kiriniko]

Tut mir leid wenn ich hier auf Deutsch antworte, aber das ist für mich gerade einfacher. Ich benutze deine Software nun seit einigen Monaten auf meinem Teamspeak Server mit dem selfhosted Server.

Die neue Server Selection mit nur einer Join Option wäre in meinen Augen sinvoll, da sie a) das joinen auf einen Server einfacher macht (vorallem bei Leuten mit weniger Ahnung bringen die Auswahlmöglichkeiten hin und wieder Verwirrung auf) und b) Self-Hosted Server priorisiert, was man als Serveradmin recht gerne sieht (zumindest meiner Meinung nach).

Bezüglich der Room Selection befürworte ich die Room List, da so für den User auch direkt sichtbar ist, wo denn gerade Leute sind (derzeit hin und wieder etwas umständlich wenn man öfter den Channel wechselt und letzten Endes nichtmehr weiß in welchem Channel-Room man jetzt ist) und da optionaler Passwort Schutz ein Feature ist das ich bisher etwas vermisst habe.

[mfreiholz]

@kiriniko Thanks for your feedback, I appreciate it a lot.

I will update my first post with some ideas about the room-list logic.

[kakomanda]

Hi Dev. Im having this issue too. They connect trough No-IP and i connect by internal LAN IP. Isn't possible to force the app to redirect all connection to a single room? At least temporarily.

Thanks for the awesome work.

[mfreiholz]

The only temporary solution is to use the same external IP address, until the new logic is implemented, sorry.

[Bluscream]

Some routers don't allow connections to your own WAN ip, tho.