Table Of Contents
Release Notes for Cisco Unified CallManager Release 4.3(2)
Updated November 10, 2008
Table 1 Information Updated Since First Edition of these Release Notes
November 10, 2008
Corrected the URL for the Compatibility Matrix in the "Compatibility Matrix and Supported Upgrades" section
June 13, 2008
Added the "Documentation Updates" section
June 10, 2008
Under Important Notes, added the "CSCso79248 Do Not Run installxml.vbs in Unified CM Release 3.3 and Later" section
April 15, 2008
Under Important Notes, added the "CSCsl14873 Need Exists for AXL API Configuration Document Sample Code to Include HTTP Version" section
March 20, 2008
Added the "Upgrading System Software" section
These release notes describe the new features and caveats in Cisco Unified CallManager Release 4.3(2).
Note To view the release notes for previous versions of Cisco Unified CallManager, go to http://www.cisco.com/en/US/products/sw/voicesw/ps556/prod_release_notes_list.html
Before you install Cisco Unified CallManager, Cisco recommends that you review the "New and Changed Information in Cisco Unified CallManager 4.3(2)" section and the "Caveats" section for information about issues that may affect your system.
To access the documentation suite for voice products, refer to the following URL:
You can access the latest software upgrades and release notes for all versions of Cisco Unified CallManager on Cisco.com (CDC) at the following URL:
These release notes discuss the following topics:
Cisco Unified CallManager, the call-processing component of the Cisco Unified Communications System, extends enterprise telephony features and capabilities to IP phones, media processing devices, voice-over-IP (VoIP) gateways, mobile devices, and multimedia applications.
Make sure that you install and configure Cisco Unified CallManager Release 4.3(2) on a Cisco Media Convergence Server (MCS) or a Cisco-approved HP server configuration or a Cisco-approved IBM server configuration.
To find which Cisco-approved HP servers or Cisco-approved IBM servers support Cisco Unified CallManager Release 4.3(2), refer to the Cisco Unified CallManager Server Support Matrix at http://www.cisco.com/en/US/partner/products/hw/voiceapp/ps378/prod_brochure_list.html.
To see which MCS server is compatible with Cisco Unified CallManager Release 4.3(2), refer to http://www.cisco.com/en/US/products/hw/voiceapp/ps378/prod_models_home.html.
Note Make sure that the matrix indicates that your server model supports Cisco Unified CallManager Release 4.3(2).
Note Some servers that are listed in the compatibility matrix may require additional hardware support for Cisco Unified CallManager Release 4.3(2). Make sure that your server meets the minimum hardware requirements, as indicated in the footnotes of the compatibility matrix. Cisco Unified CallManager requires a minimum of 2 GB of memory, 72 GB disk drive, and 2 GHz processor.
Uninterruptible Power Supply
Ensure that you connect each Cisco Unified CallManager node to an uninterruptible power supply (UPS) to provide backup power and protect your system.
Caution Failure to connect the Cisco Unified Communication Manager nodes to a UPS may result in damage to physical media and require a new installation of Cisco Unified CallManager.
Upgrading System Software
Before you upgrade the software version of Cisco Unified CallManager, verify your current software version.
To do that, open Cisco Unified CallManager Administration. The following information displays:
•Cisco Unified CallManager System version
•Cisco Unified CallManager Administration version
Software Download URLs
You can access the latest software upgrades for Cisco Unified CallManager 4.3 on Cisco.com. Table 2 lists the URLs from which you download the software.
Table 2 Download URLs for Software Upgrades
Software Download URL
Cisco Unified CallManager 4.3(2)
Cisco Security Agent (CSA)
Compatibility Matrix and Supported Upgrades
You can find which application versions are compatible with Cisco Unified CallManager Release 4.3(2) by referring to the Cisco Unified CallManager Compatibility Matrix at http://www.cisco.com/en/US/products/sw/voicesw/ps556/products_device_support_tables_list.html
Note Be aware that the release of Cisco Unified Communication products does not always coincide with Cisco Unified CallManager releases. If a product does not meet the compatibility testing requirements with Cisco Unified CallManager, you need to wait until a compatible version of the product becomes available before you can upgrade to Cisco Unified CallManager Release 4.3(2). For the most current compatibility combinations and defects, refer to the documentation that is distributed with the Cisco Unified IP telephony products.
The documentation that supports Cisco Unified CallManager Release 4.3 resides at
The following section contains important information that may have been unavailable upon the initial release of documentation for Cisco Unified CallManager Release 4.3(x).
CSCso79248 Do Not Run installxml.vbs in Unified CM Release 3.3 and Later
In previous releases, during the Unified CM installation, the installxml.vbs VB script got used to parse all the display instances and rules in the XML files, and upload the data into a table in the default database. In Unified CM Release 3.3 and later, the DBInstall.dll function CInstallXML performs the parsing of the XML files.
The troubleshooting guide for Cisco Unified CallManager (and Cisco CallManager) suggests that you can initialize the installxml.vbs script to fix problems with blank parameters after an upgrade. Do not initialize the installxml.vbs script as the troubleshooting guide recommends. Initializing the script erases all service parameters on the server.
Caution Cisco Unified CM releases 3.3.x or later do not use the installxml.vbs script. Running this script erases all Service Parameters in the server.
CSCsl14873 Need Exists for AXL API Configuration Document Sample Code to Include HTTP Version
The sample C++ and Java code at http://www.cisco.com/en/US/products/sw/voicesw/ps556/products_programming_usage_guide09186a008071edcb.html#wp36137 does not work with Unified CM Release 4.3.
The sample code works when the HTTP version is specified in the request. Therefore, the following line of code in the sample code should be changed as shown below to include the HTTP version:
sAXLSOAPRequest = "POST /CCMApi/AXL/V1/soapisapi.dll\r\n";
sAXLSOAPRequest = "POST /CCMApi/AXL/V1/soapisapi.dll HTTP/1.1\r\n";
CSCea56097 Subscriber Install Aborts Due to DCDir Install Failure
If you receive a "Failure occured trying to determine if Cisco Directory install succeeded. Aborting Cisco CallManager install" error message during installation, you must add the missing Registry entries on the publisher server.
Step 1 Copy the information below into a file.Windows Registry Editor Version 5.00[HKEY_LOCAL_MACHINE\SOFTWARE\Cisco Systems, Inc.\Directory Configuration\AppUsers\IPMASysUser]"UserID"="IPMASysUser""Description"="IPMA SysUser""DCDPW"="0c0a000a2c101c1a1003""Password"="0c0a000a2c101c1a1003"
Step 2 Name the file IPMASysUser.reg.
Step 3 Import the contents into the registry.
Step 4 Restart the installation.
Additional Daylight Savings Time Changes That Are Supported
This release of Cisco Unified CallManager adds Daylight Savings Time support for Australia and Venezuela.
DST Settings for Newfoundland and London Corrected
This release of Cisco Unified CallManager corrects inaccuracies in the beginning/ending dates and times for Daylight Savings Time experienced in Newfoundland and London.
VNC Usage During Busy Hours
Because Virtual Network Computing (VNC) consumes 30 to 40 percent of the CPU of the server, Cisco recommends that you use Virtual Network Computing (VNC) during maintenance windows rather than during busy hours. If you use VNC during busy hours, the high CPU usage may cause Cisco Unified CallManager to generate code yellow alarms.
Cisco Unified CallManager Release 4.3(2) Installation/Upgrade Media
The media provided for this installation/upgrade can be used only for a fresh installation or an upgrade from Cisco Unified CallManager
•Release 3.3.5 to Release 4.3.2
•Release 4.0(2a) to Release 4.3.2
•Release 4.1(3) to Release 4.3.2
•Release 4.2(3) to Release 4.3.2
•Release 4.3.1 to Release 4.3.2.
Using SIP Trunks Between Release 4.x and 5.x Systems
Cisco Unified CallManager Release 5.0 and later, and Cisco Unified CallManager Release 4.0 and later, support TCP and UDP as Transport Types when they are used with SIP trunks. However, release 4.x uses one TCP connection per SIP call; 5.x supports multiple SIP calls over the same TCP connection (referred to as TCP connection reuse).
The following Cisco products support TCP; however, not all support TCP Reuse (see Table 3 for more information):
•Cisco Unified CallManager Release 4.1 - No TCP Connection Reuse
•Cisco Unified CallManager Release 4.2 - No TCP Connection Reuse
•Cisco Unified CallManager Release 4.3 - No TCP Connection Reuse
•Cisco Unified CallManager Release 5.0(2) - TCP Connection Reuse
•Cisco Unified CallManager Release 5.0(4) - TCP Connection Reuse
•Cisco Unified CallManager Release 5.1(1) - TCP Connection Reuse
•Cisco IOS 12.3(8)T and above - TCP Reuse
•Cisco IOS 12.3(8)T and below - No TCP Reuse
Table 3 lists the SIP trunk connectivity that is supported between Cisco Unified CallManager Release 4.x and 5.x and the IOS gateway.
If a Release 5.x system makes multiple calls over a TCP-based SIP trunk to a 4.x system, the 4.x system will only connect one call. The rest of the calls will not get connected.When using SIP trunks between 4.x and 5.x systems, you must configure both systems to use UDP as the Outgoing Transport Type, so calls between the release 4.x and 5.x systems will connect properly. (See Table 3.)
To configure UDP, use Cisco Unified CallManager Administration.
•For Cisco Unified CallManager Release 5.0 and later that is connecting to a Release 4.x system, choose UDP as the Outgoing Transport Type from the SIP Trunk Security Profile Configuration window.
•For Cisco Unified CallManager Release 4.0 and later that is connecting to a Release 5.x system, choose UDP as the Outgoing Transport Type from the Trunk Configuration window.
For more information about SIP trunks, see the Cisco Unified CallManager System Guide and the Cisco Unified CallManager Administration Guide.
CTI Monitored Lines
To calculate the number of CTI monitored lines in a system, use the following formula:
number of pilot point DNs + (number of clients open * number of directory numbers per phone) + (number of parked directory numbers * number of open clients) = CTI Monitored Lines
New and Changed Information in Cisco Unified CallManager 4.3(2)
The following section describes new features and changes that are pertinent to Cisco Unified CallManager, Release 4.3(2).
Upgrading System Software
After you complete the Cisco Unified CallManager upgrade on every server in the cluster, reinstall all Cisco-verified applications and all plug-ins that were previously installed on the server, including the latest version of the Cisco CDR Analysis and Reporting (CAR) plug-in. If you complete an Engineering Special (ES) Cisco Unified CallManager upgrade, you should also reinstall all plug-ins that were previously installed on the server, including the latest version of the Cisco CAR plug-in.
Cisco Unified CallManager Upgrade Utility 4.3(4)
The Cisco Unified CallManager Upgrade Utility, a nonintrusive tool, detects the health of the servers in the Cisco Unified CallManager cluster before you perform an upgrade to Cisco Unified CallManager. This version of Cisco Unified CallManager Upgrade Utility replaces previous versions of Cisco Unified CallManager Upgrade Utility. Cisco Unified CallManager Upgrade Utility 4.3(4) adds support for multiple version upgrades. Use Cisco Unified CallManager Upgrade Utility, version 4.3(4) or later, to detect the health of your servers before you upgrade to Cisco CallManager Release 3.3(5), 4.0(2a), 4.1(2), 4.1(3), 4.2(1), 4.2(2a), 4.2(3), 4.3(1), 4.3(2), 5.0(x), 5.1(x), 6.0(x), and 6.1(1).
Use the Using Cisco Unified CallManager Upgrade Utility 4.3(3) document for information on running Cisco Unified CallManager Upgrade Utility 4.3(4). You can locate this document at the following URL:
G.Clear Codec Support
The G. Clear (Clear channel) codec enables tandem switching of Digital Signal-0 (DS-0) data circuits through a voice network that uses Media Gateway Control Protocol (MGCP) gateways and Cisco Unified CallManager. The MGCP gateway uses T1 PRI DS-0 circuits to communicate with Cisco Unified CallManager.
Figure 1 shows an example of the G.Clear codec configuration in an MGCP network. In this example, legacy video terminals, such as Polycoms, connect to separate PBX switches that are interconnected by the MGCP gateway. The terminals set up individual calls for each DS-0 by using "unrestricted digital information" in the Q.931 bearer capability. Cisco Unified CallManager treats the incoming ISDN signal as a voice call that is using G.Clear.
Figure 1 MGCP Network with G.Clear Codec
The G.Clear codec uses 64 kb/s of bandwidth (not including IP packet overhead), which is similar to the G.711 codec. The Cisco Unified CallManager Region Manager selects the codec of a voice call and prioritizes the G. Clear codec ahead of the G.711 mulaw and G.711 alaw codecs in the Region Manager media table.
You may require the G.Clear codec or the G.729 codec in a region or some other low-bandwidth codec for calls to remote regions. The G.729 codec, which is optimized for speech, uses significantly less bandwidth than the G. Clear codec. Be aware that the G.Clear codec is an option only to explicitly allow it to run in lower bandwidth regions.
G. Clear codec calls require separate DiffServ CodePoint (DSCP) values in the header of IP packets. This differs from traditional voice codecs and video calls. Added service parameters apply these capabilities. See Service Parameter and Enterprise Parameter Changes for more information.
G. Clear codec calls maintain consistency throughout the gateway by using the RTP dynamic payload type 125. The dynamic payload type gets statically allocated by using Cisco Unified CallManager.
The following entities do not get supported or are disabled:
•Session Initiation Protocol (SIP) trunks with the G. Clear codec do not get supported.
•ICTs with the G. Clear codec do not get supported.
•Skinny Client Control Protocol (SCCP) devices with the G. Clear codec do not get supported.
•T1 and E1 CAS with the G. Clear codec do not get supported.
•RSVP with the G. Clear codec does not get supported.
•MLPP over E1 trunks does not get supported.
•Echo cancellation and zero suppression for outbound G. Clear codec calls get disabled.
•Frame aligning individual DS-0 circuits that transit the VoIP network do not get supported because terminal equipment takes responsibility for the bonding of the individual DS-0 circuits that are defined by ITU H.244.
•Fast Start and Media Termination Point Required options in Cisco Unified CallManager do not work with G. Clear that is enabled.
Cisco Unified Communications Manager Administration Configuration Tips
No Cisco Unified CallManager Administration configuration tips exist for this feature.
A check box in the Gateway Configuration window of Cisco Unified CallManager Administration enables or disables G. Clear codec functionality. The default sets the check box to disable (no check mark in the box). Perform the following steps to enable G. Clear codec functionality.
Step 1 In Cisco Unified CallManager Administration, choose Device > Gateway.
Step 2 In the Gateway Configuration window, choose a configured MGCP gateway or click Add to create a new gateway.
Step 3 For a new gateway and in the Gateway Configuration window, input a Domain Name and Description. Choose a Cisco Unified CallManager Group from the drop-down menu as required. Click Save.
Step 4 In the Gateway Configuration window, add Voice Interface Cards as required. Choose network modules that support T1 VWICs. Click Save.
Step 5 On the right-hand side of the Gateway Configuration window and below the End Point Identifier section, click on the icon adjacent to Begin Port. Select T1 PRI as the protocol for each port.
Step 6 Interface Information section, check the G. Clear codec box to enable the functionality.
Step 7 If the system prompts you to reset the interface, reset.
Note You must enable the G. Clear Bandwidth Override if you have low-bandwidth codec regions, such as G.711 or G.729. See Service Parameter and Enterprise Parameter Changes for more information.
Service Parameter and Enterprise Parameter Changes
Seven service parameters exist for Differentiated Services Code Point (DSCP) values for Quality of Service (QoS) and for overriding bandwidth for G. Clear calls.
Tip To access the following DSCP service parameters in Cisco Unified CallManager Administration, choose Server > Service Parameters. To display help for the service parameter, click the link for the service parameter in the Service Parameter Configuration window.
•DSCP for G.Clear Calls
•DSCP for Priority G.Clear Calls
•DSCP for Immediate G.Clear Calls
•DSCP for Flash G.Clear Calls
•DSCP for Flash Override G.Clear Calls
•DSCP for Executive Override G.Clear Calls
Note The Priority, Immediate, Flash, Flash Override, and Executive Override values correspond to discrete MLPP values.
Many DSCP options display for the service parameters; for example, AF11 DSCP (001010), AF12 DSCP (001100), and AF13 DSCP (001110).
Tip To access the G. Clear Bandwidth Override service parameter in Cisco Unified CallManager Administration, choose Server > Service Parameters. Scroll down to the Clusterwide Parameters (System-Location and Region) and click True. The default specifies False or no override for this required field. To display help for the service parameter, click the link for the service parameter in the Service Parameter Configuration window.
Installation/Upgrade (Migration) Considerations
No additional network installation or upgrade considerations exist. Ensure G. Clear codec is enabled on the T1 PRI trunks that require the codec and that the bandwidth override service parameter is enabled for the regions that provide less than 64 kb/s of bandwidth per call.
No new port requirement exists.
No Cisco Unified Serviceability considerations exist for this feature. This feature requires no new alarms or counts to be added.
No BAT considerations exist for this feature.
No CAR/CDR considerations exist for this feature.
No security considerations exist for this feature.
AXL and CTI Considerations
AXL supports an optional tag, GClearEnable, in the add/update/get MGCPAPI; this tag applies to T1PRI trunks. The user can use the AXL MGCPAPI to enable or disable the G. Clear support for T1 PRI trunks.
No CTI considerations exist for this feature.
A negligible amount of delay occurs to MGCP processing.
No software, hardware, or firmware restrictions exist.
No accessibility restrictions or special configuration considerations exist.
For More Information
For the latest Cisco Unified CallManager Administration 4.X documentation, refer to the following documents:
•Cisco Unified CallManager Features and Services Guide, Release 4.2(3)
•Cisco Unified CallManager Administration Guide, Release 4.2(3)
•Cisco Unified CallManager System Guide, Release 4.2(3)
The following sections contain information on how to obtain the latest resolved caveat information and descriptions of open caveats of severity level 1, 2, and 3.
Caveats describe unexpected behavior on a Cisco Unified CallManager server. Severity 1 caveats represent the most serious caveats, severity 2 caveats represent less serious caveats, and severity 3 caveats represent moderate caveats.
You can find the latest resolved caveat information for Cisco Unified CallManager Release 4.3(2) by using Bug Toolkit, which is an online tool that is available for customers to query defects according to their own needs.
Tip You need an account with Cisco.com (Cisco Connection Online) to use the Bug Toolkit to find open and resolved caveats of any severity for any release.
To access the Bug Toolkit, log on to http://tools.cisco.com/Support/BugToolKit/action.do?hdnAction=searchBugs
Using Bug Toolkit
Known problems (bugs) get graded according to severity level. These release notes contain descriptions of
•All severity level 1 or 2 bugs.
•Significant severity level 3 bugs.
You can search for problems by using the Cisco Software Bug Toolkit.
To access Bug Toolkit, you need the following items:
•Cisco.com user ID and password
To use the Software Bug Toolkit, follow these steps:
Step 1 To access the Bug Toolkit, go to http://tools.cisco.com/Support/BugToolKit/action.do?hdnAction=searchBugs.
Step 2 Log in with your Cisco.com user ID and password.
Step 3 To look for information about a specific problem, enter the bug ID number in the "Search for Bug ID" field then, click Go.
For information about how to search for bugs, create saved searches, create bug groups, and so on, click Help in the Bug Toolkit window.
Table 4 describes possible unexpected behaviors in Cisco Unified CallManager Release 4.3(2), which are sorted by component.
Tip For more information about an individual defect, click the associated Identifier in Table 6 to access the online record for that defect, including workarounds.
Understanding the Fixed-in Version and the Integrated-in Fields in the Online Defect Record
When you open the online record for a defect, you may see data in the "First Fixed-in Version" or "Integrated-in" fields. The information that displays in these fields identifies the list of Cisco Unified CallManager interim versions in which the defect was fixed. These interim versions then get integrated into Cisco Unified CallManager releases.
Some more clearly defined versions include identification for Engineering Specials (ES) or Service Releases (SR); for example 03.3(04)ES29 and 04.0(02a)SR1. However, the version information that displays for the Cisco Unified CallManager maintenance releases may not be as clearly identified.
The following examples show how you can decode the maintenance release interim version information. These examples show you the format of the interim version along with the corresponding Cisco Unified CallManager release that includes that interim version. You can use these examples as guidance to better understand the presentation of information in these fields.
•005.000(000.123) = Cisco Unified CallManager Release 5.0(1)
•005.000(001.008) = Cisco Unified CallManager Release 5.0(2)
•005.001(002.201) = Cisco Unified CallManager Release 5.1(3)
•006.000(000.123) = Cisco Unified Communications Manager Release 6.0(1)
Note Because defect status continually changes, be aware that Table 4 reflects a snapshot of the defects that were open at the time this report was compiled. For an updated view of open defects, access Bug Toolkit and follow the instructions as described in the "Using Bug Toolkit" section.
Tip Bug Toolkit requires that you have an account with Cisco.com (Cisco Connection Online). By using the Bug Toolkit, you can find caveats of any severity for any release. Bug Toolkit may also provide a more current listing than this document provides. To access the Bug Toolkit, log on to http://tools.cisco.com/Support/BugToolKit/action.do?hdnAction=searchBugs.
Note For complete Cisco Unified IP Phone firmware release note information, refer to the applicable firmware release notes for your specific Cisco Unified IP Phone at the following URL:
This section includes the following topics:
This section includes information about errors in the Cisco Unified CallManager Documentation suite:
Music on Hold
The Cisco Unified CallManager Features and Services Guide incorrectly states that you can set up music on hold to work with Cisco Unified CallManager Attendant Console by choosing an audio source from the Network Hold Audio Source and the User Hold MOH Audio Source drop-down list boxes in the Device Pool window. To use music on hold with Cisco Unified CallManager Attendant Console, you need to create a common profile and add the attendant console pilot points to that common profile. For information on setting up a common profile, refer to the Cisco Unified CallManager Administration Guide.
4.3(2) Online Help Contents displays Cisco Unified CallManager Security Guide Twice
The Cisco Unified CallManager 4.3(2) online help displays the Cisco Unified CallManager Security Guide twice in the Contents pane on the left. The second Contents listing for the security guide produces "page not found" errors; however, you can use the first security guide listing to successfully access the help pages.
4.3(2) Online Help - Cisco Unified CallManager Troubleshooting Guide Does Not Display in the Table of Contents
In this release, the Cisco Unified CallManager Troubleshooting Guide does not display in the Table of Contents; however, you can access the troubleshooting guide by clicking the PDF button at the top of the help banner and selecting the Troubleshooting Guide PDF file, or you can access it through the following link:
CTIManager Service Parameters
In previous releases of the Cisco Unified CallManager System Guide, the default values of two service parameters described in the Computer Telephony Integration chapter were incorrectly stated. The following text correctly describes these service parameters:
CTIManager provides two advanced, clusterwide service parameters that are used in conjunction with the CTI Super Provider capability:
•Maximum Devices Per Provider—This parameter specifies the maximum number of devices that a single CTI application can open. The default specifies 2000 devices.
•Maximum Devices Per Node—This parameter specifies the maximum number of devices that all CTI applications can open on any CTIManager node in the Cisco Unified CallManager system. The default specifies 800 devices.
This section contains changes that have occurred since the original release of the Cisco Unified CallManager Release 4.2 documentation. These changes may not appear in the current documentation or the online help for the Cisco Unified CallManager application:
Unable to Place Calls to Pilot Point
The Unable to Place Calls to Pilot Point section of the Cisco Unified CallManager Troubleshooting Guide explains that users must configure a user that is named "ac" and associate the attendant phone and pilot points with that user, or the user gets a reorder tone when the user calls the pilot point. The administrator also needs to restart the Cisco CTI Manager and Cisco Telephony Call Dispatcher service.
TFTP Process Overview for SCCP Devices
The following text updates the fourth paragraph in the TFTP Process Overview for SCCP Devices section of the Cisco TFTP chapter in the Cisco Unified CallManager System Guide to provide more information and more clarity:
The device requests a configuration file from the TFTP server. The TFTP server searches three internal caches, the disk, and then alternate Cisco file servers (if specified) for the configuration file. If the TFTP server finds the configuration file, it sends it to the device. If the configuration file provides Cisco Unified CallManager names, the device resolves the name by using DNS and opens a connection to the Cisco Unified CallManager. If the device does not receive an IP address or name, it uses the TFTP server name or IP address for setting up its registration connection.
This section lists new and additional information that the current version of the Cisco Unified CallManager documentation may not include:
CTI Monitored Lines
To calculate the number of CTI monitored lines in a system, use the following formula:
number of pilot point DNs + (number of clients open * number of directory numbers per phone) + (number of parked directory numbers * number of open clients) = CTI Monitored Lines
The Cisco Unified CallManager Troubleshooting Guide does not explain that the Cisco Unified CallManager Attendant Console does not run on a PC that does not have local administration rights, unless you change the permissions for the appropriate directories.
•On a PC that runs Windows NT, change the security on the KEY_LOCAL_MACHINE\Software\Cisco Systems, Inc. registry key, so the attendants have full access to this key and all subkeys.
•On a PC that runs Windows 2000, change the NTFS permissions to allow full access to c:\program files\cisco\call manager attendant console\ and all subdirectories and files and change the security on the KEY_LOCAL_MACHINE\Software\Cisco Systems, Inc. registry key, so the attendants have full access to this key and all subkeys.
Attendant Console Upgrade
The Cisco Unified CallManager Troubleshooting Guide does not explain what you need to do if the hunt group and CTI route point give a fast busy after a Cisco Unified CallManager Attendant Console upgrade. After you verify your Cisco Unified CallManager Attendant Console configuration as described in the Cisco Unified CallManager Features and Services Guide, reset the Cisco CTI Manager and Cisco Telephony Call Dispatcher services.
Maximum Number of CTI-Controlled Devices
The Computer Telephony Integration chapter of the Cisco Unified CallManager System Guide omitted the maximum number of CTI-controlled devices per node. The maximum number of CTI-controlled devices per node varies by server class as follows:
•MCS-7825 and MCS-7835 servers support up to 800 CTI-controlled devices per node.
•MCS-7845 servers support up to 2500 CTI-controlled devices per node.
For troubleshooting information, refer to the Troubleshooting Guide for Cisco Unified CallManager, Release 4.2(3). This document provides troubleshooting procedures for Cisco Unified CallManager systems. The Troubleshooting Guide for Cisco Unified CallManager provides guidance for network administrators who are responsible for managing the Cisco Unified CallManager system, for enterprise managers, and for employees. This document does not cover every possible trouble event that might occur on a Cisco Unified CallManager system but instead focuses on those events that are frequently seen by the Cisco Technical Assistance Center (TAC).
Obtaining Documentation and Submitting a Service Request
For information on obtaining documentation, submitting a service request, and gathering additional information, see the monthly What's New in Cisco Product Documentation, which also lists all new and revised Cisco technical documentation, at:
Subscribe to the What's New in Cisco Product Documentation as a Really Simple Syndication (RSS) feed and set content to be delivered directly to your desktop using a reader application. The RSS feeds are a free service and Cisco currently supports RSS version 2.0.
CCDE, CCENT, Cisco Eos, Cisco Lumin, Cisco Nexus, Cisco StadiumVision, Cisco TelePresence, Cisco WebEx, the Cisco logo, DCE, and Welcome to the Human Network are trademarks; Changing the Way We Work, Live, Play, and Learn and Cisco Store are service marks; and Access Registrar, Aironet, AsyncOS, Bringing the Meeting To You, Catalyst, CCDA, CCDP, CCIE, CCIP, CCNA, CCNP, CCSP, CCVP, Cisco, the Cisco Certified Internetwork Expert logo, Cisco IOS, Cisco Press, Cisco Systems, Cisco Systems Capital, the Cisco Systems logo, Cisco Unity, Collaboration Without Limitation, EtherFast, EtherSwitch, Event Center, Fast Step, Follow Me Browsing, FormShare, GigaDrive, HomeLink, Internet Quotient, IOS, iPhone, iQuick Study, IronPort, the IronPort logo, LightStream, Linksys, MediaTone, MeetingPlace, MeetingPlace Chime Sound, MGX, Networkers, Networking Academy, Network Registrar, PCNow, PIX, PowerPanels, ProConnect, ScriptShare, SenderBase, SMARTnet, Spectrum Expert, StackWise, The Fastest Way to Increase Your Internet Quotient, TransPath, WebEx, and the WebEx logo are registered trademarks of Cisco Systems, Inc. and/or its affiliates in the United States and certain other countries.
All other trademarks mentioned in this document or website are the property of their respective owners. The use of the word partner does not imply a partnership relationship between Cisco and any other company. (0809R)