Full two-way roaming. Mediation ingests usage from any visited network, the convergent engine charges your own subscribers abroad, and visiting subscribers are metered and settled with their home operator through TAP-out — modeled on GSMA TAP3 semantics.
Roaming usage records from visited operators are normalised into the platform's canonical call detail records before rating. The mediation engine reads delimited, columnar and keyed text exports (CSV, JSON-Lines, fixed-width) and maps any vendor's column names, units and timestamp formats onto a single internal model.
A new partner format is added by dropping a configuration descriptor — no recompilation and no redeployment of the core engine.
Usage your own subscribers generate while abroad is rated through the same convergent engine that handles home traffic, with a dedicated roaming tariff applied per service and visited network. Charges flow into the standard offline store and the normal monthly bill cycle.
Records are de-duplicated on the mediation sequence identifier, so a re-sent batch is never double-charged.
Subscribers from other operators attaching to your network are tracked as temporary visiting-roamer records, kept entirely separate from your own subscriber base. Operators manage the full visit lifecycle — bring-in, metered usage and end-of-visit — from a dedicated CRM administration screen.
A visitor is never billed as one of your customers; their usage is settled with their home operator.
Visiting-roamer usage is priced at the wholesale Inter-Operator Tariff (IOT) and aggregated into settlement batches addressed to each visitor's home operator, with sender/recipient network codes, a monotonic per-recipient sequence and reconciled audit totals.
Output is modeled on GSMA TAP3 (TD.57) settlement semantics for inter-operator clearing.