What’s new in MR127

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 delivered by a third-party system and not covered by standard PortaBilling service settings.

They can be included in the main product or offered 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.).

• Launch and monetize provider-specific features as a part of the product.
• Define custom features once per product and provision them automatically to external systems, eliminating manual subscriber-level configuration.

• Custom service settings are defined in the PortaBilling admin web interface as service custom data. Admin can set a default value for the custom data and allow the feature to be managed by end users.

  

• The admin assigns this custom data to one or more services and may override the value at the product or account level.

  

• When the value changes at the service, product, or account level, PortaBilling generates a provisioning event.
• PortaBilling sends these events to the service provider middleware through the External System Provisioning Framework (ESPF).

This release introduces the following provisioning events:

• Service/CustomField/Changed
• Product/CustomField/Changed

See the configuration details here.

• Multiple add-on products with the same priority cannot define different values for the same service custom data. The system returns a product compatibility validation error.
• Service custom data is available in the admin web interface and via the API.

• Service custom data is not supported for resellers.
• The admin web interface does not support searching or filtering by service custom data.

PortaSwitch has already supported SIP over TLS (Transport Layer Security) for call traffic between IP phones or softphones and PortaSwitch.

With MR127, SIP over TLS support is extended to additional call scenarios, including:

• forwarded or transferred calls (for example, calls forwarded to external SIP platforms via a SIP URI)
• calls delivered to a static SIP contact
• calls routed to vendors

This allows service providers to deliver incoming calls to customers’ SIP platforms/PBXs that accept only SIP over TLS (such as modern cloud contact centers), and to route calls to vendors that require SIP over TLS.

Attract customers who rely on modern platforms that require SIP over TLS.

The TLS option will be added to the CloudPBX Self-Care Portal in a future release.

Find the configuration details here.

With this release, provisioning of corporate phone books becomes available via Add-on Mart for additional Polycom and Yealink IP phone models. Cloud PBX customers can now use the existing self-provisioning functionality in the CloudPBX Self-Care Portal to manage corporate phone books on the following 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, VVX 501
• Yealink: T33G, T53, T53W, T54W

Both auto-generated directories (based on existing extensions) and custom directories (created manually or uploaded via a CSV file) are supported. To enable directory provisioning, subscribe to the free Polycom or Yealink directory module in the Add-on Mart management portal.

This allows service providers to offer corporate phone book provisioning to customers using these Polycom and Yealink devices without additional manual configuration. The functionality is available via the CloudPBX Self-Care Portal or can be implemented in a custom portal using the PortaBilling API.

• Corporate phone book provisioning works only with an active module subscription to the specific Yealink/Polycom phone model via the Add-on Mart management portal.
• One phone book is supported for Polycom phone models with up to 500 records.
• The maximum number of phone books and records per phone book for Yealink depends on the phone model (e.g., Yealink T33G supports a single phone book with up to 1000 records).

• Cloud PBX customers save time on provisioning phone books.
• Service providers can offer a more competitive cloud PBX service.

When authorizing internet sessions with Cisco gateways, PortaBilling previously sent the full set of session parameters by default, including low-level Link Control Protocol (LCP) attributes. This universal approach worked across different network configurations but is now considered a legacy approach and is not supported by modern Cisco NAS devices.

Now, you can control LCP handling in the internet service policy and include these parameters for Cisco authorization responses only when needed. This helps prevent service disruptions and gives you more control over how policies are enforced in the Cisco network.

To control the LCP behavior, use the Lcp enabled option in the Internet service policy. For example, enable this option for Cisco devices that require LCP parameters in the authorization response to enforce speed limitations. For modern Cisco devices, disable the option and define speed limitations using ip:sub-qos-policy-in and ip:sub-qos-policy-out in the Attributes field.

For backward compatibility, all the service policies created before MR127 have the Lcp enabled option turned on.

Service providers can offer internet services using modern Cisco equipment.

Admins can now monitor on-net calls between PortaSwitch accounts from both the caller and the recipient side. This provides a more complete view of on-net traffic per customer or account.

An on-net call is handled as two call legs: an outgoing leg for the caller and an incoming leg for the recipient. With MR127, admins can view both legs on the Active sessions page. To include incoming on-net calls in the list of active sessions, enable the Show incoming on-net calls toggle. When enabled, incoming (including transferred or forwarded) on-net calls are displayed as separate records.

Accurate real-time monitoring of simultaneous calls.

Bundles can now be applied based on destination (called) numbers or origination (caller) numbers. This allows service providers to more precisely define which calls should be covered by a bundle, particularly when the same phone prefixes are used in different charging contexts.

This is especially useful in pricing models where different charging rules coexist. For example, a service provider may want to:

• charge incoming calls based on call origination (CLI),
• charge outgoing calls based on call destination (CLD), and
• apply a bundle only to outgoing calls to specific destinations.

In such cases, incoming and outgoing calls may be rated using the same phone prefixes (E.164), e.g., 331 and 336 for France. Previously, including these prefixes in a bundle would cause the bundle to also be applied to incoming calls (when the caller’s number, CLI, matched a prefix in the bundle), even if only outgoing calls were intended to consume the allowance.

With this enhancement, when creating a bundle, an admin can select a Code group set with a defined Rate match mode (for example, “Destination”). This ensures that the bundle is applied only to outgoing calls, as they are charged based on destination numbers (CLD).

Accurate charging in complex pricing setups by preventing unintended bundle usage on chargeable traffic.

The service type of bundle items is determined by the code group set assigned to the bundle. You can create bundle items only for that service type.

Find the configuration details here.

This release introduces a redesigned Service policy page that simplifies configuration for admins and unifies it with other entities:

• Search parameters have been moved from the left panel to a single row at the top.
• Editing service policies now follows the standard portal behavior: admins open a policy for editing via buttons in the Action column.

  

• When creating a service policy, all required settings are available on a single panel, organized into tabs. This allows admins to complete the configuration during creation, without reopening the policy.

  

• Admins can now see which attributes are set to their default values, Auto (default), and override them if needed. Default values are clearly indicated for attributes shown as dropdowns or text fields, making it easier to distinguish between default and modified settings, helping prevent configuration errors.

  

This enhancement helps admins avoid misconfigurations.

This release introduces an updated Audit log panel that improves visibility into changes made to entities and actions performed by admins. The Audit log now provides a consistent layout and behavior across all supported entity pages, such as customers, accounts, and SIM cards pages, allowing admins to review changes and actions in the same way.

• The Audit log button is now located at the top bar, next to Notifications and Help, instead of within entity-specific menus. This makes audit information faster to access from any supported page and allows admins to open the audit log, keeping the current page and context visible.

  

• Search controls and search results are combined into a single view, enabling admins to filter and analyze audit records, reducing the number of steps required to find relevant events.

  

Admins get faster, more consistent access to audit information across the admin interface.

This release introduces a redesigned interface for the Custom data and Services pages, making it faster for admins to search and manage these entities.

• The search parameters have been moved from the left side panel to a single row at the top, allowing for more columns to fit on the screen without horizontal scrolling.

  

• The search parameters have been moved from the left side panel to a single row at the top to be consistent with other pages.

  

This enhancement improves the user experience when managing these entities.