# 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:

- Program Hunt Groups

- Program Networked Hunt Groups

- ACD Programming

- Program RAD Greetings

- Program Speech Server/Messaging Server

- Program Voice Mail - Digital E&M Interface

- Program Voice Mail - ONS Interface

## 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.

- A Multi-Device
  This Service Level indicates that the directory number (DN) is assigned to a user that has only basic telephony functionality (e.g., emergency or attendant calls) until programmed as a member of a Multi-Device user group or suite. The DN does not use an IP User License. However, the group or suite has a Multi-device Users or Multi-device Suites license which one person can use at a time in order to receive full telephony service. DN can be programmed as a hunt group member, provided that the DN is the prime member of a Multi-device User 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. | Not selected
Hunt Group Mode | Select the mode of hunting: Terminal - The search for an idle station begins at the first station programmed in the Hunt Group. Circular - The search for an idle station begins at the station after the last one to receive a call. | Circular
Hunt Group Name | Enter a suitable label for the corresponding hunt group The label may be up to 20 alphanumeric characters in length. If the label is a system username, or an alpha tagging name, the last name must precede the first name, and a comma must separate the two (Lastname,Firstname). Do not add a space before or after the comma. A username label can have up to 21 characters, including the comma. | Blank
Class of Service - Day | Select the COS to use when the system is in Day Service mode. If no Day COS is entered, the Hunt Group uses the one assigned to the first member in the group NOTES For Network Hunt Groups, this field must be programmed before you add remote members to the group. You must program this field before you can enable a hunt group with resiliency. | Blank
Class of Service - Night1 | Select the COS to use when the system is in Night1 Service mode. If no Night1 COS is entered, the Hunt Group uses the one assigned to the first member in the group. NOTES For Network Hunt Groups, this field must be programmed before you add remote members to the group. You must program this field before you can enable a hunt group with resiliency. | Blank
Class of Service - Night2 | Select the COS to use when the system is in Night2 Service mode. If no Night2 COS is entered, the Hunt Group uses the one assigned to the first member in the group NOTES For Network Hunt Groups, this field must be programmed before you add remote members to the group. You must program this field before you can enable a hunt group with resiliency. | Blank
Zone ID | Assign a Network Zone ID (1-999) for Hunt Groups in time zones different from their host controller. The system uses this assign zone ID to determine the appropriate time zone offset when applying a Business Schedule for Call Rerouting Always. With no zone ID assigned to the Hunt Group, the system applies the business schedule using the zone ID (and related time zone) assigned to the host MiVoice Business. | Blank
Home Element | Displays the name of the primary element for the hunt group. | Blank
Secondary Element | Allows you to enable and disable resiliency for the hunt group. You can only enable resiliency if the Hunt Group Type field is set to "Voice," "VoiceMail", "Recorder" or NameTag hunt group. 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 MiVoice Business Resiliency Guide 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). This field sets the priority levels for all incoming calls. Installers can either assign a priority level, or leave the priority level blank and leave the system to default the priority level to 64. Calls inherit the priority level of the hunt group to which they are directed. For example, if an incoming call is directed to a hunt group which is assigned priority level 9, the call will retain priority 9 throughout the life of the call. | Blank
Hunt Group Type | Select a hunt group type. The options are as follows (see Hunt Group Members - Number field below for device/DN types supported by each group): Voice is used for groups of people. RAD is used for groups of Recorded Announcement Devices. Phantom is used to serially chain phantom groups ahead of MiVoice Business voice groups and to allow phantom groups to work with MiVoice Business call overflow. VoiceMail is used to associate the voice mail port with the hunt group pilot number when setting callback messages. Also used to enable auto camp-on of calls to auto attendant and IVR Interactive Voice Response is an automated call handling system in which the caller interacts with a computer device which can interpret and react to voice or touch tone commands. The interaction can be through the use of a touch tone telephone or through speech recognition. This telephone-based application prompts the inbound caller for information using a recorded or synthesised human voice. Most IVR systems do not allow the caller to respond by voice, but require user input through touch-tone response. ports in the hunt group. IMPORTANT: Other hunt group types do NOT provide auto camp-on. Without it, high traffic sites may experience system slowdowns if calls are rejected by call control due to excessive processing. 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). NOTES You cannot change to or from an Emergency Hunt Group to another type of hunt group. To make the change, delete the members, followed by the group, then recreate it. For other hunt group types you only need to delete the members before you can change the type. Sets with Line Interface Modules configured should NOT be configured as members of an Emergency Hunt Group. 69xx devices configured with Mobile Line keys CANNOT be members of an Emergency Hunt Group. | 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 a total of 32 DNs of which 8 can be ONS CLASS only, SIP sets only, or a combination of both. The others can be display-equipped IP sets. The total of 32 sets for 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. Personal ring group and Multi-device user group DNs cannot be included in Emergency Hunt Groups. NOTE: A Registration DN The directory number (DN) of a phone that is provisioned for Hot Desk use. Not to be confused with the Login DN which the user enters to log in to the hot desk phone. cannot be added to an Emergency or Recorder Hunt Group while a Hot Desk user is logged into the device. Only existing directory numbers may be listed. A mix of standard telephones and multiline sets may appear in any hunt group. Except where noted above, Multiline set prime or non-prime single line numbers; key system numbers; personal ring group and multi-device 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 or multi-device user 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. |