Averix is a distributed VoIP platform for operators who sell landlines to households. A central server owns customers, billing, licensing and configuration; a node at each site connects to the carriers and handles every call — and no call ever depends on the link between them.
Everything a call needs lives at the site: the phones, the call engine, the local decision store and the carrier links out to the telephone network. The centre manages — and reaches a node only over a link the node opens.
Owns customers, wallets, rates, carrier settings, reports and provisioning. Publishes configuration that every node pulls. Keeps the recording archive. Is never in the path of a call.
Connects to the carriers and handles every call in real time. Authorisation, rating, routing and number translation are all answered from the node's own local store — so it places and receives calls indefinitely with the centre unreachable.
Proven, not assumed: with the central server switched off, a node translated numbers, kept its carrier link registered, and authorised, rated and completed a call.
A full recording disk, an expired licence, a broken sync link, a saturated uplink — none may drop a call. Enforced in the software, not by convention.
Numbers are stored in one international format and translated at two edges: the subscriber's and the carrier's. Adding a carrier is a row of rules, not a change to the engine.
Does a real number route? Is each carrier reachable? Is anything stuck on its way to the centre? — not "is the service running".
All telephony features run on the node and survive an outage of the centre.
Any SIP carrier, by IP or registration. Per-carrier settings, channel limits and priority. Carriers are tried in order; a congested route fails over, a declined call does not.
Four ordered rule sets — outbound called, outbound caller, inbound called, inbound caller — with a simulator in the panel that runs the same logic as the node.
A carrier's address block, gateway and media ranges are entered once; the node sets up its own addresses, routes and firewall openings from that record.
Unconditional, busy, no-answer and unavailable rules per line. A forward to an outside number is billed to whoever set the rule and presented as their own number.
Busy is a real outcome with somewhere to go — busy forward, then voicemail. Mailboxes per line with greetings and quotas, retrieval by *97.
PIN-protected conference rooms with capacity checked before admission — and the join confirmed, not assumed.
Captured on the node, compressed, and uploaded to the centre at a trickle by day and full rate at night. A recording failure never affects a call. Recording pauses at 90% disk and resumes itself.
The node hands out network addresses to the subscribers' phone adapters, with a fixed address per household — on one named interface, never one it guessed.
Prefix blacklist pushed to every node, rate-based fraud counters, and a generated firewall that admits exactly the carriers on your links and nothing else.
The centre grants each node bounded permission ahead of time — a lease against the subscriber's wallet — and reconciles afterwards. A call reserves its maximum cost up front, the node enforces the call length that reservation buys, and on hangup the call is rated, deducted and the unused part returned.
| Central holds | Node holds |
|---|---|
| Customers, numbers, plans, wallets | Every line on this node, with its settings and rules |
| Rate tables | The same rates, ready for exact local rating |
| Carrier definitions and number rules | Rendered call-engine config, routes, firewall |
| Leases granted, calls charged once | Open leases, calls in flight, records waiting to sync |
| Recording archive by date | Recordings awaiting upload |
Served by your central server. Roles and permissions are read fresh on every request — changing someone's role takes effect at once.
One row per household: number, holder, balance, state, node and billing type. Provisioning a subscriber is one action, not three screens.
Caller, callee, direction, duration, node, carrier and where a call was forwarded to — the number asked for is always kept separate from where it went.
Links, their four number-rule sets and the simulator: type a number, see what the carrier receives and which rule caught it.
Enrol, rebuild a replaced machine with its old identity, push phone addressing, fetch recordings, drain and retire.
The step-by-step trace of any call, built from what the node captured.
Listed the moment they are ready; playback by signed-in administrators only, with an audit row on every play.
Rate tables, open leases and the wallet ledger, with the reservation totals audited.
Check in, verify, download and apply a signed release — and revert to the previous one in about forty seconds.
You provide a fresh Linux server; we add it in the Nexecode panel, confirm its identity, secure its access and run the installer remotely — nobody types a command on your machine.
Every release is signed on a machine that is never on the internet. Your central verifies the signature against a key built into the software before anything is written, and nodes fetch their update from their own central.
An update that fails its health check rolls itself back. One that installs cleanly but is still the wrong software has a button: the previous version is kept beside the running one and comes back in about forty seconds.
Create it in the panel, get a one-hour single-use token and one command. The new machine talks to exactly one thing: the central it is about to join.
A failed disk or replaced box comes back with its old identity: same subscribers, carriers, rates and phone addressing, typed in by nobody.
The built-in check asks whether a real number routes, whether each carrier is loaded and reachable, and whether anything is stuck on its way to the centre.
Every deployment gets the whole product. You pay once for the central server and once for each node; support and new releases are a yearly subscription per node. The licence is perpetual — it never expires.
The full platform on every deployment, whatever the size.
| Averix | Rs 100,000 |
| 3 Nodes | Rs 150,000 |
| Total, Paid Once | Rs 250,000 |
| Support & Updates (First Year Included) | Rs 30,000 / year |
We'll size the deployment, quote it, and install it for you.
