If you are searching for a VOS3000 alternative, it is usually for one of two reasons: you are running out of capacity, or your customers are asking for a phone system and the switch will not sell them one.
VOS3000 sits in wholesale VoIP: termination, origination, sometimes calling cards. It does that job, and it does it cheaply. What operators tell our sales team is that they hit a ceiling on capacity, and that Cloud PBX is the next service they want to sell and cannot.
PortaSwitch covers both. PortaSIP carries the carrier routing and the Cloud PBX on one platform, and PortaBilling rates and bills every call in real time against the same customer record.
What this looks like under load
Datora, a Brazilian carrier, moved PortaBilling into Oracle Cloud in São Paulo and kept the PortaSIP servers in their own datacenter. Their requirement was 1,000 calls per second. The deployment measured 1,270 CPS and 190,500 concurrent calls, at a 300-second average call duration and 50% ASR.
That is the number to hold against your own busy hour. A single PortaSIP processing node handles about 200 call attempts per second and proxies up to 3,000 concurrent calls. You add nodes from there.
Sources: PortaOne OCI hybrid cloud case study · PortaSIP performance
VOS3000 versus PortaSwitch
Where this table says not found, we searched VOS3000’s published manual and website in September 2026 and did not find the feature documented. VOS3000 may support it without documenting it publicly.
| Feature | PortaSwitch | VOS3000 |
| Softswitch class | PortaSIP is a Class 4 SBC and a Class 5 softswitch in one platform, so carrier routing and retail subscriber services run from the same system | SIP and H.323 softswitch built for carrier routing, with LCR, ASR-based and priority-based routing (VOS3000 switch functions) |
| Cloud PBX and UCaaS | PortaSwitch runs Cloud PBX on the same billing system: extensions, IVR auto-attendant, call queues, voicemail, customer self-care, white-labelled mobile and WebRTC apps | Built for wholesale termination, origination and calling card services rather than as a hosted PBX platform |
| Capacity | About 200 call attempts per second and 3,000 concurrent calls per PortaSIP node, scaling by adding nodes. Datora measured 1,270 CPS and 190,500 concurrent calls in production (case study) | Capacity depends on server sizing. No published benchmark figures found |
| Routing | PortaSwitch routes by least cost, with per-customer routing plans, route preference and huntstop, equal-cost load balancing and automatic failover. Adaptive routing measures vendor ASR, PDD, ALOC and PPM and moves underperforming vendors down the list. Profit-guarantee mode removes routes where vendor cost exceeds the customer charge, during real-time route calculation | Least-cost routing and ASR-based routing strategies (VOS3000 Manual v2.1.7.01) |
| Billing | PortaBilling rates and bills inside the call flow: real-time authorization, balance check, fund locking so prepaid balances cannot go negative, prepaid and postpaid on one customer record, convergent across services | Billing and account management, including balance management, recharge and rate configuration (VOS3000 Manual v2.1.7.01) |
| Invoicing and tax | PortaBilling issues invoices with sequential numbering per environment, reseller or customer, and calculates tax through external tax services or generic VAT and GST rules (invoicing and taxation) | Rate management and billing configuration (VOS3000 Manual v2.1.7.01) |
| Reporting | xDR browser and admin reports in the web interface, PortaOne AI Datalink to move billing data into an external BI tool, and full data access over the API | Report Management, Revenue Details Report, Account Balance Report, Gateway Bill Report, and Phone Bill Report (VOS3000 Manual v2.1.7.01) |
| Fraud | Fraud controls run against the billing engine, not alongside it: geo-IP profiles with Trustful, Cautious and Paranoid zones, country blacklist, account quarantine behind a screening IVR with an unblock code, calls-per-second limits per account, plus SBC topology hiding and DoS protection (fraud prevention tools) | Dynamic blacklist, IP blacklist, geographic call restrictions, and IP, port or password call authentication modes |
| Resellers | Unlimited multi-level sales channels: resellers, distributors and representatives, each with their own portal, rates and branding (resellers) | Agent accounts and sub-account management (VOS3000 Manual v2.1.7.01) |
| Redundancy | Redundant deployments across servers and across sites in different cities or countries, with automatic failover and traffic redirection if the primary site becomes unavailable | Linux server deployment. Geo-redundant deployment not found in published documentation (VOS3000 Manual v2.1.7.01) |
| Deployment | On-premise on physical or virtual servers, Oracle Cloud, or hybrid with billing nodes in the cloud and switches on site. Server count depends on capacity and redundancy requirements (OCI case study) | Linux server deployment (VOS3000 Manual v2.1.7.01) |
| Administration | Web interface, reachable from anywhere, with per-user access rights | Windows desktop client (VOS3000 Manual v2.1.7.01) |
| Updates | More than 20 builds a year, new features every seven weeks on dates published in advance. Dual Version PortaSwitch moves customers to a newer version in small batches while the old one keeps running | Release cadence not published |
| APIs | PortaBilling API, PortaSIP API, Call Control API and ESPF API, over HTTP with token authentication. Source code available | Web API for automation and external system integration, with a dedicated developer manual |
| STIR/SHAKEN | PortaSIP signs and verifies calls through TransNexus, with full, partial and gateway attestation (STIR/SHAKEN support) | Not found in published documentation |
| Number portability | Internal ported-number database, Telnyx via ENUM or XML, HLR lookup for SMS, or your own porting service over ENUM (number portability) | Not found in published documentation |
| AI agents | Public MCP server for PortaBilling at github.com/portaone/mcp-portabilling, so an AI agent can query billing data through MCP-compatible tools | Not found in published documentation |
| Licensing | One-time perpetual license for a set number of servers, or a monthly subscription priced on billable events | Server-bound licensing model (VOS3000 Manual v2.1.7.01) |
Where PortaSwitch actually differs
Wholesale voice and a full Cloud PBX on the same BSS. This is the one that matters most to operators moving off VOS3000. Carrier termination and hosted phone systems run on one platform, against one customer record, with one set of rates and one invoice. You do not run a separate Class 5 box and reconcile two sets of records at month end.
Billing happens during the call, not after it. PortaBilling authorizes, checks the balance and locks funds while the call is live. A prepaid customer cannot go negative, and a fraud pattern is stopped mid-session instead of turning up in yesterday’s CDRs. Blacklists and IP rules stop known bad traffic; a balance that cannot go negative stops the traffic nobody has blacklisted yet.
Routing that defends the margin. Adaptive routing watches each vendor’s ASR, PDD and ALOC and demotes the ones that degrade. Profit-guarantee mode removes any route that would cost more than the customer is charged, at the moment the route is calculated.
Capacity you add rather than replace. Each PortaSIP node adds roughly 200 CPS and 3,000 concurrent calls. Growing means adding nodes, not migrating again.
Support, updates and staying patched
Worth checking before any migration: what happens to your platform over the next five years.
An older softswitch deployment raises three practical questions. Will it keep receiving security patches? Is there a published release schedule you can plan around? And when an update does come, what happens to live customers while it is applied? A softswitch facing the public internet without current patches is an operational risk regardless of which vendor built it.
PortaSwitch ships more than 20 builds a year, with new features every seven weeks and maintenance release dates published in advance, so upgrade windows can be planned months ahead. Dual Version PortaSwitch runs the previous and the new version side by side and moves customers across in small batches, so an upgrade is not an outage you have to schedule at 3am.
Sources: PortaSwitch release process · Dual Version PortaSwitch
Planning the move
The question behind most platform decisions is not whether the new system is better. It is whether the move is survivable.
Cgates, a Lithuanian operator, moved its billing to PortaOne with its subscriber base live throughout. That project is written up in full, including what transferred, what had to be rebuilt, and how the cutover was staged: Cgates billing migration.
For the general shape of a telecom data migration, our migration cookbook covers what moves, what gets recreated, and where the real work sits.
Talk to us
Considering a move off VOS3000? Tell us what you run today, how many concurrent calls you carry at busy hour, and what your customers are asking for that your current platform cannot deliver. We will walk through what the move involves, including the parts that are real work.
FAQ
PortaSwitch is the alternative most often evaluated by VOS3000 operators, because it adds capacity and a full Cloud PBX to carrier routing while PortaBilling rates traffic in real time on the same platform. Compare candidates on capacity headroom, Cloud PBX features, billing integration, routing control, redundancy and update policy.
Yes. PortaSwitch covers the Class 4 routing and billing that VOS3000 does, and adds Cloud PBX, invoicing, tax calculation, geo-redundancy and a web administration interface. What the migration involves depends on your current deployment, services and integrations.
Two reasons come up most often with PortaOne. The first is capacity: the platform will not carry the traffic the business has grown into. The second is Cloud PBX, because customers want a hosted phone system and a wholesale switch does not sell one. Billing is the third: operators want invoices, tax and prepaid balances handled by the same system that switches the call.
Yes. PortaBilling is part of PortaSwitch. It authorizes and rates calls in real time, locks funds so prepaid balances cannot go negative, handles prepaid and postpaid on the same customer, and issues invoices with tax.
PortaSIP picks routes by least cost, using a routing plan set per customer, with preference and huntstop settings and equal-cost load balancing. If a route fails, the next one is tried automatically. Adaptive routing tracks each vendor’s ASR, PDD, ALOC and PPM and demotes vendors that fall below your thresholds, and profit-guarantee mode drops any route that would cost more than the customer is charged.
One PortaSIP node handles about 200 call attempts per second and up to 3,000 concurrent calls, and capacity grows by adding nodes. In production at Datora, PortaSwitch measured 1,270 CPS and 190,500 concurrent calls.
PortaSwitch combines the controls you would expect, including country blacklists and geo-IP profiles, with real-time billing: funds are locked during the call, so a prepaid account cannot run up a balance it does not have. Suspicious accounts can be quarantined behind a screening IVR, calls per second are capped per account, and the SBC hides your network topology and absorbs DoS traffic.
Yes. PortaOne sells a one-time perpetual license for an installation of a specified number of servers, and also offers a monthly subscription priced on billable events, which includes hosting and support.
Yes. PortaSwitch runs on your own hardware, in Oracle Cloud, or split across both. Datora runs PortaBilling in Oracle Cloud São Paulo with the PortaSIP servers in their own datacenter.
Dual Version PortaSwitch runs the old and the new version side by side and moves customers across in small batches, skipping up to 15 releases if needed. Customers keep service on the version they are on until their batch moves.
List the Cloud PBX features your customers actually use, your busy-hour concurrent calls and CPS, your carrier and rate card setup, your integrations, and what happens to historical CDRs, invoices and open balances. PortaOne works through each of these before quoting a migration.
