Menu
Latest
12 meetings · Prague, Jeju · 12–16 Oct
Reports
RAN1#126-bis · SA2#177

Glossary term · Services

Call leg

Call Leg

Services →

Call leg is a segment of a communication path, either a SIP dialogue or, in OSA context, the access link between a mobile station and the core network, with two such legs joined in a mobile-to-mobile call.

Introduced
Rel-8
Where
Core Network › 5G Core
Specifications
2 specs
Call leg Description Purpose Neighbours Specifications

Description

A call leg is a fundamental concept in telecommunications service architecture, representing one segment of a communication path between endpoints. In 3GPP specifications TS 23.284 and TS 29.998, the term has two related meanings depending on context. In a SIP context, a call leg is another name for a SIP dialogue — a peer-to-peer signaling relationship between two SIP user agents, identified by a Call-ID, From tag, and To tag. In an OSA (Open Service Access) context, a call leg is the communication path as seen from an application to an addressable entity or call party in the network.

The concept is essential for understanding how multi-party and mobile-to-mobile calls are structured. A basic mobile-to-mobile call consists of two call legs: one from the calling mobile station to the core network, and one from the core network to the called mobile station. The core network (typically the MSC Server or, in IMS, the S-CSCF and related entities) bridges the two legs, handling call control, media negotiation, and supplementary services on each leg independently. This separation allows features like call hold, call transfer, and conferencing to be implemented by manipulating individual legs.

In the OSA/Parlay architecture, the call leg abstraction allows applications to interact with calls at a high level without dealing with the underlying SIP signaling details. An application can monitor, answer, or terminate a call leg through standardized APIs. This abstraction was important in the era of service delivery platforms, where third-party applications needed controlled access to call control functions. TS 29.998 specifies the OSA API mapping for these operations.

The definition of call leg changed significantly in Rel-10. The original Rel-8 definition described it as a SIP dialogue or an OSA communication path. The Rel-10 revision replaced this with a more network-centric definition: "The access link between the mobile station and the Core Network. A mobile to mobile call consists of two call legs and the link through the Core Network." This shift reflects the evolution from service-platform abstractions toward a clearer network-topology view of call segmentation, likely driven by the need to describe call handling in the context of CS fallback, SRVCC, and IMS interworking.

The call leg concept remains relevant in modern networks for call forking, forking to multiple devices (e.g., simultaneous ringing), and for legal interception, where each leg may need to be monitored separately. It is a foundational abstraction for understanding call control in both circuit-switched and packet-switched domains.

Purpose & Motivation

The call leg concept exists to decompose complex communication sessions into manageable, independently controllable segments. In any call involving more than two endpoints — or even a simple mobile-to-mobile call — the network must handle each side of the communication separately. Without a formal notion of call legs, it would be impossible to implement features like call hold (put one leg on hold while the other remains active), call transfer (replace one leg with another), conferencing (bridge multiple legs), or forking (ring multiple devices simultaneously).

Historically, the concept emerged from both the SIP/IMS world and the OSA/Parlay service platform world. In SIP, the dialogue concept naturally maps to a call leg, and SIP's dialog identifiers allow precise manipulation of individual legs. In OSA, the call leg abstraction allowed third-party applications to interact with calls without deep SIP knowledge, which was important for the service delivery platform era. The Rel-10 redefinition shifted the emphasis toward network topology, reflecting the growing importance of describing call handling across the access and core network boundaries.

The concept solves the problem of modularity in call control. By treating each leg as an independent object, the network can apply different policies, charging, and supplementary services to each leg. It also enables legal interception and billing to operate per-leg, which is essential for regulatory compliance and accurate charging in multi-party scenarios.

Release Timeline

Evolution Across Releases

An overview written from the defining specifications, not a verified change history. For the exact text, open the specifications listed below.

Rel-8 Initial

Initial definition: 'another name for a dialogue in a SIP context. In an OSA context the communication path as seen from an application to an addressable entity/call party in the network.' Emphasized SIP and OSA service-platform perspectives.

Definition carried over unchanged from Rel-8.

Definition revised to a network-topology view: 'The access link between the mobile station and the Core Network. A mobile to mobile call consists of two call legs and the link through the Core Network.' This replaced the SIP/OSA-centric wording with a clearer description of call segmentation across access and core.

Definition carried over unchanged from the Rel-10 revision.

Definition carried over unchanged.

Definition carried over unchanged.

Definition carried over unchanged.

Definition carried over unchanged.

Definition carried over unchanged.

Definition carried over unchanged.

Definition carried over unchanged.

Definition carried over unchanged.

Defining Specifications

3GPP specifications that define or reference Call leg, with the latest known release. Sourced from the 3GPP document catalog — see methodology.

SpecificationTitleRelease
TS 23.284 vj00 Local Call Local Switch Stage 2 Rel-19 read
TR 29.998 v320 OSA API Mapping to CAP and MAP R99 read