Team talk on Linux: How to set up clients

Introduction:

Hello! Me again, back for yet another nerdy and possibly very boring post! Either way, its another Linux how to today. This time, we’re going to be setting up team talk, the popular conferencing software that can be found over here. Lets get started, shall we?

Getting things ready:

First of all, its important to note that you ***absolutely*** must run the team talk software for your architecture. For this guide, I’m using Ubuntu 16.04, 64 bit. That means we’ll be downloading the debian7 package, and we’ll make sure its the x86_64 version. This is important because of the libraries used by the client software.
For ease of use, lets use wget to grab our tar archive. Open a terminal for this part, and be prepared to keep it open.
“wget http://bearware.dk/teamtalk/v5.2.1/teamtalk-v5.2.1-debian7-x86_64.tgz”
After that downloads, you can type:
“tar xvf teamtalk-v5.2.1-debian7-x86_64.tgz”
to inflate the archive. Now, cd to the directory the tar archive just created, then “cd client”, to get to the fun part.

Permissions:

Lets make sure we have the correct permissions for the software to run.
“chmod +x run.sh”
and:
“chmod +x teamtalk5”
should do the trick.

Running the software:

If you managed to complete all the above steps without issue, its time to run your new team talk! From your terminal window, in your client directory, simply type.
“nohup ./run.sh &”
“nohup” insures that we will have a log file to refer to, and the “&” makes sure it vanishes into the background, never to bother your terminal window again! Well, maybe. We still might have to do some…

troubleshooting:

Yeah, this. The fact is, there are far too many things that can go wrong while running team talk software. Your sound devices might just refuse to work, you might have incompatible drivers, and you might not have any libraries! If the software refuses to run all together, you might want to try looking in the “README” file located in the client directory. It provides commands to install all dependencies that are required. Also make sure you didn’t grab the wrong archive. I’m using 64 bit, but you might not be.

Conclusion:

So from this guide, we can work out that team talk, though complicated to run on Linux, is worth it. Its completely accessible, with only a few quirks to speak of, most notably the fact you’re going to have to do some serious messing around with sound devices to make them play nice. I might be able to help with this, but there are far too many details to go into in one post. If you want help, I’m happy to oblige as and when I can, over on my twitter. If you liked this, please be sure to tell me about it.
Thanks for reading!

Advertisements

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s