A carrier call type is a translation rule. Every call record (CDR) that arrives from a carrier carries a charge band code:the carrier’s own label for what kind of call it was. Before the platform can rate the call against your tariffs, it needs to convert that carrier-specific code into one of your internal call types (National, Mobile, International, and so on). Carrier call types are the list of conversions the platform uses to do that.
Each carrier has its own set of codes, and you can have the same internal call type mapped from many different carrier codes. For example, “National” might be mapped from:
NATon one wholesale carrier’s feeds.UK_STDandUK_GEOon another carrier who splits geographic codes out.G21on a legacy carrier using their own numeric scheme.
The platform matches each CDR to exactly one carrier call type: it looks up the carrier the file came from, finds the row with a matching charge band, and uses the linked internal call type for rating. If no row matches, the call falls back to default rating and typically flags a chargeband discrepancy for you to investigate. That makes this mapping the single biggest lever for keeping call-rating accuracy high, especially when you onboard a new carrier or a carrier changes their coding scheme.
Typical times you’ll be editing this list:
- New carrier onboarding: build out mappings for every charge band that carrier sends, so the first CDR import rates cleanly instead of flooding the chargeband discrepancy report with unknown codes.
- Carrier code changes: add new rows when a supplier introduces a new charge band (for example, a new international destination, or a split of one code into several).
- Resolving discrepancies: when the discrepancy report flags an unrecognised code, add a mapping (or confirm the CDR is genuinely malformed) so the rating engine can handle it next time.
What this page covers
- A full field reference for every field on the carrier call type record.
- How mappings drive CDR rating during billing runs.
For the related non-call equivalent, see Carrier Transaction Types.
Field Reference
The table below lists every field on the carrier call type record.
Carrier Call Type
This section defines the mapping between carrier charging codes (found in CDRs) and internal call types used within the platform. This allows the system to properly categorise and bill calls based on carrier-provided charge band information.
| Field | Description |
|---|---|
| Carrier | The carrier to which this charge band mapping applies |
| Call Type | The internal call type that this charge band maps to |
| Charge Band | The carrier-specific charge band code used to identify call types |
System Information
| Field | Description |
|---|---|
| Last Modified | Timestamp of the most recent modification to this carrier call type |
| Created | Timestamp when this carrier call type was created |
Notes on key fields
Charge Band
The charge band code as it appears in the carrier’s CDR files, up to 50 characters. This must match exactly what the carrier sends, otherwise the mapping won’t fire and calls will fall back to default rating.
Call Type
When the platform sees the Charge Band in a CDR file from this carrier, it uses the linked internal call type for rating. Different carriers can map the same internal call type from different charge band codes.