System settings

The panel's SETTINGS menu groups everything that applies to the whole switch: the currencies you bill in, the timezone and balance rules, the view into the SIP engine, and backups. These are the options that affect every customer at once, so you touch them rarely and deliberately.

Currencies (Settings → Currencies)

NEXIA bills internally in USD. The currencies you add here are conversions on top of that base: each one carries a rate saying how much 1 USD is worth in that currency.

• The default currency is listed first, tagged Default, with a rate of 1.00 (base). It is the system-wide reference: it cannot be edited or deleted, and the panel refuses both explicitly.
• + Add Currency opens the catalogue of supported currencies, showing only the ones you have not added yet. Pick one and it lands in the table with its symbol and name.

The table has one row per currency, with these columns:

Automatic rate syncing

With Auto Sync on, the switch queries public exchange-rate services and updates the value by itself. The check runs in the background every minute, but only writes when your interval has elapsed — so with 12h configured the rate refreshes twice a day, not every minute.

• Turning Auto Sync on for a currency fetches the rate right then.
• The row's Sync button forces an immediate update without waiting for the interval.
• While Auto Sync is on, the rate field is locked: the source of truth is the rate service, not manual editing. Turn it off if you want to pin your own value.
• If the external service does not answer, the previous rate is kept: it never drops to zero or invalidates itself.

Adding, editing, syncing and deleting currencies requires the administrator role.

Server Configuration (Settings → Server Configuration)

Two blocks: Global Settings (the timezone) and Billing & Call Limits (the balance rules). Every change saves immediately — you will see a small Saved flag next to the field. Changing this page requires the superadministrator role.

Server Timezone

This is the switch-wide timezone. Calls are always stored in UTC in the database, but the panel shows them converted to this zone, end to end:

• Dates and times in Calls → Last Calls and in reports.
• The server clock in the footer of every page.
• The hour the daily backup fires (Settings → Backups).

In other words: changing this option does not change the CDRs themselves, only the hour you read them at. Set it to the zone you close your operation and your billing in.

Hangup active calls when balance reaches zero

Decides what happens to calls already in progress when a customer's balance crosses the minimum:

• Off (default): only new calls are blocked. Calls already up finish naturally.
• On: the moment the balance crosses the minimum, every active call of that customer is dropped.

Turning it on caps your overspend exposure; leaving it off prioritises never cutting anyone off mid-sentence. It is a commercial decision, not a technical one.

Call limit balance threshold (USD)

The balance threshold below which the customer's channel allowance is recalculated in proportion to what is left. Default: 10. While the balance stays above the threshold, the channel limit configured on the customer applies with no trimming.

Calls allowed per USD below threshold

How many simultaneous calls the customer is entitled to per dollar of balance once they fall below the threshold. Default: 1. The allowance becomes floor(balance × calls-per-USD), and never exceeds the customer's own limit.

With the defaults (threshold 10, one call per USD):

The allowance recalculates by itself: when a payment or a charge lands, when you edit the customer, and when you change either of these two values (which recalculates every customer at once).

SIP Engine (Settings → SIP Engine)

This is the X-ray of the call engine, live and read-only: it shows how the switch is configured and what it is doing right now, without you having to read the SIP proxy configuration. Everything on it is derived from the running system, not from a hand-written description. Requires the administrator role.

The page has six sections:

• Capacity — how many simultaneous calls are up, this switch's licensed ceiling, how much headroom is left, and the real peak over the last 7 and 30 days. This is the section you plan capacity with.
• The journey of a call — the full path a call takes before it connects, step by step and in order: identifying the source, validating the account, fraud scoring, the balance and channel check, the tariff, the routing rules, carrier selection and handover to the media server. Each step opens up to explain what it decides and when it says no.
• Live engine vitals — the SIP proxy's vital signs: version, uptime, active dialogs, transactions and memory usage. Refreshes every 5 seconds.
• How a call is carried — the parts of the engine and the job each one does.
• Limits in force — the guard-rails protecting the switch: the maximum simultaneous calls and the maximum new calls per second, with the value actually in effect.
• Licence — this server's licence state and the enabled modules. Click it to open the licence certificate.

Backups (Settings → Backups)

This is where you control the daily database copy and automatic CDR archiving. It has its own page: Backups and CDR archiving.

Dashboard

The screen you land on after logging in (and the DASHBOARD menu link). It shows server health and refreshes itself every 10 seconds.

Global status

At the top, a traffic light summarising the whole system:

• All Systems Operational — every service is running.
• N services degraded — something is down; the cards below say which.
• Systems Down — nothing is answering.

Resources: CPU, Memory, Disk

Three cards with the usage percentage and a coloured bar. The bar turns orange at 70% and red at 90% — that is what you watch out of the corner of your eye. Below each one, the detail: core count and system load for CPU, GB used out of total for memory and disk.

Services

One card per component, green Running or red Stopped: SIP proxy (Kamailio), media server (FreeSWITCH), cache (Redis), database (PostgreSQL) and web proxy (Nginx). When a call will not go through and you do not know why, this is the first place to look.

System

Server uptime, load average over 1 / 5 / 15 minutes, and network traffic sent and received. Read the load against the core count: sustained above the number of cores, the server is asking for help.

VoIP Engine

Active Calls (calls connected this instant), media server uptime and SIP proxy state. For the call-by-call detail, go to Calls → Active Calls.

Tickets

The TICKETS menu entry is the product's support channel. The in-panel ticketing system is on its way; in the meantime the page keeps the three routes that do work today within reach: this wiki for guides, routing and troubleshooting, the support email to write to us, and the version history to see what changed in each release.

The About modal

At the foot of every panel page sits the credit © 2026 Nexia Switch. Click it and About opens, a small window with:

• The installed version of NEXIA Switch on this server.
• The link to the product site.
• The link to this wiki.

Close it with Close, the Esc key, or by clicking outside. It is the quick way to know which version you are running when you write to us for support.