Features
378
System functions and features as of R3.0
syd-0367/1.3 – R3.0 – 03.2013
9. 4. 3
Call Forwarding on No Reply (CFNR)
Unlike Call Forwarding Unconditional, the call to user B’s terminal is initially sig-
nalled in the normal way when CFNR is activated. If the called party B does not an-
swer the call after (0), 3, 5 or 7 ringing cycles, the call will also be signalled (in paral-
lel) on the terminal of user C, who has been forwarded.
If the call was forwarded to C and was not answered by B, the next call will immedi-
ately be signalled to both users B + C. The delay in the call to C is reactivated only
once the call has been answered directly by called party B. For the delay always to
be active, the parameter
CFNR immediate ring
valid throughout the system must be
configured to
No
.
Fig. 184
Call Forwarding on No Reply
Call Forwarding on No Reply responds differently depending on the system config-
uration and the function code used.
• Normal CFNR:
The user specifies the chosen call forwarding destination on his terminal.
• Preconfigured CFNR:
The call forwarding is made to a destination entered in the user configuration.
• CFNR can also be effected for both types if user B is busy. For this the option
CFNR if busy
must be activated in A’s user configuration.
Detailed Description
Tab. 159 Call Forwarding on No Reply
Interface
Operating sequence / signalling on
the terminal
Scope
B
Once the feature has been activated, B
obtains an acknowledgement tone.
C
Possible destinations:
• Users: internal, external
1)
, PISN
• Coded ringing
• UG: 17 to 21 (Aastra 415/430) or 25 to 29 (Aastra 470)
and user groups configured as "large".
Requirement:
C is not protected against calls (Do not disturb, *26) or
Call Forwarding Unconditional (*02).
1)
If caller A is an external user or a virtual network PISN user, the settings authorising exchange-to-exchange
traffic (see
"Call Forwarding Unconditional to exchange", page 373
) will have to be observed. (If the connec-
tion is not authorized, the call is not forwarded.)