Ascotel IntelliGate 2025/2045/2065
Part 2 Features 447
Chain of Call Forwarding on No Reply:
• Internal: Call Forwarding on No Reply are not chained together locally. (The call
is routed to C but cannot be routed any further.)
• In the PISN: CFNR chains within the PISN are possible if B and C are connected
to different PINXs.
Note:
CFNR chains in the PISN result in long ringing times.
For the delay always to be active, "CFNR immediate ring = No" must be config-
ured throughout the system.
1)
Note:
If a CDE destination is defined under "Default CF if no answer" in the
subscriber configuration, it is possible to configure whether CFNR or the
default call forwarding is to be executed (see also "Default Call Forward-
ing per Subscriber", page 277).
CFNR to the exchange
With Call Forwarding on No Reply to the public or private network the subscriber
remains activated in his user group.
Incoming calls on the user groups that reach this subscriber are therefore routed
to the CFNR destination (this applies to ordinary user groups, not large user
groups, see "User Group", page 236).
Note:
If in a user group several subscribers have configured CFNR to the
exchange, it may not be possible to set up some of the calls. The number
of calls that can be set up depends on the resources available at the time
(free B channels in the corresponding trunk group).
Prefix dialling procedures
Tab. 2.138: Call Forwarding on No Reply: Procedures
1)
See country-specific initialization configuration.
*/# procedure
Activate CFNR to subscriber *61 destination No.
Clear CFNR to subscriber #61
Activate CFNR to subscriber last configured *61#
Clear CFNR to subscriber last configured #61
To Next Page
Loading...
