Collapse AllExpand All

10.6.1. Feature Description Previous topic Parent topic Child topic Next topic

For each service (DTE, FAX, VOICE), you can assign a forwarding destination to a phone number. You cannot assign a forwarding destination to attendant consoles and special stations. The different criteria for call forwarding are explained in the following.
There are three different types of forwarding:
There are also the following types of call forwarding which are assigned to the above-mentioned FWD types according to Table 57 on page 96, Forwarding types. You can program destinations for these.
  • Unconditional call forwarding (FWD/CFU)
  • Call forwarding if busy (CFB)
  • Call forwarding if no response after timeout (CFNR)
  • Call forwarding if do not disturb (CFDND)
IMPORTANT:
Call forwarding type CFDND: Do-not-disturb is a separate feature that you activate with the do-not-disturb button on the station device. If you want all calls to be forwarded in this state, configure and activate a forwarding destination for SYSTEM in CFDND. This forwarding runs only when do-not-disturb is activated.
Furthermore, there are two types of forwarding that do not have separate destinations defined:
  • Call deflection, forced forwarding (CD), always uses the CFNR destination. (This type of forwarding allows you to activate the FWD action during the call by pressing the FWD key or disconnect key on the telephone.)
  • Delayed Call Forward Busy (DelCFB) always uses the CFB destination. (This type of forwarding has only been implemented for optiPoint telephones and requires the parameter DCFWBUSY. If this is set, camp-on automatically occurs at busy stations that are called and, after some time has expired, call forwarding on busy (CFB) occurs.)
Another possibility for some types of forwarding is to make a distinction based on the type of incoming connection. For example, an external connection is forwarded to a different destination than an internal incoming connection.
The following table illustrates the forwarding assignments

Table 55. Forwarding types

 
CFU
CFB
CFNR
CFBNR
CFDND
Variable
(IM and US)
INT
EXT
GEN
GEN
GEN
GEN
-----
Fixed
(not US)
GEN
-----
-----
-----
-----
System
(IM and US)
INT
EXT
GEN
INT
EXT
GEN
INT
EXT
GEN
------
INT
EXT
GEN
CFBNR defines only a common destination for CFB and CFNR but is not a separate type of forwarding. "GEN" means the same destination for internal and external calls.
IMPORTANT:
For functional terminals according to DSS1 protocol, forwarded calls that are programmed according to the protocol are shown under variable forwarding. For this reason, it is also not restricted to only one variable forwarding destination at a given time the way other station devices are (see Section 96.2.1, "Variable Call Forwarding")

Important Information for USA

In the USA, only the variable and system FWD types are used. To keep the fixed FWD out of the station device interface, you must set the parameter for the user interface without fixed forwarding in the central system data. As a result:
  • The system does not offer fixed FWD in the optiPoint menu
  • No FWD information is displayed when in the idle state
  • FWD-LED signaling also occurs for the variable CFB and CFNR
When the system is delivered, the parameter CFUI is set to "YES".

Destinations can be:

  • Configured subscribers and MASTER HT for each service
  • Hunt group code for each service
  • Personal station number of attendant console on voice
  • Attendant console call queue (M key) only for voice
  • Attendant group access code of attendant group
  • Multiple code calling/paging with "meet me" (that is, you must configure search code and attendant code)
  • Announcement via TCOM (adapter set for special equipment)
  • Server for the particular service
  • External destinations
There must be an allowed connection from the subscriber or MASTER HT to the call forwarding destination. With the parameter ITRFWD, you can centrally define whether there should be a check of the connection from the caller to the forwarding destination when there is a call.
In principle, all call forwarding actions can be chained. You can configure this centrally with parameters.
You must provide enough memory for the forwarding destinations.