Description
The Call Progress (CPG) message is a fundamental component of the call control signaling framework within 3GPP networks, primarily defined for the IP Multimedia Subsystem (IMS) and Circuit-Switched (CS) domains. It operates as part of the Session Initiation Protocol (SIP) or ISDN User Part (ISUP) signaling protocols, depending on the network domain. The message is generated by the network (e.g., by a Serving-Call Session Control Function (S-CSCF) in IMS or a Mobile Switching Center (MSC) in CS) to inform the calling party's terminal or network entity about intermediate events during call establishment or teardown. This includes indications that the called party is being alerted (ringing), the call is being connected, or call-related resources are being released.
Architecturally, the CPG message is transmitted within the signaling path established between the User Equipment (UE) and the network, or between network nodes like Media Gateway Control Function (MGCF) and MSC. In IMS, it is carried as a SIP message (e.g., a SIP INFO or re-INVITE with specific headers) and may include Session Description Protocol (SDP) updates for media negotiation. In CS networks, it is mapped to ISUP signaling messages like Call Progress (CPG) or Address Complete (ACM), ensuring interoperability between legacy and IP-based systems. Key parameters within the CPG message include the cause code (indicating the reason for the event), progress indicators (specifying the type of progress, such as in-band information or network congestion), and timestamps for synchronization.
The role of the CPG message is critical for maintaining call state consistency and providing real-time feedback to users. For instance, when a call is placed, the network sends a CPG message with a 'alerting' indication to the caller's UE, triggering the local ringback tone. This prevents the caller from hearing silence and improves user experience. Additionally, the message supports advanced services like call forwarding, where the CPG may indicate redirection events, or multimedia sessions where it conveys media stream modifications. Its standardized format across 3GPP releases ensures that multi-vendor networks and roaming scenarios operate seamlessly, reducing call failures and enhancing service reliability.
Purpose & Motivation
The CPG message was introduced to address the need for a standardized, reliable mechanism to communicate call progression events in telecommunications networks, particularly as networks evolved from pure circuit-switching to hybrid and IP-based architectures like IMS. Prior to its formalization in 3GPP, call progress signaling was often handled through proprietary or domain-specific methods, leading to interoperability issues between different network equipment vendors and between legacy CS and emerging IP networks. This fragmentation could result in inconsistent user experiences, such as missing ringback tones or delayed call connections, especially in multi-operator environments.
Historically, in early GSM and UMTS releases, call control relied heavily on CS signaling protocols like ISUP, which included basic progress indicators but lacked the flexibility for multimedia services. With the introduction of IMS in Release 5, there was a motivation to unify call control across CS and IP domains, requiring a message like CPG to bridge these technologies. The CPG message solves this by providing a common abstraction for call events, enabling smooth interworking between SIP-based IMS calls and traditional telephony. It also addresses limitations in earlier approaches by supporting richer information elements, such as cause codes for detailed error reporting and progress descriptors for in-band/out-of-band notifications, which are essential for troubleshooting and service differentiation.
Furthermore, the CPG message facilitates enhanced services like video calling, where call setup involves multiple media streams, and regulatory features like lawful interception, where progress events must be logged. By standardizing it across releases, 3GPP ensured backward compatibility and forward scalability, allowing networks to evolve while maintaining consistent call control semantics. This has been crucial for the global adoption of VoLTE, VoNR, and other real-time communication services, where predictable call behavior is a key quality metric.
Key Features
- Conveys standardized call progress events like alerting, connect, and disconnect
- Supports both SIP-based IMS signaling and ISUP-based CS signaling
- Includes cause codes and progress indicators for detailed event reporting
- Enables interworking between circuit-switched and IP multimedia domains
- Triggers user feedback mechanisms such as ringback tones in UE
- Facilitates advanced services like call forwarding and media negotiation
Evolution Across Releases
Introduced the CPG message as part of the CAMEL Phase 3 enhancements for intelligent network services, primarily in CS domains. It provided basic call progress signaling between MSC and gsmSCF, enabling standardized event notifications during call setup for prepaid and other value-added services. The initial architecture focused on ISUP mapping and basic cause code support.
Defining Specifications
| Specification | Title |
|---|---|
| TS 23.087 | 3GPP TS 23.087 |
| TS 24.173 | 3GPP TS 24.173 |
| TS 24.404 | 3GPP TS 24.404 |
| TS 24.405 | 3GPP TS 24.405 |
| TS 24.504 | 3GPP TS 24.504 |
| TS 24.505 | 3GPP TS 24.505 |
| TS 24.604 | 3GPP TS 24.604 |
| TS 29.163 | 3GPP TS 29.163 |
| TS 29.235 | 3GPP TS 29.235 |