Skip to main content
Version: Next — legacy draft snapshot

Server groups

Retained Next source

This page preserves the merged Next documentation snapshot at e1ddcf6940adb7b619ce509063749e740eecc795. It can describe implementation beyond the source revision selected for the rebuilt Next guides. Retain the implementation-scope notes below and confirm your deployed version before applying these details. This is not a current-release availability or deployment claim. For the task-based entry point, see the rebuilt guide.

Path: /admin-settings → Server Groups tab

Server groups define pools of API or voice processing servers. They control how traffic is distributed across servers (load balancing) and how the platform automatically adds or removes instances based on demand (auto-scaling).

Server group​

FieldRequiredDescription
Group NameYesUnique (e.g. premium, standard, api-platform).
RoleYesvoice or api. v0.9.15 uses the same model for both.
DescriptionNoNotes.
Servers CountAutoCurrent instances.
EnabledYesMaster toggle.

Load balancing​

FieldRequiredDefaultDescription
LB MethodYes—round_robin / least_connections / weighted_round_robin.
Max Concurrent CallsYes100Per-server cap. When reached, new calls route elsewhere.
PriorityYes—1 – 10 (higher = preferred). Used when multiple groups are available.

Auto-scaling​

FieldRequiredDefaultDescription
Scaling EnabledYesfalseMaster toggle.
Min InstancesYes1Never scales below.
Max InstancesYes10Never scales above.
Scale Up ThresholdYes0.7Utilisation (0 – 1) triggering scale-up.
Scale Down ThresholdYes0.3Utilisation triggering scale-down.
Cooldown SecondsYes300Min wait between scaling actions.
Scaling ProviderYes—hetzner, aws, custom.
Scaling ConfigNo—Provider-specific JSON (machine type, region, SSH keys, …).

How scaling works​

  1. The Scaler monitors average utilisation per group.
  2. When utilisation > Scale Up Threshold, a new instance is provisioned.
  3. When utilisation < Scale Down Threshold, an instance is removed.
  4. The Cooldown prevents rapid up / down churn.
  5. Instance count stays between Min and Max.

Chain to teams​

Voice server groups chain through Server Group → Base Number → Team → Endpoint. Assign groups to base numbers (Base numbers) and to teams (Users and teams).

API server groups use the same scaling model for TelAPI instances. A deployment normally has one api role group for the API fleet.

Workflows​

Create a server group​

Click Create → name + description → configure LB (method, max concurrent, priority) → configure auto-scaling if needed (enable, thresholds, min/max, cooldown, provider, config) → enable → save → assign in Base numbers and Teams.

Adjust scaling thresholds​

Edit the group → adjust Scale Up / Down Threshold and Cooldown → save.

See also​