IMS Voice Strategy in MVNO Wholesale Agreements

MVNO voice strategy is now a wholesale operating question, not merely a migration from legacy interconnect. As hosts retire 2G and 3G dependencies, the commercial viability of an MVNO increasingly rests on the allocation of IMS interconnect costs, emergency-call liability, location accuracy and CLI governance. The central negotiating issue is emergency call ownership: who controls the call path, who supplies location, who carries regulatory exposure, and how those obligations are priced into the host agreement.

IMS migration changes the wholesale boundary

Legacy hosting agreements often price voice as part of a bundled wholesale allowance. That structure may distinguish on-net and off-net minutes, but it rarely separates RAN access, core voice control, transit, termination and emergency routing with sufficient precision. Circuit-switched fallback concealed some of those boundaries because established network processes absorbed exceptions. Once the host withdraws 2G or 3G coverage, previously implicit functions become identifiable operating costs and contractual dependencies.

In a hosted IMS model, the MNO usually retains the EPC or 5G SA core, IMS control and emergency-routing logic. The MVNO retains tariff design, subscriber communications and first-line care. This division does not by itself settle responsibility. A customer who cannot register for voice contacts the retail brand, while the root cause may sit in host provisioning, device policy, subscriber records or IMS configuration. The wholesale schedule therefore needs to connect operational control to cost recovery, incident ownership and service-credit exposure.

The service description should state whether the MVNO receives hosted VoLTE, a direct IMS interconnect, an SBC hand-off or a narrower voice-resale service. Hosted VoLTE places more control and assurance work with the MNO. An IMS interconnect or SBC hand-off may shift integration, capacity, security and fault-isolation obligations toward the MVNO or its enablement partner. A resale construct can reduce initial capital requirements but gives the MVNO less control over routing policy and diagnostic evidence. The commercial schedule should reflect those differences rather than attach one undifferentiated per-minute rate to all models.

VoLTE availability is not a binary feature. Device certification, IMS registration success, roaming treatment, MNP states and emergency-call fallback determine the effective service experience. The distinction matters for churn because a nominally active subscriber may still encounter failed registration, one-way audio or inconsistent calling after a port or firmware change. Wholesale reporting that records only platform availability will not reveal these cohort-level failures.

For Tier-2 MNO, Western Europe, ~18M subscribers, a planned 3G retirement required the hosted MVNO base to move from inclusive voice pricing to an explicit IMS service schedule. The review exposed device-testing and emergency-routing work that had not been separately priced. The issue was not simply an increase in network cost. It was the absence of a contractual method for approving test scope, allocating regulatory change costs and determining whether remediation belonged inside the recurring host fee. Until those points were resolved, neither party could model post-migration margin with confidence.

Emergency calls require a named operational owner

A general warranty that the host will provide compliant voice service is too broad for emergency operations. Obligations should be assigned by control point. Where the MNO controls IMS, the packet core and the emergency-routing policy, it should normally own call routing, connectivity to the PSAP, network-side location acquisition and core incident escalation. It should also maintain the routing records and technical evidence required to establish how a call was treated.

The MVNO should own the accuracy of subscriber identity records supplied through agreed interfaces, customer contact procedures, tariff disclosures and device communications. That remit includes communications concerning compatible handsets, firmware, roaming limitations and eSIM profile treatment. It should also escalate provisioning faults that prevent IMS registration. The host agreement needs a corresponding acceptance process so that an escalation cannot be rejected merely because the subscriber remains attached for data.

Call completion and location delivery require separate measures. An emergency call may reach the correct authority while the associated location record is stale, absent or unavailable at the relevant interface. Conversely, location data may be present while routing fails. Combining both outcomes into a single availability measure weakens incident analysis and creates ambiguity over service credits, regulatory reporting and remediation charges.

CLI policy also requires explicit treatment. The schedule should cover emergency calls, domestic outbound voice, international destinations, CLI screening and ported-number states. Generic presentation rules can fail when the MSISDN, IMSI and serving-network records are not aligned. That failure can produce rejected calls, incorrect presentation or an investigation in which the parties rely on different identifiers. The contract should name the authoritative record for each decision and state how quickly mismatches must be corrected.

The operating schedule should identify 24-hour contacts, severity thresholds, evidence-retention periods and regulatory notification ownership. It should set post-incident review timing and address complaints arising from device-specific VoLTE failures. These are commercial provisions as much as operational ones. Without fixed escalation and evidence rules, fault attribution can remain unresolved beyond the invoice-dispute window, leaving the MVNO to absorb customer credits and care costs while the host retains the full recurring charge.

Price the IMS voice stack as a governed cost base

A per-active-subscriber IMS fee can provide predictable economics where the host supplies registration, service continuity and standard assurance. The definition of active, however, must be contractual. Suspended subscribers, secondary SIMs, dormant profiles and data-active subscribers without successful IMS registration can materially change the billed base. A recurring fee should not obscure exceptional engineering, certification or regulatory-change costs, but neither should those costs remain open-ended.

Voice termination, transit, roaming voice, number portability and emergency routing should retain identifiable settlement treatment even where the retail proposition includes unlimited domestic calling. Unlimited retail pricing transfers usage variability into the MVNO margin; it does not eliminate underlying interconnect expense. The parties need a source hierarchy for CDR and IPDR data, including the treatment of mediation gaps, rerated events and late roaming records.

Settlement cadence affects working capital. Monthly invoicing may appear standard, but the economic result depends on record availability, dispute windows and credit-note governance. If roaming records arrive after the initial close, the MVNO may face retrospective adjustments after customer revenue has already been recognised. If disputes require payment in full before investigation, the host receives a financing benefit. A balanced schedule should set materiality thresholds, allow documented withholding of disputed amounts and impose a deadline for evidence exchange.

Revenue-share models require the same precision. Gross revenue should state whether it includes promotional credits, bad debt recoveries, taxes, interconnect charges, fraud losses, handset support and eSIM subsidies. A share calculated before unavoidable network charges has a different margin profile from one calculated after those charges. The agreement should also prevent double recovery where a recurring IMS fee and a revenue share both purport to fund the same assurance function.

Recurring IMS hosting charge

Per active IMS-capable subscriber per month; define inactive, suspended and multi-SIM treatment.

Voice usage settlement

Rated minutes, termination, transit and roaming voice; specify CDR/IPDR source hierarchy and dispute window.

Emergency-service change cost

Pass-through or capped change-control item for PSAP, location-interface or regulatory modifications.

Device and eSIM certification

Agreed annual test envelope, with a defined rate card for additional OEM, profile or firmware work.

Service-credit exposure

Capped against the affected wholesale charge, with exclusions for handset defects, third-party emergency networks and force majeure.

Migration milestones should connect payment and service credits to measurable outcomes. Suitable measures include activation success, IMS registration by eligible device cohort, emergency-route test completion and fault-resolution time. An undifferentiated penalty for any perceived voice issue invites dispute because it does not identify the affected control point. Credits should be capped against the relevant wholesale charge, while repeated failure against the same milestone should trigger remediation governance rather than merely another invoice adjustment.

Governance determines whether migration protects retention

A joint migration board should begin before legacy withdrawal dates become fixed. Its reporting pack should track IMS registration rates, failed-call patterns, device cohorts, ported-number exceptions, emergency incidents, complaint volumes and churn by activation cohort. Churn is a lagging measure, so the board should also examine repeat contacts, failed registration after profile changes and complaint concentration by handset or firmware. These indicators show whether a network issue is becoming a retail retention cost.

The host must provide enough operational detail for the MVNO to isolate addressable failures without exposing unnecessary core-network or security-sensitive data. Aggregated platform availability is insufficient when the commercial question concerns a specific device cohort, porting state or provisioning path. Reports should also reconcile with billing populations. If assurance data counts registered subscribers while invoices count all provisioned profiles, the parties cannot test whether the recurring fee corresponds to delivered capability.

Exit and transition provisions become more important after circuit-switched alternatives disappear. The agreement should define the process for MNP, subscriber-data handling, eSIM profile continuity and outstanding settlement reconciliation. It should specify access to records during the transition period and the handling of unresolved incidents after termination. A nominal right to migrate has limited value if number-porting windows, profile dependencies or evidence retention prevent an orderly transfer.

Renewal pricing should follow measurable changes in active-base scale, VoLTE penetration, support burden and regulatory scope. A general reopening clause gives little protection once the host has completed network retirement and the MVNO has fewer practical alternatives. Volume bands, indexation, change-control caps and benchmark rights provide a more auditable basis for negotiation. They also allow the CFO to distinguish scale effects from genuine increases in compliance or assurance cost.

A broader partnership review can map IMS voice against HLR and MNP dependencies, eSIM RSP responsibilities and IPRN exposure. That review should occur before commercial schedules are finalised. Otherwise, a voice migration may resolve registration and call routing while leaving numbering, profile lifecycle or fraud controls outside the operating model.

IMS migration will reward wholesale agreements that make emergency routing, location delivery, CLI handling and incident accountability commercially explicit. The decisive question is not whether an MVNO can offer VoLTE, but whether both parties can price and govern the obligations that sit behind every completed call.