How Roaming Impacts TS.43 Entitlement Flows and Why Your Services Break Abroad

Introduction – What an Entitlement Server Is (and Why You Should Care)

If you’ve ever turned on your phone in a foreign country and wondered why WiFi calling, VoLTE or eSIM-based features sometimes just work (or sometimes don’t) there’s a hidden system working quietly behind the scenes: the entitlement server, guided by the rules of GSMA TS.43.

Entitlement servers let carriers and networks decide what your device is allowed to do, based on your subscription, device type and network readiness. With TS.43, once you insert the SIM (or activate eSIM), your phone checks in with the entitlement server: if everything matches, IMS-based services like VoLTE, VoWiFi, SMS-over-IP and companion-device support are switched on automatically.

That’s why many of us enjoy a seamless experience at home. But what happens when you roam across borders? Will that smooth flow still work, or will the experience break?

In this article, we explore how roaming or international/regional variation impacts entitlement flows; what TS.43 enables, and what it cannot guarantee.

Also read: Entitlement Server Use Cases

How Entitlement Checks Work When You’re at Home Network

Before diving into roaming, it helps to understand how entitlement works under normal (home network) conditions.

What TS.43 Actually Checks

• TS.43 covers a set of IMS-based services such as Voice-over-Cellular (VoLTE / VoNR), Voice-over-WiFi (VoWiFi), SMS over IP (SMSoIP), and On-Device Service Activation (ODSA) for eSIM devices, including primary phones, companion devices (like smartwatches/tablets), and enterprise devices.
• When you enable a service (or boot the device), your phone or companion device triggers an entitlement request to the carrier’s Entitlement Server. This uses a standard protocol flow (often via EAP-AKA authentication when SIM/eSIM is used).
• The entitlement server checks several factors: whether your subscription plan supports the service; whether the device type is allowed; whether the network (IMS core, operator infrastructure) is ready; and possibly consent or policy compliance. If all checks pass, it returns a “service allowed” response, and your phone automatically configures itself.

Why This Matters (Dynamic, Subscription-Aware Activation)

This dynamic check-and-activate mechanism is much more flexible than older static provisioning methods. In the past, services and device configurations often had to be manually provisioned or were locked to specific SIMs/devices. With TS.43-enabled entitlement servers, carriers can roll out or revoke services dynamically. That means less friction for users and lower overhead for operators: new features, companion devices or eSIM-based activations just work (or don’t) depending on entitlement and network readiness.

Also read: How to implement an entitlement server?

What Changes When You Roam (Why Roaming Tests the Limits of Entitlement Servers)

When you travel abroad and roam onto a foreign network, a few things change, and that can potentially break entitlement flows. Here’s why roaming introduces complexity.

Different Network, Different IMS / Core Infrastructure

• Roaming means connecting to a network other than your home operator, and that network may have entirely different IMS implementation, or may not support the same IMS-based services at all (VoLTE, VoWiFi, SMSoIP).
• Even if your home entitlement server says “yes, you can use VoLTE/VoWiFi,” the visited operator’s network must have compatible IMS, roaming-capable core infrastructure and service interworking. If it doesn’t, entitlement can’t magically force those services to work.
• In practice, if the roaming network lacks IMS or VoLTE/VoWiFi support in roaming mode, your phone might fall back to legacy networks (2G/3G) or degrade service quality, even if entitlement is granted.

eSIM / Companion Devices & Profile Constraints Under Roaming

• TS.43 supports ODSA (On-Device Service Activation) flows for eSIM, for primary and companion devices.
• But when roaming: the visited network may not accept external eSIM profiles, may restrict multi-device configurations, or may impose other policy/regulatory limitations. That means even if your eSIM is valid and entitlement is cleared, the network might refuse to allow features, or your companion device may not get proper activation.
• Regional differences in eSIM implementation, roaming agreements, or local regulations can block eSIM activation or companion-device support while roaming.

Regional / Regulatory / Operator Policy Differences

• Countries and operators differ in how they support IMS-based services, roaming, eSIM, and companion devices. Even global OEMs and carriers may implement different policies per region.
• Local regulations, network readiness, roaming agreements among operators, all of these affect whether entitlement passed under TS.43 translates to actual working services abroad.
• So entitlement is only one part of the puzzle: network infrastructure compatibility, operator policies, and regional rules often dictate whether services will actually work.

What TS.43 Guarantees And What It Cannot Do When You Roam

What TS.43 Still Provides Under Roaming

• TS.43 defines a standardized, interoperable mechanism for entitlement checks. If both device and carrier support it, entitlement requests can still be made when roaming. The device (or ODSA/eSIM client) uses standard APIs to ask the entitlement server whether services are allowed.
• Because the entitlement check (EAP-AKA or equivalent authentication) relies on the SIM/eSIM subscription and not on region-specific credentials, the mechanism itself remains valid even if you’re roaming.
• If the visited/roaming network supports the required IMS services and network configuration, services like VoLTE, VoWiFi, SMSoIP or companion-device features can be activated, just like in the home network.

What TS.43 Cannot Guarantee, Why Things May Still Break

• TS.43 does not (and cannot) control or guarantee the IMS infrastructure or roaming-service support at the visited operator. If the roaming network doesn’t support VoLTE/VoWiFi/IMS-roaming, entitlement won’t make services magically work.
• It cannot override regulatory or operator-specific restrictions: for example, some operators intentionally disable certain services (eSIM, companion devices, VoWiFi over roaming) due to policy or licensing constraints.
• It cannot guarantee performance quality (e.g. call quality, latency, fallback reliability) because that depends on roaming agreements, inter-operator IMS interworking, network coverage and capacity.

Also read: GSMA TS.43 best practices.

Practical Scenarios — When Entitlement + Roaming Works … and When It Doesn’t

When Things Work Smoothly

• You travel abroad to a country whose operators support IMS roaming, VoLTE/VoWiFi roaming, and allow eSIM or companion-device use. Your phone boots up, does the TS.43 entitlement check, and automatically gets all the services enabled, as if you were at home.
• A companion device (e.g. smartwatch or secondary eSIM device) gets activated using ODSA and entitlement flows; perfect for people who travel often but want their devices to continue working seamlessly.

When Users Face Issues

• Roaming to a network lacking VoLTE/IMS support: despite entitlement clearing, voice calls fall back to old 2G/3G legacy, losing HD voice or VoWiFi benefits.
• Attempting to activate a companion device with eSIM when roaming: visited network rejects multi-device eSIM profile or disallows companion-device service, leading to no service on the second device.
• Inconsistent behavior due to regional regulations or operator policies: even for the same device and subscription, user experience differs depending on the visited country/operator.

What Operators, OEMs and Users Should Know — Tips & Checklist

• Operators should ensure that their roaming-partner networks support IMS, VoLTE/VoWiFi, eSIM/ODSA and companion-device policies, otherwise entitlement flows won’t deliver value to roaming users.
• For global operators launching eSIM or multi-device offerings: it’s critical to test entitlement flows across roaming networks and multiple countries before rollout.
• Users (especially frequent travellers) should know: entitlement server + TS.43 is a necessary condition for smooth service, but not sufficient; final service availability depends on roaming infrastructure and operator policies.

Conclusion — Entitlement Servers + Roaming: Promising, But Not Magic

Entitlement servers based on TS.43 are a powerful leap forward for telecom networks. They bring flexibility, dynamic service activation, seamless eSIM and companion-device support, and make life easier for users and operators alike. But once roaming enters the picture, things get more complex. The entitlement flow remains valid, but the ultimate experience depends heavily on roaming network support, IMS infrastructure compatibility and regional constraints.

So next time your phone works seamlessly across borders (or fails halfway) remember there’s a mix of standardization, infrastructure and operator readiness behind the scenes. Entitlement + TS.43 give you a shot at smooth connectivity abroad, but only if everything else is in sync.

FAQs

Will our VoLTE and VoWiFi services continue to work for subscribers roaming on networks that do not support IMS?

No. Even if your entitlement server approves VoLTE or VoWiFi, these services will not work on a roaming network that lacks IMS support. TS.43 confirms that the subscriber is entitled to the service, but the visited network must also support VoLTE roaming, IMS interworking and VoWiFi policies. If not, the device automatically falls back to legacy 2G or 3G calling, and WiFi Calling is typically disabled.

‍

Do we need to maintain separate entitlement rules for roaming scenarios or can TS.43 handle everything with a single policy set?

In most cases, a single unified TS.43 policy set is sufficient because entitlement validation happens through the home operator’s server. However, many telcos still choose to add roaming-specific conditions to prevent service activation in countries where IMS, VoWiFi or companion-device support is absent or restricted. TS.43 does not require separate rules, but roaming-aware enhancements often improve experience and compliance.

‍

Will the entitlement server still authenticate devices correctly if the subscriber is connected through a roaming partner’s network or WiFi overseas?

Yes. TS.43 authentication mechanisms such as EAP-AKA still work when roaming or using foreign WiFi. The entitlement request is routed back to the home carrier’s entitlement server over secure channels. Authentication will succeed, but actual feature availability depends on whether the visited network supports the required IMS services.