Control and monetize custom service features within your products
You can now define any custom service features, such as parental control or a custom ringback tone, and control them at the product level, even if they are not covered by standard PortaBilling service settings.
You can use custom features to monetize services (such as voice, data, or messaging), either by including them in the main product or by offering them as paid add-ons. You can also offer your custom features as standalone value-added services (e.g., automatically activating or deactivating the subscriber’s access to premium video streaming, paid apps, or other services delivered by your partner).
When a product is assigned, modified, or canceled, the service configuration, including the custom feature parameters, is updated automatically for the subscriber. A middleware (such as NSPS or the Boomi low-code platform) retrieves these custom feature parameters via the API and changes the service configuration in the relevant external system accordingly (activates or deactivates the service, changes the limits, etc.).
Example
Owl Mobile introduces a Custom ringback tone add-on priced at $2 per month for its voice service. The Owl Mobile admin defines a custom service setting, “Custom ringback tone,” with two values: enabled and disabled. The admin then enables this setting in an add-on product. When the add-on product is assigned to a subscriber, the $2 fee is applied, and PortaBilling generates a provisioning event and triggers the middleware to enable the feature for the subscriber in the mobile core. Now there is no need for separate activation via USSD codes or by calling the support desk.
What’s improved?
New monetization options
Launch and monetize provider-specific features as a part of your product.
Centralized control
Define custom features once per product and provision them automatically to external systems, eliminating manual subscriber-level configuration.
Find more details here.
Deliver calls to customer platforms and vendors that only support SIP over TLS
Some SIP platforms (such as cloud PBXs and AI-powered contact centers), as well as some vendors, accept calls only over SIP connections secured with TLS (Transport Layer Security).
With MR127, PortaSwitch supports SIP over TLS not only for simple calls to and from IP phones and softphones, but also for forwarded and transferred calls, calls delivered to a static SIP contact, and calls routed to vendors’ VoIP gateways. As a result, you can meet the requirements of platforms and vendors that only support SIP over TLS using your existing network setup.
Example
Owl Telecom provides virtual business numbers. ABC Company purchases a number and wants all incoming calls to be handled by an AI-powered cloud call center (Genesys Cloud CX) that accepts only SIP over TLS.
The Owl Telecom admin uploads TLS certificates to PortaSwitch and configures call delivery using TLS for ABC’s account.
What’s improved?
Compatibility with modern customer and partner platforms
Attract customers who rely on cloud PBXs and AI contact centers, and partner with vendors that require SIP over TLS.
Find more details here.
Corporate phone book self-service for more IP phone models
Cloud PBX customers can now self-provision corporate phone books to multiple IP phones at once on additional Polycom and Yealink models:
- Polycom: VVX 250, VVX 300, VVX 301, VVX 310, VVX 311, VVX 350, VVX 400, VVX 401, VVX 410, VVX 411, VVX 450, VVX 500, and VVX 501
- Yealink: T33G, T53, T53W, and T54W
Phone books can be generated automatically from existing extensions or customized by adding numbers manually or uploading them from a file. This feature is available in the CloudPBX Self-Care Portal, or you can implement it in your own portal using the PortaBilling API.
To enable provisioning of corporate phone books, activate the free Polycom or Yealink module in the Add-on Mart management portal.
What’s improved?
Better customer service
Enable easy self-management of corporate phone books across all employees’ IP phones on popular Polycom and Yealink models.
Find more details here.
Exclude legacy internet session parameters for modern Cisco gateways
Some modern Cisco gateways no longer support Link Control Protocol (LCP) parameters during internet session authorization. When these parameters are sent, the gateway may reject the authorization request or apply service rules incorrectly.
Previously, PortaBilling always sent LCP parameters to Cisco gateways. This worked for older models, where LCP was used to enforce service rules such as speed limits.
Now, admins can choose to not send LCP parameters when working with modern Cisco gateways, and instead define speed limits using the attribute–value pairs that modern Cisco equipment supports.
For older Cisco gateways, nothing breaks: existing service policies will still send LCP parameters, preserving backward compatibility.
What’s improved?
Reliable internet session authorization
Internet session parameters are configurable for both modern and legacy Cisco gateways.
Find more details here.
Active sessions page shows incoming on-net calls
Admins can now monitor on-net calls between PortaSwitch accounts from both the caller and the recipient side. This provides a complete view of on-net traffic per customer or account.
Previously, only outgoing on-net calls were visible on the Active sessions page. With MR127, incoming on-net calls (including transferred or forwarded calls) can also be shown as separate records.
Example
Owl Telecom offers SIP trunking with a limit on simultaneous incoming calls. During peak hours, the admin opens the Active sessions page, filters calls by the customer’s SIP trunk account, and sees all active incoming calls routed to the SIP trunk (including calls from other Owl Telecom customers) that are consuming trunk capacity.
What’s improved?
Easier administration
Access accurate real-time monitoring of simultaneous on-net calls.
Find more details here.
Web interface changes
Redesigned “Service policy” panels:
- All settings are now available on the policy creation panel, organized into tabs. Admins can complete the configuration during creation without reopening the policy.
- Default values are clearly marked as “Auto (default),” making it easier to see which settings were changed and avoid configuration errors.
- Search parameters are now placed in a single row at the top, and service policies are edited using standard action buttons, ensuring a consistent layout across PortaBilling UI.
Redesigned “Audit log” panel:
- The “Audit log” button has been moved to the top bar, instead of being hidden in entity-specific menus. This makes the audit information faster to access from any supported page.
- When the “Audit log” panel is open, the current page and context remain visible.
- Search filters and results are combined into a single view.
Redesigned “Custom data” and “Service” pages:
- Search parameters have been moved to a single row at the top of the page, allowing more columns to fit on screen and reducing the need for horizontal scrolling.
What’s improved?
Easier administration
Reduce errors and find needed data faster without extra clicks.
Find more details here.
