Call Hunting Best CIsco CCNA Training Center in Delhi

Network Bulls
www.networkbulls.com
Best Institute for CCNA CCNP CCSP CCIP CCIE Training in India
M-44, Old Dlf, Sector-14 Gurgaon, Haryana, India
Call: +91-9654672192

CUCM call-hunting implementation is composed of the following components:
■ Phone DNs or voice-mail ports are assigned to line groups.
■ Line groups are assigned to hunt lists. A hunt list can have one or more line groups.
Line group hunt options and distribution algorithms can be specified to define how call
hunting should be performed for the members of the line group.
■ Hunt lists are assigned to hunt pilots. A hunt list is an ordered list of one or more line
groups.
■ Hunt pilots are the numbers that will match on dialed digits to invoke the hunting
process. A hunt pilot can be called directly or a call may be forwarded to the hunt pilot
from an IP phone that received a call and is configured to forward calls to the hunt pilot
to provide call coverage.
While hunting, the forwarding configuration of line group members is not used. If the
hunting algorithm is ringing a phone and the call is not answered, the CFNA setting of that
phone is ignored, and the hunting algorithm goes on to the next line group member.
Figure 14-3 illustrates the call-hunting process and components. The hunt pilot in this
example has been configured as 1 800 555-0111. Calls are distributed among the four DNs
at the bottom of the figure.
Call Hunting 343
Figure 14-3 Call Hunting
In the following example, two line groups are configured:
■ Agents line group: Contains the DNs 2001 and 2002.
■ Operators line group: Contains the DNs 2101 and 2102.
The line groups are assigned to the hunt list HelpDesk:
■ The first line group is Agents.
■ The second line group is Operators.
A hunt pilot of HelpDesk with the pattern 2222 is configured to use hunt list HelpDesk for
call coverage.
IP IP IP IP
Line Group 1
1000 1001
Line Group 2
1003 1004
Hunt List
1 800 555-0111
Hunt Pilot
1st Choice 2nd Choice
344 Chapter 14: Call Coverage
Figure 14-4 and the list that follows illustrate the call-coverage components involved in
distributing a call from the hunt pilot.
Figure 14-4 Call-Hunting Process
1. A call is received for extension 2222. The CUCM digit analysis result matches the hunt
pilot number of 2222. The hunt pilot distributes the call to the hunt list HelpDesk.
2. The hunt list uses top-down processing of the line groups. The first line group of
Agents is processed.
3. The line group distributes the call to agent DNs. Assuming the top-down calldistribution
algorithm was selected, 2001 would ring, then 2002. The various calldistribution
algorithms are covered later in this chapter.
4. If no agent answers, the hunt list sends the call to the second line group, Operators.
5. The line group Operators distributes the call to the operator DNs.
Hunt pilots are dialable patterns in the call-routing database (similar to route patterns,
translation patterns, and DNs). The hunt pilot points to a hunt list. The hunt list points to
one or more line groups, which include DNs.
QuickTime™ and a
Graphics decompressor
are needed to see this picture. IP
Hunt List HelpDesk
Line Group Agents
2001
2002
Line Group Operators
2102
2101
User Dials 2222
1
HL distributes call
to LG.
2
If no agents answers,
HL sends call to
second LG.
4
IP
IP
IP
IP
LG distributes
call to agents.
3
LG distributes call
to operators.
5
Hunt Pilot
HelpDesk
2222
Call Hunting 345
Beginning with CUCM Release 4.1, calls can be redirected to a final destination when the
hunting fails. Hunting may fail for one of the following reasons:
■ All hunting options have been exhausted, and the call has not been answered.
■ The maximum hunt timer has expired (configured at the hunt list level).
This call redirection is configured in the Hunt Forward Settings section of the Hunt Pilot
Configuration page, and the destination for this redirect can be either of the following
options:
■ A specific destination configured globally at the hunt pilot.
■ A personal preference, configured at the DN of the originally called number when
hunting on behalf of that number fails. The personal preference is configured using the
CFNC settings at the phone line.
You can implement the personal preferences option by configuring a user’s phone so that
the Forward No Answer field redirects the call to a hunt pilot, to search for someone else
who can answer the call. If the call hunting fails, either because all the hunting options were
exhausted or because a timeout period expired, the call can be sent to a destination personalized
for the person who was originally called. For example, if the Forward No Coverage
field is set to voice mail, the call will be sent to that person’s voice-mail box when hunting
fails.
The following considerations apply to calls handled by hunt pilots:
■ Call Pickup and Group Call Pickup are not supported on calls distributed by a hunt
pilot. A member of the line group cannot pick up the hunt pilot call offered to another
member in the line group, even if they belong to the same call-pickup group.
■ The hunt pilot can distribute calls to any of its line group members, regardless of the
partition of the line group member. Class of service is not implemented in the callcoverage
paradigm.
A hunt list is a prioritized list of line groups used for call coverage. Hunt lists have the
following characteristics:
■ Multiple hunt pilots can point to the same hunt list.
■ Multiple hunt lists can contain the same line group.
■ A hunt list is a prioritized list of line groups; line groups are hunted in the order of their
configuration in the hunt list.
346 Chapter 14: Call Coverage
Line groups control the order in which a call is distributed, and they have the following
characteristics:
■ Line groups point to specific extensions, which are typically IP phone extensions or
voice-mail ports.
■ The same extension may be present in multiple line groups.
■ Line groups are configured with a global distribution algorithm that is used to select
the next line group member for hunting.
■ Line groups are configured with a hunt option that describes how hunting should be
continued after trying the first member of the line group. The hunt option is configured
per hunt failure event: No Answer, Busy, and Not Available.
■ The Ring No Answer Reversion (RNAR) timeout specifies how long the hunting
algorithm rings a member of the line group before it continues hunting according to the
line group No Answer hunt option setting.
Line group members are the endpoints accessed by line groups, and they can be of any of
the following types:
■ Any SCCP endpoints, such as Cisco Unified IP Phone models VG248 or ATA 188
■ SIP endpoints
■ Voice-mail ports
■ H.323 clients
■ Foreign Exchange Station (FXS) extensions attached to an Media Gateway Control
Protocol (MGCP) gateway
Computer telephony integration (CTI) ports and CTI route points cannot be added to a line
group. Therefore, calls cannot be distributed to endpoints controlled through CTI applications
such as Cisco Customer Response Solution (CRS), Cisco Unified IP Interactive Voice
Response (IVR), and so forth.
Call-Hunting Options and Distribution Algorithms
Various hunt options are available at the line group configuration level. The default works
for most implementations, but life is rife with options to accommodate the requirements of
various organizations and collaborative groups. The following hunt options are available:
■ 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.
Call Hunting 347
■ 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: Do not proceed to the next Line Group or next member.
The line group distribution algorithm specifies the order line in which group members
should be used during the hunting process. The available algorithms are as follows:
■ Top down: If you choose a top-down distribution algorithm, CUCM distributes the call
to idle or available members starting from the first idle or available member at the top
of the line group to the last idle or available member (bottom of the list). In Figure 14-5,
a top-down distribution algorithm would extend the next call to 1000, then to 1001,
then to 1002, then 1003, and back to 1000 depending on the line state of the destination
DN. An important distinction in this model is that every new call attempts to use
extension 1000, no matter how long the lines in the line group are idle. If extension
1000 is available every time there is a new call distributed, extension 1000 will receive
the call. The user at extension 1000 would be very busy in this model.
■ Circular: If you choose a circular distribution algorithm, CUCM distributes the call
to idle or available members starting from the first member of the line group (1000).
CUCM retains the most recently extended call target in memory and attempts to place
the second call to the second member of the line group (1001). The third call is distributed
to the third member of the line group (1002), and the fourth call is extended to the
fourth member of the line group (1003). The circular distribution algorithm might
appear to be the same as the top-down distribution algorithm, but it is much fairer
in its distribution of calls.
■ Longest idle time: If you choose a longest idle time distribution algorithm, CUCM
distributes the call to the member that has been idle for the longest amount of time.
Only members in the idle call state are considered by this distribution algorithm.
Available and busy call states do not receive calls. A phone in the available state is
servicing a call but can manage a second call. Figure 14-5 assumes that 1000 has
been idle for 10 minutes and 1003 has been idle for 5 minutes. A longest idle time
distribution mechanism extends the call to extension 1000.
■ Broadcast: If you choose a broadcast distribution algorithm, CUCM distributes the
call to all idle or available members of a line group simultaneously.
Distribution algorithms are configured once per line group in CUCM Administration.
348 Chapter 14: Call Coverage
Figure 14-5 Line Group Distribution Algorithms
Call-Hunting Flow
The call-hunting flow in CUCM is as follows:
1. A direct call is placed to the hunt pilot number, or a call is forwarded to the hunt pilot
number from a phone.
2. The hunt pilot starts the maximum hunt timer to monitor the overall hunting time. If
the timer expires, hunting stops, and final forwarding is performed. The hunt pilot is
logically associated with a hunt list.
3. The hunt list associated with the hunt pilot sends the call to the first line group
configured in the hunt list.
—The call is sent to the next line group member based on the distribution
algorithm configured at the line group. Each line group is attempted until
all resources are exhausted (or the maximum hunt timer expires).
4. If the call to the hunt pilot goes unanswered, hunt failure has occurred. Possible hunt
failure reasons include no one answered the phone or everyone is busy servicing other
customers.
Figure 14-6 illustrates the call-coverage distribution of a call destined to a hunt pilot of 7000.
Figure 14-7 illustrates the final forwarding options of the hunt pilot configuration.
If hunting stops (ring no answer or busy) and the hunt pilot is not configured for final
forwarding, the call fails and a reorder tone is played.
If a final forwarding number is specified at the hunt pilot, the call is routed to the number.
If Use Personal Preference is selected, the call is routed as configured for Call Forward No
Coverage at the phone line that invoked the call to the pilot number.
IP IP IP IP
1000 1001 1002 1003
Idle
10 min.
Available Idle
5 min.
Available, CUCM
Last Extended Call
Line Group 1
Call Hunting 349
Figure 14-6 Call-Hunting Flow
Figure 14-7 Call-Hunting Flow
Hunt Pilot
7000
Hunt List
First Line
Group
Second
Line Group
Direct Call to Hunt Pilot or
Call Forwarded from Phone
Call Sent to First Line Group of Hunt List
Call Sent to Next Member as per
Line Group Distribution Algorithm
If Hunt List maximum hunt
timer Expires, Stop
Hunting
No Answer (Based on
Line Group RNAR Timer)
Busy Not
Available
Stop Hunting
Go to Next Line Group
Try Next Member of This Line
Group; If None Left, Stop
Hunting
Try Next Member of This Line
Group; If None Left, Go to Next
Line Group; If No Line Group
Left, Stop Hunting
Check Line Group Hunt Option How to Continue
IP IP IP
IP
IP
Check Hunt Pilot
Final Forward
Configuration
Hunting Stopped
No Final
Forwarding
Call Failed
(Reorder)
Hunt Option: Stop Hunting
Hunt Exhaustion (No More
Line Groups or Line Group
Members)
Hunt List Maximum Hunt
Timer Expired Final
Forwarding
Number
Specified in
Hunt Pilot
Use
Personal
Preference
Route Call to
Number Specified
in Hunt Pilot
Route Call to
Number
Specified at
Phone Line
(Call Forward No
Coverage)
350 Chapter 14: Call Coverage
Call-Hunting Configuration
To access the line group, hunt list, and hunt pilot configuration windows in CUCM
Administration, choose Call Routing > Route/Hunt.
When configuring hunting, follow these steps:
Step 1 Create the line groups, add members, and configure the distribution
algorithm and hunt options.
Step 2 Create the hunt list and add the line groups.
Step 3 Create the hunt pilot, associate the hunt list with the hunt pilot, and
configure hunt forward settings.
Step 4 Configure personal preferences on phone lines in the event that hunting
ends with no coverage.
These steps are covered in more detail on the following pages.
The DNs that will become the members of the line group must already exist in the database
before you can complete this procedure. The following steps describe the creation of a line
group. The configuration of the line group is illustrated in Figure 14-8.
Step 1 Choose Call Routing > Route/Hunt > Line Group from CUCM
Administration.
Step 2 Click the Add New button.
Step 3 Enter a name in the Line Group Name field. The name can contain up to
50 alphanumeric characters and can contain any combination of spaces,
periods (.), hyphens (-), and underscore characters (_). Ensure that each
line group name is unique to the route plan. Use a naming nomenclature
that is brief and descriptive of the line group usage in the environment. It
is good practice to append _LG to the line group name so that it can be
easily identified.
Step 4 Configure the distribution algorithm, hunt options, and ring no answer
reversion (RNAR) timeout as desired. The RNAR parameter limits the
amount of time (in seconds) that each DN in the line group rings before
CUCM reports a No Answer condition.
Step 5 Add members to the line group. To locate a DN, choose a route partition
from the Partition drop-down list, enter a search string in the Directory
Number Contains field, and click Find. To find all DNs that belong to a
Call Hunting 351
partition, leave the Directory Number Contains field blank and click
Find. A list of matching DNs is displayed in the Available DN/Route
Partition pane.
Step 6 In the Available DN/Route Partition pane, select a DN to add and click
Add to Line Group to move it to the Selected DN/Route Partition pane.
Repeat this step for each member that you want to add to this line group.
Step 7 In the Selected DN/Route Partition pane, choose the order in which the
new DNs will be accessed in this line group. To change the order, click a
DN and use the up and down arrows to the right of the pane.
Step 8 Click Save to add the new DNs and to update the DN order for this line
group.
Figure 14-8 Line Group Configuration
To add a hunt list, follow these steps:
Step 1 Choose Call Routing > Route/Hunt > Hunt List.
Step 2 Click the Add New button.
352 Chapter 14: Call Coverage
Step 3 In the Name field, enter a descriptive name for the hunt list functionality
and append _HL to indicate that the item is a hunt list. The name can
include up to 50 alphanumeric characters and can contain any
combination of spaces, periods (.), hyphens (-), and underscore
characters (_). Each hunt list name must be unique.
Step 4 Choose a CUCM group from the drop-down list.
Step 5 Click the Save button. The Hunt List Configuration window will display
the newly added hunt list.
Step 6 Add at least one line group to the new hunt list. To add a line group, click
Add Line Group. The Hunt List Detail Configuration window will open.
Step 7 From the Line Group drop-down list, choose a line group to add to the
hunt list.
To add the line group, click Save. The popup window is shown stating that for the
changes to take effect, you must reset the hunt list. Click OK to confirm the
message.
The line group name is displayed in the Selected Group list on the right side of the
window.
Step 8 To add more line groups to this list, click Add Line Group and repeat the
preceding two steps.
Step 9 When you finish adding line groups to the hunt list, click Save.
Step 10 A popup window will launch. Click OK to reset the hunt list.
CUCM accesses line groups in the order in which they are shown in the hunt list. The access
order of line groups is changed by selecting a line group from the Selected Groups pane and
clicking the up or down arrow on the right side of the pane to move the line group up or
down in the list. Figure 14-9 illustrates the configuration order of the hunt list configuration.
Follow these steps to create a hunt pilot:
Step 1 Choose Call Routing > Route/Hunt > Hunt Pilot from the menu.
Step 2 Click the Add New button.
Step 3 Enter the hunt pilot number in the Hunt Pilot field.
Step 4 Assign the hunt pilot to a hunt list using the Hunt List drop-down list.
Step 5 Scroll down to the bottom of the page to configure final forwarding
settings and the maximum hunt timer.
Step 6 Click the Save button.
Call Hunting 353
Figure 14-9 Hunt List Configuration
The hunt pilot configuration is illustrated in Figure 14-10. The Hunt Forward Settings pane
of the Hunt Pilot Configuration window specifies the final forwarding settings and
maximum timer values, as described in Table 14-1.
Figure 14-10 Hunt Pilot Configuration
354 Chapter 14: Call Coverage
Table 14-1 Hunt Forward Settings
Setting Description
Forward Hunt No
Answer
When the call distributed through the hunt list is not answered within a
specific period of time, this field specifies the destination to which to forward
the call. Choose from these options:
Use Personal Preferences: Enables the CFNC settings for the original called
number that forwarded the call to this hunt pilot.
The CFNC setting specifies a call-forwarding reason that you administer in
the Directory Number Configuration window.
Calls are diverted based on the value in the Coverage/Destination field of
the DN when a call to the DN first diverts to coverage, and coverage either
exhausts or times out, and the associated hunt pilot for coverage specifies
Use Personal Preferences for its final forwarding.
When the Use Personal Preferences check box is checked, CUCM ignores the
settings in the Destination and Calling Search Space fields.
Destination: This setting indicates the DN to which calls are forwarded.
Calling Search Space: This setting applies to all devices that are using this
DN.
Forward Hunt Busy When the call distributed through the hunt list encounters only busy lines for a
specific period of time, this field specifies the destination to which to forward
the call. Choose from these options:
Use Personal Preferences: Use this check box to enable the CFNC settings
for the original called number that forwarded the call to this hunt pilot.
When this check box is checked, CUCM ignores the settings in the
Destination and Calling Search Space fields.
Destination: This setting indicates the DN to which calls are forwarded.
Calling Search Space: This setting applies to all devices that are using this
DN.
Maximum Hunt
Timer
Specifies the maximum time for hunting (in seconds).
Call Hunting 355
The Directory Number Configuration window provides configuration options for internal
and external forwarding based on whether a call is CFA or CFNA, as specified in
Table 14-2.
Table 14-2 Hunt Forward Settings
Field Description
Forward All Specifies the forwarding treatment for calls to this DN if the DN is set to
forward all calls.
Voice Mail: Check this check box to use settings in the Voice Mail Profile
Configuration window.
When this check box is checked, CUCM ignores the settings in the
Destination and Calling Search Space fields.
Destination: This setting indicates the DN to which all calls are forwarded.
Use any dialable phone number, including an outside destination.
Calling Search Space: This setting applies to all devices that are using this
DN.
Forward Busy
Internal
Forward Busy
External
When the call distributed through the hunt list encounters only busy lines for a
specific period of time, this field specifies the destination to which to forward
the call. Choose from these options:
Use Personal Preferences: Use this check box to enable the CFNC settings
for the original called number that forwarded the call to this hunt pilot.
When this check box is checked, CUCM ignores the settings in the
Destination and Calling Search Space fields.
Destination: This setting indicates the DN to which calls are forwarded.
Calling Search Space: This setting applies to all devices that are using this
DN.
continues
356 Chapter 14: Call Coverage
The following five examples explore the related call-forwarding options used at the Cisco
IP Phone and the hunt pilot configuration. In Example 14-1, User A at DN 3000 has the DN
configuration illustrated in Figure 14-11.
Example 14-1 Call Forwarding Without Forward No Coverage Settings
Figure 14-11 shows the following configuration:
■ CFB: Call Forward Busy has two settings: Forward Busy Internal and Forward Busy
External. Both forwarding options are set to 3001. This setting forwards both internal
and external (PSTN) calls to 3001 when 3000 is busy. 3001 is probably the second line
of the phone, but this cannot be determined from Figure 14-11 alone.
■ CFNA: Call Forward No Answer has two settings as well: Forward No Answer
Internal and Forward No Answer External. The CFNA setting in Figure 14-11 forwards
internal calls to 3001, and external calls to 303 555-0111 when 3000 does not answer.
■ CFNC: Call Forward No Coverage does not have a configuration. Any calls that are
sent back to this phone from the hunt pilot for personal treatment will result in a reorder
tone.
Forward No Answer
Internal
Forward No Answer
External
Specifies the forwarding treatment for internal or external calls to this DN if
the DN does not answer.
Voice Mail: Check this check box to use settings in the Voice Mail Profile
Configuration window.
When this check box is checked, CUCM ignores the settings in the
Destination and Calling Search Space fields.
Destination: This setting indicates the DN to which an internal call is
forwarded when the call is not answered. Use any dialable phone number,
including an outside destination.
Calling Search Space: This setting applies to all devices that are using this DN.
Forward No
Coverage Internal
Forward No
Coverage External
This setting applies only if you configure one of the other forwarding fields
(CFA, CFB, or CFNA) with a hunt pilot number in the Destination DN field.
For the hunt pilot settings, you must also configure the Forward Hunt No
Answer or Forward Hunt Busy fields and check the Use Personal Preferences
check box under the Hunt Forward Settings section in the Hunt Pilot
Configuration window; otherwise, the Forward No Coverage configuration in
the Directory Number Configuration window has no effect.
Table 14-2 Hunt Forward Settings (Continued)
Field Description
Call Hunting 357
Figure 14-11 Call Hunting: Example 14-1
The following examples will discuss scenarios where the Hunt Pilot final forwarding rules
are used. Example 14-2 is a scenario where no final forwarding rules were configured.
Example 14-2 Forward No Coverage Examples
User A at DN 3000 has the configuration shown in Figure 14-12 in the Directory Number
Configuration window:
■ CFB: When busy, incoming internal calls are forwarded to 3001, and external calls are
forwarded to hunt pilot 7000.
■ CFNA: When there is no answer, incoming internal calls are forwarded to 3001,
whereas external calls are forwarded to hunt pilot 7000.
Hunt pilot 7000 is associated with hunt list abc and has four hunt parties equally distributed
over Line Group 1 and Line Group 2. Hunt pilot 7000 has no final forwarding fields
provisioned (default).
Question: What behavior results when an internal caller calls 3000 and user 3000 is busy?
Answer: The call forwards to line 3001.
Question: What behavior results when an external caller calls 3000 and user 3000 does not
answer?
Answer: The call forwards to hunt pilot 7000, which will cause hunting to lines 3001, 3002,
4001, and 4002. If one of the hunt parties answers, the caller is connected to that party. If
no hunt party answers, then, regardless of the reason, the caller receives a reorder tone (or
an equivalent annunciator announcement).
358 Chapter 14: Call Coverage
Figure 14-12 Call Hunting: Example 14-2
Example 14-3 Call Coverage: Forward Hunt No Answer
In call-hunting Example 14-3 in Figure 14-13, hunt pilot 7000 has the Forward Hunt No
Answer field set to 3002, but all Forward Hunt Busy fields are empty.
Figure 14-13 Call Hunting: Example 14-3
Line Group 1
3001
3002
Hunt List abc
Hunt Pilot 7000
Hunt List abc
Line Group 2
4001
4002
Forward Hunt Busy
Forward Hunt No Answer
UPP Dest.
UPP = Use Personal Preferences
Line Group 1
3001
3002
Hunt List abc
Hunt Pilot 7000
Hunt List abc
Line Group 2
4001
4002
Forward Hunt Busy
Forward Hunt No Answer
Dest.
3002
UPP
UPP = Use Personal Preferences
Call Hunting 359
If an external caller calls 3000 and user 3000 does not answer, the call forwards to hunt pilot
7000, which causes hunting to lines 3001, 3002, 4001, and 4002. If one of the hunt parties
answers, the caller is connected to that party.
If all hunt parties are busy, the caller receives a reorder tone. The reorder tone was sent
because of the missing Forward Hunt Busy configuration in the hunt pilot.
If at least one hunt party is alerted (phone rings) but does not pick up, the call forwards to
3002 because 3002 is the value configured for the Forward Hunt No Answer field.
Example 14-4 illustrates a scenario where user personal preferences are used for the final
forwarding for forward hunt busy. The forward hunt no answer calls to 3002.
Example 14-4 Call Coverage: Forward Hunt Busy
Figure 14-14 is different from Figure 14-13 because Forward Hunt Busy is configured at
the hunt pilot level. The DN configuration also differs from previous examples because the
DN has two Call Forward No Coverage numbers configured.
Figure 14-14 Call Hunting: Example 14-4
When an external caller calls 3000 and user 3000 does not answer, the call forwards to hunt
pilot 7000, which hunts to lines 3001, 3002, 4001, and 4002.
If one of the hunt parties answers, the caller is connected to that party. If at least one party
is alerted, but hunting exhausts the hunt list, the call is forwarded to 3002.
Line Group 1
3001
3002
Hunt List abc
Hunt Pilot 7000
Hunt List abc
Line Group 2
4001
4002
Forward Hunt Busy
Forward Hunt No Answer
Dest.
3002
UPP
UPP = Use Personal Preferences
360 Chapter 14: Call Coverage
If all hunt parties are busy, the call is forwarded as configured by the DN that forwarded the
call to the hunt pilot. The DN’s Forward No Coverage External setting determines what
happens to the call if the hunt pilot has Use Personal Preferences configured. In this case,
the call will forward to 303 555-0111.
Example 14-5 illustrates a situation in which the Forward No Coverage External has not
been configured. This missing configuration will cause any external calls forwarded to Hunt
Pilots to result in reorder tone.
Example 14-5 Call Coverage: Forward No Coverage External Missing
Figure 14-15 has a similar configuration to Figure 14-14, but the DN does not have a
Forward No Coverage External provisioned.
Figure 14-15 Call Hunting: Example 14-5
NOTE If the hunt pilot is configured to use personal preferences, the corresponding
Forward No Coverage field should be set at the phone forwarding the call to the hunt
pilot. A call forwarded from a phone to the hunt pilot leveraging personal preferences
with no Forward No Coverage setting will result in a reorder tone. This is similar to the
behavior when final forwarding settings are missing at the hunt pilot.
Line Group 1
3001
3002
Hunt List abc
Hunt Pilot 7000
Hunt-List abc
Line Group 2
4001
4002
Forward Hunt Busy
Forward Hunt No Answer
Dest.
3002
UPP
UPP = Use Personal Preferences
Chapter Summary 361
The RNAR timer for a line group determines how long hunting will ring a hunt party before
moving to the next party in its list (assuming that the customer did not select the broadcast
algorithm). This timer has a default value of 10 seconds.
In Figure 14-15, there are four hunt parties. How long will it take before hunting exhausts?
It will take 40 seconds before hunting exhausts (10 seconds RNAR default × 4 hunt
members).
Assume that the maximum hunt timer for hunt pilot 7000 is set to 25 seconds. The call must
be answered within this hunt timer. In this example, the maximum hunt timer is 2.5 times
the RNAR timer, which is 10 seconds.
If a user calls hunt pilot 7000, the call attempts to hunt for the four parties. If all the phones
ring but no one picks up within 25 seconds, hunting terminates and the cause is treated as
no answer. Hunting terminates after the third member has been alerted for 5 seconds (10
seconds RNAR on each of the first two members leaves 5 seconds before expiration of the
25 seconds maximum hunt time configured at the hunt pilot). The call forwards to 3002
because hunting failed with a No Answer condition.