Guest

Cisco Unified Attendant Consoles

Installation and Administration Guide, Release 1.2(1)

  • Viewing Options

  • PDF (532.9 KB)
  • Feedback
Cisco CallManager Attendant Console Administration Guide, Release 1.2(1)

Table Of Contents

Cisco CallManager Attendant Console Administration Guide, Release 1.2(1)

Contents

Cisco CallManager Attendant Console Configuration Checklist

Before You Begin

Understanding How Dependency Records Work (Available with Cisco CallManager 3.3)

Configuring Cisco CallManager Attendant Console Users

Finding an Attendant Console User (Available with Cisco CallManager 3.3)

Adding an Attendant Console User

Viewing, Updating, and Deleting Attendant Console Users

Attendant Console User Configuration Settings

Understanding Pilot Points and Hunt Groups

Understanding Linked Hunt Groups

Understanding Circular Hunt Groups

Configuring Pilot Points

Finding a Pilot Point (Available with Cisco CallManager 3.3)

Adding a Pilot Point

Viewing, Updating, or Deleting a Pilot Point

Resetting a Pilot Point (Available with Cisco CallManager 3.3)

Pilot Point Configuration Settings

Configuring Hunt Groups

Adding Hunt Group Members

Configuring Linked Hunt Groups

Viewing, Updating, or Deleting Hunt Group Members

Hunt Group Configuration Settings

Configuring the ac User in the User Information Window

Associating Devices and Pilot Points with the ac User

Activating the Cisco Telephony Call Dispatcher Service

Activating the CTIManager Service

Understanding the Cisco CallManager Attendant Console Directory

Cisco CallManager Attendant Console Server Configuration

Viewing Cisco CallManager Attendant Console Performance Monitors

Cisco CallManager Attendant Console Requirements

Attendant Console Requirements

Cisco IP Phone and Voice Mail Requirements for Use with the Attendant Console

Downloading Cisco CallManager Attendant Console from CCO

Installing the Cisco CallManager Attendant Console on the User PC

Configuring Cisco CallManager Attendant Console Settings on the User PC

Configuring Cisco CallManager Attendant Console System Files

Configuring Circular Hunt Groups

Configuring Cisco CallManager Attendant Console to Access Voice Mail

Configuring Held Icon Timers

Obtaining Documentation

Cisco.com

Documentation CD-ROM

Ordering Documentation

Documentation Feedback

Obtaining Technical Assistance

Cisco.com

Technical Assistance Center

Cisco TAC Website

Cisco TAC Escalation Center

Obtaining Additional Publications and Information


Cisco CallManager Attendant Console Administration Guide, Release 1.2(1)



Note If you are running Cisco CallManager 3.2, Cisco WebAttendant displays in Cisco CallManager Administration instead of Cisco CM Attendant Console. If you are running Cisco CallManager 3.3, Cisco CM Attendant Console and cascading menus display in Cisco CallManager Administration.

Illustrations that show Cisco CallManager Administration support Cisco CallManager 3.2.


Cisco CallManager Attendant Console, a client-server application, allows you to set up Cisco IP Phones as attendant consoles. Employing a graphical user interface, the attendant console uses speed-dial buttons and quick directory access to look up phone numbers, monitor line status, and direct calls. A receptionist or administrative assistant can use the attendant console to handle calls for a department or company, or another employee can use it to manage his own telephone calls.

The attendant console installs on a PC with IP connectivity to the Cisco CallManager system. The attendant console works with a Cisco IP Phone that is registered to a Cisco CallManager system. Multiple attendant consoles can connect to a single Cisco CallManager system.

The application registers with and receives call-dispatching services from the Cisco Telephony Call Dispatcher (TCD) service on the Cisco CallManager.

Contents

This document contains the following topics:

Cisco CallManager Attendant Console Configuration Checklist

Before You Begin

Understanding How Dependency Records Work (Available with Cisco CallManager 3.3)

Configuring Cisco CallManager Attendant Console Users

Understanding Pilot Points and Hunt Groups

Configuring Pilot Points

Configuring Hunt Groups

Configuring the ac User in the User Information Window

Associating Devices and Pilot Points with the ac User

Activating the Cisco Telephony Call Dispatcher Service

Activating the CTIManager Service

Understanding the Cisco CallManager Attendant Console Directory

Cisco CallManager Attendant Console Server Configuration

Viewing Cisco CallManager Attendant Console Performance Monitors

Cisco CallManager Attendant Console Requirements

Cisco IP Phone and Voice Mail Requirements for Use with the Attendant Console

Downloading Cisco CallManager Attendant Console from CCO

Installing the Cisco CallManager Attendant Console on the User PC

Configuring Cisco CallManager Attendant Console Settings on the User PC

Configuring Cisco CallManager Attendant Console System Files

Cisco CallManager Attendant Console Configuration Checklist

Perform the steps in the following table to set up the attendant console:

Table 1 Attendant Console Configuration Checklist 

Configuration Steps
Related Procedures and Topics

Step 1 

Verify that the servers in the cluster run a compatible version of Cisco CallManager.

Before You Begin

Step 2 

Add attendant console users in Cisco CallManager Administration.

Configuring Cisco CallManager Attendant Console Users

Step 3 

Set up pilot points and hunt groups in Cisco CallManager Administration.

Understanding Pilot Points and Hunt Groups

Step 4 

Configure a user called "ac" in Cisco CallManager Administration and associate the attendant console phones and pilot points to the ac user.

Configuring the ac User in the User Information Window

Associating Devices and Pilot Points with the ac User

Step 5 

Make sure that the Cisco Telephony Call Dispatcher (TCD) service activates and runs on all servers that run the Cisco CallManager service.

Make sure that the CTIManager service runs on one server in the cluster.

Activating the Cisco Telephony Call Dispatcher Service


Activating the CTIManager Service

Step 6 

If you are running Cisco CallManager 3.3(3), install the Cisco IP Telephony Locale Installer on every server in the cluster. If you do not install this executable, the text in the attendant console GUI does not display entirely in the language that the attendant chose.

Cisco IP Telephony Locale Installer documentation

Step 7 

Make sure that each attendant Cisco IP Phone is set up correctly for use with attendant console.

Cisco IP Phone and Voice Mail Requirements for Use with the Attendant Console

Step 8 

Download the Cisco CallManager Attendant Console plugin from the web.

Downloading Cisco CallManager Attendant Console from CCO

Step 9 

Install and configure the attendant console on each attendant console user PC.

Installing the Cisco CallManager Attendant Console on the User PC

Configuring Cisco CallManager Attendant Console Settings on the User PC

Attendant Console Requirements

Step 10 

Configure Cisco CallManager Attendant Console system files.

Configuring Cisco CallManager Attendant Console System Files


Before You Begin

Before you configure and install Cisco CallManager Attendant Console, verify that the Cisco CallManager cluster that is associated with the attendant console runs a compatible version of Cisco CallManager. Refer to the Cisco CallManager Compatibility Matrix for more information. To obtain the document, click the following URL:

http://www.cisco.com/univercd/cc/td/doc/product/voice/c_callmg/ccmcomp.htm

For Cisco CallManager installation and upgrade procedures, click the following URL and navigate to the appropriate documentation:

http://www.cisco.com/univercd/cc/td/doc/product/voice/c_callmg/index.htm

When you download the executable from the web, you automatically replace the Cisco CallManager Attendant Console plugin in Cisco CallManager Administration with the plugin that is used for the Cisco CallManager Attendant Console. You also replace the existing Cisco TCD service with an updated version of the Cisco TCD service. You must download the executable on every server in the cluster.

Understanding How Dependency Records Work (Available with Cisco CallManager 3.3)

The Dependency Records Summary window displays information about directory numbers that use a pilot point or hunt group. To find attendant console user directory numbers for a specific pilot point or hunt group, you can click the Dependency Records link that is provided on Cisco CallManager Attendant Console User or the Pilot Point Configuration windows. To find out more information about the directory number or hunt group, click the directory number or hunt group, and the Dependency Records Details window displays.

For more information about Dependency Records, see the "Viewing, Updating, and Deleting Attendant Console Users" section or "Viewing, Updating, or Deleting a Pilot Point" section.

Configuring Cisco CallManager Attendant Console Users

Attendant console users comprise special user accounts that are created in the Cisco CallManager Attendant Console User Configuration window in Cisco CallManager Administration. Administrators can add or delete attendant console users and modify user IDs and password information from Cisco CallManager Administration.

Before a user can log in to an attendant console to answer and direct calls, you must add the user as an attendant console user and assign the user a password.


Note Be aware that attendant console user IDs and passwords are not the same as Directory users and passwords that are entered in the User area of Cisco CallManager Administration.


If a user cannot log in to the attendant console, make sure that Cisco CallManager and Cisco TCD are both running. Verify that the user has been added in the Cisco CallManager Attendant Console User Configuration area of Cisco CallManager Administration and that the correct user name and password are specified in the attendant console Settings dialog box.

This section covers the following procedures:

Finding an Attendant Console User (Available with Cisco CallManager 3.3)

Adding an Attendant Console User

Viewing, Updating, and Deleting Attendant Console Users

Finding an Attendant Console User (Available with Cisco CallManager 3.3)

This section describes how to find an attendant console user.

Procedure


Step 1 Choose Service > Cisco CM Attendant Console > Cisco CM Attendant Console User.

The Find and List window displays.

Step 2 From the drop-down list box, choose one of the search criteria.

Step 3 Specify the appropriate search text, if applicable, and click Find. You can also specify how many items per page to display.


Tip To find all attendant console users that are registered in the database, click Find without entering any search text.


A list of attendant console users displays by Name.


Adding an Attendant Console User

This section describes how to add an attendant console user. You must add users through the Cisco CallManager Attendant Console User Configuration window in Cisco CallManager Administration before they can log in to an attendant console.


Note Be aware that attendant console user IDs and passwords are not the same as Directory users and passwords that are entered in the User area of Cisco CallManager Administration.


Procedure


Step 1 Perform one of the following tasks, depending on the Cisco CallManager release that runs in the cluster.

For Cisco CallManager 3.2, choose Service > Cisco WebAttendant.

In the upper, right corner of the window, click the Cisco CallManager Attendant Console User Configuration link.

For Cisco CallManager 3.3, choose Service > Cisco CM Attendant Console > Cisco CM Attendant Console User.

In the upper, right corner of the window, click the Add a New Cisco CallManager Attendant Console User link.

Step 2 Enter the appropriate configuration settings as described in Table 2.

Step 3 Click Insert to add the new user. The Cisco CallManager Attendant Console User Configuration window refreshes, and the new User ID displays in the list on the left side of the window.

Step 4 To add additional users, repeat Step 2 and Step 3.


Viewing, Updating, and Deleting Attendant Console Users

This section describes how to view, update, or delete a Cisco attendant console user.

Using Dependency Records (Available with Cisco CallManager 3.3)

To find out which hunt groups are using the attendant console user, click the Dependency Records link from the Cisco CallManager Attendant Console User Configuration window. For more information about dependency records, see the "Understanding How Dependency Records Work (Available with Cisco CallManager 3.3)" section. If you try to delete an attendant console user that is in use, Cisco CallManager displays an error message. To delete an attendant console user that is currently in use, you must perform either or both of the following tasks:

Assign a different attendant console user to any hunt groups that are using the attendant console user that you want to delete. See the "Viewing, Updating, or Deleting Hunt Group Members" section.

Delete the hunt groups that are using the attendant console user. See the "Viewing, Updating, or Deleting Hunt Group Members" section.

Procedure


Step 1 Perform the following task, depending on the Cisco CallManager release that runs in the cluster.

For Cisco CallManager 3.2, choose Service > Cisco WebAttendant.

In the upper, right corner of the window, click the Cisco WebAttendant User Configuration link.

For Cisco CallManager 3.3, perform the procedure in "Finding a Pilot Point (Available with Cisco CallManager 3.3)" section.

Step 2 Click the name of the user that you want to modify or delete.

Step 3 Make the desired changes. See Table 2 for a description of Cisco CallManager Attendant Console user configuration settings.

Step 4 Click Update to save the changes, Delete to remove the user, or, if available, Cancel Changes to exit the window without making any changes.


Attendant Console User Configuration Settings

Use Table 2, which describes Cisco CallManager Attendant Console user configuration settings, to complete procedures in the "Adding an Attendant Console User" and "Viewing, Updating, and Deleting Attendant Console Users" sections.

Table 2 Attendant Console User Configuration Settings

Field
Description

User ID

Enter the login name for the new attendant console user. Enter up to 50 alphanumeric characters.

Password

Enter a password of up to 50 alphanumeric characters.

Confirm

Re-enter the same password.

Station Type

Not used. If specified, the attendant console ignores this setting.

This setting exists for Cisco CallManager 3.2 only.


Understanding Pilot Points and Hunt Groups

A pilot point, a virtual directory number that is never busy, alerts the Cisco Telephony Call Dispatcher (TCD) to receive and direct calls to hunt group members. A hunt group comprises a list of destinations that determine the call redirection order.

For Cisco TCD to function properly, make sure that the pilot point number is unique throughout the system (it cannot be a shared line appearance). When configuring the pilot point, you must choose one of the following options from the Pilot Point Configuration window in Cisco CallManager Administration:

First Available Hunt Group Member—Cisco TCD goes through the members in the hunt group in order until it finds the first available destination for routing the call.

Longest Idle Hunt Group Member—This feature arranges the members of a hunt group in order from longest to shortest idle time. Cisco TCD finds the member with the longest idle time and, if available, routes the call. If not, Cisco TCD continues to search through the group. This feature evenly distributes the incoming call load among the members of the hunt group.


Note You can also configure pilot points to use circular hunting in which Cisco TCD maintains a record of the last hunt group member to receive a call. When a new call arrives, Cisco TCD routes the call to the next hunt group member in the hunt group. For more information on this option, see the "Understanding Circular Hunt Groups" section.


If the voice-mail number is the longest idle member of the group, Cisco TCD will route the call to voice mail without checking the other members of the group first.


Note In the Pilot Point Configuration window in Cisco CallManager Administration, you must choose a device pool that is associated with the pilot point for pilot point redundancy to work.

Make sure that you configure the ac user and associate all pilot point numbers with the ac user. For information on how to perform these tasks, see "Configuring the ac User in the User Information Window" and "Associating Devices and Pilot Points with the ac User" section.


When a call comes into a pilot point, Cisco TCD uses the hunt group list and the selected call- routing method for that pilot point to determine the call destination. During hunt group configuration, you must specify one of the following options for each hunt group member:

Directory number (device member)

If a directory number is specified, Cisco TCD only checks whether the line is available (not busy) before routing the call.

Attendant console user plus a line number (user member)

The number of lines that are configured for the attendant phone determines the number of available lines that display in the attendant console graphical user interface. For example, if you provide the attendant with a Cisco IP Phone Model 7960 and two attachments of the Cisco IP Phone Expansion Module 7914, a total of 34 lines can display in the graphical user interface if you associated a directory number with each line.

If a user and line number are specified, Cisco TCD confirms the following details before routing the call:

That the user is logged in to the attendant console

That the user is online

That the line is available

When you specify a user and line number, the user can log in to and receive calls on any Cisco IP Phone in the cluster the attendant console controls.


Caution To handle overflow conditions, configure your hunt groups, so Cisco TCD can route calls to one or more attendant consoles or voice-mail numbers. To ensure that the voice-mail number can handle more than one call at a time, check the Always Route Member check box in the Hunt Group Configuration window.

Example 1 Pilot Points and Hunt Groups Working Together

Assume a pilot point named Support exists at directory number 4000. The hunt group for the Support pilot point contains the following members:

Support Admin, Line 1 and Support Admin, Line 2 (Support Admin represents the attendant console login for the administrative assistant for Support.)

Three directory numbers for support staff, i.e., 1024, 1025, and 1026, listed in the hunt group in that order

A voice-mail number, 5060, which is the final member of the hunt group

Figure 1 Pilot Point and Hunt Group Example

As shown in Figure 1, the following example describes a simple call-routing scenario where the user chose First Available Hunt Member during the configuration of the pilot point:

1. The attendant console receives a call and directs it to the Support Pilot Point, directory number 4000.

2. Because 4000 is a pilot point and First Available Hunt Group Member is chosen as the call-routing option, the Cisco Telephony Call Dispatcher (TCD) that is associated with the pilot point checks the members of the hunt group in order, beginning with Support Admin, Line 1. Cisco TCD determines that the Support Admin user is not online, directory number 1024 is busy, directory number 1025 is busy, and directory number 1026 is available.

3. Cisco TCD routes the call to the first available directory number, which is 1026. Because 1026 is available, the Cisco TCD never checks the 5060 number.

Understanding Linked Hunt Groups

Linking hunt groups together allows the Cisco TCD to search through more than one hunt group when routing calls. When configured properly, pilot points create a link between hunt groups. Cisco TCD searches each hunt group according to the call-routing method that was chosen during configuration.

Consider the following guidelines when linking hunt groups together:

Configure the individual pilot points and hunt groups first.

For all except the last hunt group, make sure that the final member of the hunt group is the pilot point for the next hunt group. The pilot point from each group creates a link between the hunt groups, as seen in Figure 2.

To handle overflow conditions, choose a voice-mail or auto-attendant number as the final member of the last linked hunt group in the chain. If Cisco TCD cannot route the call to any other members in the hunt groups, the call goes immediately to the voice-mail number in the final hunt group.

In the Hunt Group Configuration window, check the Always Route Member check box for only the final member of each hunt group.


Caution Cisco strongly recommends that you do not link the last hunt group back to the first hunt group.

Example 2 Linked Hunt Groups Working Together

Consider the following information shown in Figure 2:

Three pilot points that are numbered 1, 2, and 3 exist at directory numbers 1000, 2000, and 3000, respectively.

The last hunt group member of Pilot 1 acts as the pilot point for Pilot 2, while the last hunt group member of Pilot 2 serves as the pilot point for Pilot 3.

During hunt group configuration, the administrator checked Always Route Member for the last member of each hunt group.

Each hunt group contains four members, including the linked pilot point.

JSmith, RJones, and CScott designate attendant console users that are specified as user/line pairs in the hunt groups.

In Pilot 2, two directory numbers, 35201 and 35222, exist.

The final hunt group member of Pilot 3, voice-mail number 5050, handles overflow conditions. The administrator checked Always Route Member when this final hunt group member was configured.

Figure 2 Linked Hunt Group Example

As represented in Figure 2, the following example describes a simple call-routing scenario for linked hunt groups:

1. The attendant console receives a call and directs it to the first pilot point of the chain, directory number 1000.

2. Because 1000 is a pilot point and First Available Hunt Group Member is chosen as the call-routing method, the Cisco Telephony Call Dispatcher (TCD) checks the members in the hunt group in order, beginning with JSmith, Line 1. Cisco TCD determines that the first three members of the hunt group are unavailable and, therefore, routes the call to directory number 2000, the link to Pilot 2.

3. When the call reaches Pilot 2, Cisco TCD attempts to route the call to the longest idle hunt group member. Directory numbers 35201 and 35222 are busy, and RJones, Line 3, is offline. Cisco TCD routes the call to the last member of the group, directory number 3000, the link to Pilot 3.

4. Cisco TCD searches through Pilot 3 to find the first available member who is not busy. When Cisco TCD determines that CScott, Line 2, is the first available member, Cisco TCD routes the call to that line. Cisco TCD never checks voice-mail number 5050.

Understanding Circular Hunt Groups

Circular hunt groups enable Cisco TCD to route calls on the basis of last hunt group member to receive a call. Each hunt group maintains a record of which hunt group member receives a call. When a new call arrives, Cisco TCD dispatches the call to the next hunt group member in the hunt group. In other words, Cisco TCD routes the first call to a hunt group to the first hunt group member, the second call to the second hunt group member, and so on. When the last hunt group member receives a call, Cisco TCD routes calls beginning with the first hunt group member again.

To set up circular hunt groups, add the pilot points of those hunt groups to the CIRCULAR_HUNTING_PILOT variable in the ACServier.properties file that is located in ..\Program Files\Cisco\CallManager Attendant Console\etc on the Cisco CallManager Attendant Console server. If you want to use circular hunting for linked hunt groups, include each of the pilot points of the linked hunt groups.

Example 3 Circular Hunting

Assume a pilot point that is named Circular exists at directory number 4000 and that the circular hunting pilot variable in the ACServer.properties file contains the Circular pilot point (CIRCULAR_HUNTING_PILOT=Circular.) The hunt group for this pilot point contains the three directory numbers; i.e., 1024, 1025, and 1026, that are listed in the hunt group in that order. Because the Always Route check box is not checked for any of the hunt group members, Cisco TCD does not determine whether the directory number is busy before routing the call.

Figure 3 Circular Hunting Example

As shown in Figure 3, the following example describes a simple call-routing scenario where the user configured a Circular pilot point:

1. The attendant console receives a call and directs it to the Circular pilot point, directory number 4000.

2. Because 4000 is a pilot point and Circular Hunting is chosen as the call-routing option, the Cisco TCD routes the call to the first hunt group member, which is directory number 1024.

3. The attendant console receives another call and directs it to the Circular pilot point, directory number 4000.

4. Because Circular Hunting is chosen as the call-routing option and directory number 1024 received the last call, Cisco TCD attempts to route the call to the next hunt group member, which is directory number 1025.

5. Cisco TCD determines that directory number 1025 is busy and routes the call to the next hunt group member, directory number 1026.

6. The attendant console receives another call and directs it to the Circular pilot point, directory number 4000.

7. Because Circular Hunting is chosen as the call-routing option and directory number 1026 received the last call, Cisco TCD attempts to route the call to the next hunt group member, which is directory number 1024.


Note You do not configure circular hunt groups through Cisco CallManager Administration. For information on configuring circular hunt groups, see the "Configuring Circular Hunt Groups" section.


Configuring Pilot Points

You must configure pilot points and hunt groups through Cisco CallManager Administration before the Cisco Telephony Call Dispatcher (TCD) can route calls.

This section contains the following topics:

Finding a Pilot Point (Available with Cisco CallManager 3.3)

Adding a Pilot Point

Viewing, Updating, or Deleting a Pilot Point

Resetting a Pilot Point (Available with Cisco CallManager 3.3)

Pilot Point Configuration Settings


Note After you configure the pilot points, make sure that you configure the ac user and associate all pilot points with the ac user. For information on how to perform these tasks, see "Configuring the ac User in the User Information Window" and "Associating Devices and Pilot Points with the ac User" section.


Finding a Pilot Point (Available with Cisco CallManager 3.3)

This section describes how to find a pilot point.

Procedure


Step 1 Choose Service > Cisco CM Attendant Console > Pilot Point.

The Find and List window displays.

Step 2 From the drop-down list box, choose the search criteria.

Step 3 Specify the appropriate search text, if applicable, and click Find. You can also specify how many items per page to display.


Tip To find all pilot points that are registered in the database, click Find without entering any search text.


A list of pilot points display.


Adding a Pilot Point

This section describes how to add a pilot point.

Procedure


Step 1 Perform one of the following tasks, depending on the Cisco CallManager release that runs in the cluster.

For Cisco CallManager 3.2, choose Service > Cisco WebAttendant.

In the upper, right corner of the window, click the Cisco WebAttendant Pilot Point Configuration link.

For Cisco CallManager 3.3, choose Service > Cisco CM Attendant Console > Pilot Point.

Step 2 Enter the appropriate settings as described in Table 3.

Step 3 Click Insert.

Now that the pilot point is created, the Pilot Point Configuration window refreshes to display the name of the new pilot point in the list on the left. The new pilot point and its settings display.

After the pilot point is created, you must configure a hunt group to specify how the calls that come in to the pilot point are redirected.


Viewing, Updating, or Deleting a Pilot Point

This section describes how to view, update, or delete a pilot point.

Using Dependency Records (Available with Cisco CallManager 3.3)

To find out which virtual directory numbers are using the pilot point, click the Dependency Records link from the Pilot Point Configuration window. For more information about dependency records, see the "Understanding How Dependency Records Work (Available with Cisco CallManager 3.3)" section. If you try to delete a pilot point that is in use, Cisco CallManager displays an error message. To delete a pilot point that is currently in use, you must delete the virtual directory numbers that are using the pilot point.


Note For the deletion to take effect, you do not have to restart Cisco TCD or Cisco CallManager after deleting a pilot point.


Procedure


Step 1 Perform one of the following tasks, depending on the Cisco CallManager release that runs in the cluster.

For Cisco CallManager 3.2, choose Service > Cisco WebAttendant.

For Cisco CallManager 3.3, locate the pilot point by using the procedure in the "Finding a Pilot Point (Available with Cisco CallManager 3.3)" section.

Step 2 Click the name of the pilot point that you want to modify or delete. The window refreshes to display information for the chosen pilot point.

Step 3 Make the desired changes. See Table 3 for a description of pilot point configuration settings.

Step 4 Click Update to modify the pilot point or click Delete to remove the pilot point.

Within approximately 10 minutes after you delete a pilot point, Cisco TCD will stop directing calls to any hunt group members that are associated with that pilot point.


Resetting a Pilot Point (Available with Cisco CallManager 3.3)

You must reset the pilot point after you update pilot point configuration settings. When you reset the pilot point, the Cisco CallManager service continues to run, and call processing continues to occur. Perform the following procedure to reset the pilot point:

Procedure


Step 1 Choose Service > Cisco CM Attendant Console > Pilot Point.

The Pilot Point Configuration window displays, and the list on the left side of the window shows all currently configured pilot points.

Step 2 Click the name of the pilot point that you want to modify or delete. The window refreshes to display information for the chosen pilot point.

Step 3 Make the desired changes. See Table 3 for a description of pilot point configuration settings.

Step 4 Click Update.

Step 5 Click Reset.

The Reset window displays.

Step 6 Click one of the following buttons:

Restart—Restarts the selected device for the pilot point without shutting the device down (reregisters the phones with Cisco CallManager).

Reset—Shuts down the selected device for the pilot point and brings it back up (performs a complete shutdown and reinitialization of the phone).

Close—Returns you to the previous window without restarting or resetting the selected device.


Pilot Point Configuration Settings

Use Table 3, which describes pilot point configuration settings, to complete procedures in the "Adding a Pilot Point" and "Viewing, Updating, or Deleting a Pilot Point" sections.

Table 3 Pilot Point Configuration Settings 

Field
Description

Pilot Name

Enter up to 50 alphanumeric characters, including spaces, to specify a descriptive name for the pilot point.

Device Pool

The device pool comprises a group of Cisco CallManagers in prioritized order. The first Cisco CallManager in the list represents the primary Cisco CallManager for the pilot point.

Partition

From the drop-down list box, choose None.

Attendant console pilot points do not belong to partitions.

Calling Search Space

To designate the partitions that the pilot point searches when attempting to route a call, choose a calling search space from the drop-down list.

Pilot Number (DirN)

Enter a directory number into this field to designate a directory number for this pilot point.

Make sure that this number is unique throughout the system (that is, it cannot be a shared line appearance).

Route Calls To

From the drop-down list, choose the First Available Hunt Group Member option to route incoming calls to the first available member of a hunt group.

From the drop-down list, choose the Longest Idle Hunt Group Member option to order members based on the time that each directory number or line remains idle.

If the voice-mail number is the longest idle member of the group, Cisco TCD will route the call to voice mail without first checking the other members of the group.


Configuring Hunt Groups

After you configure the pilot point, you must configure the hunt group. A hunt group comprises a list of destinations (either directory numbers or attendant console user/line numbers) that determine the call redirection order.

This section covers the following procedures:

Adding Hunt Group Members

Configuring Linked Hunt Groups

Viewing, Updating, or Deleting Hunt Group Members

Hunt Group Configuration Settings


Note You do not configure circular hunt groups through Cisco CallManager Administration. For information on configuring circular hunt groups, see the "Configuring Circular Hunt Groups" section.


Adding Hunt Group Members

This section describes how to add hunt group members.

Procedure


Step 1 Perform one of the following tasks, depending on the Cisco CallManager release that runs in the cluster:

If the server runs Cisco CallManager 3.2, choose Service > Cisco WebAttendant.

The Pilot Point Configuration window displays.

Choose the pilot point for which you want to add hunt group members. A list of available pilot points appears on the left side of the Pilot Point Configuration window.

To add hunt group members to this pilot point, click the link to Hunt Group Configuration in the upper, right corner of the Pilot Point Configuration window.

If the server runs Cisco CallManager 3.3, choose Service > Cisco CM Attendant Console > Hunt Group. The Hunt Group Configuration window displays, and the pilot points display in the pane on the left of the window.

Click the pilot point for which you want to add hunt group members.

Figure 4 shows an example of the Hunt Group Configuration window.

Figure 4 Hunt Group Configuration Window

Step 2 Click Add Member. The Hunt Group Members list initially displays the text <<Not Configured>>.

Step 3 Decide whether the hunt group member that you want to add will be a directory number (device member) or a user and line number (user member):

If you specify a directory number, Cisco TCD always attempts to route the call to that number.


Note Cisco TCD handles overflow conditions by routing calls to multiple attendant consoles or voice-mail numbers. In the Hunt Group Configuration window, check the Always Route Member check box, so the voice-mail number receives multiple calls at the same time.


If you specify an attendant console user and line number, Cisco TCD first checks whether the attendant console user is logged in to an attendant console and online before attempting to route the call. When you specify a user and line number, the user can log in to and receive calls on any Cisco IP Phone in the cluster that the attendant console controls.

Step 4 Enter the appropriate configuration settings for the new hunt group member as described in Table 4:

If the hunt group member is a directory number, fill in only the Partition and Directory Number fields in the Device Member Information section. The optional Always Route Member check box only applies to directory numbers.

If the hunt group member is a user and line number, fill in only the User Name and Line Number fields in the User Member Information section.


Note The User Name that you specify designates an attendant console User ID. This user name does not duplicate a User ID that is added through the Cisco CallManager User area of Cisco CallManager Administration.


As you make selections, the Hunt Group Members list box reflects the information that you choose. The Hunt Group Members list displays either the device directory number or the attendant console user name and line number; for example:

#1 Call directory number 35201 (directory number example)

#2 Direct Call to Mary Brown, Line 1 (user and line number example)

Step 5 To add more hunt group members to the pilot point, repeat Step 3 and Step 4.


Note To reorder the hunt group list, choose the member that you want to reorder from the list. Then, using the up and down arrows, move that member to a new position in the list.


Step 6 Click Update to save the hunt group member information and complete hunt group configuration.


Configuring Linked Hunt Groups

This section describes how to configure linked hunt groups.

Procedure


Step 1 For each hunt group in the chain, use the following information when performing Step 1 through Step 4 from the "Adding Hunt Group Members" section.

For all except the last hunt group in the chain, make sure that the final member of the hunt group is the pilot point for the next hunt group.


Caution Cisco strongly recommends that you do not include any other pilot point numbers (besides the final member) in the hunt group. Including other pilot point numbers in the hunt group may cause a continuous route loop.

Check the Always Route Member check box for only the final member of each hunt group.

To handle overflow conditions, choose a voice-mail or auto-attendant number as the final member of the last linked hunt group in the chain. Check the Always Route Member check box to ensure that voice mail can handle multiple, simultaneous calls.

Step 2 After you configure each hunt group, click Update to save the information.


Caution Cisco strongly recommends that you do not link the last hunt group back to the first hunt group.

Step 3 Verify configuration of the linked hunt groups by reviewing the information that you entered in the previous steps.


Viewing, Updating, or Deleting Hunt Group Members

This section describes how to view, update, or delete hunt group members.

Procedure


Step 1 Perform one of the following tasks, depending on the version of Cisco CallManager that runs in the cluster.

For Cisco CallManager 3.2, choose Service > Cisco WebAttendant.

At the top of the window, click the Hunt Group Configuration link.

The Hunt Group Configuration window displays, and the list on the left side of the window displays all currently configured pilot points.

For Cisco CallManager 3.3, Choose Service > Cisco CM Attendant Console > Hunt Group.

Step 2 Click the name of the pilot point that is associated with the hunt group for which you want to view, modify, or delete members.

The Hunt Group Configuration window displays information for the chosen pilot point.

Step 3 Make any desired changes. See Table 4 for a description of hunt group configuration settings:

To update settings for a hunt group member, choose that member name in the list; modify the settings as needed; then, click Update to save the changes.

To change the order of the hunt group members, choose the name of the member that you want to move and use the arrow buttons to move it to a new position in the list.

To delete a hunt group member, highlight that member name in the list and click Delete Member.

If available, you can press Cancel Changes at any time to restore any settings that you changed before clicking Update.

Step 4 Before you leave the Hunt Group Configuration window, click Update to save the changes.


Hunt Group Configuration Settings

Use Table 4 to complete procedures in the following sections:

Adding Hunt Group Members

Configuring Linked Hunt Groups

Viewing, Updating, or Deleting Hunt Group Members

Table 4 Hunt Group Configuration Settings 

Field
Description

Partition

If a hunt group member is a directory number, fill in the Partition and Directory Number fields in the Device Member Information section.

This field designates the route partition to which the directory number belongs:

If the directory number for this hunt group member is in a partition, you must choose a partition from the drop-down list.

If the directory number is not in a partition, choose None.

Always Route Member, an optional check box, applies only to directory numbers.

If this check box is checked, Cisco Telephony Call Dispatcher (TCD) always routes the call to this hunt group member, whether it is busy or not.

If this check box is checked, Cisco TCD does not check whether the line is available before routing the call.

To manage overflow conditions, check this check box for voice-mail or auto-attendant numbers that handle multiple, simultaneous calls.

For linked hunt groups, only check the Always Route Member check box when you are configuring the final member of each hunt group.

Directory Number

Enter the directory number of the hunt group member device in this field. Make sure that this number is unique throughout the system (that is, it cannot be a shared line appearance).

When the directory number is not in the specified partition, an error dialog box displays.

User Name

If the hunt group member is a user and line number, fill in only the User Name and Line Number fields in the User Member Information section.

From the drop-down list, choose attendant console users that will serve as hunt group members.

Only attendant console user names that were added by using Cisco CallManager Attendant Console User Configuration appear in this list.

Line Number

From the drop-down list, choose the appropriate line numbers for the hunt group.

Note You can add the same user to the same line only once within a single hunt group. For example, you cannot add Mary Brown, Line 1, more than once in the hunt group.


Configuring the ac User in the User Information Window

You must configure one user named "ac" in Cisco CallManager Administration and associate the attendant phones and the pilot points with the user. If you do not configure this user, the attendant console cannot interact with CTIManager. Perform the following procedure to configure the ac user:

Procedure


Step 1 From Cisco CallManager Administration, choose User > Add a New User.

The User Information window displays, as shown in the example in Figure 5.

Figure 5 User Information Window

Step 2 In the First Name and Last Name fields, enter ac or another name that you can remember.

Step 3 In the User ID field, enter ac.

Step 4 In the User Password field, enter 12345.

Step 5 In the Confirm Password field, enter 12345.

Step 6 Enter a PIN and telephone number.

Step 7 Check the Enable CTI Application Use check box. You must check this box for the attendant console to interact with CTIManager.

Step 8 If you are running Cisco CallManager 3.3, check the Call Park Retrieval Allowed check box.

If you forget to check the check box, an error message displays when the attendant attempts to log in to the attendant PC.


Note If you upgrade to Cisco CallManager 3.3, you must check this check box after the upgrade for the attendant console to work.


Step 9 Click Insert.

Step 10 Associate the devices by performing the procedure in "Associating Devices and Pilot Points with the ac User" section.


Associating Devices and Pilot Points with the ac User

Before the attendant uses the attendant console, you must associate the attendant console phones and pilot points to the ac user. Perform the following procedure:

Procedure


Step 1 Make sure that the ac user information appears in the User Information window. If it does not display, perform a search for the user. Refer to the Cisco CallManager Administration Guide for more information on how to perform this task.

Step 2 In the Application Profiles column of the User Information window, click Device Association.

Step 3 Perform one of the following tasks:

a. To view all devices, click Select Devices, and go to Step 4.

b. To limit the list of available devices to a specific selection, enter the criteria by which you want to search by using the following methods:

Choose device name, description, or directory number.

Choose the comparison operator.

Enter a text or number entry.

Click Select Devices, and go to Step 4.

Step 4 Check the check box(es) of the attendant console phones and pilot point numbers that Cisco requires that you associate with the user.

Step 5 When you have completed the assignment, click Update to assign the phones to the ac user.


Activating the Cisco Telephony Call Dispatcher Service

The attendant console application registers with and receives call dispatching services from the Cisco Telephony Call Dispatcher (TCD). The Cisco TCD, a Cisco CallManager service, provides communication among Cisco CallManager servers, attendant consoles, and the Cisco IP Phones that are used with the attendant consoles.

When you download the executable from the web, you automatically replace the Cisco CallManager Attendant Console plugin in Cisco CallManager Administration. You also replace the Cisco TCD service.


Note If you use the attendant console in a cluster environment, make sure that you install and run the Cisco TCD service on all servers that run the Cisco CallManager service. Attendant console redundancy requires this setup to work properly; however, not all Cisco TCDs are required to have a route point.


Cisco TCD handles attendant console requests for the following items:

Call dispatching from pilot point to the appropriate hunt group destination

Line status (unknown, available, on hook, or off hook)

User directory information (Cisco TCD stores and periodically updates directory information for fast lookup by the attendant console.)


Note Cisco TCD only monitors the status of internal devices and phones. An attendant console user cannot see line state for a phone that is connected to a gateway.


Cisco TCD also provides the mechanism for automated recovery for the attendant console if a Cisco CallManager fails. If a Cisco CallManager fails, the following events occur:

Another Cisco TCD service that is running on a Cisco CallManager server within the cluster takes over servicing of the route points that are associated with the failed Cisco CallManager.

The attendant console that is attached to the failed Cisco TCD service attempts to locate and connect to the Cisco TCD service on the Cisco CallManager server where its associated Cisco IP Phone registered after failover.

When the Cisco CallManager comes back up, its Cisco TCD will resume servicing its route points and attendant consoles.


Note Automated recovery exists. If a Cisco TCD service fails, another Cisco TCD service takes over.


The following procedure describes how to verify that the Cisco TCD service is running and how to start Cisco TCD if it is stopped.

Procedure


Step 1 Refer to the Cisco CallManager Serviceability Administration Guide for information on how to verify and start the Cisco TCD if it is stopped.

Step 2 Activate the Cisco TCD service on all servers in the cluster that run the Cisco CallManager service.


Activating the CTIManager Service

For hunt groups and the attendant console to function properly, you must start and run the CTIManager service on one server in the cluster. Perform the following procedure to start the service:

Procedure


Step 1 Refer to the Cisco CallManager Serviceability Administration Guide for information on how to verify and start the Cisco CTIManager service if it is stopped.

Step 2 If the service is not running on any server in the cluster, activate/start the Cisco CTIManager service on one server in the cluster.


Understanding the Cisco CallManager Attendant Console Directory

The attendant console server reads and caches directory entries at startup; after an initial handshake determines whether the directory entries changed since the previous log in, the attendant console downloads the directory user list. The attendant console searches the following files for the user list, as indicated in the following order:

Specified user list file on the attendant console

CorporateDirectory.txt file under the User List Directory on the server

Automatically generated user list file on the server

The user list file exists in comma separate value (CSV) format and contains the following information:

Last Name

First Name

Telephone Number

Department


Note Directory entries without telephone numbers do not display in the attendant console Directory window.


The attendant console server also stores per-attendant information such as speed-dial groups/entries and window positions in the directory, which ensures that each attendant can see the saved information and GUI layout from any attendant console.

Cisco CallManager Attendant Console Server Configuration

The Cisco CallManager Attendant Console Server Configuration window lists service parameters and enables you to configure trace parameters for the Cisco Telephony Call Dispatcher (TCD). You obtain information about the parameters by clicking the "i" button help icon in the upper, right corner of the Cisco CallManager Attendant Console Server Configuration window.


Caution Do not change any service parameters without permission of a Cisco Technical Assistance Center engineer. Doing so may cause system failure.

Perform the following steps to update Cisco TCD trace parameters.

Procedure


Step 1 Perform one of the following tasks, depending on the version of Cisco CallManager that runs in the cluster.

For Cisco CallManager 3.2, choose Service > Cisco WebAttendant.

The Pilot Point Configuration window displays.

Click Cisco WebAttendant Server Configuration in the upper, right corner of the window.

For Cisco CallManager 3.3, choose Service > Cisco CM Attendant Console > Cisco CM Attendant Console Server.

The Cisco CallManager Attendant Console Server Configuration window appears.

Step 2 Choose a server from the list on the left side of the window or choose a server from the drop-down box and click Insert.

The window refreshes and displays all configured service parameters for the Cisco TCD. Figure 6 shows an example of the Cisco CallManager Attendant Console Server Configuration window.

Figure 6 Cisco CallManager Attendant Console Server Configuration Window


Note After you insert or choose a server, you can click Trace Configuration in the Cisco WebAttendant (or Cisco CM Attendant Console) Server Configuration window and then refer to the Cisco CallManager Serviceability Administration Guide and the Cisco CallManager Serviceability System Guide to configure trace parameters.



Viewing Cisco CallManager Attendant Console Performance Monitors

The CcmLineLinkState performance monitor for the attendant console provides a quick way to check whether the attendant console is functioning correctly:

If the CcmLineLinkState counter is 11, this state indicates that Cisco TCD is functioning normally.

The left-most digit of CcmLineLinkState indicates whether Cisco TCD is connected to and registered with the Cisco CallManager CTI. If this digit
is 0, a problem may exist with the CTI or the directory.

The right-most digit of CcmLineLinkState indicates whether Cisco TCD can perceive line state information through Cisco CallManager. If this digit is 0, a problem probably exists with Cisco CallManager.


Note When an attendant console user cannot log in to the attendant console and no line state information is available, view the CcmLineLinkState performance monitor to verify that all components of attendant console are functioning properly.


When viewing a counter report for attendant console, as seen in Figure 7, you may see similar performance monitoring information.

Figure 7 Sample Performance Counter Report for Cisco CallManager Attendant Console

The following list gives other performance monitoring information that is provided for the attendant console:

Heartbeat—This counter represents the number of seconds that the Cisco TCD has been running.

StartTime—This counter represents the time in milliseconds since the Cisco TCD started. Based on the real-time clock in the PC, this counter indicates the current time and the length of time since the service started. The reference point for the real-time clock equals January 1, 1970.

CallsTotal—This counter represents the total number of all calls that have occurred since the Cisco TCD service started.

CallsActive—Do not use this counter. Information in this counter may not accurately represent the total number of active calls.

LinesTotal—Do not use this counter. Information in this counter may not accurately represent the total number of lines.

ClientsTotal—This counter represents the total number of attendant consoles that are currently registered with the Cisco TCD service. This number equals the number of attendant console users that are configured in the Cisco CallManager Attendant Console User Configuration window in Cisco CallManager Administration.

TotalCtiRoutePoints—This counter provides the number of pilot points (route points) for this Cisco TCD.

ClientsOnline—This counter represents the total number of attendant consoles that are currently online. This number equals the number of configured attendant console users that are currently online. This number increases by one for each user that goes online and decreases by one for each user that goes offline.

PilotPointsTotal—This counter represents the total number of pilot points that are configured in Cisco CallManager Administration.

Lines Active—Do not use this counter. Information in this counter may not accurately represent the total number of active lines.

LinesIdle—Do not use this counter. Information in this counter may not accurately represent the total number of idle lines.

CallsRedirected—This counter represents the total number of redirected calls for this Cisco TCD service. This number increases every time that a pilot point receives a call and redirects the call to a member of its hunt group.

ClientsRegistered—This counter represents the total number of registered clients for this Cisco TCD service. This number increases by one for each new registration of a Cisco CallManager Attendant Console client when the client logs in to the application.

CcmLineLinkState—This counter represents the line state. Line state values equal 0, 1, 10, or 11. A value of 0 indicates that the Cisco TCD service has not registered or has not received line link state information from Cisco CallManager. A value of 1 indicates that the Cisco TCD service has registered and is receiving line link state information from the Cisco CallManager. A value of 10 indicates the Cisco TCD service has logged in to CTI but has not registered or has not received line link state information from Cisco CallManager. A value of 11 indicates that the TCD service has logged into CTI, has registered, and is receiving line link state information.

Version—This counter represents the Cisco TCD version.

Perform the following procedures to view CcmLineLinkState and other performance monitoring information for Cisco TCD and the attendant console:

Procedure


Step 1 Log in to the Cisco CallManager server.

Step 2 Choose Start > Programs > Administrative Tools > Performance.

Step 3 Click the View report data icon.

Step 4 Click the + (Add counter) icon.

Step 5 Choose System Monitor; enable All Counters, and choose Cisco CallManager Attendant Console from the Object drop-down list box.

Step 6 Click Add.


Cisco CallManager Attendant Console Requirements

See the following sections for PC requirements and Cisco IP Phone requirements for using the attendant consoles:

Attendant Console Requirements

Cisco IP Phone and Voice Mail Requirements for Use with the Attendant Console

Attendant Console Requirements

The following list provides PC requirements for the attendant console:

Operating system—Microsoft Windows 98, Windows 2000, Windows XP, or Windows NT 4.0 (highest Service Pack 6) workstation or server

Network connectivity to the Cisco CallManager

Cisco IP Phone and Voice Mail Requirements for Use with the Attendant Console

The attendant console works in conjunction with a Cisco IP Phone. Configure the attendant console to connect the Cisco IP Phone to its registered Cisco CallManager server. To do this, make sure that the IP Address or Host Name field in the Attendant Console Settings dialog box specifies the address of the Cisco CallManager server to which the Cisco IP Phone is normally registered.

Cisco IP Phones that are used with the attendant console must meet the following guidelines:

Use the attendant console with any Cisco IP Phone Model 7960/7940.

Make sure that the Cisco IP Phone is added as a device in Cisco CallManager before it is used with the attendant console.

Do not use a shared-line appearance on any phone that is used with the attendant console. Make sure that directory numbers assigned to a Cisco IP Phone do not appear on any other device in the system.

Make sure that you associate the attendant directory numbers (the pilot points and devices) with the ac user that you configured in User area of Cisco CallManager Administration.

Make sure that you configure voice mail for each directory number that is accessible by the attendant. If you do not, the attendant cannot forward calls to voice mail.


Note The line on which the attendant console transfers the call remains unavailable for the duration of the transfer. For voice mail, the system identifies the attendant as the calling party rather than the original calling party.


Make sure that you include information about each voice-mail system in your organization in the VoiceMailProfiles.xml file that is located in the ..\Program Files\Cisco\CallManager Attendant Console\etc directory.

For more information on how to perform this task, see the "Configuring Cisco CallManager Attendant Console to Access Voice Mail" section.

Disable call forwarding for lines and directory numbers on Cisco IP Phones that are used as attendant consoles.

If an attendant console user will be logging in to the attendant console at more than one phone, ensure that each phone is set up according to these guidelines and that each phone is registered with its own attendant console.

Cisco does not support the use of Cisco CallManager Extension Mobility with Cisco IP Phones that are used as attendant consoles.

Cisco does not support the use of call waiting with Cisco IP Phones that are used as attendant consoles.

Downloading Cisco CallManager Attendant Console from CCO

When you download the executable from the web, you automatically replace the Cisco CallManager Attendant Console plugin in Cisco CallManager Administration with the new Cisco CallManager Attendant Console plugin that works with the Cisco CallManager Attendant Console. If you do not download the files, you cannot use Cisco CallManager Attendant Console. To download the executable from the web, perform the following procedure on each server in the cluster:

Procedure


Step 1 Click http://www.cisco.com/kobayashi/sw-center/sw-voice.shtml and complete the following procedure:

a. Depending on the Cisco CallManager version that is running in the cluster, click Cisco CallManager Version 3.2 or Cisco CallManager Version 3.3.

b. Download the file executable onto Cisco CallManager server(s) in the cluster.

c. Double-click the downloaded file.

d. Wait while the files load to your server.

e. Choose Install.

Step 2 After the installation completes, restart your computer for the update to take effect.

Step 3 Make sure that you perform this procedure on each Cisco CallManager server in the cluster.


Installing the Cisco CallManager Attendant Console on the User PC

This section describes how to install the attendant console on a user PC.

Procedure


Step 1 If you have not already done so, add the attendant console user and the phone that you want to associate with the attendant console to the Cisco CallManager database.

Step 2 If you have not already done so, download the plugin from the web onto each server in the cluster. See the "Downloading Cisco CallManager Attendant Console from CCO" section.

Step 3 From each Cisco CallManager Attendant Console PC, browse into a server running Cisco CallManager Administration and log in with administrative privileges.


Tip To browse into the server, enter http://<CM-server-name>/CCMAdmin/main.asp, where <CM-server-name> equals the name of the server, in the Address bar in the web browser.


Step 4 From Cisco CallManager Administration, choose Application > Install Plugins.

Step 5 Click the icon for the Cisco CallManager Attendant Console (or Cisco WebAttendant).

The Cisco CallManager Attendant Console installation wizard runs.

Step 6 Click Yes to acknowledge the installation.

Step 7 Click Next in the initial installation wizard window.

Step 8 You can install the attendant console to the default location or use the Browse button to specify a new location; after specifying a location, click Next.

Step 9 In the Ready to Install window, click Next.

Step 10 After the installation program finishes installing files, choose whether you want to restart the computer now or later; then, click Finish.

Step 11 If prompted, restart the computer.

After you install the application, you can configure or update any attendant console settings that you did not configure during the installation process.


Configuring Cisco CallManager Attendant Console Settings on the User PC

On the attendant console user PC, configure each attendant console to meet the following criteria:

Provide the attendant console user and password

Connect to the correct Cisco CallManager TCD server and directory number for the Cisco IP Phone that the attendant uses with the attendant console

After you install the attendant console, you must configure the attendant console before a user can log in to the console. Use the procedure in this section to configure settings that are not specified during installation, to view current settings, or to update the attendant console configuration.

Once configured, the attendant console operates with the specified settings until the administrator changes them.

Procedure


Step 1 On the PC where the attendant console is installed, choose Start > Programs > Cisco CallManager > Cisco CallManager Attendant Console or click the Cisco CallManager Attendant Console icon on the desktop; then, click Yes to launch the attendant console.

Step 2 Enter the attendant console user name and password.

Step 3 Click Settings.

Step 4 Enter the appropriate configuration settings, as described in Table 5.

Step 5 Click Save. You have now configured the settings for the attendant console, and the settings can now be used for call-distribution activities.


Use Table 5, which provides information on attendant console configuration settings, with the "Configuring Cisco CallManager Attendant Console Settings on the User PC" section.

Table 5 Settings Dialog Box 

Field/Check Box
Notes
Basic Tab (Cisco requires that you enter the information in the appropriate fields.)

Attendant Server Host Name or IP Address

Enter the appropriate information in the field.

Directory Number of Your Phone

Confirm or enter the directory number of the Cisco IP Phone that the attendant uses with the attendant console

Advanced Tab (You can enter information into these optional fields to change the default settings.)

Path of Local Directory File

Enter the user list file that specifies the directory information.

Call Processing Server Host Name or IP Address

Enter the appropriate information in the field.

Local Host IP Address (for line state)

Enter the appropriate information in the field.

Note If the attendant PC has two Network Interface Cards (NICs), you can specify the IP address that will receive line state updates.

Enable Trace check box

Check the check box to ensure that you can troubleshooting issues associated with the attendant console.

Audible Alerting Ring Setting

Click the button to choose a ring setting, a "beep," that alerts the attendant to the call through the PC sound card and speakers.


Configuring Cisco CallManager Attendant Console System Files

Some Cisco CallManager Attendant Console configuration procedures, including configuring circular hunt groups, require that you must edit various system files.

This section covers the following procedures:

Configuring Circular Hunt Groups

Configuring Cisco CallManager Attendant Console to Access Voice Mail

Configuring Held Icon Timers

Configuring Circular Hunt Groups

Circular hunt groups enable Cisco TCD to route calls on the basis of the last hunt group member to receive a call. Each hunt group maintains a record of which hunt group member receives a call. When a new call arrives, Cisco TCD dispatches the call to the next available hunt group member from the last hunt group member to receive a call. Cisco TCD searches each hunt group according to the call-routing method that was chosen during configuration.

Perform the following procedure to configure circular hunt groups:

Before You Begin

Before you create the circular hunt groups, perform the following tasks:

Create the pilot points as described in the "Attendant Console User Configuration Settings" section.

Create the hunt groups as described in the "Configuring Hunt Groups" section.

Procedure


Step 1 Open the ACServer.properties file that is located in the ..\Program Files\Cisco\CallManager Attendant Console\etc directory on the Cisco CallManager Attendant Console server.

Step 2 Add the pilot points to the circular hunting pilot variable, CIRCULAR_HUNTING_PILOT. If you have multiple circular hunt groups, separate the hunt group names by commas as shown:

CIRCULAR_HUNTING_PILOT=pilot point name, pilot point name


Note If you want to use circular hunting for linked hunt groups, add each pilot point of the linked hunt groups to the circular hunting pilot variable in the ACServer.properties file.


Step 3 Save and close the ACServer.properties file.


Configuring Cisco CallManager Attendant Console to Access Voice Mail

To access voice mail from Cisco CallManager Attendant Console, you must include information about each voice-mail system in the appropriate system file on the Cisco CallManager Attendant Console server. To configure the system file, perform the following procedure:

Procedure


Step 1 On the Cisco CallManager Attendant Console server, open the VoiceMailProfilesExample.xml file that is located in the ..\Program Files\Cisco\CallManagerAttendant\etc directory.

Step 2 Copy the contents of this file into the VoiceMailProfiles.xml file that is located in the same directory.

Step 3 For each voice-mail system that Cisco CallManager Attendant Console needs to access, provide the following information:

Voice-mail profile name

Voice-mail pilot number

DTMF sequence that Cisco Attendant Console uses to call the voice-mail system for internal callers

DTMF sequence that Cisco Attendant Console uses to call the voice-mail system for external callers

Number of seconds that Cisco Attendant Console waits to enter the DTMF sequence after connecting to the voice-mail system.

Step 4 Save and close the VoiceMailProfiles.xml file.


Configuring Held Icon Timers

From the attendant PC, you can configure the duration after which the held icons in the attendant console change color. The color of the held icons indicates how long a call has been on hold. By default, the held icon turns yellow when a call remains on hold for 60 seconds and turns red when the call remains on hold for 120 seconds. To change these values, edit the WaitTimeMedium and WaitTime Long parameters in the GlobalUI.properties file that is located on the attendant PC in C:\Program Files\Cisco\CallManager Attendant Console\etc. The WaitTimeMedium parameter indicates the time before the held icon turns yellow. The WaitTimeLong parameter indicates the period of time before the held icon turns red.


Tip Cisco recommends that you do not change the default values of the WaitTimeMedium and WaitTimeLong parameters.


To configure the duration after which the held icons change color, perform the following procedure.

Procedure


Step 1 Open the GlobalUI.properties files that are located on the attendant PC in the ..\Program Files\Cisco\CallManager Attendant Console\etc directory.

Step 2 To change the time before the held icon turns yellow, edit the WaitTimeMedium parameter.

Step 3 To change the time before the held icon turns red, edit the WaitTimeLong parameter.

Step 4 Save and close the GlobalUI.properties file.


Obtaining Documentation

Cisco provides several ways to obtain documentation, technical assistance, and other technical resources. These sections explain how to obtain technical information from Cisco Systems.

Cisco.com

You can access the most current Cisco documentation on the World Wide Web at this URL:

http://www.cisco.com/univercd/home/home.htm

You can access the Cisco website at this URL:

http://www.cisco.com

International Cisco websites can be accessed from this URL:

http://www.cisco.com/public/countries_languages.shtml

Documentation CD-ROM

Cisco documentation and additional literature are available in a Cisco Documentation CD-ROM package, which may have shipped with your product. The Documentation CD-ROM is updated regularly and may be more current than printed documentation. The CD-ROM package is available as a single unit or through an annual or quarterly subscription.

Registered Cisco.com users can order a single Documentation CD-ROM (product number DOC-CONDOCCD=) through the Cisco Ordering tool:

http://www.cisco.com/en/US/partner/ordering/ordering_place_order_ordering_tool_launch.html

All users can order monthly or quarterly subscriptions through the online Subscription Store:

http://www.cisco.com/go/subscription

Ordering Documentation

You can find instructions for ordering documentation at this URL:

http://www.cisco.com/univercd/cc/td/doc/es_inpck/pdi.htm

You can order Cisco documentation in these ways:

Registered Cisco.com users (Cisco direct customers) can order Cisco product documentation from the Networking Products MarketPlace:

http://www.cisco.com/en/US/partner/ordering/index.shtml

Nonregistered Cisco.com users can order documentation through a local account representative by calling Cisco Systems Corporate Headquarters (California, U.S.A.) at 408 526-7208 or, elsewhere in North America, by calling 800 553-NETS (6387).

Documentation Feedback

You can submit comments electronically on Cisco.com. On the Cisco Documentation home page, click Feedback at the top of the page.

You can e-mail your comments to bug-doc@cisco.com.

You can submit comments by using the response card (if present) behind the front cover of your document or by writing to the following address:

Cisco Systems
Attn: Customer Document Ordering
170 West Tasman Drive
San Jose, CA 95134-9883

We appreciate your comments.

Obtaining Technical Assistance

Cisco provides Cisco.com, which includes the Cisco Technical Assistance Center (TAC) website, as a starting point for all technical assistance. Customers and partners can obtain online documentation, troubleshooting tips, and sample configurations from the Cisco TAC website. Cisco.com registered users have complete access to the technical support resources on the Cisco TAC website, including TAC tools and utilities.

Cisco.com

Cisco.com offers a suite of interactive, networked services that let you access Cisco information, networking solutions, services, programs, and resources at any time, from anywhere in the world.

Cisco.com provides a broad range of features and services to help you with these tasks:

Streamline business processes and improve productivity

Resolve technical issues with online support

Download and test software packages

Order Cisco learning materials and merchandise

Register for online skill assessment, training, and certification programs

To obtain customized information and service, you can self-register on Cisco.com at this URL:

http://tools.cisco.com/RPF/register/register.do

Technical Assistance Center

The Cisco TAC is available to all customers who need technical assistance with a Cisco product, technology, or solution. Two types of support are available: the Cisco TAC website and the Cisco TAC Escalation Center. The type of support that you choose depends on the priority of the problem and the conditions stated in service contracts, when applicable.

We categorize Cisco TAC inquiries according to urgency:

Priority level 4 (P4)—You need information or assistance concerning Cisco product capabilities, product installation, or basic product configuration. There is little or no impact to your business operations.

Priority level 3 (P3)—Operational performance of the network is impaired, but most business operations remain functional. You and Cisco are willing to commit resources during normal business hours to restore service to satisfactory levels.

Priority level 2 (P2)—Operation of an existing network is severely degraded, or significant aspects of your business operations are negatively impacted by inadequate performance of Cisco products. You and Cisco will commit full-time resources during normal business hours to resolve the situation.

Priority level 1 (P1)—An existing network is "down," or there is a critical impact to your business operations. You and Cisco will commit all necessary resources around the clock to resolve the situation.

Cisco TAC Website

The Cisco TAC website provides online documents and tools to help troubleshoot and resolve technical issues with Cisco products and technologies. To access the Cisco TAC website, go to this URL:

http://www.cisco.com/tac

All customers, partners, and resellers who have a valid Cisco service contract have complete access to the technical support resources on the Cisco TAC website. Some services on the Cisco TAC website require a Cisco.com login ID and password. If you have a valid service contract but do not have a login ID or password, go to this URL to register:

http://tools.cisco.com/RPF/register/register.do

If you are a Cisco.com registered user, and you cannot resolve your technical issues by using the Cisco TAC website, you can open a case online at this URL:

http://www.cisco.com/tac/caseopen

If you have Internet access, we recommend that you open P3 and P4 cases online so that you can fully describe the situation and attach any necessary files.

Cisco TAC Escalation Center

The Cisco TAC Escalation Center addresses priority level 1 or priority level 2 issues. These classifications are assigned when severe network degradation significantly impacts business operations. When you contact the TAC Escalation Center with a P1 or P2 problem, a Cisco TAC engineer automatically opens a case.

To obtain a directory of toll-free Cisco TAC telephone numbers for your country, go to this URL:

http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml

Before calling, please check with your network operations center to determine the Cisco support services to which your company is entitled: for example, SMARTnet, SMARTnet Onsite, or Network Supported Accounts (NSA). When you call the center, please have available your service agreement number and your product serial number.

Obtaining Additional Publications and Information

Information about Cisco products, technologies, and network solutions is available from various online and printed sources.

The Cisco Product Catalog describes the networking products offered by Cisco Systems, as well as ordering and customer support services. Access the Cisco Product Catalog at this URL:

http://www.cisco.com/en/US/products/products_catalog_links_launch.html

Cisco Press publishes a wide range of networking publications. Cisco suggests these titles for new and experienced users: Internetworking Terms and Acronyms Dictionary, Internetworking Technology Handbook, Internetworking Troubleshooting Guide, and the Internetworking Design Guide. For current Cisco Press titles and other information, go to Cisco Press online at this URL:

http://www.ciscopress.com

Packet magazine is the Cisco quarterly publication that provides the latest networking trends, technology breakthroughs, and Cisco products and solutions to help industry professionals get the most from their networking investment. Included are networking deployment and troubleshooting tips, configuration examples, customer case studies, tutorials and training, certification information, and links to numerous in-depth online resources. You can access Packet magazine at this URL:

http://www.cisco.com/go/packet

iQ Magazine is the Cisco bimonthly publication that delivers the latest information about Internet business strategies for executives. You can access iQ Magazine at this URL:

http://www.cisco.com/go/iqmagazine

Internet Protocol Journal is a quarterly journal published by Cisco Systems for engineering professionals involved in designing, developing, and operating public and private internets and intranets. You can access the Internet Protocol Journal at this URL:

http://www.cisco.com/en/US/about/ac123/ac147/about_cisco_the_internet_protocol_journal.html

Training—Cisco offers world-class networking training. Current offerings in network training are listed at this URL:

http://www.cisco.com/en/US/learning/le31/learning_recommended_training_list.html

Copyright © 2003 Cisco Systems, Inc. All rights reserved.