Call Forwarding on No Reply

Description

Call Forwarding on No Reply (CFNRY) is a network-based supplementary service standardized in 3GPP specifications, primarily within the charging and management domain (TS 32.250). It operates within the core network's service layer, specifically as part of the Home Subscriber Server (HSS) or Home Location Register (HLR) service profile and is executed by the Mobile Switching Center (MSC) or IP Multimedia Subsystem (IMS) Call Session Control Functions (CSCFs). The service is invoked during call establishment when the called party's device is reachable (rings) but no answer is detected before a configurable timer expires.

The technical implementation involves several network elements. The subscriber's CFNRY service data, including the forward-to number and the no-reply timer value, is stored in their service profile within the HSS/HLR. When a call arrives at the MSC Server (in circuit-switched networks) or the Serving-CSCF (in IMS), the network checks if CFNRY is active. If active, the network attempts to alert the called user. A timer, typically configurable by the subscriber or network operator (often defaulting to a value like 15-30 seconds), starts upon alerting. If the call is not answered before this timer expires, the MSC or S-CSCF releases the initial call attempt and initiates a new call setup to the pre-registered forward-to number.

The service logic is governed by basic state models and detection points defined in Customized Applications for Mobile networks Enhanced Logic (CAMEL) or IMS Service Control (ISC) interfaces. In IMS, the service can be implemented as an initial Filter Criteria (iFC) in the S-CSCF, triggering application server interaction. Charging records (CDRs) are generated for both the original attempted call and the forwarded call leg, with specific indicators to denote the CFNRY invocation. The service works in conjunction with other call forwarding variants (like CFU, CFB, CFNRc) with a defined priority order to avoid conflicts.

CFNRY's role is to enhance service completion rates and user convenience. It is a foundational telephony service that has evolved from legacy GSM into 3G, 4G, and 5G networks, now supported within both circuit-switched and IP-based IMS service architectures. Its reliable operation depends on accurate subscriber data management, precise timer handling, and proper integration with charging systems to ensure correct billing for the forwarded call.

Purpose & Motivation

CFNRY was created to solve the problem of missed calls and inefficient communication attempts. Before such standardized forwarding services, if a user did not answer their phone, the caller would simply receive a busy tone or voicemail after a timeout, requiring them to redial or leave a message. This was inefficient for time-sensitive communication or when the called party was temporarily unavailable but wanted calls to reach an alternative contact (like a secretary or mobile phone). CFNRY automates this redirection, ensuring the call reaches a viable endpoint without caller intervention.

The service addresses limitations of manual call handling and basic voicemail by providing proactive, automated call completion. Historically, it was part of the GSM Phase 2 supplementary services introduced to compete with fixed-line telephony features. Its standardization in 3GPP (from Release 8 in the context of evolved charging specifications) ensured interoperability across networks and vendors, allowing subscribers to use the same service when roaming. It solved the issue of subscriber accessibility, increasing network utilization and perceived service quality.

In modern networks, CFNRY remains relevant for business continuity, personal convenience, and as a component of richer call handling services (like call screening or sequential ringing). It integrates with other forwarding conditions to give users granular control over call routing based on different scenarios (busy, unreachable, no reply). This flexibility helps optimize communication flow in both personal and enterprise contexts.

Key Features

• Automatic call redirection upon expiry of a configurable no-reply timer
• Network-based service execution requiring no action from the called party during invocation
• Subscriber-configurable forward-to destination number via network provisioning
• Generation of specific charging records (CDRs) for the original and forwarded call legs
• Interoperability across circuit-switched (CS) and IMS-based networks
• Defined priority and interaction rules with other call forwarding services (CFU, CFB, CFNRc)

Evolution Across Releases

Defining Specifications