Create a hunt group

What it is for

A hunt group distributes calls to a shared number across several lines. In the CUCM it consists of three objects: the Hunt Pilot (the dialled number), the Hunt List and at least one Line Group with its member lines.

EasyUC creates these objects in one operation via AXL. Since 4.8, a wizard with the two steps Configuration and Members guides you through the creation. You set forwarding on busy or no answer and the queue afterwards when editing the group.

The list shows every hunt group as a card with Hunt Pilot, alerting name, pickup group and the line groups including distribution and number of members.

Prerequisites

• Licence module cucm and an active CUCM connection.
• Permission View Hunt Groups Page (ROLE_APP_VIEW_HUNT_GROUP_PAGE) for the page, Create Hunt Groups (ROLE_APP_CREATE_HUNT_GROUP) for creating and Update Hunt Groups (ROLE_APP_UPDATE_HUNT_GROUP) for changes.
• A location with a number range. In the previous template model, additionally a hunt group template; with Template 2.0, an enabled Sammelgruppen (hunt groups) area at the location.
• A free number for the Hunt Pilot and the lines of the future members.
• For forwarding destinations, a CSS is stored at the location.

Step by step: Create a hunt group

1. Open Groups → Hunt Groups. The page is called Manage Hunt Groups.
2. Click Create. The wizard opens with the step 1 Configuration.
3. Select the Location. With Template 2.0, Package appears in addition; the field can stay empty.
4. In the previous template model, select the Template. With Template 2.0, the note "Template 2.0 – this location’s configuration is applied automatically." is shown there instead.
5. Under Group details, enter the Name and the Description. The name is prefilled as the alerting name and description of the Hunt Pilot as long as you do not enter your own values there.
6. Under Hunt Pilot, enter the hunt group number in Pattern or click Get Free phone number.
7. Check Alerting Name and Description of the Hunt Pilot.
8. Expand Check number usage if you want to see whether the number is already in use.
9. Under Pickup group, optionally select Use existing pickup group and an existing group, or Create new pickup group with the Pickup Group Template.
10. Click Continue to members. The button only becomes active when location, name, hunt pilot number and alerting name are set.
11. In the step 2 Members, set the RNA Reversion Timeout and the Distribute Algorithm of the line group.
12. On the left under Found Users, search by name or phone number and drag the cards to the right into Line Group Members. The order on the right is the order in the Line Group.
13. Click Create hunt group. EasyUC creates Line Group, Hunt List and Hunt Pilot in the CUCM.

Step by step: Set forwarding and queue

1. On the card of the hunt group, select Action → Update.
2. Adjust Name, Description, Alerting Name and the Pickup Group.
3. Under Forward Hunt No Answer, select one of the three options. For Forward Unanswered Calls to, enter the Destination and the Maximum Hunt Timer.
4. Select accordingly under Forward Hunt Busy and enter the Destination if required.
5. Enable Queue if callers are to wait. Select the Moh Audio Source and enter the limits.
6. For the three cases queue full, maximum wait time and no member, define whether EasyUC sets Disconnect Call or the call goes to a destination.
7. Click Save.

Fields and options

Check the result and troubleshoot

• The new hunt group appears as a card in the list. The figures All Calls, Calls Answered and Calls not Answered come from the CDRs.
• "Location, name, hunt pilot and alerting name are required.": One of the required fields in the first step is missing.
• "This feature is not configured or is disabled in Template 2.0 for the selected location. Please check the location configuration.": Enable the Sammelgruppen area in the template settings of the location.
• „Die Sammelgruppe konnte nicht angelegt werden. Bitte Eingaben und CUCM-Konfiguration prüfen.“ (the hunt group could not be created, check your input and the CUCM configuration): The CUCM has rejected the creation. The message Please check the following fields names the fields concerned.
• "There is no css in the location": Store a CSS at the location before you save a forwarding destination.
• With Logs on the page you see the log entries for hunt groups.