All group members can activate CFU (Call Forwarding Unconditional). Incoming group calls routed to the group member follow the CFU. If the CFU destination is recognized as being a server, for example OpenScape Xpressions, then CFU is not followed and the member will not be rung for the group call.

An option can be configured to consider any member with CFU active as being available, for example if the group option "busy if at least one member is busy" is chosen, then the group is not considered busy.

UFIP that is not in service and is a Parallel Hunt Group member with CFU set in data base should allow CFU execution.

The party forwarded to the device cannot LOG ON to or LOG OFF from the group on behalf of the forwarding member.

The CFU settings of the master of a master hunt group control the CFU for the entire group, for example if the master has activated CFU, then all incoming group calls are routed to the CFU destination of the master. This also applies in case the master has activated CFU to a server, for example OpenScape Xpressions. This does not apply for a non master hunt group.

CFNR (Call Forwarding on no Reply) and CFB (Call Forwarding Busy) settings for all group members are ignored for incoming group calls.

Regular Call Forwarding processing applies for non group calls, for example if the extension number of the group member has been dialed by the call originator.

Overview: FOLFWBSY and BUSYCOND if CQMAX=0:

All group members can activate do not disturb.

Regular do not disturb processing applies for incoming group calls, for example calls are not routed to members with do not disturb active, etc.

All group members can initiate outgoing calls while being rung for an incoming group call via either keypad dialing or use of a feature key (name key etc.).

If the last ringing group member places an outgoing call, then the incoming group call is queued.

Busy group members with call waiting active are alerted to an incoming group call by an audible and visible (if applicable) indication.

Call waiting is not invoked if the group member decided to initiate an outbound call while the incoming call was ringing.

Only answered calls are logged for the member who answered the call. There is no log for missed calls.

For more information, see the Feature interaction section in OpenScape 4000 V10, Feature Description document.

Only private calls to the hunt group members are signalled on all pickup group members. Calls to the master of a hunt group with parallel ringing are not signalled on other pickup group members

All members offer an incoming call to applications that have registered for the offered event. The call forwarding rules apply if the application deflects the call.

CSTA support is offered only for the following scenarios:

* Basic call to free PRL HG

- call to PRL HG

- all members ring

- a member answers the call

- the other members stop ringing

* Basic call to busy PRL HG

- call to PRL HG

- first call is ringing at members

- second call comes in and gets queued

- a member answers the first call

- the second call is signaled at the remaining free members

* CFU and CFNR to free PRL HG

* Speed extend to free PRL HG

- attendant speed extend of incoming trunk call to HG with free members

- a member answers the call

- the other members stop ringing

* External scenarios

- internal PRL HG member has CFU to external member

- call to PRL HG

- all internal members ring

- external member rings

- internal member answers the call or external member answers the call

- the other members stop ringing

* Other scenarios may work, but are not explicitly supported

If a DID call to a parallel group is intercepted, only the attendant station will ring regardless if the parallel intercept is set on the system.