PortaSwitch is a unified platform for telecommunication service providers, wholesale carriers, ISP, MVNO and NGN operators for unifying voice, messaging, and data traffic within a single converged network.
PortaSwitch provides various prepaid, postpaid, retail and wholesale telecommunication services, including calling cards, Vonage- and Skype-like services, CLEC type services, MVNO & MVNE, ISP, WiMAX & WiFi and much more. It includes 2 main components:
How does it work?
The key difference between PortaSwitch and more traditional "switch" products is that PortaSwitch offers much more. It includes the B/OSS component, and so is a unified service management and delivery platform that:
PortaSwitch stores all the information about the products, rates and customers and the service configuration for individual customers or phone lines. It is managed via a web interface and includes a self-care portal for your end users. Internally, PortaBilling controls call processing on PortaSIP as well as real-time routing.
PortaSwitch communicates with IP phones, mobile dialers and communication clients, and media gateways via the SIP protocol. There are no restrictions as far as the vendor or model of the equipment, so any communication device that supports SIP can be used in conjunction with PortaSwitch for services such as voice or video calls, presence or instant messaging.
PortaSwitch Architecture OptionsPortaSwitch is available in 3 options that are exactly the same in terms of functionality and available features but differ in scalability and redundancy options:
PortaSwitch 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, while charges for the different services will be grouped on a single bill.
PortaSwitch in its standard configuration
PortaSwitch in its standard configuration is normally installed on 5 physical servers with main and replica databases located on separate machines to provide database redundancy:
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.
Several physically independent PortaSIP servers may be used in a single system cluster environment to provide fault-tolerant services. Connected to PortaBilling, the system of multiple PortaSIP servers provides all the required service provisioning information and maintains a global database of SIP phone registrations.
A SIP phone user may connect to any of the available PortaSIP servers. If one server is unavailable due to a hardware failure or network problem, the other PortaSIP servers will handle calls.
PortaSwitch Procinctus is twice as much powerful than a standard PortaSwitch and thus requires twice as many physical servers to be installed on (10 all together):
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.
Other Scalability and Redundancy Options
The unmatchable flexibility and scalability of PortaSwitch allows for various options to improve its performance and high availability of the services as well as optimize the service provider's network utilization. PortaSIP, the switching part of the platform, can form clusters for load balancing and redundancy; multiple PortaSIP servers can be installed in various locations around the globe; and PortaBilling can be expanded with Oracle RAC.
Service providers with global business exposure may choose to install a clustered system of multiple PortaSIP servers in various separate geographical locations. This allows them to keep the service running even if a whole hosting center in one place is down.
This kind of architecture also improves the network utilization: for instance, users in Asia would primarily use a PortaSIP server hosted in Singapore or Hong Kong, while European customers will work with a PortaSIP server in Frankfurt or London.
Remote Site Redundancy
PortaSwitch site redundancy allows to:
Why you need it
The only way to overcome catastrophic events and provide uninterrupted service is to have another set of servers in a different location that can continue operating during the outage at the main site.
The per-server redundancy when there are two physical servers and each runs a copy of an application such as PortaSIP, addresses the situation when a single server fails (e.g. hardware fault). However there is another class of catastrophic events that can render all servers installed in the same location (rack, hosting center, etc.) unavailable. Such events include natural disasters, power outages at the collocation provider, network routing errors, etc.
The secondary site (or multiple sites) can be installed in the hosting facility in the same city or in a totally different location across the globe. The only requirement is the sufficient amount of bandwidth between the sites to keep the data replication going.
How it works
Main site unavailable: If the secondary site detects that the main site has become unavailable, the "stand-alone" mode is activated on the secondary site and now it provides the service to end-users using the latest available snapshot of the service configuration.
Secondary site operation: When a service is provided on the secondary site, the billing engine continues to calculate applicable charges according to product, tariff and the responsible party's other billing parameters (e.g. from the account that originated the call).
Separate DB for changes: All changes to the balance and new xDRs are written into a separate "delta" database running on the same physical server as the stand-by database. This allows the billing engine to keep track of already consumed services and avoid a balance overdraft - even if a secondary site has to operate in stand-alone mode for an extended period of time - and this, therefore, results in a clear history of all produced charges.
Switching back to main site: When the primary site becomes available again, these changes are automatically applied to the primary database - and the secondary site is switched back to "normal" ("stand-by") mode. All of this happens automatically, without any need for PortaSwitch administrator involvement - and an end-user might not even notice that there were any problems at the main site.
Hardware requirements for a redundant site: A simple redundant site will require 3 servers:
Of course, this minimal configuration can easily be scaled up, expanded and clustered to increase the maximal load capacity of the secondary site and achieve per-server redundancy at the secondary locations. PortaOne technical sales team will assist you to determine your PortaSwitch network redundancy needs and advise you on the best site redundancy configuration for your project
PortaSwitch with Oracle RAC
To addresses the issues of the ultimate reliability, performance, and virtually unlimited scalability, the billing part of PortaSwitch can be replaced with PortaBilling Oracularius, an Oracle Real Application Cluster (RAC) based system.
Sharing absolutely the same feature set with standard My SQL-based PortaBilling and acting as the main core of PortaSwitch platform, PortaBilling Oracularius has a fundamentally different architecture of 3 clusters:
For more information about PortaBilling Oracularius technical capabilities, architecture, and pricing please download Oracularius Concepts Guide and contact our sales team.
PortaSwitch licensing model is based on a one-time per-installation basis. The license is perpetual, e.g. lifelong with no recurring fees are required to operate the software and unlimited with no extra charges based on the number users, customers, ports, minutes or channels - ever. More specifically, the license includes:
PortaSwitch comes with unlimited license and since there are absolutely no artificial limitations on the software side, and the only thing that limits its performance is the processing power of the servers it is installed on. Of course, the actual performance will depend on the system's configuration, traffic patterns, and the types of services provided. From our experience, at least the following numbers may be expected with modern equipment and industry-standard traffic quality:
Both multiple PortaSIP nodes and the ability of Oracle Real Application Cluster database embedded in PortaBilling Oracularius to linearly scale up the capacity of an installation address those situations when higher volumes are expected and better system performance is required.
For more detailed information on PortaSwitch performance please refer to the respective Guides on the Documentation page.