1. D, 2. C, 3. E, 4. A, 5. B
By selecting one of the hunt group members as an "always-route member," the Cisco CallManager will route the call to the destination when the queue is full or the hold time has been reached. This destination is typically a voice mail or auto-attendant system.
C and E
The Cisco Telephony Call Dispatcher (TCD) must be active to dispatch calls to the active Attendant Console clients. The CTIManager must be active to integrate the CTI-based Attendant Console software with the CallManager system.
Only the longest-idle distribution algorithm can be configured from the Pilot Point Configuration window. All others must be configured either from the Hunt Group Configuration window or from the Attendant Console Configuration Tool.
A CallManager cluster can have a maximum of 32 hunt groups.
When you have configured Broadcast Hunting (using the Attendant Console Configuration Tool), the incoming calls to the pilot point will be immediately placed into a queue that the attendants can answer, using the Attendant Console client, as they become available.
The ac user must be created and associated with all Cisco IP Phones used by the Attendant Console clients. As a good security practice, this username and password should be changed using the Attendant Console Configuration Tool.
Accessing the Attendant Console Configuration Tool is a strange task indeed. You must first dig through the hard drive to find the batch file and execute it for the Java-based utility to appear.
An operator can revert a parked call in many ways. The easiest is to right-click on the parked call in the Attendant Console software and choose Revert Park.
Attendant Console users are not added through the user menu; rather, they are added through the Service > Cisco CM Attendant Console > Cisco CM Attendant Console User window. Users added through the normal User menu will not be available to select as Attendant Console users.
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