Simplified forwarding management via voice application
This release introduces a voice application for simple call forwarding. This application prompts users to enter only the forwarding number, while all other forwarding settings (e.g., the answering mode “Ring, Forward, Voicemail”) are configured by the PBX admin.
Owl Telecom provides cloud PBX service to ABC Apartments. John, a leasing agent, answers residents’ calls during the day. At 5 PM, John enables call forwarding to the on-call technician who handles 24/7 emergencies such as water leaks, heating failures, and gas odors. Since the technician on duty changes daily, John updates the forwarding number every workday. This ensures residents always reach someone who can help.
ABC Apartments’ admin on the CloudPBX portal sets the default answering mode for John’s extension to Ring Then Forward and enables call forwarding:
- Forward to: 17731113333 (the current technician)
- Timeout: 20 seconds
- Calling party display: Caller number and name
- Keep original CLD: Enabled
The next day, John receives the phone number of a different on-call technician. At 5 PM, John dials *99 on his desk phone, hears the current forwarding number, and enters the new number for tonight’s technician. The system updates only the forwarding number, while the 20-second timeout and other settings remain unchanged. Then he enables DND on the phone and leaves the office.
In the morning, John disables DND to handle all incoming calls.
Configuration
Go to the Voice applications page, create a new voice application and fill in the following details:
- Name – specify the application name, e.g., Simple call forwarding.
- Application type – select Simple call forwarding.
- Description – add a short description of the application.
- Number – specify the number end users will dial to access the application, e.g., *99.
Click Save&Edit details to configure additional options if needed.
- Easy and quick forwarding management for end users.
- Service providers can offer a more competitive cloud PBX service.
- Users can manage their forwarding numbers only if Simple forwarding is enabled for their extension (on the cloud PBX portal: Extensions > Call forwarding tab).
- Users cannot manage forwarding numbers via this voice application if they have Hide CLI enabled.
- Supported languages for the voice application are English, Spanish, and Brazilian Portuguese. More languages can be added on request.
Quickly find periodic task logs in the web interface using a unique task execution ID
With the Grafana integration introduced in earlier releases, your engineers can access and analyze logs of background tasks (such as subscription charging, invoice calculation, taxation, periodic payments, and report generation) directly through the web interface. Grafana displays the periodic task logs (taskstack.log/task_queue.log files) collected from all servers and stored in OpenSearch.
To simplify log filtering and speed up troubleshooting, MR126 introduces a unique execution ID for each run of a periodic task. Using a single execution ID to trace a task run eliminates the need to combine multiple filters (e.g., customer ID, timestamps, task type). PortaBilling generates the execution ID automatically and records it in all related log rows, including parent and subtask entries. The ID can be taken from the xDR details in the PortaBilling UI, and Grafana now includes a dedicated field for filtering logs by this value.
An engineer can copy the ID from the xDR generated by periodic tasks (a subscription charge, a DID charge, an auto-payment, a tax, or a measured service charge) and paste it into the Grafana UI to immediately view the log lines associated with that specific task execution.
In the filtered logs, the execution IDs of all related tasks and subtasks are displayed together as a single linked chain (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 task run.
For more-in-depth analysis, additional filters, such as searching by message text, can be used.
Owl Telecom’s accountant notices that the subscription charge for one of their customers is less than expected and asks an engineer to investigate.The engineer opens the customer’s xDRs in PortaBilling and locates the subscription charge. They copy the execution ID from the xDR details.
In the Grafana web interface, they paste this ID in the Viewer execution ID filter field.
Grafana displays the log entries related to this specific subscription charge. The charged amount was calculated by the parent task. To see the full calculation process for the subscription charge, the engineer opens one of the log entries, copies the parent task execution ID (one level up), and pastes it in the same filter field.
Grafana then shows log entries for the entire subscription calculation run.
From the log messages, the engineer sees that a 50% discount was applied to the subscription, which explains the reduced amount. The engineer reports this finding to the accountant, resolving the issue without further escalation.
This improvement helps your engineers resolve billing questions faster without contacting PortaOne support.
Web interface changes
Redesigned SIM cards, DID/MSISDN inventory, and Log viewer pages
This release introduces a redesigned interface for the SIM cards, DID/MSISDN inventory, and Log viewer pages, making it faster for admins to search, review, and manage these entities.
SIM card inventory
- 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. Less frequently used search parameters for the SIM card are grouped under the More menu, keeping the main panel compact while still providing access to advanced filters across SIM card details.
- Admins can now open a SIM card record and view all available SIM card parameters on a single Configuration page. One page with separate sections provides instant access to SIM card details without any clicks.
DID/MSISDN inventory
- 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. Less frequently used search parameters for the DID numberare grouped under the More menu, keeping the main panel compact while still providing access to advanced filters across DID number details. Tax transaction codes are now accessible from the toolbar as a separate dialog, avoiding confusion.
- All available data in the DID inventory – such as vendor batches, pricing batches, and DID groups – is now organized into tabs on a single page. All tabs share a consistent structure: admins can manage any entity using the Actions column, and view or edit parameters in a side sheet.
Log viewer
- The search panel has been moved to the top of the page, allowing more log details to be visible without horizontal scrolling.
Admins save time and make fewer errors while managing these entities.
Reassign vendor batches for DID numbers when porting numbers
Service providers can now change vendors for DIDs in the inventory without service interruption, even if the DIDs are in use. Previously, it was not possible to change the vendor for DIDs in the inventory, which prevented accurate cost calculation and caused inconvenience. For example, DIDs might be ported to another company due to poor service or better pricing. Now, this can be done in a few clicks via the PortaBilling web interface by selecting the DIDs and choosing a new batch in the Group operations with DIDs panel. This saves time and keeps cost calculations accurate.
- Admins save time by assigning DID numbers to a different vendor in just a few clicks.
- Customers continue to receive calls while the vendor batch for DIDs is updated.
