Hunt groups can be formed for all service types, the hunt group code or master station number being service-neutral. The services are selected using a separate code number.

The call with the highest priority in the queue is assigned to the first group member who becomes available. The priority order within the queue is emergency call, CO call, tie call, internal call.

The previously queued call is presented to the next member who becomes available if it is still in ringing state, for example there is only one call ringing the group and not one call ringing member A and another call ringing member B.

A terminal can belong to several hunt groups. However, it cannot be master of more than one and cannot appear more than once in one and the same hunt group. For a voice hunt group, an overflow to a call queue can be established or a mailbox be added to the voice mail server in case all of a hunt group's stations are busy.

A functional terminal (ISDN terminal) requires the COS parameter MULTRA to ensure that all features work properly. However, when a functional terminal is configured in a hunt group, the COS parameter MULTRA may not be set. Otherwise the hunt group will not work properly and a CP Advisory message (CC:15295 / EC:2015) will be sent. Solution: Delete the MULTRA parameter for the affected terminal, then delete the hunt group, and set it up again.

A hunt group member station can be reached separately under its number or more or less randomly under the huntigroup code. The master station can only be reached as a hunt group member. It must always be the first station of a hunt group.

Attendant terminals cannot be integrated in a hunt group. They have to be accessed via the ATND group by dialing the ATNDDID or ATND group codes.

All group members can LOG ON to and LOG OFF from the group. An option can be configured to allow the last active member of the group to LOG OFF. The LOGON/LOGOFF operation is effective for all groups of which the phone is a member. The operation can be invoked by means of an access code or key or via the service menu.

Names can be assigned to all groups. The group name is presented to the calling party's display while the call is in the ringing state. An option can be configured to show the group name or the name of the group member who accepted the call in the connected state.

By specifying the CPS in AMO SA, availability of the hunt group can be restricted, for example, not available for DID or consultation hold. The DPLN group must be specified if the hunt group code has been added in the DPLN with a DPLN group branch.

Basically, a hunt group can be reached under several code numbers, for example, *80, and by replacing *, under 880. The hunt group must then be duplicated for each further code. This is very simple using the ADD command and the DUPL (duplicate) type branch. Changes made to such hunt groups apply to all code numbers.

The hunt group type "parallel" is only supported for voice (STYPE=PRL is rejected for SVC=DTE/FAX).

A hunt group with parallel ringing can have up to 20 members.

It is possible to assign virtual nodes (defined with KNDEF) to hunt groups in order to ensure correct number modification in complex E164 numbering environments.