Cisco Conference Connection

This FAQ document is intended to answer some of the primary questions about Cisco Conference Connection (CCC).

A. CCC operates on the Cisco MCS-7845, Cisco MCS-7825-800, MCS-7825-1133, MCS-7835-1000 and MCS-7835-1266 Media Convergence Servers as well as the Compaq DL320 and DL380 servers. The server must be dedicated to the CCC application. You cannot deploy Cisco CallManager or other applications on the same server. IBM, ICS7750 and other platforms are not supported at this time.

A. You can use one of these solutions to resolve your Metalink problem:

• Remove Metalink and upgrade to CCC 1.2 (no Metalink software is required for CCC 1.2). If you upgrade to CCC 1.2, additional features such as password protection for conferences and end of conference warning are available for use.

• Examine the Metalink logs and attempt to debug the problem.

Note: Metalink should run from the PUBLISHER DC directory.

A. CCC must have a static address because the SlaveTable in DCMS database uses the IP address to make connection to the Cisco CallManager.

Note: It is good practice to use static addresses for server products.

A. Upgrade the JTAPI plugin for Cisco CallManager. Go to the Cisco CallManager Administration page and click Application > Install Plugins. Download Cisco JTAPI and install on the CCC server.

A. Complete these steps to properly uninstall CCC:

1. Uninstall the applications.
2. Reboot the server to remove any files that were not deleted.
3. Remove the C:\MSSQL7 folder after the uninstall in complete in order to delete the Microsoft Data Engine (MSDE) installation. This assumes that you have no conference data in the database. Otherwise, the data files that persist can cause problems later.

   Note: Step 3 is optional, but recommended.

A. When you list users in CCC, all users that are present in the DC Directory are listed. This includes Extension Mobility application User, JTAPI application user, Attendant Console user, etc. Set a user description to CiscoPrivateUser in order to hide the user from the Cisco CallManager user administrator.

A. In CCC version 1.1(3), Active Directory is not supported. However, CCC version 1.2 and later directly support Active Directory and Netscape directory. If you use CCC version 1.2 or later, there is no need to perform any synchronization, and all user authentications are done based on the directory configuration from the Cisco CallManager.

A. The H.323 gateway device must not be within a group or list that contains music on hold resources.

A. You can restore the original English language .wav files (prompts) from default backup subdirectories, which are created and saved in these three directories:

• C:\Program Files\wfavvid\Prompts\system\en_US

• C:\Program Files\wfavvid\Prompts\user\en_US

• C:\Program Files\Cisco\ConferenceConnection\Prompts

A. Dropped calls are almost never caused by CCC. Dropped calls are most frequently caused by something external such as Cisco CallManager, gateway problems, or location problems.

A. Complete these steps in order to change the CCC password:

1. In Windows Explorer, locate and double-click the pwdupdate.vbs. The full pathname for this file is C:\Program Files\Cisco\Conference Connection\server\pwdupdate.vbs file.
2. Enter the correct db password, confirm it, and press Enter.
3. Use the Start menu to restart the CCC service.

A. CCC 1.2 has Customer Response Applications component 2.2(4), which is not compatible with CRS 3.0. Two instances of the Application engine cannot coexist on one server, or share the same profiles.

Note: The CRS 2.2(5) SPB is compatible with CCC and is recommended to resolve various issues.

A. There are three access levels: guest, regular, and administrator. This table describes the available functions for the three access levels.

	Access Level
Function	Guest	Regular	Administrator
Conferences in Progress	Yes	Yes	Yes
Scheduled Conferences	Yes	Yes	Yes
Past Conferences	Yes	Yes	Yes
Add a Conference	—	Yes	Yes
List Users	—	—	Yes
Administration Tasks and Reports	—	—	Yes

In CCC 1.1(x), users are in the SQL database on the CCC server itself, so they can be assigned different access levels.

In CCC 1.2, users are pulled from whatever directory the Cisco CallManager uses (for example, DC Directory). Everyone in the search base is a regular access level user. Certain users can be marked as administrator access level users. In other words, there is no Guest privilege level, only Regular and Administrator in CCC 1.2.

A. There is no communication between different CCC servers. It is possible for you to conference two conferences that are hosted by different CCC servers, but this practice is not recommended.

A. CCC 1.1 had the ability to limit user access to the scheduling page. However, CCC 1.2 does not have this ability.

In order to limit user access to the scheduling page for CCC 1.2, front end the CCC server with a proxy server and then limit access to the CCC server.

You can also limit user access with these methods, but Cisco does not recommend the use of these methods:

• Use Access Control Lists (ACLs) in Cisco switches and routers—This method does not work well in a Dynamic Host Configuration Protocol (DHCP) environment.

• Use Internet Information Server (IIS) security and access rights—This method can be overly complex and difficult to manage.

A. The data is updated at a certain interval of time. The odbcagr.txt file contains a parameter called TimeInterval, which is set to 600 seconds by default—updates occur every 600 seconds. You can change this value if required. However, a change to a very small value is not recommended, as this overloads the Cisco CallManager.

A. When you are logged in as a regular user in CCC, you can create conferences up to four hours long. As an administrator, you can create conferences up to 24 hours long. You can then set up a speed dial so it dials the GWPrefix number, conference ID and number, then the caller is joined into the conference.

A. Verify that the user has the n.!# Route Pattern (RP), where n is any number that represents the RP. In addition, the user must have .!# for call termination, because Cisco CallManager expects that for call termination.

A. Complete these steps if a user cannot access or log into the CCC web interface:

1. Check the URL the user uses for the CCC web interface.

2. Make sure the user uses the Cisco CallManager user ID and password.

3. Make sure the directory server functions correctly and that there is a network path between the CCC and the directory. CCC looks up the user ID and password in the Cisco CallManager directory to validate login attempts. If the directory is unavailable, no one can log into the CCC.

4. If the user receives a Cannot find server or DNS error message, either the URL is incorrect or the server is not available. Verify that the CCC server runs properly.

5. Verify that DNS works properly and names can be resolved by the CCC server.

6. Verify that the Cisco CallManager directory server is available. Check the c:\dcdsrvr\logs event log for errors.

A. Verify the accuracy of the URL for the service. The URL is case sensitive.