Hunt Groups

Purpose:

The Hunt Groups form is used to gather directory numbers into terminal or circular groups. The form consists of a group pilot number, hunt mode, name and a list of all directory numbers belonging to the group. In order to create hunt groups, it is only necessary to list the group members (directory numbers) under the appropriate pilot number. This form uses Range programming.

Use this form when performing the following tasks:

Conditions

The First RAD, Second RAD, First Threshold, Second Threshold, Alert Device DN and Phase Timer Ring fields cannot be programmed for a phantom group. To route calls directly from a phantom group to a NIGHT RAD, any Busy/DND First Alternate rerouting must be omitted for the phantom group.

Field Descriptions

Parameter	Description	Default Value
Hunt Group	Enter a unique directory number up to seven digits in length for the hunt group pilot number. The pilot number is the number dialed to access the hunt group. The leading digits of the hunt group pilot number must be greater than the RAD group numbers (see Hunt Group Conditions for details).	Blank
Local-only DN	Allows you to specify the directory number of the Hunt Group as a local-only directory number in a cluster. This check box only appears in the form if your system has been migrated to support Remote Directory Number Synchronization.	Not selected
Hunt Group Mode	Select the mode of hunting: "Circular" for circular hunting in which the stations that form the group are searched in a circular manner beginning with the station following the last used station as listed in the group. "Terminal" for terminal hunting in which the stations that form the group are searched starting at the first station and ending with the last station in the group. Note: You must select Circular if the Hunt Group Type is "VoiceMail". In a Network Hunt Group, circular hunting is preferred to minimize making network calls to busy remote members. If you must use terminal hunting in a Network Hunt Group, it is more efficient to place local members at the top of the member list.	Circular
Hunt Group Name	System-generated, protected field. Indicates the name under which the hunt group is listed in the telephone directory. If no name exists in Telephone Directory for the pilot number, this field is blank.
COS (Day)	If no Class of Service is programmed, the Hunt Group uses the COS of the first programmed member. To specify a COS for all Hunt Group members, enter values appropriate to the switch service (Day, Night1, or Night2). Notes: For Network Hunt Groups, these fields must be programmed before you add remote members to the group. You must program these fields before you can enable a hunt group with resiliency.	Blank
COS (Night1)
COS (Night2)
Home Element	Displays the name of the primary element for the hunt group.
Secondary Element	Allows you to enable and disable resiliency for the hunt group. You can only enable resiliency if the Group Type field is set to "Voice" or "VoiceMail". On the primary (local) element, select the secondary element for the resilient hunt group. If the primary element fails, the hunt group fails over to the secondary element that is specified in this field. You must program the COS fields before you can enable a hunt group with resiliency. Refer to the 3300 ICP Resiliency Guide on Mitel Online for instructions on how to configure hunt group resiliency. In this form, the secondary element field displays "Not Assigned" if the group is not resilient. If the secondary element field is blank, the group is resilient but the secondary element name is blank. In the Add and Change window, the secondary element field allows you to enable resiliency. To enable resiliency, select an element from the drop-down list. To disable resiliency, select the "Not Assigned" from drop-down list. On the secondary element, this field is read-only. If the Local-only DN box is checked, this field is disabled.	Not Assigned
First RAD	Enter the directory number of the RAD containing the first message to be given to callers when members of the hunt group are busy, in Do Not Disturb or when they fail to answer the call. A timer, defined in the Class of Service Options form, determines how long the caller listens to ringback while waiting for the first message.	Blank
Second RAD	Enter the directory number of the RAD containing the second message to be given to callers. Timers, defined in the Class of Service Options form, determine the interval between messages.	Blank
NIGHT Answer RAD	Enter the directory number of the RAD containing the message given to callers if either the hunt group, or all members of the hunt group, are in do not disturb mode.	Blank
Hunt Group Priority	Enter the priority number of the Incoming calls (1 to 64, with 1 being the highest and 64 being the lowest). For calls with priority levels 1 through 63, the priority level of the first group reached by a caller determines the call's priority through all phases of call handling and rerouting. Calls with a priority level of 64 inherit the priority level of the next group into which they overflow. If an agent is in more than one ACD hunt group, the priority of the hunt group determines the order in which his calls are routed. A hunt group programmed with a blank priority field will be assigned a priority of 64 upon commit.	Blank
Hunt Group Type	Group types are "Voice", "RAD", "Phantom", "VoiceMail", "HCI Reroute", "Recorder" "Emergency", or "NameTag". Voice is used for groups of people. RAD is used for groups of Recorded Announcement Devices. Phantom is used to serially chain phantom groups in front of MCD voice groups and to allow phantom groups to work with MCD call overflow. VoiceMail is used to associate the voice mail port with the hunt group pilot number when setting callback messages. HCI Reroute allows external applications to tell the system how to route calls. Recorder is used for groups of devices using the Record-A-Call feature. Emergency identifies the group as an Emergency Call Notification hunt group. NameTag identifies the group as using destination-based name tags for display on the ringing sets (see Destination-based Call Display for information). Note: You cannot change the Hunt Group Type if the group contains members. To make the change, first delete the members.	Voice
Phase Timer Ring	Enter the maximum required delay for the successive seizures of recorded announcement devices for a group is programmed as the RAD Phase Timer. If no delay is required, then 0 is programmed.	Blank
Hunt Group Members
Member Index	System-generated, protected field. Indicates the number of the member within the group. A station may appear in more than one group.
Number	Enter the directory numbers belonging to the hunt group. Up to 64 Directory Numbers can belong to a hunt group. If the Hunt Group Type is Emergency, you can enter Directory Numbers for up to 32 digital display sets. You can enter up to 8 directory numbers for ONS CLASS sets. The total of 32 sets for Emergency Call Notification does not include Directory Numbers for Attendant Consoles, which are programmed using the Emergency Call Notification parameters in the Class of Service Options form. See Hunt Group Description for a list of phones that can be members of an Emergency Hunt Group. Hot Desk user DNs cannot be included in Emergency or Recorder Hunt Groups. Note: A Registration DN cannot be added to an Emergency or Recorder Hunt Group while a Hot Desk user is logged into the device. 5010 IP Phones and generic SIP IP phones cannot be included in Emergency Hunt Groups. Only existing directory numbers may be listed. A mix of standard telephones and multiline sets may appear in any hunt group. Multiline set prime or non-prime single line numbers, key system numbers, personal ring group numbers, and multicall numbers are allowed in hunt groups. Remote directory numbers and system speedcall numbers are allowed in Network Hunt Groups. Attendant console directory numbers and other pilot numbers are not allowed in hunt groups. Voice mails with COS option voice mail ports cannot be members of more than one hunt group. Note: A personal ring group pilot or member is only allowed to be programmed as a member of a hunt group if the hunt group type is Voice or NameTag.	Blank
Presence	Select whether the member is available (present) or unavailable (absent) to receive calls to its hunt group. Applies to members of Voice and Nametag type hunt groups only. See Group Presence for more information.	Present
Name	System-generated, protected field indicating the name corresponding to the directory number, as entered in the Telephone Directory form. If no name exists for the associated directory number the field is blank.
Home Element	System-generated, protected field that displays the name of the home (primary) element of the hunt group member.
Secondary Element	System-generated, protected field. If a hunt group member is resilient, this field displays the name of the member's secondary (backup) controller.