PortaOne CDR Detail - Version 20.0

Overview

The PortaOne CDR Detail - Version 20.0 collector retrieves individual call detail records (CDRs) from a PortaOne billing and switching environment, covering voice call activity across Reseller, Reseller Customer, and Retail customer types.

This collector provides granular visibility into individual call records, submitting one record per call with details including the calling and called numbers, call duration, destination, and cost. This enables organizations to validate charges at the individual call level and allocate costs within Varibill.

By default, the collector retrieves rated data, meaning call cost values are supplied by PortaOne and submitted directly to Varibill. An optional VAT factor can be applied to adjust charged amounts before submission. The collector can also be configured to run in unrated mode, which omits cost and total values from the output — pricing is then applied entirely within Varibill.

This is a historically capable collector, meaning each execution retrieves CDR data for a configurable date range in the past, rather than a snapshot of the current state.

For general instructions on creating and running Source Collectors, see: Configuring a New Cloud Source Collector

Collector Summary

About PortaOne

PortaOne is a telecommunications software company that provides integrated billing and service management solutions for communication service providers worldwide. Founded in 2001, PortaOne serves over 500 telecom operators across more than 100 countries, ranging from wholesale carriers to retail service providers.

PortaOne’s core platform, PortaSwitch, is a unified service management and delivery platform covering voice, messaging, IoT/M2M, and data traffic. PortaBilling, its accompanying billing component, enables service providers to manage subscriber accounts, rating, and revenue collection.

PortaOne is used by a broad range of providers including Mobile Virtual Network Operators (MVNOs), cloud PBX operators, traditional carriers, and internet-based telephony providers.

Data Collected

The PortaOne CDR Detail - Version 20.0 collector retrieves individual call detail records from PortaOne for a configurable historical date range. Unlike the CDR Aggregate collector, which groups call records by customer, destination, and date, the CDR Detail collector submits one record per individual call.

Each record includes:

• The call duration (quantity) in seconds
• The charged amount for the call, adjusted by the configured VAT factor (in rated mode)
• The vendor cost for the call, where available (in rated mode)
• The destination country and description that identify the call type
• The calling number (CLI) and called number (CLD)
• The date and time of the call
• The customer name, customer type (Reseller, Customer, or Retail), and reseller name (where applicable)

The collector retrieves the customer account data needed to scope collection — covering Reseller, Reseller Customer, and Retail customer types. Customer filtering options allow collection to be limited to or exclude specific customers.

The collector also retrieves vendor XDR data to determine the vendor-side cost for each call. When a vendor cost is available for a given call, it is used as the Cost value; otherwise the customer-side charged amount is used.

The time window covered by each collection run is configurable, enabling the collector to align with your billing cycle and to recover data from prior periods where needed. A time zone offset parameter ensures that date boundaries align with your local time zone.

The identifiers submitted to Varibill for each record are constructed as follows:

• Product Identifier — constructed as {Product Identifier Prefix}{country}#{description}, where the country and description values are derived from the PortaOne CDR data. For example: South Africa#VODACOM - MOBILE, Skywire#South Africa#Local
• Client Identifier — the PortaOne customer ID, optionally prefixed with the configured Client Identifier Prefix. When the Use Account as Client Identifier parameter is enabled, both the customer ID and account ID are included.
• Record Identifier — describes the individual call (for example, Call from: 27333420447 Call to: 0333456903 Date and Time: 2026-05-01 06:14:48 GMT)
• Unique Identifier — the PortaOne XDR record ID, optionally prefixed with the configured Unique Identifier Prefix (for example, 22768638 or P#22768638)

Prerequisites

Before configuring this collector, ensure that:

• You have access to a PortaOne environment (PortaSwitch / PortaBilling)
• You have a PortaOne user account with read access to CDR data
• You have an API token associated with that account
• You have noted the base URL of your PortaOne instance (for example, https://portaone.example.com)
• You have access to the Varibill Source Collector configuration screen

Configuration Parameters

The parameters below are entered when configuring the collector in Varibill. They are grouped by function.

Connection Parameters

These parameters identify and authenticate against your PortaOne instance.

Rating Parameters

Identifier Prefix Parameters

These parameters allow you to prepend a custom string to the identifiers submitted to Varibill. This is useful when multiple PortaOne environments or tenants submit data to the same Varibill instance and identifiers need to be distinguished.

Customer Filtering Parameters

These parameters control which PortaOne customers are included in or excluded from each collection run.

Customer Type Collection Switches

These parameters control which categories of PortaOne customer are included in each collection run. Set each switch to false to exclude that customer type.

Identifier Parameters

Date Range Parameters

These parameters define the time window of CDR data collected on each run.

Operational Parameters

These parameters control API pagination and file management behavior.

Configuration Steps

Step 1: Prepare Your PortaOne Environment

1. Confirm that your PortaOne instance is accessible via HTTPS.
2. Identify the PortaOne user account that Varibill will use to connect. This account must have read access to CDR data for the customer scope you intend to collect.
3. Obtain or generate an API token for that user account.
4. Note the base URL of your PortaOne instance (for example, https://portaone.example.com).

Step 2: Configure the Collector in Varibill

1. In the Varibill User Interface, open the Source Collector configuration screen.

2. Enter the required field values under the Details tab:

   • Hosting Provider: Select Varibill Cloud
   • Source Collector Name: Select PortaOne CDR Detail - Version 20.0

3. Enter the connection parameters:

   • Portaone Host: The base URL of your PortaOne instance
   • Portaone Username: The PortaOne user account name
   • Portaone Token: The API token for that account

4. Set the Vat Factor according to whether your PortaOne environment returns call costs inclusive or exclusive of VAT.

5. Set Run as Unrated to true if you want to omit cost and total values from the collected data and apply pricing within Varibill instead.

6. Configure the identifier prefix parameters (Product Identifier Prefix, Client Identifier Prefix, Unique Identifier Prefix) if you need to distinguish data from multiple PortaOne environments or tenants.

7. Configure the customer filtering and collection switch parameters to match the customer scope you want to collect.

8. Set the date range parameters (Days Offset and Days Range) to match your billing cycle.

9. Set the Time Zone Hourly Offset to reflect the UTC offset of your local time zone.

10. Save the collector configuration.

Step 3: Run the Collector

Run or schedule the collector according to your standard Source Collector execution process.

For detailed instructions, see: Configuring a New Cloud Source Collector

Troubleshooting

If the collector fails to connect to PortaOne, verify that:

• The Portaone Host URL is correct and includes https:// with no trailing slash.
• The Portaone Username is correct and the account is active.
• The Portaone Token is valid and has not expired or been revoked.
• The PortaOne instance is reachable from the Varibill Cloud environment. If your PortaOne instance restricts access by IP, ensure Varibill’s collector IP addresses are permitted.

If the collector connects successfully but returns no data, verify that:

• The Days Offset and Days Range values cover a period in which CDR data exists.
• At least one customer type collection switch (Collect Reseller, Collect Reseller Customers, Collect Retail) is set to true.
• The Collect for Specific Customer value, if populated, corresponds to a valid PortaOne customer ID that has CDR data in the requested date range.

If identifier values in Varibill are unexpected, verify that:

• The Product Identifier Prefix, Client Identifier Prefix, and Unique Identifier Prefix values include any required separator characters (for example, Skywire# rather than Skywire).
• The Use Account as Client Identifier setting matches your intended Client Identifier format.

PortaOne References

The following resources may assist with locating values or understanding your PortaOne configuration.

PortaOne Documentation (External)

• PortaOne Website
• PortaOne Documentation Portal