If you have checked the Use Personal Preferences check box in the Hunt Forward Settings section of the Hunt Pilot Configuration window, CallManager will check the Call Forward No Coverage settings for the original called number that forwarded the call to the hunt pilot. If you have not defined a number for this setting, the caller will receive a reorder tone when CallManager attempts to forward the call.
Using the top-down distribution algorithm causes the Cisco CallManager to distribute the incoming call to the first member of the line group and work down if the parties are unavailable. If you were using the circular distribution algorithm, the call would have been distributed to party 4 because party 3 received the last call.
The maximum hunt timer always overrides the RNA reversion timeout configured on the line group. In this case, the call would only hunt through the first three members of the group before the call reached the maximum timer of 15 seconds.
A, B, and C
To configure a hunt group, you must first configure a line group, which groups member DNs together. Then, you must set up a hunt list, which orders one or more line groups together. Finally, you must configure a hunt pilot pointing to the hunt list.
Available lines are serving an active call but can accept a new call. Idle lines are those categorized as not serving any calls at this time.
The broadcast distribution algorithm rings all members of the line group at the same time. The first one to retrieve the incoming call will receive it.
The Stop Hunting selection causes the CallManager to use just the first member DN in the line group and stop if the member is unavailable.
By checking the Use Personal Preferences check box, CallManager ignores any call forward settings defined under the hunt pilot. Instead, it looks to the Call Forward No Coverage section of the original called party that triggered the call to the hunt group.
Hunt groups are configured from the bottom up, just like the CallManager route plan. You must first add member DNs to the CallManager configuration, then group them into a line group, followed by the hunt list and hunt pilot.
By default, CallManager matches the hunt pilot DN and hunts through the members listed in all line groups defined in the hunt list. This could take a considerable amount of time if there are many members or line groups configured.
Part I: Cisco CallManager Fundamentals
Introduction to Cisco Unified Communications and Cisco Unified CallManager
Cisco Unified CallManager Clustering and Deployment Options
Cisco Unified CallManager Installation and Upgrades
Part II: IPT Devices and Users
Cisco IP Phones and Other User Devices
Configuring Cisco Unified CallManager to Support IP Phones
Cisco IP Telephony Users
Cisco Bulk Administration Tool
Part III: IPT Network Integration and Route Plan
Cisco Catalyst Switches
Configuring Cisco Gateways and Trunks
Cisco Unified CallManager Route Plan Basics
Cisco Unified CallManager Advanced Route Plans
Configuring Hunt Groups and Call Coverage
Implementing Telephony Call Restrictions and Control
Implementing Multiple-Site Deployments
Part IV: VoIP Features
Configuring User Features, Part 1
Configuring User Features, Part 2
Configuring Cisco Unified CallManager Attendant Console
Configuring Cisco IP Manager Assistant
Part V: IPT Security
Securing the Windows Operating System
Securing Cisco Unified CallManager Administration
Preventing Toll Fraud
Hardening the IP Phone
Understanding Cryptographic Fundamentals
Understanding the Public Key Infrastructure
Understanding Cisco IP Telephony Authentication and Encryption Fundamentals
Configuring Cisco IP Telephony Authentication and Encryption
Part VI: IP Video
Introducing IP Video Telephony
Configuring Cisco VT Advantage
Part VII: IPT Management
Introducing Database Tools and Cisco Unified CallManager Serviceability
Configuring Alarms and Traces
Using Additional Management and Monitoring Tools
Part VIII: Appendix
Appendix A. Answers to Review Questions