ASPnix does not limit bandwidth on our TeamSpeak services, nor do we restrict which sound codecs your server can use. File transfers are limited to 128KBps for both uploading and downloading. We actively monitor our TeamSpeak systems for pirated or copyrighted material; any server found containing such content will be terminated. Several virtual server settings cannot be changed, including server slot count, host message (distinct from the welcome message), host icon (distinct from the host banner), file transfer speed limits, file transfer quota limits, minimum client version, and writing to the server log which is disabled. Other virtual server permissions may also be unavailable for editing on our shared systems.

These policies exist to deliver consistent performance across all hosted instances while protecting the shared infrastructure and meeting legal obligations. Bandwidth caps would degrade audio during peak concurrent usage, and codec restrictions would limit your ability to balance quality against network efficiency. The file transfer throttle prevents one server from saturating host resources. Locked settings maintain separation between customer environments. Understanding these boundaries upfront eliminates trial-and-error configuration and lets you focus on permitted customizations that deliver a robust voice chat experience.

#Bandwidth and Sound Codec Policies

Unrestricted bandwidth means your TeamSpeak server can sustain its full complement of voice channels and clients without artificial throughput ceilings. This matters for gaming groups, training sessions, or large communities where dozens of users may speak simultaneously. Audio quality remains high because the server never has to compress or drop packets due to imposed limits. Similarly, every sound codec supported by the TeamSpeak server software is available. Administrators can select Opus for superior fidelity or narrower-bandwidth options when users connect over mobile or low-speed links. The absence of codec restrictions gives you operational flexibility that many other hosts remove in the name of cost control.

#File Transfer Restrictions

While voice traffic is unrestricted, file transfers receive measured limits to protect the host from bandwidth-intensive abuse. Both upload and download speeds are hard-capped at 128 kilobytes per second. This rate is sufficient for sharing configuration files, small mod packs, or documents but prevents large media libraries from saturating the network interface. A common pitfall is expecting high-speed FTP-like performance inside the TeamSpeak client; attempting to transfer multi-gigabyte archives will be slow and may trigger user complaints. If your workflow depends on frequent large file sharing, consider external services and use TeamSpeak only to distribute links.

  • Upload speed limit: 128KBps
  • Download speed limit: 128KBps

#Settings That Cannot Be Changed

On shared TeamSpeak infrastructure, the following items are locked and cannot be edited through the client, ServerQuery, or any other interface. These restrictions prevent one administrator from altering resource allocations or global host behavior that would affect other customers or violate the hosting agreement.

  • Server slot count
  • Host message (not the same as the welcome message)
  • Host icon (not the same as the host banner)
  • File transfer speed limits
  • File transfer quota limits
  • Minimum client version
  • Writing to the server log is disabled

You may discover additional virtual server permissions are also read-only. This is intentional on shared systems to maintain stability, security, and equitable resource distribution. Attempting to modify these locked values typically results in permission errors or silently failing changes. The distinction between host message and welcome message is frequently misunderstood: the host message appears in server lists and connection dialogs at the host level, while the welcome message is displayed to clients after they successfully join and is user-editable.

#Monitoring for Copyrighted Material

All TeamSpeak servers hosted by ASPnix are subject to active monitoring for pirated software, music, movies, or other copyrighted content. Detection triggers immediate termination of the offending virtual server. This practice complies with legal requirements and shields both the provider and the customer from liability. Administrators should ensure that any files made available through the file browser or channel descriptions are either original or properly licensed. A practical safeguard is to publish clear rules in the welcome message and enforce them with channel moderators.

#Working Within Allowed Permissions

Focus configuration efforts on the broad set of permissions that remain accessible. You can still create complex channel hierarchies, define user groups with granular rights, set custom welcome messages, deploy bots, and adjust most runtime parameters. The official TeamSpeak ServerQuery interface and desktop client continue to expose the majority of day-to-day administrative functions.

#Example: Updating the Welcome Message

bash 
serveredit virtualserver_welcomemessage="Welcome to our TeamSpeak server.\nPlease read the rules in the Information channel.\nTeamspeak 3.1.0 or newer recommended."

# Run this via telnet or a ServerQuery tool after selecting the virtual server instance.

Review the official TeamSpeak permission documentation to identify every editable flag. Test changes in a local development server first so you can distinguish between features blocked by ASPnix policy and those limited by your own permission setup.

Takeaway: Map your intended server design against the locked settings before deployment. Use welcome messages, channel descriptions, and group permissions to communicate rules and capabilities that cannot be enforced through restricted host-level options. This approach yields a stable, policy-compliant voice server that performs well for all connected users. Contact support if you need clarification on whether a particular setting is intentionally unavailable.