# Configuring Hunt, Page, Pickup, and Ring Groups
(Mitel Integrated Configuration Wizard)

Hunt Groups, Page Groups, Call Pickup Groups and Ring Groups all present calls to multiple devices to help ensure they're answered. Use this page to create the groups and the next page to then assign them members.

You can create groups by entering the required data manually or by importing it. Most of the configuration data, such as the hunting method (Terminal or Circular) for hunt groups and the ring type (All or Cascade) for ring groups is defaulted (see below) and not displayed. This 'hidden' data, if present in the imported CSV file, is preserved and gets used when the configuration is applied to MiVoice Business.

The number of groups you can create varies by platform type:

Group Type | Platform Type
MiVoice Business for Industry Standard Server | All Others
Hunt | 2000 with Extended Hunt Group disabled or 64 with option enabled. | 176 with Extended Hunt Group option disabled or 16 with option enabled.
Page | 64* | 16*
Call Pickup | 800 | 200
Ring | 1000 | 255

* Expandable to 400 groups on all controllers by flexing system dimensions.

TIP: You can copy data from an Excel spreadsheet into this page.

To configure groups:

1. Enter the number of groups you want to create, and then click Add.

2. Type a Name for each of the groups for identification purposes.

3. For hunt groups, select a Group Type.
   Options are Voice for regular hunt groups and Emergency for hunt groups that handle emergency calls.

4. (Optional) Select a Secondary MiVoice Business for each group that requires service resiliency
   Resilient networks are made up of network elements that provide reliable fail-over mechanisms-either within the device or through working in conjunction with other network elements in order to ensure that all network devices can be used simultaneously. In this way the failure of one device will not bring down the entire network, thereby eliminating single points of failure on the network. A truly resilient network will provide the maximum amount of network uptime without requiring an entire duplicate network..
   This option is only available when provisioning a cluster
   Refers to a grouping of systems (for example, a cluster MiVoice Business systems) that share common dialing plans, or common directory information, such as Remote Directory Numbers with Telephone Directory..

5. Click Next to assign group members.

### Configuration Defaults

Click the following links for a summary of defaults used when creating groups in MiCW:

Hunt Group Data

Field Name | Allow Edit? | Default Value
Hunt Group Number | Yes | <blank>
Mode (Circular or Terminal) | No | Circular Note: As no member ordering is offered, Administrators will need to manually set this to Terminal mode if desired, at which time they can set the order of the group members.
Hunt Group Name | Yes | <blank>
First RAD | No | <blank>
Second RAD | No | <blank>
Night Answer RAD | No | <blank>
Hunt Group Priority (0-64) | No | 64
First Threshold/Second Threshold | No | <blank>
First Threshold/Second Threshold | No | <blank>
Alert DN Device | No | <blank>
Hunt Group Type (Voice, RAD, Phantom, Voicemail, HCIReroute, Recorder, Emergency, Nametag) | Yes | Voice <selections limited to ‘Voice’ and ‘Emergency’>
Phase Timer Ring | No | <blank>
Class of Service – Day Class of Service – Night 1 Class of Service – Night 2 | No | 25 with the following options set to "Yes": SMDR External Public Network Access via DPNSS Public Network To Public Network Connection Allowed
Home Element | No | <current node> [system-generated]
Secondary Element | Yes (in Modify Cluster only) | <blank>
Service ID GUID | No | <blank> [system-generated]
Local-only DN | No | <blank>

Page Group Data

Field Name | Allow Edit? | Default Value
Page Group | Yes | <blank>
Page Group Name | Yes (saved in Telephone Directory) | <blank>
Home Element | No | <current node> [system-generated]
Secondary Element | Yes (in Modify Cluster only) | <blank>
Service ID GUID | No | <current node> [system-generated]
Local-Only DN | No | False

Call Pickup Group Data

Field Name | Allow Edit? | Default Value
Group GUID | No | <blank> [system-generated]
Pickup Group Number | Yes | <blank>
Auto-Pickup (No, Yes) | No | No
Comment (displayed as Name) | No | <blank>
Cluster Enabled (No, Yes) | No | Yes
NE GUID list | No | <blank>
NE Names list | No | <blank>

Ring Group Data

Field Name | Allow Edit? | Default Value
Ring Group | Yes | <blank>
Ring Group Name | Yes (saved in Telephone Directory) | <blank>
Ring Group Mode (Ring All, Cascade Ring) | No | Ring All Note: As no member ordering is offered, Administrators will need to manually set this to Cascade Ring if desired, at which time they can set the order of the group members.
Call Queued Timer (5 – 300) | No | 20
Call Ringing Timer (5 – 300) | No | 20
Cascade Ring Timer (5 – 125) | No | 20
Overflow Point | No | <blank>
Class of Service – Day Class of Service – Night 1 Class of Service – Night 2 | No | 26 with the following options set to "Yes": SMDR External Public Network Access via DPNSS Public Network To Public Network Connection Allowed
Home Element | No | <current node> [system-generated]
Secondary Element | Yes (in Modify Cluster only) | <blank>
Service ID GUID | No | <blank> [system-generated]
Local-Only DN | No | False