PortaOne Source Collector Versions

Modified on Tue, 17 Nov at 1:47 PM

PortaOne Source Collector Versions

This page provides a quick comparison of the available versions for each PortaOne Source Collector. Use the tables below to identify what changed between versions and to determine which version is right for your environment.

For full configuration details, refer to the individual collector guide linked in each table.

CDR Detail

The CDR Detail collector retrieves individual call detail records from PortaOne, submitting one record per call. It supports both rated and unrated modes.

Available Versions

VersionRating ModelParametersGuide
21.0 (latest)Rated (default) / Unrated25PortaOne CDR Detail - Version 21.0
20.0Rated (default) / Unrated23PortaOne CDR Detail - Version 20.0
19.8Rated / Unrated21PortaOne CDR Detail - Version 19.8

What Changed

Version 21.0 (from 20.0)

AreaChange
New parameter: Include Vendor CostControls whether vendor XDR data is retrieved. When enabled (the default), the collector fetches vendor-side cost data and uses it as the Cost value for each record. When disabled, vendor XDR retrieval is skipped and the Cost equals the Total. In version 20.0, vendor cost retrieval was always performed.
New parameter: Include History Tag in Product IdentifierWhen enabled, a tag derived from the CDR’s SIP routing data is appended to the Product Identifier (for example, South Africa#National Mobile#sbc01.example.com). When disabled (the default), the Product Identifier ends at the description, matching the behavior of prior versions.

Version 20.0 (from 19.8)

AreaChange
Vendor cost dataAdded vendor XDR retrieval. The collector now fetches vendor-side cost data from PortaOne and uses it as the Cost value when available. In version 19.8, no vendor cost data was collected.
Identifier prefix parametersThe Product Identifier Prefix, Client Identifier Prefix, and Unique Identifier Prefix parameters are now grouped under their own section with clearer descriptions and default value guidance.
New parameter: Date FormatAdded a configurable date format parameter for date calculations (default: yyyy-MM-dd).
Product Identifier labelThe Product Identifier now references the destination “description” rather than “tariff name” in the documentation, reflecting the actual PortaOne field used.

CDR Aggregate

The CDR Aggregate collector retrieves aggregated call detail records from PortaOne, grouping call data by customer, destination, and date. It operates in rated mode only.

Available Versions

VersionRating ModelParametersGuide
18.0 (latest)Rated17PortaOne CDR Aggregate - Version 18.0
17.5Rated17PortaOne CDR Aggregate - Version 17.5

What Changed

Version 18.0 (from 17.5)

AreaChange
Vendor cost dataAdded vendor cost retrieval. The collector now fetches vendor-side cost data from PortaOne and includes it alongside the customer-facing charged amount. When vendor cost data is not available for a record, the charged amount is used as the cost value.
VAT Factor scopeThe VAT Factor is now applied to both the charged amount and the vendor cost before submission. In version 17.5, it was applied only to the charged amount.
Unique IdentifierThe CRC32 hash used to generate the Unique Identifier now includes the Tag value in addition to the Client Identifier, Product Identifier, and date. This produces a more precise unique key for each aggregated record.

Single-Version Collectors

The following PortaOne collectors have only one published version. No version comparison is needed — refer to the individual guide directly.

CollectorVersionRating ModelGuide
PortaOne Extensions10.0—PortaOne Extensions - Version 10.0
PortaOne Transaction15.0—PortaOne Transaction - Version 15.0
PortaOne Transaction By Account15.0—PortaOne Transaction By Account - Version 15.0
PortaOne Trunk8.0—PortaOne Trunk - Version 8.0

Was this article helpful?

That’s Great!

Thank you for your feedback

Sorry! We couldn't be helpful

Thank you for your feedback

Let us know how can we improve this article!

Select at least one of the reasons
CAPTCHA verification is required.

Feedback sent

We appreciate your effort and will try to fix the article