Knowledgebase: TeamSpeak 3 (ATHPs)
I just received a bill for ATHP licensing. How can I verify the charges? Is there some way to cross-reference the virtual server IDs I'm being billed for?
For starters, it is critical for hosters to understand that TeamSpeak 3 virtual servers should be referenced by their unique virtual server ID and NOT just their IP and Port (like TeamSpeak 2). One reason behind this logic is that TeamSpeak 3 allows you to assign multiple virtual servers to the same port. Therefore, it makes little sense to reference a virtual server by just its IP and Port.

Stated another way, with TeamSpeak 3 we strongly suggest that you retain BOTH your virtual server's IDs and IP (or some other reference point) as part of your billing or provisioning system to help you locate each virtual server. Most hosters already keep track of the IP and Port that they have assigned to a customer. With TeamSpeak 3, hosters should ALSO keep track of the unique virtual server ID provisioned for each of their customers. This will make it a lot easier to later cross-reference your bill.

UPDATE: Our developers have also created an easy-to-use, Perl based script which will aid you in finding the IP, PORT, and VIRTUAL SERVER ID of all of your hosted TeamSpeak 3 Servers to further assist you in cross-referencing your bill. The script includes documentation and sample output. You can download it HERE.

What follows is an example of how to manually verify the slot count on a given virtual server ID. You will need to make use of the TeamSpeak 3 server's query port as follows. Note that we're using localhost as an example and this particular TS3 server has only one virtual server running (most ATHPs have multiple virtual servers running per master binary instance). You can of course replace the localhost and default port 10011 with your physical server's IP address and whatever query port you're using.

% telnet localhost 10011
Connected to localhost.localdomain (
Escape character is '^]'.

We then ask to get a serverlist, including the virtual server IDs as follows:

serverlist -uid
virtualserver_id=1 virtualserver_port=9987 virtualserver_status=online
virtualserver_clientsonline=1 virtualserver_queryclientsonline=1
virtualserver_maxclients=32 virtualserver_uptime=8130166 virtualserver_name=TeamSpeaks]I[sServer virtualserver_autostart=1 virtualserver_machine_id virtualserver_unique_identifier=eIbse78G5JY/TQSbONcYvAStuE8=
error id=0 msg=ok

Notice that we're adding the param "-uid" to the serverlist command. In addition to the normal results for the serverlist command, we also are given the "virtualserver_unique_identifier" which should match with one of the line items on your TeamSpeak 3 ATHP bill. This simplified example only has one single virtualserver, but if we had a number of virtualservers, they would each appear in this listing. Also note the "virtualserver_maxclients" (slots) = 32 in this case...BUT keep in mind that we bill you based on the average monthly slot count which is calculated by adding up the daily configured slot counts on each virtual server you host and dividing by the number of days in the month we're billing you for (again, AVERAGE). In other words, the currently configured slot count you see here may not match what you're being billed for. However, by comparing your own internal data with this data you should be able to determine the accuracy of what you're being billed for.

Another example...let's say that we already know a specific virtualserver running on a specific port and we only want to retrieve that information instead of a full listing so we will instead use the "serveridgetbyport" command. In this case, we want to find out information for the virtualserver running on port 9987:

serveridgetbyport virtualserver_port=9987
error id=0 msg=ok

So, "server_id=1" is returned, giving us the internal server_id that we'll use in following commands. We first need to select this server with the 'use' command ("use server_id") and then retrieve the info with the "serverinfo" command as follows:

use 1

The above serverinfo results are LONG, so we've removed the extra lines for brevity.
(3 vote(s))
Not helpful

Comments (0)