
Originally Posted by
Schlumpi
These days, you need to have this: A link that can be posted anywhere by anyone that, if clicked, does something invisible in background that makes the person who clicked the link connected to the Teamspeak server that was linked by that link. A zero-installation Teamspeak client that works seemlessly within the browser. This is state of the art, this is the kind of voip application that is expected by users.
I know, there is something like client identity, authentication and so on, but you have to work out a system that works without any interaction by the user. Not one click for 95% of the users; the defaults must work. The user just wants to talk. He doesn't want to or is even unable to install and configure things. If you need to dumb down the server and the permission system on the server to support these kind of users: do it! For heaven' sake, do it! Implement what users want and support them up to their capabilities, and their capabilities with computer handling lessens each year with each new generation of computer users, so you need to dumb down and automate software more and more.
If you can have a standalone installable client with more options, fine, but the default app these days must be zero-install and zero-configuration. It should just work without even one click of configuration, if the user set up his headset as default device or default communication device in Windows. Which is the default in Windows, if you plug in the headset.
A modern voip workflow must be this:
1. plug in headset
2. click on link in website
2.5 authenticate or connect as guest
3. talk
This is possible. I work in an enterprise that uses collaboration systems that work this way, so even guests can join immediately and seamlessly without any prerequisite on their client besides headset device and modern browser.