Routing elements
148
System functions and features as of R3.0
syd-0367/1.3 – R3.0 – 03.2013
Cyclic call distribution and CFNR of user group members
*67 (Call Forwarding Busy) and *61 (Call Forwarding on No Reply) to any destina-
tions can always be activated without causing the members to be excluded from
the user group.
Special case call forwarding on no reply if busy:
Situation:
A user in a user group has activated CFNR to an internal destination (case A), an ex-
ternal destination (case B), a PISN user (case B), an integrated mobile phone (case B)
or voice mail (case B).
The assigned permission set of this user has the parameter CFNR if busy configured
to Yes. The user and all other members in the user group are busy.
Response to an incoming call:
Case A: The call forwarding on no reply is executed in each case.
Case B: The call forwarding on no reply is executed only if both parameters in
Tab. 35 are configured to Ye s. Otherwise, the response is as described in section
" Response if busy" below.
Status of the user group members
The status of the UG members can be viewed for each user group under CM_3.1.2
in AMS. A distinction is made depending on whether the member was logged off
manually or automatically by an external redirected call.
Response if busy
If all the members are busy, the system will respond as follows:
• An external call will be routed in accordance with the emergency routing con-
cept (see "Response if busy", page 193.
• An internal call will be acknowledged with the busy tone.
Caller identification on the terminal
• Call identification during the signalling phase:
The name of the user group is displayed along with the CLIP
• Once a member has answered a call, an entry is made in the list of answered calls
for this member.
If the call remains unanswered, it generates entries in the lists of unanswered
calls of all the UG members. This can be modified in a permission set (CM_4.5,
Authorizations tab, Unanswered calls via UG in calling list parameter).
To Next Page
Loading...
