Simple IVR for updating the call forwarding number
You can now provide your cloud PBX customers with an IVR application that allows end users to update only the forwarding destination number. All other settings, such as answering mode (for example, “Ring then forward”), ring timeout, and CLI handling, are predefined by the PBX admin.
This IVR is designed for scenarios where the forwarding destination changes frequently (for example, a rotating on-call technician), while the other forwarding settings remain unchanged.
The IVR supports English, Spanish, and Brazilian Portuguese. More languages can be added on request.
Example
John is a leasing agent at ABC Apartments. The ABC Apartments PBX admin configures John’s extension with call forwarding to an on-call technician responsible for handling emergencies. The PBX admin sets the answering mode to “Ring then forward” and defines the call forwarding settings (ring for 20 seconds, display the original caller’s number and name).
Because the on-call technician changes daily, John dials the IVR number (*99) at the end of his workday, hears the currently configured forwarding number, and enters the new number for that night’s technician. No other settings are requested or modified.
What’s improved?
Better customer service
End users can quickly update the forwarding number via IVR, without risking misconfiguration.
Find more details here.
Analyze billing run logs faster using a unique task execution ID
Your engineers can now find logs related to a specific customer billing run using a single identifier, instead of combining multiple filters like customer ID, timestamps, and task type.
For each billing run, PortaBilling generates a unique execution ID. Billing tasks performed within that billing run, such as subscription charging, invoice calculation, and taxation, also receive separate execution IDs. If a task includes subtasks, those subtasks receive their own execution IDs as well. Using any of these execution IDs, engineers can instantly retrieve the relevant logs in the Grafana web interface.
Engineers copy the execution ID (for example, one associated with a specific subscription charge) from the xDR details in PortaBilling and paste it into the corresponding filter field in Grafana.
In the filtered logs, the execution ID of the billing run and the execution IDs of all related tasks and subtasks are displayed together as a single linked chain (billing_run_ID / task_ID / subtask_ID). By filtering logs using any execution ID from this chain, engineers can choose the level of detail they need — from a single operation to the entire billing run.
Example
An accountant at Owl Telecom notices that a customer’s subscription charge is lower than expected and asks an engineer to investigate.
The engineer opens the customer’s xDRs in PortaBilling, locates the subscription charge, and copies the execution ID from the xDR details. In Grafana, the engineer pastes this ID into the execution ID filter field.
Grafana displays log entries related to that specific subscription charge. From the log messages, the engineer sees that a 50% discount was applied, which explains the reduced amount. The engineer reports this finding to the accountant, resolving the issue without further escalation.
What’s improved?
Faster troubleshooting
Quickly find and check logs for a specific billing run to identify issues.
Find more details here.
Reassign DID numbers to a different vendor when porting numbers
In PortaBilling, vendor batches group DID numbers and link them to a vendor for cost attribution.
When DIDs already stored in the inventory need to be moved to another vendor (for example, when you later engage a local carrier for the same region and port existing numbers to it to reduce routing hops and costs), admins can now easily reassign the vendor batch, even when the DIDs are already in use. The update is applied without service interruption for customers.
An admin simply selects the required DIDs and assigns a new vendor batch using the “Group operations with DIDs” panel.
What’s improved?
Easier DID management
Assign DID numbers to a different vendor batch in just a few clicks.
Find more details here.
Redesigned inventory and log pages
The SIM card, DID/MSISDN inventory, and Log viewer pages in PortaBilling have been redesigned to help admins find needed data faster without extra clicks and scrolling.
Across all three pages, search filters have been moved from the left side panel to a single row at the top. Less frequently used filters are grouped under More. This frees up screen space so more data fits on one screen without horizontal scrolling.
Additional improvements include:
- SIM card inventory
All SIM card details, including custom parameters (for example, the marketplace where SIM cards are sold), are now available on one page. - DID/MSISDN inventory
All related data (vendor batches, pricing batches, and DID groups) is organized into tabs on one page. Each tab uses a consistent layout with an Actions column and a side sheet for viewing and editing parameters.
What’s improved?
Easier administration
Admins can manage SIM cards, phone numbers, and logs in fewer steps.
Find more details here.
