Comparison · Migration

A VOS3000 alternative: what to check before you migrate

For a large part of the wholesale market, VOS3000 is the switch people learned the business on. It is also the one most operators want to replace and fewest dare to move. This page separates the real reasons from the forum ones, and sets out what has to be solved before you touch anything.

Why operators look for a replacement

VOS3000, by Linknat, has been the default wholesale transit softswitch across much of Latin America, Asia and Africa for over a decade. It carried — and still carries — an enormous amount of traffic. The reasons an operator starts looking elsewhere are almost always the same four, and only one of them is technical:

The hard, public data point: in 2020 ESET researchers documented CDRThief, Linux malware written specifically to target Linknat VOS2009 and VOS3000 softswitches and exfiltrate call metadata — CDR records with times, duration, source and destination. This is not forum hearsay: it is published research, and it describes a platform family widespread enough that someone wrote bespoke malware for it.

None of this makes VOS3000 a bad product: the vendor's software is legitimate commercial software. What is true is that the risk concentrates in how it reached your server, and that question — who compiled what you are running — does not always have an answer.

What is actually worth comparing

The useful comparison is not feature lists: both will have rates, gateways and CDRs. It is the five things you feel while operating:

What to askNEXIA SwitchCommon in the market
Provenance of the running binaryEd25519-signed bundles, verified against a pinned key before installRPM of varying origin depending on who sold it
PricePublished on the site, no negotiationDepends on the reseller and the country
Trying it without buyingFree and permanent up to 100 channels, complete platformScheduled demo or a borrowed copy
Balance integrityAppend-only ledger; the database rejects UPDATE and DELETE on entriesBalance in an editable column
Public surfaceExactly one: the admission proxy. Media server, database and panel on loopbackVaries with how whoever installed it left it
Per-call marginCost, sell and margin on the same CDR rowComputed by exporting and cross-referencing

What you carry over from the old install

The move is scarier than it is expensive, because there are four things to bring and three of them are spreadsheets:

  1. Buy and sell rates. They export as CSV or Excel from the old switch and import by prefix. This is the bulk of the work and it is mechanical.
  2. Customers and their connection points. Authorised IP or SIP user, channel cap and opening balance. They get recreated; there is no standard format that migrates itself.
  3. Carriers and routes. The dial peers get rebuilt with the new switch's prefix logic, which is rarely identical.
  4. CDR history. Archive it, do not migrate it. Keep the export: the new switch has no business understanding the old schema.

How to do it without risk: do not cut over at once. Stand the new switch up in parallel, send it one test customer and one carrier, compare the billing on that traffic against what the old one would have charged, and only then move the rest in batches. The free 100-channel plan exists precisely so that stage costs nothing.

What will not change, and is worth knowing

To be fair to the comparison, there are things a new switch does not fix:

What NEXIA Switch offers

NEXIA Switch is a self-hosted Class 4 softswitch, written from scratch for the job VOS3000 does today in many operations: hardened SIP admission at the edge with Kamailio, a routing and rating core compiled in Rust, LCR with a minimum margin, real-time billing on an immutable ledger and anti-fraud active from install.

It installs with one command on a clean Ubuntu 24.04, the installer verifies the bundle signature before touching the server, and the free plan of 100 concurrent calls is permanent: enough to run the migration in parallel without rushing and without paying two licences in the same month.

Frequently asked questions

Can you migrate from VOS3000 without an outage?
Yes, and it is the recommended way: stand the new switch up in parallel on another server, send it one test customer and one carrier, compare billing against the old switch, and only then move the rest in batches. The free 100-channel plan covers that whole stage at no cost.
Do VOS3000 rates import directly?
You export them to CSV or Excel from the old switch and import by prefix on the new one. There is no standard format across platforms, so columns almost always need reordering, but it is mechanical spreadsheet work, not programming.
What happens to my CDR history?
Archive it, do not migrate it. Keep the old switch's full export for whatever period your accounting requires and start the new switch with an empty history: mixing two different CDR schemas in one database complicates any future audit.
Is VOS3000 actually insecure?
The vendor's software is legitimate commercial software. The documented risk is in the ecosystem around it: modified installers and licence generators of unknown origin, and malware written specifically for the platform — ESET documented CDRThief in 2020, targeting Linknat VOS2009 and VOS3000 to steal CDRs. If you cannot say who compiled the binary running on your server, that is the problem.
How long does migration take?
For a mid-sized operation — dozens of customers and a handful of carriers — a weekend of spreadsheet loading with the old switch still running is a realistic estimate. What takes the time is not installing: it is reviewing rates and rebuilding routing rules.

Run it on your own server

Free up to 100 concurrent calls, forever, no card. Installed in an afternoon, with public pricing for when you grow.