Configuring the CRA Engine for Cisco Conference Connection

Cisco Conference Connection uses the Cisco Customer Response Applications Engine (CRA Engine) to run the Conference Director interactive voice response (IVR) application. This application is used to ask callers which conference call they want to attend. You must configure several elements for the CRA Engine using the CRA Application Administration web interface.

4. Add a CTI port group in the Cisco CRA Engine's JTAPI subsystem that contains the CTI ports that you created for Cisco Conference Connection's use. See the "Adding the CTI Port Group" section for more information.

6. Optionally, replace the Conference Director's prompts with Japanese prompts, if your conference call attendees are primarily Japanese speakers. See the "Using Japanese Voice Prompts" section for more information.

For more detailed information about configuring the CRA Engine and using the CRA Application Administration web interface, see the online help.

Logging In and Configuring Directory Information

The Cisco IP Telephony Directory server stores two types of information used by the Cisco Customer Response Application (Cisco CRA) Engine. First, it stores directory information, which includes CTI port and routing configurations. Second, it contains the repository subdirectory, which stores the applications used with the Cisco CRA Engine.

Cisco recommends that you use one IP Telephony Directory with Cisco Conference Connection, rather than split the directory information and repository subdirectories onto separate servers.

Procedure

Step 3 Use Table 4-1 to fill in the fields on the Directory Configuration page. Look at your existing IP Telephony Directory to determine the correct values.

Table 4-1 Directory Configuration

Field	Description	Default for DC Directory
Directory hostname	DNS name or IP address of the Cisco IP Telephony Directory server to be used for the Cisco CRA Engine profile. Normally, this is the Publisher Cisco CallManager directory server.
Directory port number	The port number of the Cisco IP Telephony Directory.	8404
Directory user (DN)	The user name (also 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
User Base	The branch of the Cisco IP Telephony Directory tree that contains user-defined information.	ou=Users, o=cisco.com
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—MS Active Directory, Netscape Directory Server, or DC Directory.	DC Directory
Configuration Profile Name	The profile name that identifies this engine configuration. If you are reinstalling or upgrading Cisco Conference Connection, enter the profile name you previously used. This will recover your previous configuration for the CRA Engine subsystems and the Conference Director application script.

If you want to maintain separate profiles for your directory and repository configurations, select Use a Different Repository Profile. However, Cisco recommends that you do not select this for Cisco Conference Connection. If you leave this unchecked, the Cisco Conference Connection server uses the directory configuration information to build the application repository configuration.

If you elected to use a different repository profile, the repository configuration window appears. Complete these fields with the configuration information appropriate for your repository directory.

Configuring the Cisco CRA Engine's Database Subsystem

You must configure the Cisco CRA Engine's database subsystem so that Cisco Conference Connection can control entry into conferences. The conference scheduling information is kept in this database. If the database is not available (or configured incorrectly):

Procedure

Cisco CRA Application Administration opens the Enterprise Database Subsystem Configuration page.

Configuring the JTAPI Subsystem on the Cisco CRA Engine

You must configure the JTAPI subsystem on the Cisco CRA Engine. The Cisco CRA Engine uses the JTAPI subsystem to send and receive calls from Cisco CallManager. This enables callers to connect to the Conference Director IVR application, and have their calls connected to a conference.

Procedure

However, the first system you list must be available when the CRA Engine starts or the JTAPI subsystem will not start.

Adding the CTI Port Group

Identify the CTI ports you created for Cisco Conference Connection's use on the JTAPI Configuration page in the Cisco CRA Application Administration configuration. The collection of these ports are called a CTI port group.

Procedure

Step 3 On the Add a new CTI Port Group page, select Applications for CTI Port Group Type and click Next.

The port group contains all CTI ports from the first port to the last port, inclusive of these ports. Ensure that you have defined all of these ports in Cisco CallManager.

Configuring the Conference Director IVR Application

After you have configured the Cisco CRA Engine subsystems, you can configure the Cisco Conference Connection IVR application. After you complete this configuration, users will be able to call the Cisco Conference Connection CTI route point and request to be connected to specific conference calls.

Procedure

Cisco CRA Application Administration opens the Application Parameters Configuration page.

Step 5 Enter this information on the Application Parameters Configuration page:

CTI Route Point—The CTI route point that you created for Cisco Conference Connection as described in the "Creating the Conference Call CTI Route Point" section. For example, 5000.
Maximum Number of Sessions—The number of CTI ports you added in Cisco CallManager as described in the "Creating the CTI Ports" section. For example, 10.
Enabled—Select Yes to start the Conference Director IVR application.
GWPrefix—The number from the route pattern you created for Cisco Conference Connection as described in the "Creating the Route Pattern" section. Only enter the number; do not include the dot or wildcards. For example, if the route pattern is 11111.!#, enter 11111.
OperExtn—The extension of the phone that will be used by the human operator. Callers are transferred to the operator if they fail to supply a valid conference ID in three tries. If you do not want callers to be transferred to an operator, enter the word null. If enter an invalid extension, callers will hear a message that the extension is invalid.
DefaultPassword—The default conference call password. If you enter a password, it must be a numeric string from 1 to 10 digits long. If a conference call is created without an owner-supplied password, callers must enter this default password to attend the conference. If you do not want to password-protect conferences when the owner does not supply a password, enter the word null.

If you enter a password with non-numeric characters, or one that is longer than 10 digits or shorter than 4 digits, callers hear the "system problem" message mentioned in the "Caller Gets "System Problem" Message" section and are disconnected.

The default password is only used for callers who try to join a conference by calling the CTI route point. Callers who use the IP Phone Service bypass this application and are only required to enter owner-specified passwords (if any). If you want to force all callers to supply passwords, configure Cisco Conference Connection to require them for all conferences, as described in the "Customizing the Information Page and Configuring System Settings" section.

Cisco CRA Application Administration adds the application and returns to the Applications page.

When the Engine status is "running" and the subsystems indicate they are "in service," Cisco Conference Connection is functional. People can call into the Cisco Conference Connection by dialing the directory number of the CTI route point.

Using Japanese Voice Prompts

You can replace the Conference Director's voice prompts with equivalent Japanese voice prompts if you are supporting Japanese speakers. However, adding Japanese voice prompts does not change the language used on the Cisco Conference Connection web pages.

Before You Begin

You must complete the Cisco CRA Engine and Cisco Conference Connection configuration before you replace the voice prompts. Ensure the Conference Director application is running correctly before proceeding.

Procedure

C:\Program Files\Cisco\ConferenceConnection\InternationalPrompts\
setupJapanesePrompts.bat

Step 2 When asked if you want to overwrite the existing .wav files, reply All.

The batch file copies the Japanese voice prompts into the appropriate directories, and creates backup copies of the English prompts. You can restore the English prompts from these backup directories:

Table of Contents