Skip to content
AMBER
Games Pricing Voice Network Docs Blog
DE

Region

  • RUMoscow
  • DEFrankfurt
  • FIHelsinki
  • NLAmsterdam
  • USAshburn
  • PLWarsaw
  • EETallinn
  • LVRiga
  • SWEStockholmSE
  • LITVilniusLT
  • CHZZurichCH
  • FRParis
Request access
Home/Docs/Voice relay setup
  • Quick startFrom an approved access request to a running server, in about ten minutes.
  • SFTP accessHow to connect, where the world files live, and the three paths you should never delete.
  • Mods and pluginsInstalling Paper plugins, Forge modpacks, Valheim BepInEx mods and Workshop collections, and what breaks when a game updates.
  • Backups and restoresWhen backups run, how long they are kept, and how to restore without losing the last hour of play.
  • Ports and firewallWhich ports each template opens, how to add extra ports, and why a port can look open from outside while the server is down.
  • Billing, invoices and trafficHow periods, discounts, VAT and the traffic counter work — and what happens at the limit.
  • TroubleshootingThe failures we see most often, in the order they are worth checking.
  • Voice relay setupChannels, permissions, codec settings and the invite line your players need.

Voice relay setup

Channels, permissions, codec settings and the invite line your players need.

What the relay is

A voice relay process on the node next to your game server. It speaks Opus over UDP and supports a TCP fallback for networks that block UDP. It is not tied to a third-party account: the admin token from the panel is the only credential.

First setup

  1. Open the channel managerPanel → Voice → Channels. The admin token is pre-filled.
  2. Create a lobby channelSet the codec to Opus 64 kbit/s stereo and a jitter buffer of 40 ms. Mono at 48 kbit/s is fine for a large channel where clarity matters less than bandwidth.
  3. Set permissionsChannels are password-protected by default. Grant join and speak to the group you use for players, and keep move and ban for admins.
  4. Copy the inviteThe panel builds a single line with the address, port and channel name. Paste it into your Discord or forum; players click it and their client opens.

Bandwidth

CodecPer listener32 listeners
Opus mono 32 kbit/s~4 KB/s~0.9 Mbit/s
Opus mono 48 kbit/s~6 KB/s~1.4 Mbit/s
Opus stereo 64 kbit/s~8 KB/s~1.9 Mbit/s

The relay is bidirectional: the figures above are per direction, so a full stereo channel uses roughly 3.8 Mbit/s total. A 250 GB monthly allowance is far more than a busy 32-slot channel needs.

Latency

Relay latency on the same node as the game server is under 2 ms. End-to-end for a player in the same city is typically 18–24 ms, which is comparable to a hosted voice service and does not depend on a route through another continent.

Recording and privacy

The relay does not record audio and does not keep a history after a channel empties. Connection metadata — address, channel, connect and disconnect time — is retained for seven days for abuse handling. We do not share it unless a lawful request requires it, and we publish that in the acceptable use policy.

Moving the relay

A relay can be moved to another node in the same region from the panel; the address changes, so the invite line has to be sent again. If you have a DNS record pointing at the old address, update it before the move.

AMBER

Game servers and voice for small communities

Amber Network OÜ
Hanauer Landstraße 182, 60314
Frankfurt
+49 69 4609 0000
support@amber.cfngg.net

Operational All systems operational

Product

  • Pricing
  • Game servers
  • Voice servers
  • Network
  • Status

Resources

  • Documentation
  • Blog
  • Changelog
  • FAQ
  • Contact

Company

  • About
  • Terms of service
  • Privacy
  • Acceptable use
  • Service level

Legal

  • Impressum

© 2026 AMBER. Prices include VAT where applicable. Traffic is counted per calendar month.

Amber Network OÜ · Frankfurt, DE