How to read the Server Versions page

The Server Versions page is a one-table summary of every server in your VICIdial cluster — it tells you at a glance whether each box is up, on the right software build, and not about to run out of resources.

Where to find it

Navigate to the Admin Utilities section, which appears as a level-9 link at the bottom of the main reports page. From there, choose Server Versions. The page loads immediately — no date range to set, no filters. You get one row per server, refreshed each time you reload.

What every column means

Each row has these columns, left to right:

• Server name and description — the internal label you gave the box in Administration. For a single-server setup this is typically one row; multi-server clusters show every node.
• IP address — the address VICIdial uses for internal communication. Verify it matches the actual network interface; a stale IP means the cluster cannot reach that node.
• Load — the current Unix load average sampled from that server. This is the same figure you would read with uptime on the command line. Numbers below the CPU core count are normal; numbers that exceed it by a wide margin need attention.
• Channels — the count of active Asterisk channels at the moment the page was loaded. Every call leg, including ringing and hold, occupies a Channel. A count far above what your logged-in agents would explain is a sign of stuck or zombie calls.
• Disk space — the percentage of disk used on that server. This is your early-warning column. When disk fills, recordings stop and the dialer can wedge.
• Time — the system clock on that server. A clock that drifts from the others in your cluster can cause Call recording timestamps to disagree and may break scheduled jobs.
• Version — the astguiclient build string installed on that server. All servers in a cluster must show the same value. A mismatch after a partial upgrade is a known source of subtle, hard-to-reproduce breakage.
• Last change date and time — when the server record was last modified in the Administration panel. Useful for auditing whether someone changed server settings recently.
• Active — whether the server is currently enabled. An inactive server means VICIdial will not send it calls. This column should read Y for every node you expect to be handling traffic.

What a healthy row looks like

A healthy row has: load below the server's core count, a channel figure that matches roughly the number of active calls you would expect, disk usage below 80%, a clock within a second or two of the other nodes, a version string that is identical across all rows, and Active set to Y. Any deviation from that pattern is worth investigating before it becomes an outage.

flowchart TD
  A["Server Versions row"]
  A --> B{"Active = Y?"}
  B -->|No| C["Server excluded from calls"]
  B -->|Yes| D{"Load below core count?"}
  D -->|No| E["Investigate overload"]
  D -->|Yes| F{"Disk below 80 pct?"}
  F -->|No| G["Clear old recordings or logs"]
  F -->|Yes| H{"Version matches other rows?"}
  H -->|No| I["Finish the upgrade on all nodes"]
  H -->|Yes| J["Row is healthy"]

Using this page in your daily routine

Most operators reload this page once at the start of the dialing day and again after any maintenance window. It is quick to scan because you are looking for exceptions, not reading every cell. Pair it with the Server Performance Report when you want the time-series trend behind the current snapshot.

This page fits into the broader habit of checking server state regularly. For a full framework of what to watch and how often, see the guide to monitoring VICIdial server health and capacity.

Want a managed VICIdial box where these numbers are sensible from day one? Start a VICIfast trial and get a fully configured server live in under 40 seconds, with performance logging on from first boot.