cc/td/doc/product/voice/c_ipphon/english/ccc/admin
hometocprevnextglossaryfeedbacksearchhelp
PDF

Table of Contents

Cisco CallManager Configuration for Cisco Conference Connection Server
Adding the Cisco Conference Connection Server as an H.323 Gateway
Adding a Route Pattern
Adding CTI Route Points in Cisco CallManager
Adding CTI Ports in Cisco CallManager
Creating a Cisco CallManager JTAPI User for Cisco Conference Connection
Creating a Cisco CallManager IP Phone Service for Cisco Conference Connection
Creating a Cisco CallManager Guest User for Cisco Conference Connection
Configuring the Cisco Conference Connection Server
Setting Up Cisco Conference Connection Users

Cisco CallManager Configuration for Cisco Conference Connection Server


This chapter provides instructions for configuring Cisco CallManager for Cisco Conference Connection Server.

Refer to the appropriate topics in this chapter to understand how to configure Cisco CallManager for Cisco Conference Connection Server.

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

To add the Cisco Conference Connection Server as an H.323 Gateway, perform the following steps.


Note   If you need more information or if the information you see is not exactly the same as described here, see the Cisco CallManager documentation.


Step 1   On the Cisco CallManager server, choose

Start > Programs > Cisco CallManager3.1.x > CallManager Administration

You can also connect to the Cisco CallManager web server using any computer on your network by using the following URL:

http://servername/ccmAdmin

where servername is the DNS name or IP address of your Cisco CallManager server.

You will be prompted for a network username and password.

The Cisco CallManager Administration screen appears.

Step 2   Choose Device > Add a New Device.

The Add Device screen appears.

Step 3   From the Device type list box, choose Gateway .

The Add a New Gateway screen appears.

Step 4   From the Gateway Type list box, choose H.323 Gateway .

Step 5   From the Device Protocol list box, choose H.225 (default).

Step 6   Click Next.

Step 7   Enter the appropriate settings as described in the following table.

Field Description

Device Name

Enter the IP address or DNS name of the Cisco Conference Connection Server.

Description

Enter a description that clarifies the purpose of the device (for example, Conf Connection).

Device Pool

Choose the appropriate device pool from the list box. If no pool has been created, choose Default.

Media Resources Group List

Choose the appropriate group list if one has been created. Otherwise choose None.

Network Hold Audio Source

Choose the appropriate audio source if one has been created. Otherwise choose None.

User Hold Audio Source

Choose the appropriate audio source if one has been created. Otherwise choose None.

Calling Search Space

Choose the appropriate calling search space if one has been created. Otherwise, choose None.

Location

Choose the appropriate location if one has been created. Otherwise choose None.

Caller ID DN

Leave this field blank.

Calling Party Selection

Any outbound call on a gateway can send directory number information. This field determines which directory number is sent.

Choose Originator.

Presentation Bit

Choose whether to transmit or block caller ID.

Choose Allowed.

Display IE Delivery

Leave this check box unchecked.

Gatekeeper Name

You must choose None.

Media Termination Point Required

Leave this check box unchecked.

Num Digits

Choose 32.

Sig Digits

Leave this check box unchecked.

Prefix DN

Leave this field blank.

Run H225D on Every Node

Leave this box checked.

Called Party IE Number Type

Choose Cisco CallManager.

Calling Party IE Number Type

Choose Cisco CallManager.

Called Numbering Plan

Choose Cisco CallManager.

Calling Numbering Plan

Choose Cisco CallManager.

Step 8   Click Insert.

Step 9   Click Reset Gateway to reset the gateway to apply the changes.

Step 10   Click Reset to initiate the reset, and then click OK.



Adding a Route Pattern

To add a Route Pattern, perform the following steps.


Note   If you need more information or if the information you see is not exactly the same as described here, see the Cisco CallManager documentation.


Step 1   On the Cisco CallManager server, choose

Start > Programs > Cisco CallManager3.1.x > CallManager Administration

You can also connect to the Cisco CallManager web server using any computer on your network by using the following URL:

http://servername/ccmAdmin

where servername is the DNS name or IP address of your Cisco CallManager server.

You will be prompted for a network username and password.

Step 2   Choose Route Plan > Route Pattern.

Step 3   Enter the appropriate settings as described in the following table.

Field Description

Route Pattern

Enter the route pattern, including numbers and wildcards (do not use spaces). For Cisco Conference Connection the format is n.! (for example 5321.!).

Note This must be an available route pattern string that is not being used any other configured device in Cisco CallManager.

Partition

Choose the appropriate partition from the list box. If no partition has been created, choose None.

Numbering Plan

Choose a numbering plan.

Route Filter

Choose None.

Gateway/Route List

Choose the H.323 Gateway device name you created in "Adding the Cisco Conference Connection Server as an H.323 Gateway".

Route Option

Choose the Route this pattern option button.

Provide Outside Dial Tone

Uncheck this check box.

Urgent Priority

Do not check this check box.

Use Calling Party's External Phone Number Mask

Do not check this check box.

Calling Party Transform Mask

Leave this field blank.

Prefix Digits (outgoing calls)

Leave this field blank.

Discard Digits

Choose PreDot from the list box.

Called Party Transform Mask

Leave this field blank.

Prefix Digits (Outgoing Calls)

Leave this field blank.

Step 4   Click Insert.

The route pattern appears in the list on the left side of the page.



Adding CTI Route Points in Cisco CallManager

To add a CTI route point in Cisco CallManager for Cisco Conference Connection, perform the following steps.


Note   If you need more information or if the information you see is not exactly the same as described here, see the Cisco CallManager documentation.


Step 1   On the Cisco CallManager server, choose

Start > Programs > Cisco CallManager3.1.x > CallManager Administration

You can also connect to the Cisco CallManager web server using any computer on your network by using the following URL:

http://servername/ccmAdmin

where servername is the DNS name or IP address of your Cisco CallManager server.

You will be prompted for a network username and password.

Step 2   Choose Device > Add a New Device

Step 3   Use the Device Type drop-down arrow to select CTI Route Point

Step 4   Click Next

Step 5   In the Device Name field, enter a name of your choice for the CTI route point. Choose a name that is descriptive, for example CCC_RP.

Step 6   In the Device pool field, select the device pool for this CTI route point. If no other pool has been created, select Default.

Step 7   In the Calling Search Space field, select the appropriate calling search space from the list. Otherwise, select None.

Step 8   In the Location field, select the appropriate location from the list. Otherwise select None.

Step 9   Click Insert.

Step 10   The following prompt appears: "CTI Route Point has been inserted into the database. Would you like to add a directory number for Line 1 of this CTI Route Point now?"
Click OK.

Step 11   In the Directory Number field, enter the directory number for this CTI route point. Users will dial this number to reach this CTI route point (for example, 5000).


Note    This number must be an available number that is not used by any other configured device in Cisco CallManager.

Step 12   Click Insert. Now you need to add CTI ports to Cisco CallManager.



Adding CTI Ports in Cisco CallManager

CTI ports in a CTI port group must have consecutive directory numbers. For example, to add 10 CTI ports in a particular CTI port group, if the first is number 5001, the rest of the ports will be 5002 through 5010.

To add CTI ports in Cisco CallManager, perform the following steps.


Note   If you need more information or if the information you see is not exactly the same as described here, see the Cisco CallManager documentation.


Step 1   On the Cisco CallManager server, choose Start > Programs > Cisco CallManager3.1.x > CallManager Administration

You can also connect to the Cisco CallManager web server using any computer on your network by using the following URL:

http://servername/ccmAdmin

where servername is the DNS name or IP address of your Cisco CallManager server.

Step 2   Choose Device > Add a New Device

Step 3   Use the Device Type drop-down arrow to select Phone and click Next.

Step 4   Use the Phone type drop-down arrow to select CTI Port and click Next.

Step 5   In the Device name field, enter a name for the device (for example, CTI_Port1).

Step 6   Use the Device Pool drop-down arrow to select the device pool for this CTI port. If there is no other pool, select Default.

Step 7   In the Calling Search Space field, select the appropriate calling search space from the list. Otherwise, select None.

Step 8   In the Media Resource Group List field, select the appropriate group list. Otherwise, select None.

Step 9   In the User Hold Audio Source field, select the appropriate audio source. Otherwise, select None.

Step 10   In the Network Hold Audio Source field, elect the appropriate audio source. Otherwise, select None.

Step 11   In the Location field, select the appropriate location from the list. Otherwise select None.

Step 12   Click Insert.

Step 13   The following prompt appears: "The Phone has been inserted in the database. Would you like to add a directory number for Line 1 of this phone now?"
Click OK.

Step 14   In the Directory Number field, enter the directory number of this CTI port (for example, 5001).


Note    This number must be an available number that is not used by any other configured device in Cisco CallManager. CTI port groups must contain sequential CTI port directory numbers.

Step 15   Click Insert.



You can continue to add ports using consecutive numbers. After you have added and configured CTI ports for Cisco Conference Connection, configure a Cisco CallManager JTAPI user for the Cisco Conference Connection.

Creating a Cisco CallManager JTAPI User for Cisco Conference Connection

To create a Cisco CallManager JTAPI user for use by the Conference Director component of Cisco Conference Connection, perform the following steps.


Note   If you need more information or if the information you see is not exactly the same as described here, see the Cisco CallManager documentation.


Step 1   On the Cisco CallManager server, choose Start > Programs > Cisco CallManager 3.1.x >
CallManager Administration

You can also connect to the Cisco CallManager web server by using the following URL:

http://servername/ccmAdmin

where servername is the DNS name or IP address of your Cisco CallManager server.

You will be prompted to enter the network password.

Step 2   Choose User > Add a New User.

Step 3   In the Add a New User screen, enter a first name( for example, conference), last name( for example, connection), and UserID (for example, confconn).

Step 4   Enter a password of your choice in the User Password and Confirm Password fields.

Step 5   Enter a PIN of your choice in the PIN and Confirm PIN fields.

Step 6   Make sure that the Enable CTI Application Use check box is checked.


Caution   When you create a Cisco CallManager user for Cisco Conference Connection, you must click the Enable CTI Application Use check box on the Cisco CallManager Add a New User screen. If you do not click the Enable CTI Application Use check box, the application server will be unable to receive calls from Cisco CallManager.

The new configuration appears in the left pane on the page.

Step 7   In the left pane, click Device Association.

The User Information page appears.

Step 8   Click Select Devices and then click OK.

Step 9   From the list of available devices, select all of the devices created earlier (for example, CCC_RP and all of the CTI ports you created).

Step 10   Click Update.



Creating a Cisco CallManager IP Phone Service for Cisco Conference Connection

You can configure the Cisco Conference Connection as an IP Phone service so that users can join conferences from a Cisco IP Phone 7960/7940.

Configuring Cisco Conference Connection as an IP Phone service is done through the Cisco CallManager Administration application. Once Cisco Conference Connection is configured as an IP Phone service, users need to subscribe to the service through the IP Phone Configuration Web page. Alternatively, the Cisco CallManager administrator can give default access to the Conference Connection IP Phone service to some or all users.

To configure Cisco Conference Connection as an IP Phone service, follow these steps.


Step 1   Start Cisco CallManager and log in using your Cisco CallManager administrator user name and password.

The Cisco CallManager Administration page appears.

Step 2   From the menu, choose Feature > Cisco IP Phone Services.

The Cisco IP Phone Services Configuration page appears.

Step 3   Enter a service name (for example, ConferenceConnection) and service description (for example Audio Conference Service).

Step 4   Enter a service URL (URL of the server that provides the service), as follows:

http:// CCC_server_IP_addr/servlet/DCL.MeetingServer.Admin.DCMSAdmin
?Template=telecastfindmeet&DialPrefix=Number, where

CCC_server_IP_addr = the IP address of the Cisco Conference Connection server

Number = the route pattern created in the "Adding a Route Pattern" section.


Note    For more information, refer to the Cisco CallManager Administration online help, or the Cisco CallManager documentation.

Step 5   Click Insert.

The Service page redisplays.

Step 6   Click New to add the UserName parameter.

    a. In the Parameter Name field, enter "UserName".

    b. In the Parameter Display Name field, enter "UserName".

    c. For the default value, enter "guest".

    d. In the Parameter Description field, type "Enter Conference Connection user name."

    e. Select the Parameter is Required check box.

Step 7   Click Insert.

The Service page redisplays.

Step 8   Click New to add the Password Parameter.

    a. In the Parameter Name field, enter "Password".

    b. In the Parameter Display Name field, enter "Password".

    c. Leave the default value blank.

    d. In the Parameter Description field, type "Enter Conference Connection user password."

    e. Select the Parameter is a Password (mask contents) check box.

Step 9   Click Insert and Close.

Step 10   Click Update Subscriptions.

The new service appears in the list of Cisco IP Phone Services.


Note   Make sure you tell your users how to access their IP Phone User Options Web pages so that they can subscribe to the Conference Connection Service and join conferences from their Cisco IP Phones 7960/7940.



Creating a Cisco CallManager Guest User for Cisco Conference Connection

In Cisco CallManager you can define a "guest" user for the Cisco Conference Connection service. A "guest" user could access the Cisco Conference Connection service from a Cisco IP Phone 7960/7940 to view scheduled conferences. It is also possible to set up a number of Cisco IP Phones 7960/7940 with the Cisco Conference Connection service (including phones in conference rooms) so that "guest" users can view scheduled conferences.

To add a "guest" user to Cisco CallManager, perform these steps.


Step 1   Start Cisco CallManager and log in using your Cisco CallManager administrator user name and password.

The Cisco CallManager Administration page appears.

Step 2   From the menu, choose User > Add a New User.

The User: New User page appears.

Fill in the fields and use "guest" as the UserID and password.


Note    For more information, refer to the Cisco CallManager Administration online help, or the Cisco CallManager documentation.

Step 3   Click Insert.



You may also want to create other "guest" accounts within Cisco CallManager for non-Cisco CallManager users. These "guest" users could use the Cisco Conference Connection Web Interface to schedule and view conferences.

By default, all users have "regular" permissions. You may wish to change the guest account to "guest" permissions. See the "Administering Users in Cisco Conference Connection" section.

Configuring the Cisco Conference Connection Server

After you have configured Cisco CallManager for Cisco Conference Connection Server, the Cisco Conference Connection Server must be configured to communicate with Cisco CallManager and the Cisco IP Telephony Directory.

Refer to the appropriate topics in this section to configure the Cisco Conference Connection Server.

Configuring Directory Information

To configure Directory information on the Cisco Conference Connection Server, perform the following steps.


Step 1   Connect to the Application Administration web server by using the following URL:

http://servername/AppAdmin

where servername is the DNS name or IP address of your Cisco Conference Connection server.

If you are using the computer that is running the Cisco Conference Connection server, you can connect to the web pages by choosing:

Start > Programs > Cisco CRA Administrator> Application Administrator.

You will be prompted to enter the network username and password.

Step 2   At the Cisco CRA Setup screen, click Setup.

Step 3   Use the following table to fill in the fields.

Field Description Default for DC Directory

Directory hostname

Hostname or IP address of the Cisco IP Telephony Directory server used by the current Application Engine profile. (Typically, this would be the Publisher Cisco CallManager.)

 

Directory port number

The port number of the Cisco IP Telephony Directory.

8404

Directory user (DN)

The user name (called the distinguished name) configured on the directory server for the user that has permission to modify the Cisco IP Telephony tree and object entries.

cn=Directory Manager, o=cisco.com

Directory password

The password for the Directory user.

ciscocisco

Base Context

The branch of the Cisco IP Telephony Directory tree that contains the Cisco configuration information.

o=cisco.com

Server Type

The type of LDAP directory—DC Directory.

DC Directory

Configuration Profile Name

The profile name that identifies this engine configuration.

 

Step 4   Click OK.

Step 5   At the Install Application Scripts Installation completed prompt, click Main Menu.

Step 6   It is recommended that you leave the use a different repository profile check box unchecked.


Note    By default, the Cisco Conference Connection server will use the directory configuration information to build the application repository configuration.

If you want to maintain separate profiles for your directory and repository configurations, click the use a different repository profile check box.


Note    If you clicked the use a different repository profile check box, the Repository configuration window appears. Complete these fields with the configuration information appropriate for your repository directory.

Step 7   Click Update to save your changes.



Configuring the JTAPI Component on the Cisco Conference Connection Server

After you complete the directory configuration, you must configure the JTAPI component on the Cisco Conference Connection Server. The Cisco Conference Connection Server uses the JTAPI component to receive calls from Cisco CallManager.

To configure the JTAPI component, perfom the following steps.


Step 1   At the Application Administration Main Menu, click the JTAPI link in the Option column.

Step 2   In the JTAPI Provider field, enter the IP address or DNS name of the Cisco MCS running both the Cisco CallManager and the CTI Manager.

Step 3   In the Username field, enter the Cisco CallManager UserID you defined in "Creating a Cisco CallManager JTAPI User for Cisco Conference Connection" section.

Step 4   Enter the password you defined for this UserID in the Password field.

Step 5   Click Update to save your changes.



Adding a CTI Port Group

To add a CTI Port Group, perform the following steps.


Step 1   On the JTAPI configuration page, click the Add new CTI Port Group link.

Step 2   On the Add a new CTI Port Group page, use the Type drop-down arrow to select Applications and click Next.

Step 3   On the CTI Port Group Configuration page, enter 1 in the Number field.

Step 4   In the Initial CTI Port field, enter the first CTI Port directory number you established in Step 9 of the "Adding CTI Ports in Cisco CallManager" section. If you are using the provided sample values, enter 5001.

Step 5   In the Last CTI Port field, enter the CTI Port directory number of the last CTI port you defined in Cisco CallManager. If you are using the provided sample values, enter 5010.


Note    CTI port groups must contain sequential CTI port directory numbers.

Step 6   Click Update.



Adding a New Cisco Conference Connection Application

When you have configured the appropriate subsystem on the Cisco Conference Connection Server, you can use the conference.aef script to create an application and start the Cisco Conference Connection.

To add a new Cisco Conference Connection application, perform the following steps.


Step 1   Connect to the Application Administration web server by using the following URL:

http://servername/AppAdmin

where servername is the DNS name or IP address of your application server.

Step 2   Click the Telephony Application link on the Application page.

Step 3   On the Application page, click the Add new application link.

Step 4   At the Application Configuration page, select the conference.aef script. The system populates the Script Name field with "conference.aef."

Step 5   Provide a name for the application by entering it in the Application Name field and click Next.

Step 6   At the Application Parameters Configuration page, provide the CTI route point for this Application. If you are using the provided sample values, enter 5000.

Step 7   In the Maximum Number of Sessions field, enter the number of CTI ports you added in Cisco CallManager. If you are using the provided sample values, enter 10.

Step 8   Set the Enabled option to Yes.

Step 9   In the GW Prefix field, enter the digits of the route pattern string you created in the "Adding a Route Pattern" section (for example 5321).

Step 10   In the OperExtn field, enter the extension of the phone that will be used by the human operator.

Step 11   Click Update.

Step 12   Select Main Menu > Engine.

Step 13   On the Engine page, click Start.



When the Engine status is "running" and the subsystems indicate they are "in service", you can call into the Cisco Conference Connection by dialing the directory number of the CTI route point you added to Cisco CallManager. If you are using the provided sample values, dial 5000.

Setting Up Cisco Conference Connection Users

The Cisco Conference Connection user profiles are set up from the user profiles in the Cisco CallManager directory. To set up Cisco Conference Connection users, you need to start the synchronization process between the Cisco CallManager directory and the Cisco Conference Connection database.

Starting the Synchronization Process

To set up Cisco Conference Connection users and start the synchronization process, perform the following steps on the Cisco CallManager server.


Step 1   Configure an ODBC data source on the Cisco CallManager directory machine as follows:

    a. From Windows 2000 desktop, select Start > Programs >Administrative Tools > Data Sources (ODBC).

    b. Select the System DSN tab and click Add.

    c. Select SQL Server from the list of drivers, and click Finish.

    d. At the next screen, enter DCMS in the Name field, and optionally enter a description.

    e. In the Server field, select the name of the server on which you have installed Cisco Conference Connection and click Next.

    f. At the next screen, select SQL Server authentication.

    g. Enter `sa' in the Login ID field and the password that you set during the installation.

    h. Click Next.

If you receive this error: "Connection failed.... client unable to establish connection", then you will need to do the following:

    i. At the next screen, select "Change the default database to", and select DCMS from the list as the default database.

    j. Uncheck "Use ANSI nulls, paddings and warnings" and click Next.

    k. At the next screen, select "Use regional settings when outputting..." and click Finish.

The ODBC data source is created.

    l. At the next screen, click Test Data Source.

A screen pop-up should display "Tests Completed Successfully."

    m. Click OK.

    n. At the next screen, click OK again.

Step 2   Copy ConvEmail.dll from the ccc\LDAPSync directory on the Cisco Conference Connection CD to the $DCDSRVR\lib directory on the Cisco CallManager directory machine (where $DCDSRVR is typically C:\dcdsrvr).

Step 3   Copy odbcagr.txt, odbcdcms.cfg, and delete.txt from the ccc\LDAPSync directory on the Cisco Conference Connection CD to the $DCDCONFIG directory on the Cisco CallManager directory machine (where $DCDCONFIG is typically C:\dcdsrvr\run\dcx500\config).

Step 4   Edit the odbcagr.txt file and verify the values of the following parameters:

Step 5   Make sure that the Metalink server is running. At the command prompt, enter the following command:

dcdmlkag $DCDSRVR\run\dcx500\config\odbcagr.txt
(where $DCDSRVR is the directory path, normally C:\dcdsrvr)



Changing the Synchronization Process TimeInterval Parameter

To change the TimeInterval parameter, follow these steps.


Note   You do not have to stop the synchronization process before you change the TimeInterval parameter.


Step 1   Locate the odbcagr.txt file.

Step 2   Open the file and change the TimeInterval parameter to set it to the new value (in seconds).

Step 3   Save and close the file.


Note   The new TimeInterval will take effect approximately 5 minutes from the time you saved and closed the odbcagr.txt file.



Stopping the Synchronization Process

Normally, after the synchronization process is started, you will not need to stop it. However, you may want to stop the synchronization process if:


Warning Stopping the synchronization process might create inconsistencies and users might have difficulties logging in to the Cisco Conference Connection Web Interface.

To stop the synchronization process, perform these steps on the Cisco CallManager directory machine:


Step 1   Locate C:\$DCDSRVR\run\dcx500\config\delete.txt.

Step 2   In the delete.txt file, change the agreementID parameter so that it is the same as the one in odbcagr.txt.

Step 3   At the command prompt, enter the following command:

dcdmlkag $DCDSRVR\run\dcx500\config\delete.txt
(where $DCDSRVR is the directory path, normally C:\dcdsrvr)

Step 4   At the command prompt, enter the following command:

dcdexprt ALL export.gen /o=cisco.com/ou=Users

Step 5   At the command prompt, enter the following command to delete all the entries under this subtree:

dcddel /o=cisco.com/ou=Users

Step 6   At the command prompt, enter the following command to re-import the exported data:

dcdimprt POPULATE export.gen

This will stop the synchronization between the Cisco CallManager directory machine and the Cisco Conference Connection server.



To restart the synchronization process, see the "Starting the Synchronization Process" section and perform Steps 4 and 5.

For more information on managing user accounts, see the "Managing Accounts" section.


hometocprevnextglossaryfeedbacksearchhelp
Posted: Mon May 5 18:34:55 PDT 2003
All contents are Copyright © 1992--2003 Cisco Systems, Inc. All rights reserved.
Important Notices and Privacy Statement.