Configuring Cisco CallManager for Cisco Conference Connection

Configuring Cisco CallManager for Cisco Conference Connection
Overview of Cisco CallManager Configuration
Creating the Conference Call CTI Route Point
Creating the CTI Ports
Creating a Cisco CallManager JTAPI User for Cisco Conference Connection
Adding the Cisco Conference Connection Server as an H.323 Gateway
Creating the Route Pattern
Creating the Cisco Conference Connection Administrative User
Creating the Cisco Conference Connection IP Phone Service
Disabling Music On Hold for Conference Calls

Configuring Cisco CallManager for Cisco Conference Connection

These topics describe how to configure Cisco CallManager in preparation for deploying Cisco Conference Connection. The procedures described are for Cisco CallManager 3.2. If you are using a different version of Cisco CallManager, some of the individual steps might be different, but the items you need to configure and their attributes are the same. See the Cisco CallManager online help for more specific information on using Cisco CallManager.

Overview of Cisco CallManager Configuration

You must configure several elements in Cisco CallManager for Cisco Conference Connection to use. Figure 3-1 illustrates the communication between Cisco CallManager and Cisco Conference Connection.

Figure 3-1 Cisco CallManager Configuration for Cisco Conference Connection

These are the interactions between Cisco CallManager and Cisco Conference Connection:

1. To attend a conference call, the user dials the CTI route point. This extension connects the user to the Conference Director interactive voice response (IVR) application, which asks the user to identify the desired conference. While connected to Conference Director, the user uses one of the CTI ports defined for the CTI route point. To make this work, you must:

a. Create the CTI route point. This is the telephone number people will call to use Cisco Conference Connection. See the "Creating the Conference Call CTI Route Point" section.

b. Create CTI ports for use by the CTI route point. The number of ports you create determines the number of simultaneous callers that can use the Conference Director application. This does not control the number of callers that can be on conference calls—it only controls the number of people who can interact with Conference Director at the same time. Callers only interact with the application while they are telling Conference Director to which conference call they want to be connected. See the "Creating the CTI Ports" section.

c. Create a Cisco CallManager user for Cisco Conference Connection to control the CTI route point and CTI ports. See the "Creating a Cisco CallManager JTAPI User for Cisco Conference Connection" section.

2. After Conference Director validates that the user's requested conference is in progress, and that the user has entered a valid password (if required), Conference Director forwards the caller to the Cisco Conference Connection H.323 gateway, which hosts the actual conference (this is called the Conference Mixer). The Conference Director application appends the conference ID to a route pattern, and Cisco CallManager forwards the call to the Cisco Conference Connection H.323 gateway based on this route pattern. Cisco Conference Connection places the caller into the correct conference by stripping the route pattern prefix and using the conference ID. At this point, if there is no available port, the caller hears a busy signal. (There might not be an available port if the conference is already using all the ports reserved for the conference.) To make this work, you must:

a. Configure the Cisco Conference Connection server as an H.323 gateway in Cisco CallManager. See the "Adding the Cisco Conference Connection Server as an H.323 Gateway" section.

b. Create a route pattern that forwards calls to the H.323 gateway. See the "Creating the Route Pattern" section.

3. You must also create a Cisco Conference Connection administrative user so that you can log into the software and configure it. Create this user in Cisco CallManager. See the "Creating the Cisco Conference Connection Administrative User" section.

4. Optionally, you can add a Cisco Conference Connection service to those Cisco IP Phones that support IP Phone Services. This gives users direct access into public conference calls. See the "Creating the Cisco Conference Connection IP Phone Service" section.

5. Optionally, you can disable music on hold for conference calls. This eliminates the annoyance of hearing music and misleading announcements on a conference call if one of the conference attendees places the call on hold. See the "Disabling Music On Hold for Conference Calls" section.

These topics assume you know how to use Cisco CallManager. If you do not, see the Cisco CallManager documentation or online help.

Creating the Conference Call CTI Route Point

Create a CTI route point in Cisco CallManager for use as the conference call number used to access Cisco Conference Connection. This is the telephone number that callers will call to attend conferences. The Conference Director application answers calls to this CTI route point.

Procedure

Step 1 In Cisco CallManager, select Device>CTI Route Point.

The Find and List CTI Route Points page displays.

Step 2 Click Add a new CTI Route Point.

The CTI Route Point Configuration page displays.

Step 3 Fill in the CTI route point properties:

Enter a unique name, such as ConferenceConnection, in the Device Name field to identify this as the Cisco Conference Connection number.
Select the appropriate device pool from the Device Pool menu.

Step 4 Click Insert to add the new CTI route point.

Cisco CallManager adds the route point and asks if you want to configure line 1. Click OK to configure line 1.

Cisco CallManager opens the Directory Number configuration page.

Step 5 In the Directory Number field, enter the directory number for this CTI route point. This is the number that callers will dial to reach this CTI route point (for example, 5000). You can also fill in other fields as appropriate for your telephony network.

Step 6 Click Insert.

Cisco CallManager adds the line to the device. Only create one line for the device.

Tip

To start Cisco CallManager, open http://servername/ccmAdmin in your web browser, where servername is the DNS name or IP address of the system running Cisco CallManager.

If you are using a version of Cisco CallManager other than 3.2, the steps for creating the CTI route point might be slightly different. See the Cisco CallManager online help for more specific information.

Creating the CTI Ports

Create CTI ports for use with the Cisco Conference Connection CTI route point. The number of ports you create determines the number of simultaneous callers that can use the Conference Director IVR application to request the desired conference call. If all ports are in use when a caller calls, the caller hears a busy signal.

The CTI port is only used while a caller is using the Conference Director application. These ports are not used while a caller is on the conference call. Therefore, you do not need to create the same number of CTI ports as the number of Cisco Conference Connection ports. Instead, Cisco recommends you create the following number of CTI ports based on Cisco Conference Connection ports:

Up to 60 Cisco Conference Connection ports—Create 10 CTI ports.
More than 60 Cisco Conference Connection ports—Create 15 CTI ports.

Before You Begin

All CTI ports in a CTI port group must have consecutive directory numbers. For example, if you want 10 CTI ports in a particular CTI port group, and the first is number 5001, the rest of the ports must be 5002, 5003, and so on up to 5010.

Procedure

Step 1 In Cisco CallManager, select Device>Phone.

Cisco CallManager opens the Find and List Phones page.

Step 2 Click Add a New Phone.

Cisco CallManager opens the Add a New Phone page.

Step 3 Select CTI Port for Phone Type and click Next.

Cisco CallManager opens the Phone Configuration page.

Step 4 Configure the CTI Port, entering at minimum this information:

Device Name—Enter something meaningful to you, for example, CTI5001.
Device Pool—Select an appropriate device pool.

Step 5 Click Insert.

Cisco CallManager creates the CTI port and asks if you want to configure line 1. Click OK. Cisco CallManager opens the Directory Number Configuration page.

Step 6 In the Directory Number field, enter an unused extension number for the port, such as 5001. All subsequent numbers you configure for the Cisco Conference Connection CTI route point must be consecutive with this number.

Step 7 Click Insert.

Cisco CallManager adds the line to the device. Repeat the procedure to create each CTI port that you require. Only create one line for each CTI port.

Tip

To start Cisco CallManager, open http:// servername/ccmAdmin in your web browser, where servername is the DNS name or IP address of the system running Cisco CallManager.

If you are using a version of Cisco CallManager other than 3.2, the steps for creating the CTI ports might be slightly different. See the Cisco CallManager online help for more specific information.

Creating a Cisco CallManager JTAPI User for Cisco Conference Connection

Create a JTAPI user for Cisco Conference Connection in Cisco CallManager. Cisco Conference Connection uses this account to gain access to Cisco CallManager and control the CTI route points and CTI ports you defined for its use.

Procedure

Step 1 In Cisco CallManager, select User>Add a New User.

Cisco CallManager opens the User Information page.

Step 2 Complete the following required fields:

First Name—Use a descriptive name such as "CCC"
Last Name—Use a descriptive name such as "JTAPI"
UserID—Use a descriptive name such as "cccjtapi"
User Password and Confirm Password—Enter a password and enter it again for confirmation
PIN and Confirm PIN—Enter a PIN and enter it again for confirmation
Enable CTI Application Use—Select this checkbox.

Step 3 Click Insert to create the user.

Cisco CallManager adds the user.

Step 4 Click Device Association in the left-hand column.

Cisco CallManager opens the Assign Devices subpage of the User Information page.

Step 5 Enter search criteria to list the desired CTI route point and CTI ports, or enter nothing to list all devices, and click Select Devices to list the devices.

Step 6 In the list that Cisco CallManager produces, select these devices:

The CTI route point created for Cisco Conference Connection. See the "Creating the Conference Call CTI Route Point" section for more information.
All CTI ports created for Cisco Conference Connection's use. See the "Creating the CTI Ports" section for more information.

Make sure you select the No Primary Extension radio button.

Step 7 Click Update to save your changes.

Tip

To start Cisco CallManager, open http:// servername/ccmAdmin in your web browser, where servername is the DNS name or IP address of the system running Cisco CallManager.

If you are using a version of Cisco CallManager other than 3.2, the steps for creating the user might be slightly different. See the Cisco CallManager online help for more specific information.

Adding the Cisco Conference Connection Server as an H.323 Gateway

You must define the Cisco Conference Connection server as an H.323 gateway in Cisco CallManager. The server must be defined as an H.323 gateway so that it can host conference calls.

Procedure

Step 1 Select Device>Gateway.

Cisco CallManager opens the Find and List Gateways page.

Step 2 Click Add a New Gateway.

Cisco CallManager opens the Add a New Gateway page.

Step 3 Select H.323 Gateway for Gateway Type, H.225 for Device Protocol, and click Next.

Cisco CallManager opens the Gateway Configuration page.

Step 4 Define the gateway configuration. These are the minimum settings:

Device Name—The IP address or DNS name of the Cisco Conference Connection server.
Device Pool—Select an appropriate device pool.
Caller ID DN—Leave this field blank.
Calling Party Selection—Select Originator. This sends the originator's directory number on outbound calls.
Presentation Bit—Select Allowed. This transmits caller ID on calls.
Display IE Delivery—Do not select this.
Gatekeeper Name—Select None.
Media Termination Point Required—Do not select this.
Num Digits—Select 32.
Sig Digits—Do not select this.
Prefix DN—Leave this field blank.
Run H225D On Every Node—Select this.
Called Party IE Number Type—Select Cisco CallManager.
Calling Party IE Number Type—Select Cisco CallManager.
Called Numbering Plan—Select Cisco CallManager.
Calling Numbering Plan—Select Cisco CallManager.

Step 5 Click Insert.

Cisco CallManager creates the gateway.

Step 6 Click Reset Gateway to reset the gateway and apply the changes.

Cisco CallManager opens the Reset Gateway window. Read the information and click Reset.

Tip

To start Cisco CallManager, open http://servername/ccmAdmin in your web browser, where servername is the DNS name or IP address of the system running Cisco CallManager.

If you are using a version of Cisco CallManager other than 3.2, the steps for creating the gateway might be slightly different. See the Cisco CallManager online help for more specific information.

Creating the Route Pattern

Create a route pattern for Cisco Conference Connection's use. When a caller asks to be connected to a conference call, Conference Director appends the conference ID to the route pattern and forwards the call. The route pattern must be defined in Cisco CallManager so that these calls are forwarded to the H.323 gateway configured on the Cisco Conference Connection server.

Procedure

Step 1 Select Route Plan>Route Pattern.

Cisco CallManager opens the Find and List Route Patterns page.

Step 2 Click Add a New Route Pattern.

Cisco CallManager opens the Route Pattern Configuration page.

Step 3 Enter the information for the route pattern:

Route Pattern—A unique pattern that can be routed to the Cisco Conference Connection H.323 gateway. Use n.!#, where n is a unique number in your dial plan. For example, 11111.!#.

The route pattern must be different from the CTI route point created in the "Creating the Conference Call CTI Route Point" section.

Numbering Plan—Select the numbering plan for your area.
Route Filter—Select None.
Gateway/Route List—Select the Cisco Conference Connection H.323 gateway.
Route Option—Select Route this pattern.
Provide Outside Dial Tone—Do not select this.
Urgent Priority—Do not select this.
Calling Party Transformations—Leave all of these fields blank, unselected, or defaulted.
Called Party Transformations—Select PreDot for Discard Digits. Leave all other fields blank.

Step 4 Click Insert.

Cisco CallManager saves the route pattern.

Tip

To start Cisco CallManager, open http://servername/ccmAdmin in your web browser, where servername is the DNS name or IP address of the system running Cisco CallManager.

If you are using a version of Cisco CallManager other than 3.2, the steps for creating the route pattern might be slightly different. See the Cisco CallManager online help for more specific information.

Creating the Cisco Conference Connection Administrative User

Create a Cisco CallManager user for Cisco Conference Connection administration in Cisco CallManager. You must create this user so that you can log into Cisco Conference Connection with administrator authority. After you gain access to Cisco Conference Connection, you can assign other users administrator authority. You can then delete the cccadmin user from Cisco CallManager if you so desire.

Procedure

Step 1 In Cisco CallManager, select User>Add a New User.

Cisco CallManager opens the User Information page.

Step 2 Complete the following required fields:

First Name—Use a descriptive name such as "CCC"
Last Name—Use a descriptive name such as "Admin"
UserID—Enter cccadmin
User Password and Confirm Password—Enter a password and enter it again for confirmation
PIN and Confirm PIN—Enter a PIN and enter it again for confirmation

Step 3 Click Insert to create the user.

Cisco CallManager adds the user.

Tip

To start Cisco CallManager, open http:// servername/ccmAdmin in your web browser, where servername is the DNS name or IP address of the system running Cisco CallManager.

If you are using a version of Cisco CallManager other than 3.2, the steps for creating the user might be slightly different. See the Cisco CallManager online help for more specific information.

Creating the Cisco Conference Connection IP Phone Service

You can create a service for Cisco IP Phones that support IP Phone Services that provides easy access to Cisco Conference Connection conference calls.

If you create this service, users can subscribe to the service from the Cisco CallManager User Options page that they use to configure their other telephone settings (such as speed dials). The service appears in the Services menu. Alternatively, you can define the service as a default service for all or for a set of users.

Hidden conference calls are only displayed to conference owners and Cisco Conference Connection administrators. Other users cannot see these conferences on the phone. This prevents unauthorized access to a conference.

Procedure

Step 1 Select Feature>Cisco IP Phone Services.

The Cisco IP Phone Services Configuration page appears.

Step 2 Enter the information for the service:

Service Name—The name of the service as it will appear on the phone. For example, ConferenceConnection.
Service Description—A description of the service. For example, "Connect to conference calls."
Service URL—The URL required to connect to the service. The URL is:

http://CCCserver/servlet/DCL.MeetingServer.Admin.DCMSAdmin?Template=teleservice&DialPrefix=Number

where:

CCCserver is the IP address of the Cisco Conference Connection server.
Number is the number from the route pattern created in the "Creating the Route Pattern" section. Do not include the dot or the wildcards. For example, if the route pattern is 11111.!#, enter 11111 in the URL.

Step 3 Click Insert.

Cisco CallManager adds the service. Now you must create the parameters for the service.

Step 4 Click New to add the UserName parameter.

Cisco CallManager opens a separate window for creating the parameter. Enter these settings:

Parameter Name—Enter Name.

You can also define the Name parameter as any of these: UserName, name, username, Username, userName.

Parameter Display Name—Enter Name.
Default Value—Leave blank.
Parameter Description—Enter a meaningful description, such as "Enter your Cisco CallManager user name."
Parameter is Required—Select this.

Step 5 Click Insert.

Cisco CallManager adds the parameter.

Step 6 Click New to add the Password Parameter. Enter these settings:

Parameter Name—Enter Password.

You can also define the Password parameter as any of these: password, UserPassword, userPassword, Userpassword, userpassword.

Parameter Display Name—Enter Password.
Default Value—Leave blank.
Parameter Description—Enter a meaningful description, such as "Enter your Cisco CallManager password."
Parameter is a Password (mask contents)—Select this.

Step 7 Click Insert and Close.

Cisco CallManager creates the parameter and closes the window.

Step 8 Click Update Subscriptions on the Cisco IP Phone Services Configuration page.

The new service appears in the list of Cisco IP Phone Services and users can now select it.

Tip

To start Cisco CallManager, open http:// servername/ccmAdmin in your web browser, where servername is the DNS name or IP address of the system running Cisco CallManager.

If you are using a version of Cisco CallManager other than 3.2, the steps for creating the IP Phone Service might be slightly different. See the Cisco CallManager online help for more specific information.

Disabling Music On Hold for Conference Calls

In Cisco CallManager, you can configure music on hold so that callers hear music when one of your users places a call on hold. This can be disruptive if a user places a conference call on hold. The music, and possible announcements, can prevent other callers on the conference call from continuing the call until the user who placed the call on hold returns to the call.

You can disable music on hold for conference calls by creating a Media Resource Group in Cisco CallManager for all music on hold resources, and adding all phones for which you want to enable music on hold to the resource group list with the group. This disables music on hold for callers within the same Cisco CallManager cluster, but does not disable music on hold for outside callers.

This procedure shows how to create a new Media Resource Group for music on hold resources.

Procedure

Step 1 Select Service>Media Resource>Media Resource Group.

Cisco CallManager opens the Media Resource Group Configuration page.

Step 2 Enter this information:

Media Resource Group Name—The name of the group. For example, MOHGroup.
Devices for this Group—Select all of the music on hold servers in the available resources list and click the down arrow to add them to the selected resources list.

Step 3 Click Insert.

Cisco CallManager adds the group.

Step 4 Select Service>Media Resource>Media Resource Group List.

Cisco CallManager opens the Media Resource Group List Configuration page.

Step 5 Enter this information:

Media Resource Group List Name—The name of the resource group list. For example, MOHList.
Media Resource Groups for this List—Select the music on hold resource group you just created in the available media resource groups list and click the down arrow to add them to the selected media resource groups list.

Step 6 Click Insert.

Cisco CallManager adds the group list.

Step 7 Configure all phones for which you want to support music on hold to use the Media Resource Group List you just created. You can use the BAT tool to reconfigure many phones at one time.

Note Make sure you do not assign a music on hold Media Resource Group List to the Cisco Conference Connection H.323 gateway. This will re-enable music on hold for conference calls.

Tip

To start Cisco CallManager, open http:// servername/ccmAdmin in your web browser, where servername is the DNS name or IP address of the system running Cisco CallManager.

If you are using a version of Cisco CallManager other than 3.2, the steps for creating the media resource group and group list might be slightly different. See the Cisco CallManager online help for more specific information.

Table of Contents