Hunt groups let you dial a pilot number and have the call completed to the first idle station in a group of stations. Any station within a Hunt Group may be accessed directly by dialing the station number.
Two types of hunting are provided by the system: circular and terminal. In circular hunting, the search for an idle station begins at the station after the last one to receive a call. In terminal hunting, the search for an idle station begins at the first station programmed in the Hunt Group. In both cases, the search progresses through all stations in the Hunt Group in a programmed sequence.
If there is a free member in the hunt group, that station is rung by a caller who accesses the group. If the hunt group is busy, one of the following operations take place:
An internal caller receives busy tone and has the option of going on-hook, setting a callback, or camping on.
A DIL caller receives ringback tone (from the CO or the distant system) and is placed in a first-in, first-out call queue within the system.
A DID trunk caller receives busy tone.
A transferred trunk call receives music or silence.
The first member of the hunt group to become free is connected to the next waiting caller.
You must program the leading
digits of the hunt group pilot number to be greater than its RAD group
numbers. When the system backs up or restores Hunt Groups, it does so
in the order of the leading digits of the hunt group pilot number. If
the leading digit of the hunt group number is lower than its RAD group
number, the system will be unable to back up or restore the RAD group
data and the system will display an error message (for example: "RAD
group must be a number that will be DATA RESTORED before the pilot number").
The following table provides some examples to illustrate this requirement:
|
Hunt Group Number |
RAD Group Number |
Backup/Restore Successful |
|
2 |
1 |
Yes |
|
9 |
7 |
Yes |
|
1 |
2 |
No |
|
13 |
7 |
No (leading digit 1 is not greater than RAD group number 7) |
Override cannot be performed on a Hunt Group. If you attempt to Override, you will hear reorder tone.
A Hot Desk user cannot be a member of an Emergency Hunt Group or a Recorder Hunt Group.
A Hot Desk user cannot log into a Registration DN that is a member of an Emergency Hunt Group or a Recorder Hunt Group.
The following phones can be members of an Emergency Hunt Group: SUPERSET 420, SUPERSET 430, SUPERSET 4025, SUPERSET 4125, SUPERSET 4150, 5220 IP Phone, 5224 IP Phone, 5235 IP Phone, 5140 IP Phone, 5230 IP appliance, 5240 IP Phone, 5324 IP Phone, and Navigator.
To ensure the consistent application of COS across all members of a hunt group, ensure that you program the hunt group and hunt group members with the same COS.
The Hunt Group COS (or, if no Hunt Group COS is programmed, the COS of the first member of the Hunt Group) is used for the following COS options:
Call Reroute after CFFM to busy destination
COV/ONS/E&M Voice Mail Port
ONS/OPS Internal Ring Cadence for External Callers (only if the first member is ONS/OPS)
ANSWER PLUS - Delay To Message Timer
ANSWER PLUS - System Reroute Timer
Call Forward - No Answer Timer
If members of a hunt group share a Key System line and the hunt group also includes ACD sets, ensure that a non-ACD set has the lowest directory number. After a database restore, phones get restored in numerical order. If the first phone in the Multiline Appearance Groups form is an ACD set, you cannot call the hunt group until that agent logs in.
Enter the Pilot Number and Hunt Mode in the Hunt Groups form.
Enter the Directory Number of each member in the Hunt Groups form.
Note: The order in which the numbers are entered affects the order in which the hunt is conducted.
None.
