PortaBilling is a business and operation support system (B/OSS) designed for telecommunication service providers to manage end-to-end telecom service networks


Portabilling includes:

  1. Customer management
  2. Service provisioning
  3. Carrier grade converged billing platform with online charging system, rating, and invoicing

How does it work?

Telecommunication service providers, network operators, ISPs, MVNOs, and wholesale carriers rely on PortaBilling to launch, price, provision, and constantly manage various prepaid, postpaid, retail and wholesale telecommunication services, including calling cards, Vonage- and Skypelike services, CLEC type services, MVNO/MVNE, ISP, WiMAX & WiFi and much more.

PortaBilling is a converged system; it can be used as a single administration interface to manage and bill for multiple services, including those provided by third-party network elements (for instance, LTE SAEGW or WiMAX ASN-GW), while charges for the different services will be grouped on a single bill.


As B/OSS, PortaBilling communicates with elements of the telecommunication network, provides its nodes with authentication or authorization, and gathers billing events, i.e. data about services rendered to the customers. Based on this information, PortaBilling performs rating for the services, creates transaction records, and modifies customer balances accordingly.

PortaBilling Architecture Options

PortaBilling is available in 2 options that are exactly the same in terms of functionality and available features but differ in scalability and redundancy options:

  • standard PortaBilling with MySQL database
  • PortaBilling Oracularius with Oracle Real Application Cluster (RAC) database

All this happens in real time, so the billing data is updated as soon as a session is completed. PortaBilling acts as the nerve center of the network and represents a unified platform for multiple services allowing to charge clients for their voice calls, messages, data transfer, and other services like IPTV subscriptions or video-on-demand (VoD) thus effectively deploying triple-play on a single network.

PortaBilling with MySQL database

PortaBilling in its standard configuration with MySQL database is normally installed on 4 physical servers with main and replica databases located on separate machines to provide database redundancy: PortaBilling_servers

  • Billing engine (RADIUS) server provides authentication, authorization, and both interim (keep alive) and service accounting processing.
  • Main database server contains all system's data.
  • Server for web-interfaces and replica database hosts administration interface, account and customer self-care pages, resellers' helpdesk, vendor self-care pages, representatives' self-care pages, and online web signup interface. It also contains scripts for calculating various statistics, provides data redundancy, and hosts XML API (SOAP) interface for integration with external applications.
  • Configuration server is a single point for efficient management and seamless update process of the whole installation set up. It is also used as a logging storage to remove the analytical task loads from the servers directly involved in the operational processes.

The hardware requirements can be found on a dedicated HW page and in the PortaBilling Administration Guide on the Documentation page.

Enhanced PortaBilling with Billing and Web Clusters

In addition to the ability to run several RADIUS processes in parallel on the same machine, the standard MySQL-based PortaBilling architecture allows to be expanded to utilize multiple physical servers in a cluster so it can process more RADIUS requests. To take advantage of additional servers' capacity, the MySQL databases can be installed on dedicated servers while the extra web servers may create its own cluster too.

PortaBilling Web Clusters

This expansion requires more licensed servers and provides extra performance, since incoming requests are distributed for processing among all the available clustered servers. It also offers improved reliability, as when one of the servers is down due to hardware failure, the remaining servers in the cluster will continue operating.

PortaBilling Oracularius

PortaBilling Oracularius

  • Oracle RAC instead of MySQL
  • Complete redundancy
  • Unlimited scalability

The architecture PortaBilling Oracularius addresses specifically the issues of the ultimate reliability, performance, and virtually unlimited scalability achieved with the deployment of Oracle Real Application Cluster (RAC) environments.

Since MySQL database cannot be clustered for real time applications such as B/OSS, the high availability and ability to scale up system's capacity can only be achieved with PortaBilling Oracularius running on Oracle RAC database. Sharing absolutely the same feature set with standard PortaBilling, PortaBilling Oracularius has a fundamentally different architecture of 3 clusters:

PortaBilling Oracularius

Powered by Oracle
  • The database back-end deploys multiple (at least 3) servers in the Oracle RAC database. In case one of the servers in the cluster should fail, the database will continue to operate. Also, if more performance is required, additional servers may be added to the cluster to linearly increase capacity.
  • The billing engine runs in a distributed fashion on 3 separate servers, which are organized as a cluster. This provides fault-tolerance - if one of the servers in the billing cluster goes down, this does not affect the service.
  • Administrative functions (administrator web, self-care web, XML API, etc.) run on 2 web servers in a cluster, enabling load-sharing and quick disaster recovery.
  • A configuration server is used to maintain and manage the configuration of all the other servers. This greatly simplifies tasks such as adding a new server to an installation of PortaBilling Oracularius, relocating components (e.g. one of the billing servers) to a new physical machine, or changing some other parameters.

For more information about PortaBilling Oracularius technical capabilities, architecture, and pricing please download Oracularius Concepts Guide and contact our sales team.

PortaBilling within PortaSwitch

Combined and fully integrated with PortaSIP, a class 4 (SBC functionality) and class 5 SIP softswitch, PortaBilling is a core basis of PortaOne's flagship product — PortaSwitch, an ultimate telecommunication services and subscriber management platform.

Clustered version of MySQL-based PortaBilling is a basis of PortaSwitch Procinctus, a fully redundant high performance version of standard PortaSwitch where each business critical element of the platform is placed in a cluster of multiple servers to deliver exceptional redundancy of all essential functionality; in addition, transparent load-sharing increases the capacity level of the whole system.

PortaBilling within PortaSwitch

To overcome catastrophic events such as natural disasters, power outages at the collocation provider, network routing errors, etc., provide uninterrupted service and zero downtime updates, PortaBilling can be complimented with a remote site redundancy.


Contact Sales


Toll-free calls (phone & Skype)
+1 866 747 8647
Calls & faxes from abroad:
+1 604 628 2508

PortaOne, Inc.
Suite 408, 2963 Glen Drive
Coquitlam, BC, V3B 2P7

Contact sales@portaone.com to discuss your project requirements and schedule custom-tailored interactive online demo session.

Superb Reliability and Scalability with
24/7 Professional Technical Support


Open architecture

PortaOne provides both APIs and source code for PortaSwitch to allow an easy integration

Scalability for growth

Our platforms can easily scale up by adding more servers to match your project success

Reliability and redundancy

Clustering and geo-redundant site configuration allow to address the most rigorous requirements

Constant improvement

The dedicated highly skilled development team delivers more than 20 software builds per year

24/7 technical support

Over 60% of our 300 engineers are in the technical support services, praised as the best in industry