Table Of Contents
Installing Cisco Conference Connection
Hardware and Software Requirements
IP Address and Network Interface Speed Requirements
Domain Naming System (DNS) Requirements
Installing Cisco Conference Connection on a New System
Upgrading or Reinstalling Cisco Conference Connection
Reimaging the Cisco Conference Connection Server
Backing Up the Cisco Conference Connection Database and Configuration Files
Reimaging the Server and Restarting Cisco Conference Connection
Restoring the Cisco Conference Connection Database and Configuration Files
Understanding Changes Required When Altering the Cisco CallManager Setup
Changes Required When Upgrading Cisco CallManager (Any Release)
Changes Required When Changing Directory Support
Obtaining Maintenance Releases and Upgrades from Cisco.com
Installing Cisco Conference Connection
These topics describe how to install or upgrade Cisco Conference Connection.
•
Hardware and Software Requirements
• Installing Cisco Conference Connection on a New System
• Upgrading or Reinstalling Cisco Conference Connection
• Reimaging the Cisco Conference Connection Server
• Understanding Changes Required When Altering the Cisco CallManager Setup
• Obtaining Maintenance Releases and Upgrades from Cisco.com
Hardware and Software Requirements
You can install Cisco Conference Connection on any of the platforms described in Table 2-1 or their Cisco-certified equivalents. The table shows the maximum number of Cisco Conference Connection ports that can be supported on each platform. This is the maximum number of telephones that can be connected to conference calls hosted on the server (that is, the sum of telephones connected to all concurrent conference calls). Select a server model that meets your conference call needs.
Table 2-1 Supported Cisco Media Convergence Server Platforms
Cisco Media Convergence Server Model
|
Maximum Cisco Conference Connection Ports
|
MCS 7825-800, 7825-1133
•200 MB free disk space minimum
•512 MB RAM minimum
|
60
|
MCS 7835-1000, 7835-1266
•200 MB free disk space minimum
•1 GB RAM minimum
|
100
|
Before you install Cisco Conference Connection, you must install and configure the Windows 2000 operating system on the server using the media included with your package. These topics describe some configuration requirements for the server.
• IP Address and Network Interface Speed Requirements
• Domain Naming System (DNS) Requirements
IP Address and Network Interface Speed Requirements
You must configure the server to use static IP addresses and 100 Mbps Full Duplex Ethernet connections.
Domain Naming System (DNS) Requirements
You should configure the server to use the same DNS servers that are used by the Cisco CallManager servers.
If you do not use DNS, you must create an LMHOSTS file on the Cisco Conference Connection server. This file must contain the host names for all of the Cisco CallManager servers in the cluster that the Cisco Conference Connection server supports.
This procedure explains how to create the LMHOSTS file if you do not use DNS.
Procedure
Step 1 Create LMHOSTS.txt as a plain text file on the Cisco Conference Connection server. The file must have one line per Cisco CallManager server, in this format:
IP-address host-name
where IP-address is the IP address of the Cisco CallManager server, and host-name is the Cisco CallManager server's host name. Separate the parameters with spaces or tabs. For example:
10.16.0.10 sanjose-cm1
Step 2 Open the Properties window for the Local Area Connection network connection (for example, select Start > Settings > Control Panel > Network and Dial-up Connections > Local Area Network).
Step 3 Select Internet Protocol (TCP/IP) in the list of Components and click Properties.
Step 4 On the Internet Protocol (TCP/IP) Properties window, click Advanced.
Step 5 On the Advanced TCP/IP Settings window, click the WINS tab.
Step 6 On the WINS tab, click Import LMHOSTS, find the LMHOSTS.txt file you created, and click Open.
Ensure that Enable LMHOSTS lookup is selected on the WINS tab.
Step 7 Click OK on each of the windows you opened during this procedure.
Installing Cisco Conference Connection on a New System
This topic describes how to install Cisco Conference Connection on a new system that does not have Cisco Conference Connection already installed. The procedure assumes you are installing from a CD-ROM. If you are installing a downloaded file, follow the instructions in the readme file that came with the download.
Before You Begin
Before installing Cisco Conference Connection, you must install the Microsoft Windows 2000 operating system on the server. Use the operating system installation media supplied in the Cisco Conference Connection package. When you install the operating system, ensure that you configure it to use a static IP address; do not use DHCP or BOOTP to obtain a dynamic IP address.
You must log into Windows with Administrator authority to install Cisco Conference Connection.
Do not install the software using Terminal Services.
Dedicate the server to running the Cisco Conference Connection software; do not install other voice or server applications.
Procedure
Step 1 Insert the Cisco Conference Connection Installation CD.
Step 2 Install the Cisco Customer Response Application (CRA) Engine:
a. Open the IPRV folder and launch setup.exe.
b. At the Cisco Extended Services Administrator Welcome window, click Next.
c. At the Software License Agreement windows, click Yes to accept each license agreement.
d. At the Choose Destination Location for Cisco Extended Services Administrator window, accept the default destination folder and click Next.
e. At the Choose Destination Location for administration web pages window, accept the default destination folder and click Next.
f. At the Service Username and Password window, enter your NT administrator user ID and password. Re-enter the password to confirm and click Next.
g. At the Select Program Folder window, accept the default program folder and click Next.
The installation program begins copying files for the CRA Engine.
h. After the CRA Engine files are installed, the installation program starts the installation of the JTAPI client. At the Welcome to JTAPI Client Setup window, click Next.
i. At the JTAPI Destination window, accept the default destination folder for the JTAPI class and click Next. If prompted to restart the computer, select "No."
j. At the Choose Destination Location window, accept the default destination folder for the JTAPI client and click Next.
The installation program begins copying files for the JTAPI client. If prompted to restart the computer, select "No."
k. At the Maintenance Complete screen, decide whether you want to view the readme file and click Finish. If prompted to restart the computer, select "No."
l. At the Setup Complete window, select "No, I will restart my computer later" and click Finish.
The CRA Engine and JTAPI subsystem installation is now complete.
Step 3 Install Cisco Conference Connection:
a. Open the CCC folder on the Cisco Conference Connection CD and launch setup.exe.
b. At the Cisco Conference Connection Welcome window, click Next.
c. At the Software License Agreement window, click Yes.
d. At the Choose Directory to Install MSDE window, accept the default location of the Microsoft Data Engine (MSDE) destination folder and click Next.
e. At the MSDE User Configuration window, enter a password for the user named "sa." You cannot change the database user name that Cisco Conference Connection uses. Re-enter the password to confirm and click Next.
f. At the Cisco CallManager Information window, enter the DNS name or IP address of the Cisco CallManager Directory Publisher machine, and a Windows administrator user name for the system, and click Next.
g. At the Cisco CallManager Password Configuration window, enter the password for the administrator user name you specified. Re-enter the password to confirm and click Next.
h. At the Standards Based Conference Configuration window, ensure that the displayed Windows NT machine name for this server is correct; change it if it is not correct. Click Next.
i. Confirm the installation and click Yes.
The installation program begins copying files. The MSDE and Serviceability drivers and agents installation may take some time.
j. Click Finish to complete the installation.
k. At the Setup Complete window, select "Yes I want to restart my computer now" and click Finish to restart the computer.
Step 4 Select Start > Programs > Cisco Conference Connection > Start Cisco Conference Connection to start Cisco Conference Connection.
Step 5 Configure Cisco CallManager as described in Chapter 3, "Configuring Cisco CallManager for Cisco Conference Connection."
Step 6 Configure the CRA Engine as described in Chapter 4, "Configuring the CRA Engine for Cisco Conference Connection."
Step 7 You might need to upgrade the JTAPI client. The client you require depends on the version of Cisco CallManager you are using in your telephony network. The "Fixing JTAPI Subsystem Out-of-Service Status" section on page 7-11 describes the symptoms to look for and how to upgrade the client. To be safe, you might want to upgrade the client at this point to avoid potential problems. This ensures that you are running the correct client.
Step 8 Configure Cisco Conference Connection as described in these topics (see the "Logging Into Cisco Conference Connection" section for information on how to log in).
• Entering Cisco Conference Connection License Keys
• Identifying Cisco Conference Connection Administrators
• Customizing the Information Page and Configuring System Settings
Upgrading or Reinstalling Cisco Conference Connection
Before you upgrade or reinstall Cisco Conference Connection, you should uninstall the software. When you uninstall Cisco Conference Connection, only the Cisco Conference Connection server software is uninstalled. The uninstallation process does not remove the database (thus, your conference schedules are preserved). It also does not remove the configuration information stored in the Cisco CallManager directory; this configuration information is for the CRA Engine and the Conference Director application script that runs on the CRA Engine.
These are the steps required for upgrading or reinstalling Cisco Conference Connection. This procedure assumes you are not reinstalling the operating system; if you are reinstalling the operating system, see the "Reimaging the Cisco Conference Connection Server" section for instructions.
Before You Begin
Before reinstalling the software, ensure that you have this information:
•The password for the user named "sa" for the MSDE database. To verify the password, open a command prompt and run the c:\mssql7\binn\osql -U sa command. When prompted, enter the password. If you get a login failed response, the password is incorrect. If you cannot determine the correct password, you need to reimage the server; see the "Reimaging the Cisco Conference Connection Server" section.
•The Cisco Conference Connection license keys you purchased.
•The DNS name or IP address of the Cisco CallManager directory server, and the configuration profile name you are using to store the CRA Engine configuration. In Cisco CRA Application Administration, click Directory, and on the Directory Configuration page, note down the Configuration Profile Name. The "Logging In and Configuring Directory Information" section on page 4-2 describes how to log into Cisco CRA Application Administration.
•If you are installing an upgrade, review the release notes and readme file (if there is one) for the upgrade. You can find release notes for Cisco Conference Connection at this URL:
http://www.cisco.com/univercd/cc/td/doc/product/voice/ccc_docs/index.htm
•Uninstalling Cisco Conference Connection deletes the information you customized on the Information page (as described in the "Customizing the Information Page and Configuring System Settings" section). Make a copy of this information so that you can reenter it after installing the product.
Do not upgrade or reinstall the software while conferences are running.
Procedure
Step 1 If you are upgrading from version 1.1 (any maintenance release), you must first stop the metalink agreement between the Cisco CallManager directory server and Cisco Conference Connection. Cisco Conference Connection does not use metalink agreements in releases after 1.1(3).
To stop the metalink agreement, which stops the synchronization process between the Cisco CallManager directory server and the Cisco Conference Connection server:
a. Find these files on the Cisco CallManager directory server:
Cisco CallManager 3.1
|
Cisco CallManager 3.2
|
C:\$DCDSRVR\run\dcx500\config\delete.txt
odbcagr.txt
|
C:\$DCDSRVR\run\dcx500\config\delete.txt.mmu
odbcagr.txt.mmu
|
b. In delete.txt (or delete.txt.mmu), change the agreementID parameter so that it is the same as the one in odbcagr.txt (or odbcagr.txt.mmu).
c. Open a command prompt window (for example, Start > Program > Accessories > Command Prompt) and enter the appropriate command:
Cisco CallManager 3.1
|
Cisco CallManager 3.2
|
dcdmlkag $DCDSRVR\run\dcx500\config\delete.txt
Where $DCDSRVR is the directory path, normally c:\dcdsrvr.
|
dcdmmu PROCESS $DCDSRVR\run\dcx500\config\delete.txt.mmu
Where $DCDSRVR is the directory path, normally c:\dcdsrvr.
|
d. At the command prompt, enter this command:
dcdexprt ALL export.gen /o=cisco.com/ou=Users
e. At the command prompt, enter this command to delete all the entries under this subtree:
dcddel /o=cisco.com/ou=Users
f. At the command prompt, enter this command to reimport the exported data:
dcdimprt POPULATE export.gen
g. Delete the c:\dcdsrvr\lib\ConvEmail.dll file.
Step 2 On the Cisco Conference Connection server, uninstall all Cisco Conference Connection components:
a. Select Start > Programs > Cisco Conference Connection > Uninstall to uninstall the Cisco Conference Connection server software. Do not restart the server when the system finishes uninstalling the software.
b. Select Start > Programs > Cisco Extended Services Administrator > Uninstall Cisco Extended Services Administrator to uninstall CRA Application Administration. If you are asked if you want to remove shared files, say Yes. Do not restart the server when the system finishes uninstalling the software.
c. Select Start > Settings > Control Panel > Add/Remove Programs, and uninstall the Cisco JTAPI client.
d. Restart the server.
e. Select Start > Run, and run this command:
net stop SNMP /y
f. Remove these directories:
•C:\Program Files\wfavvid
•C:\Program Files\Cisco\ConferenceConnection
Step 3 Install the upgrade or reinstall Cisco Conference Connection following the procedure described in the "Installing Cisco Conference Connection on a New System" section. Keep these points in mind during the installation:
•When prompted for the password for the MSDE user named "sa," enter the same password used previously; do not specify a different password.
•The "Installing Cisco Conference Connection on a New System" section includes steps for configuring Cisco CallManager, the CRA Engine, and Cisco Conference Connection. Do not complete these steps.
Your existing Cisco CallManager configuration is reusable, unless the release notes for the upgrade specify changes you need to make. If the release notes require Cisco CallManager changes, make them after installing Cisco Conference Connection.
Step 4 Verify the CRA Engine configuration and restore it if necessary.
a. Log into the Cisco CRA Application Administration page by opening http://servername/AppAdmin in your web browser, where servername is the DNS name or IP address of the Cisco Conference Connection server. Use a Windows NT network administrator account to log into the application.
If Cisco CRA Application Administration opens the setup page, you need to recover the configuration. Click Setup to open the Directory Configuration page, and enter the directory host name and configuration profile name you noted before reinstalling Cisco Conference Connection. Click OK, and Cisco CRA Application Administration retrieves the configuration from the directory server. Proceed with step c.
b. Click Directory, and verify that the directory host name and configuration profile name are the same as you noted before reinstalling Cisco Conference Connection.
If they are not, enter the correct information, or select the profile name from the list of profiles, and click OK. Cisco CRA Application Administration retrieves the configuration from the directory server.
c. Return to the main menu and complete the database configuration as described in the "Configuring the Cisco CRA Engine's Database Subsystem" section on page 4-4.
d. Return to the main menu and click Engine to view the CRA Engine status. The engine should be running (start it if it is not running), and these subsystems should all be in service:
•Database
•Application
•JTAPI
The correct subsystem status might take a few minutes to reflect correctly. If you are unsure of the status, stop and then restart the engine to get a clean view of the subsystems.
If the JTAPI subsystem is out of service, you probably need to upgrade the JTAPI client. See the "Fixing JTAPI Subsystem Out-of-Service Status" section on page 7-11 for instructions.
Step 5 Check the Cisco Conference Connection license keys and update them if necessary:
a. Log into Cisco Conference Connection as described in the "Logging Into Cisco Conference Connection" section.
b. Update the license keys as described in the "Entering Cisco Conference Connection License Keys" section.
Step 6 If you are installing an upgrade, make any configuration changes that are described as required in the release notes or readme file for the upgrade. Make optional configuration changes if you want to use the optional capabilities.
Step 7 Select Start > Programs > Cisco Conference Connection > Start Cisco Conference Connection to start Cisco Conference Connection.
The system is now ready to host conference calls.
Reimaging the Cisco Conference Connection Server
If you need to reimage the Cisco Conference Connection server, that is, if you need to destructively reinstall the operating system, first back up the Cisco Conference Connection database and the Cisco Conference Connection configuration files so that you can restore the conference information already configured. These are the steps; the sections cited provide further details for each step:
1. Back up the Cisco Conference Connection database and configuration files, as described in the "Backing Up the Cisco Conference Connection Database and Configuration Files" section.
2. Reinstall the software, recover the CRA Engine configuration, and check the configuration, as described in the "Reimaging the Server and Restarting Cisco Conference Connection" section.
3. Restore the Cisco Conference Connection database and configuration files, as described in the "Restoring the Cisco Conference Connection Database and Configuration Files" section.
Backing Up the Cisco Conference Connection Database and Configuration Files
Back up the Cisco Conference Connection database and configuration files before reimaging the server. You should also consider regularly backing up the database so that you can restore it if the database becomes corrupted due to system problems or virus attacks.
Before You Begin
Do not back up the database while conferences are running.
Ensure that you have the Cisco Conference Connection database password that was configured during installation. You will need this when you reinstall the software.
Procedure
Step 1 Select Start > Programs > Cisco Conference Connection > Stop Cisco Conference Connection to stop Cisco Conference Connection.
Step 2 Stop the MSDE services:
a. Select Start > Programs > MSDE Service Manager.
b. In MSDE Service Manager, stop all SQL services on the Cisco Conference Connection server.
c. After all SQL services have stopped, close Service Manager.
d. On the Windows taskbar, find and right-click the Service Manager icon and select Exit.
Step 3 Copy c:\MSSQL7\Data\DCMS_DATA.mdf and c:\MSSQL7\Data\DCMS_log.ldf to a secure backup location. You will need to retrieve these files when you restore the Cisco Conference Connection database.
Step 4 Copy the following configuration files to a secure backup location.
•all files with the ".properties" extension from the C:\Program Files\wfavvid directory.
•c:\WINNT\system32\ccn\ccndir.ini
•c:\Inetpub\Jenga\CUSTadmin.tem
You will need to retrieve these files when you restore the Cisco Conference Connection database.
Reimaging the Server and Restarting Cisco Conference Connection
This procedure describes how to reimage the Cisco Conference Connection server. This involves reinstalling the operating system so that you have a fresh installation, and then installing the Cisco Conference Connection software. Because you are reinstalling Cisco Conference Connection, you can recover some configuration information that does not reside on the server.
Before You Begin
If you intend to recover your existing Cisco Conference Connection configuration, ensure that you:
•Back up the database as described in the "Backing Up the Cisco Conference Connection Database and Configuration Files" section.
•Obtain the password for the user named "sa" for the MSDE database.
•Obtain the Cisco Conference Connection license keys you purchased.
•Write down the DNS name or IP address of the Cisco CallManager directory server, and the configuration profile name you are using to store the CRA Engine configuration. In Cisco CRA Application Administration, click Directory, and you can find this information on the Directory Configuration page. The "Logging In and Configuring Directory Information" section on page 4-2 describes how to log into CRA Application Administration.
If you are installing an upgrade, review the release notes and readme file (if there is one) for the upgrade. You can find release notes for Cisco Conference Connection at this URL:
http://www.cisco.com/univercd/cc/td/doc/product/voice/ccc_docs/index.htm
Note If you are upgrading from Cisco Conference Connection 1.1, you must first remove the metalink agreements with the Cisco CallManager directory, as described in the "Upgrading or Reinstalling Cisco Conference Connection" section.
Do not reimage the server while conferences are running.
Procedure
Step 1 Reinstall and configure the Windows operating system using the CD-ROM included with Cisco Conference Connection.
Step 2 Install Cisco Conference Connection using the instructions in the "Installing Cisco Conference Connection on a New System" section. When prompted for a database password, ensure that you use the same password you noted down when backing up the database (see the "Backing Up the Cisco Conference Connection Database and Configuration Files" section).
Do not redo the Cisco CallManager or CRA Engine configuration steps.
Step 3 Restore the CRA Engine Configuration by following the procedure described in the "Restoring the Cisco Conference Connection Database and Configuration Files" section.
Because reimaging the system does not remove the directory information, the profile still exists in the directory and the CRA Engine retrieves its configuration and the configuration for the Conference Director application script.
Step 4 Select Start > Programs > Cisco Conference Connection > Start Cisco Conference Connection to restart Cisco Conference Connection.
Step 5 Verify that the new database is working by logging into Cisco Conference Connection and creating a new conference.
Restoring the Cisco Conference Connection Database and Configuration Files
After you reimage the Cisco Conference Connection server, you can restore the server's database and configuration files. This restores all of the conference definitions that were current when the database was backed up. If you make regular backups, you can restore the database if system problems or viruses corrupt the database.
Before You Begin
Do not make configuration changes while restoring the database and configuration files.
Procedure
Step 1 Select Start > Programs > Cisco Conference Connection > Stop Cisco Conference Connection to stop Cisco Conference Connection.
Step 2 Stop the MSDE services:
a. Select Start > Programs > MSDE Service Manager.
b. In MSDE Service Manager, stop all SQL services on the Cisco Conference Connection server.
c. After all SQL services have stopped, close Service Manager.
d. On the Windows taskbar, find and right-click the Service Manager icon and select Exit.
Step 3 Copy the DCMS_DATA.mdf and DCMS_log.ldf backup files to c:\MSSQL7\Data\ and overwrite the files currently in that folder.
Step 4 Restore the configuration backup files by copying them to their respective folders.
•copy the files with the .properties extension to C:\Program Files\wfavvid
•copy ccndir.ini to C:\WINNT\system32\ccn\
•copy CUSTadmin.tem to C:\Inetpub\Jenga\
Overwrite the files currently in these folders.
Step 5 Use MSDE Service Manager to restart SQL services.
Step 6 Select Start > Programs > Cisco Conference Connection > Start Cisco Conference Connection to restart Cisco Conference Connection.
Step 7 Restart the CRA Engine.
a. Select Start > Programs > Cisco CRA Administrator > Application Administrator.
b. On the CRA Application Administration main menu, click Engine.
The system displays the Engine Status page.
c. On the Engine Status page, click Start Engine.
Step 8 Verify that the new database is working by logging into Cisco Conference Connection and creating a new conference.
Understanding Changes Required When Altering the Cisco CallManager Setup
If you upgrade your Cisco CallManager servers after installing Cisco Conference Connection, or alter the Cisco CallManager setup in certain ways, you might need to modify some configuration settings for Cisco Conference Connection to work properly. These topics describe configuration changes needed when upgrading from various versions of Cisco CallManager:
• Changes Required When Upgrading Cisco CallManager (Any Release)
• Changes Required When Changing Directory Support
Changes Required When Upgrading Cisco CallManager (Any Release)
When you upgrade Cisco CallManager, you should make these configuration changes for Cisco Conference Connection:
•Route Pattern—If you created the Cisco Conference Connection route pattern without using the # character (such as 11111.!), you must add # (such as 11111.!#). Select Route Plan > Route Pattern to find and change the route pattern. The "Creating the Route Pattern" section on page 3-10 explains how to create the route pattern.
•JTAPI Subsystem—If the JTAPI subsystem on the Cisco Conference Connection server does not start, upgrade the JTAPI plug-in on the server. The "Fixing JTAPI Subsystem Out-of-Service Status" section on page 7-11 explains how to upgrade the JTAPI plug-in.
Changes Required When Changing Directory Support
You can use a variety of types of directory with Cisco CallManager (such as the built-in DC directory, Microsoft Active Directory, or Netscape Directory). If you decide to convert your Cisco CallManager directory from one type to another, or if you start using a difference Cisco CallManager directory with Cisco Conference Connection, you must install new directory support on the Cisco Conference Connection server and reconfigure the server.
Before You Begin
Before removing the old directory, ensure that you write down the CRA Engine configuration on the Cisco Conference Connection server. In Cisco CRA Application Administration, write down the directory, JTAPI, database, and Conference Director application settings.
Also, in Cisco Conference Connection, write down the list of administrators. Also ensure that the cccadmin user is defined in the new Cisco CallManager directory (as described in the "Creating the Cisco Conference Connection Administrative User" section on page 3-11).
The directory must be working properly with Cisco CallManager before you can reconfigure Cisco Conference Connection.
Procedure
Step 1 On the Cisco Conference Connection server, run this program:
C:\Program Files\Cisco\ConferenceConnection\LDAPSync\RegCopy.exe
Step 2 Follow the on-screen instructions to enter this information:
•The DNS name or IP address of the Cisco CallManager Publisher directory.
•A Cisco CallManager administrator account name and password.
The RegCopy program copies the directory support files required for the type of directory Cisco CallManager is using to the Cisco Conference Connection server. The server can now communicate with the new Cisco CallManager directory.
Step 3 Select Start > Programs > Cisco Conference Connection > Start Cisco Conference Connection to restart Cisco Conference Connection. (If necessary, stop Cisco Conference Connection before restarting it.)
Step 4 Log into Cisco Conference Connection and re-enter the list of administrators, as described in these topics:
• Logging Into Cisco Conference Connection
• Identifying Cisco Conference Connection Administrators
Step 5 Reconfigure the Cisco CRA Engine using the information you saved, as described in these topics:
• Logging In and Configuring Directory Information, page 4-2
• Configuring the Cisco CRA Engine's Database Subsystem, page 4-4
• Configuring the JTAPI Subsystem on the Cisco CRA Engine, page 4-6
• Adding the CTI Port Group, page 4-7
• Configuring the Conference Director IVR Application, page 4-8
Step 6 Verify that the reconfigured directory connection is working properly:
•If you are able to log into the Cisco Conference Connection web interface, then the Cisco Conference Connection directory connection is working.
•For the CRA Engine, any of these conditions indicate a configuration problem:
–The CTI route point does not work. Check the Conference Director application configuration.
–The JTAPI subsystem is out of service. Check the JTAPI configuration. If the configuration is correct, try updating the JTAPI client as described in the "Fixing JTAPI Subsystem Out-of-Service Status" section on page 7-11.
–The database subsystem is out of service. Check the database configuration.
Obtaining Maintenance Releases and Upgrades from Cisco.com
You can obtain maintenance releases and upgrades to Cisco Conference Connection, if any are available, from the cisco.com web site.
Procedure
Step 1 Start the web browser on the Cisco Conference Connection server and open this URL:
http://www.cisco.com/cgi-bin/tablebuild.pl/ccc
Step 2 Select the desired upgrade and download it to the Cisco Conference Connection server.
Step 3 Follow the instructions in the associated readme file to install the upgrade. Also see the "Upgrading or Reinstalling Cisco Conference Connection" section.
