Discovery Lab 11

Discovery 11: Configure Hunt Groups

Hunt groups allow incoming calls to a specific number (pilot number) to be
directed to a defined group of extension numbers. In this discovery, you will
configure hunt groups.

The figure lists the steps that are required to configure a hunt group in Cisco
Unified Communications Manager. You will configure these steps in this
discovery.

Discovery Task 1: Add a Line Group

Begin the configuration of hunt groups by creating a line group. The line group
will contain the directory numbers that will be used within the hunt group. The
line group includes the distribution algorithm and the various hunt options.
Navigate to Call Routing > Route/Hunt > Line Group and click Add New.

In the window that appears, enter the following values:

Line Group Name: LG-Sales

RNA Revision Timeout: 6

Distribution Algorithm: Longest Idle Time

Configure the No Answer, Busy, and Not Available hunt options to Try next member,
then, try next group in Hunt List.

From the Available DN/Route Partition list, choose the directory

numbers 11001 and 11002 (use the shift or control key to choose multiple directory
numbers). Click Add to Line Group. The directory numbers that were chosen will
now be displayed in the Selected DN/Route Partition field. You can use the up and
down arrows to the right of this field to change the order. 11001 should be listed on
top of 11002.

Click Save to save the changes.

Discovery Reference

RNA Reversion Timeout

Optionally, change the RNA Reversion Timeout. The RNA Reversion Timeout
defines the time in seconds after which Cisco Unified Communications Manager
will distribute a call to the next available or idle member of this line group or to
the next line group if the call is not answered. If the first hunt option, Try next
member, is not answered, then the next group in the hunt list is chosen. The
RNA Reversion Timeout applies at the line-group level to all members.

Distribution Algorithm

The following options are available for the distribution algorithm:

Top Down: This distribution algorithm distributes a call to idle or available

members starting from the first idle or available member of a line group to
the last idle or available member.

Circular: This distribution algorithm distributes a call to idle or available

members starting from the (n + 1)th member of a line group, where the nth
member is the member to which Cisco Unified Communications Manager
most recently extended a call. If the nth member is the last member of a line
group, Cisco Unified Communications Manager distributes the call starting
from the top of the line group.

Longest Idle Time: This distribution algorithm distributes a call to idle

members of the line group starting from the member who has been idle for
the longest period to the member who has been idle for the shortest period.

Broadcast: Distributes a call to all idle or available members of a line group

simultaneously.

Hunt Options

After a line group member is tried and the response is no answer, busy, or not
available, hunting continues according to the configured line group hunt option.
That action is configured per event (no answer, busy, and not available) as
follows:
 Try Next Member, Then, Try Next Group in Hunt List (Default): Sends the call
to the next idle or available member of this line group. If no more members
are available in this line group, go to the next line group configured in the
hunt list. If no more line groups are available, hunting stops.

Try Next Member, but Do Not Go to Next Group: Sends the call to the next
idle or available member of this line group. If no more members are available
in this line group, hunting stops.

Skip Remaining Members, and Go Directly to Next Group: Sends the call to
the next line group. If no more line groups are available, hunting stops.

Stop Hunting: Stops the hunting process.

Discovery Task 2: Configure Hunt Lists

A hunt list comprises a collection of directory numbers as defined by line groups.

After Cisco Unified Communications Manager determines that a call will be
routed through a defined hunt list, it finds the first available device based on the
order of the line group or groups that are defined in a hunt list.

Navigate to Call Routing > Route/Hunt > Hunt List and click Add New.
In the Name field, enter HL-Sales and from the Cisco Unified Communications
Manager Group drop down list, choose Default.

Check the Enable this Hunt List check box and save the changes.

Click Add Line Group and from the Line Group drop down list, choose the previously
defined line group LG-Sales.

Click Save and OK.

Discovery Reference

A hunt list is a set of line groups that are arranged in a specific order. Each hunt
list should have at least one line group, and each line group should include at
least one directory number. However, a single-line group can appear in multiple
hunt lists. The hunt list is then associated with one or more hunt pilots.

Hunt lists determine the order in which the various line groups are accessed. The
order controls the progress of the search for available directory numbers for
incoming calls.

Discovery Task 3a: Set a Hunt Pilot

A hunt pilot comprises a string of digits and a set of associated digit

manipulations that route calls to a previously configured hunt list.
Navigate to Call Routing > Route/Hunt > Hunt Pilot and click Add New to add a new
hunt pilot.

In the window that appears, enter the following values for the hunt pilot:

Hunt Pilot: 11222

Route Partition: HQ_Internal_pt

Description: Hunt Pilot Sales

Hunt List: HL-Sales

Alerting Name: Sales Hotline

ASCII Alerting Name: Sales Hotline

Discovery Task 3b: Set Hunt Forwarding

If an incoming call to a hunt pilot cannot be answered, the administrator can

define Hunt Forward Settings. This situation may occur when all line group
members are busy or no member answers the incoming call.
In the Forward Hunt No Answer section, click the Use Forward Settings of Line
Group Member radio button.

Save the hunt pilot configuration.

From your Citrix Desktop CIPC phone, dial 11222 (pilot). Each HQ Phone should ring
for 6 seconds before the caller hears a reorder tone.

Go to Device > Phone and select HQ Phone 1.

Configure the Call Forward settings on the directory number 11001 only. Check
the Voice Mail checkbox for Forward No Answer Internal, Forward No Answer
External, Forward No Coverage Internal and Forward No Coverage External.

Forward the Call Forward No Coverage Internal and External to voicemail.

Set the No Answer Ring Duration to 10 seconds. Click Save and click Apply Config.

From the CIPC phone, dial the Hunt Pilot at 11222. Let the call ring. It rings busy
because janderson does not have a voice mailbox.

Discovery Reference
 You use the Hunt Forward Settings to configure forwarding of hunt pilot
numbers when a call cannot be answered or all members are busy. The Use
Personal Preferences check box allows you to use the personal CFNC feature in
the Directory Number Configuration window when an IP phone user has
forwarded all calls to a hunt pilot.

When the Use Personal Preferences check box is checked and a call is forwarded

to the hunt pilot, the Cisco Unified Communications Manager ignores any
numbers in the Destination field. When an extension is used where calls should
be forwarded (for example, another hunt pilot, voicemail, or operator number),
enter the number in the Destination field and define the CSS. This CSS will be
used if Forward Hunt No Answer or Forward Hunt Busy is configured with a
destination. When the Use Personal Preferences check box is checked, the CSS
of the CFNC in the directory number configuration window is used.

Note: After a hunt list is created, it will register with Cisco Unified Communications
Manager. If the administrator makes any changes to the hunt list, perform a reset.

Discovery Task 4: Set Call Queuing

This figure shows how to configure call queuing for hunt groups.
Navigate to Call Routing -> Route / Hunt -> Hunt Pilot. Click Find and select
the 11222 pilot that you just created and scroll down to the Queuing section.

Check the Queue Calls check box and notice that the Forward Hunt No Answer and
Forward Hunt Busy sections become grayed out.

Note: Forward Hunt No Answer or Forward Hunt Busy settings are designed to move
calls through the route list. Queuing, however, is used to hold callers in a route list.
Therefore, if queuing is enabled, both Forward Hunt No Answer and Forward Hunt
Busy are automatically disabled. Conversely, if Forward Hunt No Answer or Forward
Hunt Busy is enabled, queuing is automatically disabled.

Set the Network Hold MOH Source & Announcements to 1-SampleAudioSource.

Notice the other settings on the Queue but do not change them.

Save the hunt pilot configuration.

In Cisco Unified Serviceability, activate the Cisco IP Voice Media Streaming App
service.

Discovery Reference

When a hunt pilot has more calls that are distributed through the call
distribution feature than its hunt members can handle at any given time, call
queuing holds these calls in a queue until they can be answered.

Discover Lab Complete