Teamspeak 3

Keep it clean please.

Moderator: SHAC administration

Forum rules
Please keep this forum civil and work safe. NSFW topics and similar derailments must be kept to the Off-Topic forum.
Post Reply
Tink
Posts: 498
Joined: Mon Feb 18, 2008 12:21 am
Location: Woking, UK
Contact:

Teamspeak 3

Post by Tink » Tue Jan 12, 2010 6:56 pm

We have moved again! The new teamspeak3 ip is: 85.236.100.85:12517
Usual password applies!

Tink
Posts: 498
Joined: Mon Feb 18, 2008 12:21 am
Location: Woking, UK
Contact:

Re: Teamspeak 3

Post by Tink » Sun Feb 03, 2013 1:16 pm

So why did we move teamspeak 3 hosting?

Periodically (and not to be unfair, it is more rare than regular) we had issues with our teamspeak 3 hosting, lag, bandwidth etc. Each time I dealt with tech support I was essentially told to "turn it off and turn it on again". Normally I comply with their requests, but in over 10 support tickets (over 6 years), the issue is generally eventually on their servers.
Ts3 server @ 78.129.193.145:9994 currently has garbled voice transmissions.
Distorted Voice Issues
From time to time we have customers come and submit tickets that are
having voice issues with a few users on their Ventrilo server. For
instance, user A might be able to hear user B, C, and D fine, but user E
and F, come in as distorted to both A, B, C, D, etc. This is never a
server-side problem, so much as either a Ventrilo or Teamspeak server configuration
issue (i.e., your codec is too high for certain people on your server,
or too low). We generally recommend setting your voice codec to
something middle of the range in terms of bandwidth requirements, such
as a Speex 16-bit 5 Quality, or GSM 22,050 Hz. This will allow for a
high quality voice environment without impacting low-bandwith DSL or
Cable users who are gaming at the same time.

�Diagnose the Problem!
Instead, you should immediately start diagnosing the problem and
determine if it is everyone who is having problems, or just a couple of
users. If it's the entire server, and everyone in it having problems,
lower the codec. Keep lowering until the problem subsides. If it does
not subside, please submit a ticket. But remember -- if you're having 40
people in one channel, all talking at the same time -- it's possible
you will have issues if there's too much bandwidth being sent to your
users and overloading their connections. As long as you have a pretty
solid Internet connection -- you shouldn't have an issue. However, we
have seen users with large raiding groups with 20+ people in a single
channel have troubles with users that had lower-end cable connections (
< 6 Mbps ) that reported heavy congestion during peak hours. This is
why we recommend large raiding groups to use a mid-range codec, or lower
for those with low-grade DSL users.

�Is the problem limited to certain users only?
If the problem is limited to a certain user base, we recommend
talking one-on-one with each user and adjust the settings on a per-user
basis until the problem with the user goes away. Generally this is not a
server problem -- so we do not recommend submitting a support ticket
since there's generally not much we can do about client-related
problems. The only way you should submit a ticket, is if you notice that
when performing a Trace Route, that you get unusually high latency once
you reach the last hop (last hop only -- if you have high ping before
that, ignore it, as it is the router de-prioritizing those ICMP
packets).

�When to submit a ticket
The following indicators will let you know when to submit a ticket:

If the server is lagging for everyone (I.e., > 250ms ping
times for literally every user in the server) for a consistent period of
time.
If the voice distortion issues exist for every player (no
exceptions), and do not go away after lowering the codec to the lowest
possible level. You can try adjusting the codec and limiting the number
of people who talk at the same time, or who exist in the same channel
talking, to ensure that you are not overloading the users connection
speeds (Even Cable/DSL connections can easily become overloaded with
many people conversing on mid-range codecs).
If you perform a trace route and the last hop contains packet loss (indicated by *) or unusually high latency times.
If you perform a trace route and both the last two hops contain packet loss (indicated by a *) or unusually high latency times. (You may also perform a Traceroute or Pathping from a windows command prompt.)
If your server is offline.
There are a whopping 3 people in a channel. Your copy paste is not only rude but ridiculous.

The teamspeak client itself is reporting a 50%+ packetloss for all the members on the server and suggesting that we should turn the codec down from where we have had it for over two years in a channel that regularly gets up to 40 people within it is utterly hillarious.

This is not an acceptable level of technical support. I have reported an issue and your only response is "It's your fault". Have you even looked into it? Utterly unacceptable.
Greetings,

I apologize for the previous response and any inconvenience thus far. It appears there may be an issue with the server at this time but we welcome to you make use of our server redundancy feature in your account to spawn a temporary backup server. Our technicians are aware and are working to resolve this as soon as possible. Below is the message you can find in your account. Please let us know if there is anything further we can assist you with.

A voice machine has been detected as having a severe amount of packet loss or is offline completely. We are aware of this issue and our techs are working to get this resolved as quickly as possible. We will update this status with any further updates as we have them. If this message is being displayed in your panel, this outage effects you. If this outage effects you and your server is not online, there is no need to contact us regarding your server. We are aware of the issue and are working towards a resolution as quickly as possible. Please do not attempt to change your server's location during this outage, it will not work, Instead, please use the "Sever Redundancy" link in your panel to spawn a temporary server.

If you are having any problems setting up the Temporary Server please let us know and we'd be glad to assist in doing so.

Cheers,
*&%&$$$$$
I appreciated the final response, and if it was given first I would have not only been surprised, but also would likely have stayed on. But by that point and given the (unfortunate for them) timing regarding our annual renewal (something that irritatingly locks us in from Feb 12th each year even though renewal is on the 17th) I had no desire to spend another year with them. So I cancelled and by the time the final message arrived, we had already purchased new hosting.

Timing wise this also allows us to keep the old server to redirect people to the new one.

Niknaks
Posts: 214
Joined: Tue Jan 11, 2011 7:01 am
Location: Harrogate, UK

Re: Teamspeak 3

Post by Niknaks » Tue Feb 05, 2013 8:28 am

If you would like a contribution to the anual sub pm me your bank details and i'll transfer some to you mate.
It's a story about a man without a wife, a fire that didn't happen and a cat that didn't look happy!
____
My EJ thread: http://elitistjerks.com/f78/t130892-ass ... ion_mists/

Wolf
Posts: 59
Joined: Thu Jun 07, 2012 9:20 pm

Re: Teamspeak 3

Post by Wolf » Tue Feb 05, 2013 9:23 am

Same here!
"The norwegian vikings will some day return!"

Rosemary
SuperHappyAdventureClub
Posts: 227
Joined: Mon Feb 18, 2008 8:38 am
Location: Wolverhampton

Re: Teamspeak 3

Post by Rosemary » Sun Mar 03, 2013 10:00 pm

Is it down tonight?
Ataxia¬Hvarf¬Rosemary¬Tremulant
L-l-look at you, hacker: a pathetic creature of meat and bone, panting and sweating a-as you run through my corridors.
H-how can you challenge a perfect, immortal machine?

Tink
Posts: 498
Joined: Mon Feb 18, 2008 12:21 am
Location: Woking, UK
Contact:

Re: Teamspeak 3

Post by Tink » Thu Jun 06, 2019 11:45 pm

This server died when multiplay stopped selling servers. There's a mumble somewhere, feel free to poke.

Post Reply