Operation

Clients, connection points and portal

Everything that represents a customer in NEXIA lives under the Users menu: the account and its balance, the points where traffic comes in and goes out, the numbers presented as caller ID, and the self-service portal. This page walks through the four pieces and closes with the full onboarding of a new customer.

Carriers are users too. The difference isn't the account, it's the connection point: a customer has origination points, a provider has termination points. The same Users list holds both.

Users: the account

Where: Users → Users. The grid shows username, company, how many origination and termination points the account has, balance, currency, time zone and status. Every row has + BALANCE (credit funds), EDIT, HIDE and DELETE. On top you get a search box, a Hidden Users toggle and + Add New.

Account fields

  • AccountUsername and Password, the display name or company (Display Name / Company), and the Activate WEB interface checkbox (see below).
  • BillingBilling Type Prepaid or Postpaid, Currency and the current Balance. Postpaid unlocks Credit Limit (maximum negative balance allowed) and Min Balance Alert.
  • Call SettingsCall Limit and CPS at the account level: at 0 the per-connection-point limits rule; set above zero and you impose a cap on concurrent calls (or calls per second) across all of that customer's points. Also the Time Zone, which drives billing and how they see their CDRs, plus Hidden and Hide non-answered calls.
  • BlockingNot Blocked, Blocked or Block as Conditional. A blocked customer stops passing traffic immediately.
  • Warning Balance — alerts you when the balance drops below (or rises above) the threshold you set.
  • Details, Contact Emails and Address — tax ID, language, country, phone, address, and separate emails for general contact, NOC, billing and rates, so every notice reaches the right desk.

Origination Points: where traffic comes in

Where: Users → Origination Points. An OP is a customer's front door. One customer can have several — a branch, a softswitch, a dialer — and each is configured on its own.

SectionWhat it defines
GeneralThe owning user, a description, Ringing Timeout and Grace Period in seconds.
NetworkIP Address, Port (5060 by default) and Transport UDP, TCP or TLS. On creation you can enter a single IP, a CIDR range or a list of IPs and NEXIA creates one point per address.
AuthenticationThree modes: IP Based (fixed IP, no credentials), IP + Credentials (fixed IP plus user and password) and Dynamic / Registration (user and password from any IP). The Generate button builds a random login and password.
LimitsCapacity, this point's concurrent calls (0 = unlimited), and CPS, the maximum new calls per second.
CodecsDrag codecs from Available to Active and order them by priority. Enforce same codecs on calling leg forces the inbound leg onto the same codec.
RoutingTech Prefix, Sell Tariff and Routing Group.
CallerIDHow the customer presents itself outbound.
AdvancedDTMF Mode, Qualify (OPTIONS ping to know whether the point is alive) and Ignore SIP 183 without SDP.

Tech prefix

It's the prefix the customer prepends to the number. NEXIA validates and strips it before routing: if the point requires a prefix and the call doesn't carry it, the call never gets in. Every new OP is offered a unique 6-digit prefix (Generate makes another one); leave the field empty if you don't want to require one.

Sell tariff and routing group

Both live on the origination point, not on the account. That means the same customer can have one point on one rate deck and another point on a different one, or take different routes depending on where the call came in.

  • Sell Tariff — the rate deck you charge them. Without a rate covering the destination the call is rejected: NEXIA never invents a price.
  • Routing Group — the rule set that decides which carrier this point's traffic goes out through. Full detail in Routing and Dial Peers.

CallerID

  • Passthrough — send the caller's own caller ID, untouched.
  • Fixed — always the same number (and optionally a name).
  • Number pool — a random number from the chosen pool, different on every call.

Termination Points: where traffic goes out

Where: Users → Termination Points. A TP is a carrier: where NEXIA hands the call off. The form is the same one you use for an OP — network, authentication, limits, codecs, advanced — with two differences:

  • Buy Tariff — the cost rate deck, what that carrier charges you. NEXIA uses it to cost the call and to rank candidates by price. If it's empty or has no rate for the destination, sending out through that TP is rejected with 503.
  • Tech Prefix — here it's the prefix the carrier requires, and NEXIA prepends it on the way out.

Capacity works exactly as on an OP: Capacity for concurrent calls and CPS for calls per second. A TP does not route by itself: it is assigned to one or several dial peers, and that's where you define which destinations go through it, at what priority against the other carriers, and what happens if it rejects.

In the Connection Points grid, the Status column shows Active or Disabled and, next to it, the live SIP state: REG with latency if the point is registered, or SIP OK if it answers the ping. The Call Flow button opens that point's monitor and INFO its data sheet.

Number Pools

Where: Users → Number Pools. A pool is a named list of numbers you can present as caller ID. An origination point set to Number pool picks one at random on every call, so traffic rotates across your whole inventory instead of always leaving on the same number.

  • + New Pool: name, description and the numbers, one per line or comma-separated. You can also Import from file from CSV, TXT, XLS or XLSX: every cell is scanned, and headers or extra columns are ignored.
  • Formats like +1 (305) 123-4567 are normalized automatically; anything that isn't a dialable number is dropped and the panel tells you how many lines it rejected.
  • The Add to existing checkbox appends numbers instead of replacing them.
  • The grid shows name, description, number count, Used by (which points use it) and Enabled / Disabled status.
  • Changes take effect on the next call — nothing to reload.

Client portal

Turn it on with the Activate WEB interface checkbox on the user's record (Users → Users → EDIT → Account). The customer signs in through the same panel login, with the username and password on that record, and lands in a read-only area scoped to their own data: there are no write actions at all, and no cost, provider or margin data is ever shown.

What the customer sees:

  • Dashboard — their balance and account summary.
  • My Devices — their connection points: description, authentication type, IP, port, transport, tech prefix, codecs, capacity and status.
  • Active Calls — their calls in progress.
  • Last Calls — their history with date and status filters, and CSV export.
  • Rates — their own sell rate deck.

To see the portal exactly as they do, use the LOGIN AS button on the user's row (it only appears when the web interface is enabled). While you're in, a fixed bar at the bottom reminds you who you're viewing and under which admin account; Exit returns you to your own session.

Onboarding a new customer, step by step

  1. Create the account. Users → Users → + Add New: username and password, display name or company, currency, billing type and opening balance. If it's Postpaid, set the Credit Limit. Set the time zone and, if you want a global ceiling, the Call Limit.
  2. Make sure the sell tariff is loaded. Under Users → Tariffs. It has to cover the destinations that customer will dial.
  3. Create their origination point. Users → Origination Points → + Add New: pick the user, enter the IP (or generate credentials if they'll register), port and transport, codecs and capacity.
  4. Assign the sell tariff and the routing group in the Routing section of that same point. No tariff means no price; no routing group means no way out.
  5. Set their CallerID: passthrough, a fixed number, or a pool.
  6. Test before you open the gate. Use Routing → Call Simulation to see, without passing any traffic, which rule matches a number, which carrier would be picked and at what price. Then place a real call and check the row in Calls → Last Calls.
  7. Optional: enable Activate WEB interface and check their portal with LOGIN AS before handing over the credentials.
If the test call doesn't connect, the reason is written in the CDR. See Active calls and history (CDR) for how to read it and what to check in each case.
© 2026 NEXIA Networks · This wiki grows with every install: if something was missing, tell us and we add it.
On this page