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

Glossary term · Protocol

IAM

Initial Address Message

Protocol →

IAM is an ISUP signaling message used in circuit-switched mobile networks to initiate a call by carrying essential setup information like the called and calling party numbers.

Introduced
R99
Where
Services › IMS
Specifications
14 specs
Also in
Core Network
IAM Description Purpose What changed Neighbours Specifications

Description

The Initial Address Message (IAM) is a critical signaling message within the ISDN User Part (ISUP) protocol, which is part of the Signaling System No. 7 (SS7) suite used for call control in circuit-switched (CS) telephony networks. It is the first message sent in the forward direction to initiate the establishment of a call. The IAM contains all the necessary information for the network to route the call and reserve the required resources. Key information elements within the IAM include the Called Party Number (CdPN), Calling Party Number (CgPN), Nature of Connection Indicators (NCI), Forward Call Indicators, and the requested bearer capability (e.g., speech, 3.1 kHz audio). The message traverses through multiple signaling transfer points (STPs) and exchanges (e.g., MSC, GMSC) based on the dialed number, setting up the circuit path segment by segment.

Upon receiving an IAM, an exchange analyzes the Called Party Number to determine routing. If the exchange is not the final destination, it may perform number analysis and forward a new IAM to the next node in the path, while simultaneously reserving a trunk circuit from the incoming to the outgoing side. This process continues until the IAM reaches the destination exchange serving the called subscriber. The destination exchange then typically sends an Address Complete Message (ACM) back towards the originator, indicating that the address signals have been received and the called party is being alerted.

The IAM's role is central to the call setup phase. Its efficient processing directly impacts post-dial delay and call completion rates. In 3GPP specifications, IAM is used in the core network for inter-MSC calls, calls to the PSTN, and other CS-domain interactions. With the evolution towards all-IP networks (IMS), the role of ISUP and IAM has been supplemented and eventually superseded by SIP-based protocols like SIP-INVITE, but IAM remains crucial for interworking between legacy CS networks and modern IP-based systems.

Purpose & Motivation

The IAM exists to provide a reliable and standardized method for initiating telephone calls in circuit-switched networks. Before digital signaling systems like SS7, call setup relied on in-band signaling (e.g., multi-frequency tones) which was slow, insecure, and limited in feature support. The creation of SS7 and the ISUP protocol, with the IAM as its key call-setup message, solved these problems by introducing out-of-band signaling on a separate, high-speed packet-switched network. This separation allowed for faster call setup, more efficient use of voice trunks, and enabled advanced telephony services like caller ID, call forwarding, and freephone numbers by carrying rich signaling information.

The historical context is rooted in the digitalization of telephony networks. The IAM enabled the global interconnection of national telephony networks (PSTN) and early mobile networks (GSM, UMTS CS domain). It provided a common language for exchanges from different vendors to communicate. Its design addressed the limitations of previous channel-associated signaling by being highly efficient and feature-rich, forming the backbone of international and national telephony for decades. The motivation for its specific structure was to encapsulate all necessary call-routing and service information in a single, initial message to minimize signaling delay.

What changed in its specifications

The latest release-to-release comparison of specifications that define IAM. Each summary describes the whole specification, not only this term.

TR 21.905Rel-17 → Rel-18

Rel-18 brings only minor changes to TS 21.905: 0 clauses changed, with no change attributed to a release feature.

Full comparison in TR 21.905 →
TS 23.018Rel-18 → Rel-19

Rel-19 brings only minor changes to TS 23.018: 0 clauses changed, with no change attributed to a release feature.

Full comparison in TS 23.018 →

Evolution Across Releases

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

R99 Initial

Introduced as the foundational ISUP call setup message within the 3GPP framework for GSM and initial UMTS circuit-switched core networks. It was used for call establishment between MSCs and to/from the PSTN. The architecture relied on the SS7 signaling transport (MTP) and defined the standard 3GPP information element coding for mobile network use.

Defining Specifications

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

SpecificationTitleRelease
TS 03.071 v890 GSM Location Services Stage 2 R99 read
TR 21.905 vj20 3GPP Terminology and Definitions Rel-19 read
TS 23.018 vj00 Basic call handling in 3GPP CS domain Rel-19 read
TS 23.066 vj00 Mobile Number Portability Technical Realization Rel-19 read
TS 23.079 vj00 Support of Optimal Routeing (SOR) Phase 1 Rel-19 read
TS 23.087 vj00 User-to-User Signalling (UUS) Stage 2 Rel-19 read
TS 23.205 vj00 Bearer Independent CS Core Network Stage 2 Rel-19 read
TS 23.231 vj00 SIP-I based CS core network stage 2 Rel-19 read
TS 23.279 vj00 Combined CS and IMS Services (CSI) Architecture Rel-19 read
TS 24.259 vj00 Personal Network Management (PNM) Protocol Details Rel-19 read
TS 24.504 v8m0 Communication Diversion (CDIV) Protocol Specification Rel-8 read
TS 24.508 v820 TIP and TIR Service Protocol Description Rel-8 read
TS 24.604 vj00 Communications Diversion (CDIV) Protocol Spec Rel-19 read
TS 33.831 vc00 Study on Spoofed Call Detection & Prevention Rel-12 read