Automate service provisioning without learning PortaBilling internals
Traditional service provisioning required developers to understand PortaBilling in depth — including its API, data structures, and logic. As provisioning applications received minimal info (just notifications such as ”A change on account with i_account=12345 has happened”), developers had to write custom code to retrieve necessary data like the product name or configuration settings using the PortaBilling API. If there were multiple applications, e.g., for HSS, PCRF, and IPTV, they could trigger multiple identical API requests for the same account within seconds.
The New Service Provisioning System (NSPS) has a built-in component to retrieve such data. When a subscriber event occurs (e.g., a product change), NSPS retrieves all the necessary data from PortaBilling at once and caches it. NSPS then delivers the required details as a single JSON payload to an integration microservice (“handler”). The handler then updates the relevant external system — such as HSS, PCRF, or IPTV.
Benefits
- Developers no longer need to learn PortaBilling and call its API — they can just build a microservice that receives JSON and maps it to the external system’s API. PortaOne provides a sample handler for World Telecom Labs HSS that can be used as a reference. The code is available publicly on our GitLab page.
- There is only one data retrieval per event — no duplicate API calls.
- Each microservice is operating in its provisioning queue, ensuring that delays in provisioning to one system do not affect the others.
- If a provisioning event fails (e.g., a QoS profile isn’t applied), the operations team can quickly spot the error using the NSPS web UI. After fixing the cause (e.g., properly configuring the QoS profile in PCRF), they can replay the failed events to ensure the changes are correctly applied to the external systems.
NSPS complements the existing External System Provisioning Framework (ESPF) system and requires no changes to PortaBilling, making it compatible with older versions (MR100+).
Example
An MVNO needs to automate subscriber updates to its host network’s HSS and PCRF. The developers create two lightweight handlers: an HSS connector, adapted from the PortaOne sample handler built with Python/FastAPI, and a PCRF connector developed from scratch in Node.js. Both handlers are configured in the NSPS web interface.
When a subscriber upgrades their plan from 5 GB to 20 GB, PortaBilling generates a provisioning event, and the External System Provisioning Framework (ESPF) sends it to NSPS via a “webhook” (HTTP request) that includes the subscriber’s i_account. NSPS then retrieves the SIM card IMSI and new plan details from PortaBilling and sends a single JSON payload with all required data to each handler. The HSS handler updates the subscriber profile in the HSS for network authentication, while the PCRF handler activates the new QoS profile.
Watch our NSPS webinar to see a live demo.
To use NSPS, you will need:
- PortaBilling/PortaSwitch version MR100 or later
- An active subscription to the NSPS module in the Add-on Mart.
What’s improved?
Faster, scalable integrations
Build and launch real-time service provisioning flows in days — not months.
Find more details here.
Additional Polycom IP phones supported for auto-provisioning
PortaSwitch now supports five more Polycom VVX models for fast automatic setup through auto-provisioning:
- Polycom VVX300
- Polycom VVX301
- Polycom VVX310
- Polycom VVX350
- Polycom VVX450
To start using auto-provisioning for these models, you’ll need an active subscription to the corresponding Add-on Mart modules.Along with automatic delivery of essential settings — such as SIP credentials, SIP proxy addresses, and codec preferences — these models also support self-provisioning of programmable line keys. This enables cloud PBX customers to use a self-care portal (either the PortaOne CloudPBX Self-Care Portal or a custom-built portal) to configure functions like call parking, BLF, or speed dialing for specific keys, and to apply the setup to multiple phones in one go.
What’s improved?
Easier onboarding of new customers
Attract more businesses by ensuring quick phone setup for the IP phone models they already use and prefer.
Find more details here.
Real-Time Text (RTT) for accessible communication
PortaSwitch now supports Real-Time Text (RTT) — helping service providers meet upcoming European Accessibility Act (EAA) requirements (effective June 28, 2025) and NG911 rules in North America.
With RTT, each typed character is transmitted instantly during a voice call and appears on the other person’s screen as it’s entered. This is essential for users with hearing or speech impairments, especially in emergencies.
Example
A user calls 112 and types: “Fire. 14 Rosenweg, Apt 3B, Lindenstadt. Smoke from…” Because each character appears in real time, the dispatcher doesn’t have to wait for the full message and can send help immediately.
What’s improved?
Regulatory compliance
Meet legal requirements for accessible voice services in Europe (required from June 28, 2025) and North America.
Apply multiple taxes to one subscription and schedule tax rate changes
Some countries apply multiple taxes to telecom services — like VAT and excise duty — which may be calculated in a strict order or only on part of the charge. PortaBilling now supports these scenarios. You can:
- Apply multiple taxes (e.g., VAT and DA) to a single subscription
- Assign taxes to individual services or subscriptions
- Apply tax to only part of the charge (e.g., 50%)
- Choose between basic (each tax on original amount) or cumulative (each tax on the result of the previous) methods
- Schedule tax rate changes in advance and track past/current/future rates in one view
What’s improved?
Accurate taxation across regions
Meet local requirements and apply the correct taxes to each subscription.
Find more details here.
Web interface changes
- Prevent call misbilling with IP conflict alerts: When setting up an account or vendor connection, PortaBilling now warns you if the IP entered is already in use for call authorization. For example, if an admin accidentally assigns an IP address to a vendor connection and that same IP address is already linked to a SIP trunking account, calls from that IP could be authorized and billed as vendor traffic instead of account traffic. The warning helps prevent this mistake. Find more details here.
- Activate or disable origin-based rates instantly: Admins can now use a ”Now” button to instantly apply the current date and time when activating or deactivating origin-based rates (e.g., the test rates) — no need to enter it manually. Also, time defaults to 00:00:00 when changing date options, ensuring predictable rate timing. Find more details here.
- Main menu tooltip in the reseller, representative, and distributor portals: First-time users in reseller, representative, and distributor portals see a tooltip pointing to the Main menu when they log in, making it easier to find key sections. Find more details here.
Easier administration
Reduce errors, speed up admin tasks, and make the portal navigation clearer for first-time users.
