Release Notes for Cisco CallManager Release 3.0(10) Original CCO appearance: June 20, 2001 Revised: July 2, 2001 These release notes describe the new features and caveats for Cisco CallManager Release 3.0(10). For a list of the open and resolved caveats for Cisco CallManager Release 3.0(10), see “Resolved Caveats” section on page 20 and “Open Caveats” section on page 64. These release notes are updated every maintenance and major release.
Contents Contents These release notes discuss the following topics: • Introduction, page 2 • System Requirements, page 3 • Related Documentation, page 3 • New and Changed Information, page 4 • Resolved Caveats, page 20 • Open Caveats, page 64 • Documentation Updates, page 82 • Obtaining Documentation, page 100 • Obtaining Technical Assistance, page 102 Introduction Cisco CallManager, a network business communication system, provides high-quality telephony over IP networks.
System Requirements System Requirements Make sure Cisco CallManager Release 3.0 is installed and configured on a Cisco Media Convergence Server. You may also install Cisco CallManager on a Cisco-approved Compaq server configuration or a Cisco-approved IBM server configuration. Caution The installation will not complete if you do not follow the exact configuration. Access the correct Cisco-approved server configuration for IBM server or Compaq server at http://www.cisco.
New and Changed Information • Cisco IP Phone 7900 Family Administration Guide • Configuring Remote Serviceability for Cisco CallManager Release 3.0 • Using Cisco CallManager Trace Gathering Tool for Diagnostic Traces • Cisco WebAttendant Quick Start Guide • Cisco WebAttendant User Guide • Cisco JTAPI Developer Guide • Cisco TAPI Developer Guide • Software License Agreement New and Changed Information New Software Features for Release 3.0(10) Cisco CallManager Release 3.
New and Changed Information Backup Utility The Backup Utility now creates backup files with the .sti extension instead of using the .tar extension. If you have .tar files already on your system, such as from an upgrade, the Backup Utility restores those files as well, but all current back ups are saved as a .sti extension. Important Notes for Release 3.0(10) Compatibility Matrix Table 1 lists versions with which Cisco CallManager 3.0(10) has been tested.
New and Changed Information Table 1 Compatibility Matrix Component/Application Version Tested Cisco Unity 2.4.6.102 JTAPI 1.1(1.19) TAPI 3.0(1.18) Service Parameters During an upgrade, Cisco CallManager does not overwrite service parameter values that the system administrator manually configures in Cisco CallManager Administration. New Software Features in Release 3.0(9) The following section contains new and changed software features in Cisco CallManager Release 3.0(9).
New and Changed Information Service Parameters Cisco CallManager Release 3.0(9) supports new service parameters. Refer to Table 9 on page 83 for a complete listing of all service parameters, which includes descriptions and default values, that were not included in Release 3.0(5) of Cisco CallManager Administration Guide. New Software Features in Release 3.0(8) The following sections contain new and changed software features in Cisco CallManager Release 3.0(8).
New and Changed Information New Software Features in Release 3.0(7) Cisco CallManager Release 3.0(7), a maintenance release, adds no new features. Refer to the “Resolved Caveats - Release 3.0(7)” section on page 47 for more information. Important Notes for Release 3.0(7) Service Parameter Restart Conditions If you modify any of the service parameters in the following list, you must restart the Cisco CallManager 3.0(7) before the modifications take effect.
New and Changed Information Cisco IP Phone 7910 and Cisco IP Phone 7940 Compatibility Issue Cisco IP Phone 7910 and Cisco IP Phone 7940 are only supported by Cisco CallManager Release 3.0(5a) and higher. If you are running an earlier version, you must upgrade to a later version at http://www.cisco.com/cgi-bin/tablebuild.pl/callmgr. New Software Features in Release 3.0(6) The following sections contain new and changed hardware and software features in Release 3.0(6) of Cisco CallManager.
New and Changed Information Tech Prefixes Cisco CallManager Release 3.0(6) supports tech prefixes in the Gatekeeper. To properly configure the Cisco CallManager to register with a tech prefix you must go to service parameters and perform the following steps: Step 1 Choose Cisco CallManager. Step 2 Choose Cisco CallManager from Configured Services. Step 3 Enter GateKeeperSupportedPrefix in the Params section. Step 4 Choose String as the type. Step 5 Click update.
New and Changed Information New Hardware and Software Features in Release 3.0(5a) The following sections contain new and changed hardware and software features in Release 3.0(5a) of Cisco CallManager. Support for New Cisco IP Phones These new phone models, Cisco IP Phone 7910, Cisco IP Phone 7910-SW+, and Cisco IP Phone 7940, broaden the product line of Cisco IP phones.
New and Changed Information • Cisco IP Phone 7940—This is a two-line Cisco IP Phone with the following features: – Line buttons assignable as either lines or speed dials – Pixel-based display – Four soft keys with context-sensitive features – Five fixed function buttons (Messages, Services, Information, Directory, Settings) – Full-duplex speakerphone – Message waiting indicator – Dual 10/100 BaseT (RJ-45) connectors into dual port 10/100 BaseT switch – Provision for either inline or local plug power TA
New and Changed Information • Simpler configuration—Previous versions of Cisco CallManager required all Cisco CallManagers in separate clusters to be configured in the Cisco MCM as a source address/destination address (SA/DA) pair. Registration by cluster pairs meant that for a ten-site system, 90 (9 x 10) separate entries would be required in the Cisco MCM configuration.
New and Changed Information applications server. When the user selects one of the services, the service emits XML tags to the same phone according to the design behavior of the service. XML tags for menu display, item selection, graphics display, and character display are available. Customers may create HTML/XML services that are accessible to pixel-based Cisco IP Phone displays.
New and Changed Information Additional MGCP Support for Cisco VoIP Gateways Media Gateway Configuration Protocol (MGCP) support provides two primary benefits over H.323 support. First, MGCP provides a centralized dial plan. An H.323 network requires that the dial plan for each gateway be statically configured. Every dial plan change requires updating the dial plan in every gateway. MGCP provides centralized dial plan configuration support at the Cisco CallManager. Cisco CallManager Release 3.
New and Changed Information through the Cisco AVVID network, out of TDM networks to another AMIS-equivalent voice messaging system. The capabilities allowed include the ability to reply to and forward messages from one messaging system to another. User Interface Enhancements Cisco CallManager Release 3.
New and Changed Information • Cisco WebAttendant Configuration—A new set of added pages enables administrators to configure Cisco WebAttendant pilot points, hunt groups, and users. To access this page from the main Cisco CallManager Administration page, select Service > Cisco WebAttendant. • Gateway Configuration—The modified Cisco CallManager Administration interface includes support for additional MGCP gateways, such as Cisco 2600 Series gateways with FXS and FXO analog interfaces.
New and Changed Information The following example highlights the difference: The Cisco IP Interactive Voice Response System typically opens several CTI route points and CTI ports; it will always open a single CTI connection to a Cisco CallManager in the cluster. The 400 connection limit applies to the CTI connection and not the CTI ports or route points. BAT Reinstallation Administrators must reinstall BAT after installing Cisco CallManager 3.0(5a) because of a change made to the database.
New and Changed Information Note • Cluster-2 configures 5 intercluster trunks (to CCM-A, CCM-B, and CCM-C in Cluster1 and to CCM-F and CCM-G in Cluster-3). • Cluster-3 configures 5 intercluster trunks (to CCM-A, CCM-B, and CCM-C in Cluster-1 and to CCM-D and CCM-E in Cluster-2).
Resolved Caveats Resolved Caveats Resolved Caveats - Release 3.0(10) Table 2 lists and describes Caveats that were resolved in Cisco CallManager Release 3.0(10). Note If you have an account with Cisco.com (Cisco Connection Online), you can use the Bug Toolkit to find caveats of any severity for any release. To access the Bug Toolkit, log on to http://www.cisco.com/support/bugtools. Table 2 Cisco CallManager Release 3.
Resolved Caveats Table 2 Cisco CallManager Release 3.0(10) Resolved Caveats (continued) DDTS Number Summary Explanation CSCds43704 Call looping uses CPU and other resources in Cisco CallManager. A Cisco CallManager code change fixes this problem. CSCds74822 Service Configuration application does A Cisco CallManager code change fixes not function properly. this behavior.
Resolved Caveats Table 2 Cisco CallManager Release 3.0(10) Resolved Caveats (continued) DDTS Number Summary Explanation CSCdt42403 User loses a call after transferring toward a busy line. A Cisco CallManager code change corrects this behavior. This item duplicates CSCdt45632, CSCdt82239, and CSCdr58998. CSCdt47805 High CPU usage during directory searches from Cisco IP Phone 7960 occurs.
Resolved Caveats Table 2 Cisco CallManager Release 3.0(10) Resolved Caveats (continued) DDTS Number Summary CSCdt71276 Explanation Backing up Media Convergence Server The priority of the backup engine was takes about 50 minutes; in previous reduced, so it does not interfere with the versions, this took much less time. operation of the Cisco CallManager. A code change corrects this behavior, so the backup takes less time.
Resolved Caveats Table 2 Cisco CallManager Release 3.0(10) Resolved Caveats (continued) DDTS Number Summary Explanation CSCdt75620 A need exists for TAPI dwCalledID to reflect original called party. A code change ensures that TAPI dwCalledID reflects the original called party. CSCdt75990 Calls with compatible regions and capabilities fail. A code change resolves this behavior. CSCdt78337 If call park range overlaps at pattern, Cisco CallManager router thread may stop.
Resolved Caveats Table 2 Cisco CallManager Release 3.0(10) Resolved Caveats (continued) DDTS Number Summary Explanation CSCdt83902 User cannot answer a consult transfer. The fix releases the answer thread when applications invoke an answer request on a consult call that is cleared due to transfer. CSCdt84284 AVVID: Cisco WebAttendent client does not have access to wausers share.
Resolved Caveats Table 2 Cisco CallManager Release 3.0(10) Resolved Caveats (continued) DDTS Number Summary Explanation CSCdt94077 Calls going out through a digital gateway were being dropped after one Cisco CallManager in a cluster fails in a certain way (links to other Cisco CallManagers in the cluster stay up, even though its devices fail over), and its phones and gateways have registered with the backup Cisco CallManager. Device tables do not update correctly after failover occurs.
Resolved Caveats Table 2 Cisco CallManager Release 3.0(10) Resolved Caveats (continued) DDTS Number Summary Explanation CSCdt96338 Intercluster calls stop at 248 active calls per H.323 device. A code change allows 360 calls to be in place simultaneously. The simultaneous call limit for H.323 device equals 248 when it should be 360. Users experience this problem only with Cisco CallManager Release 3.0(8) or earlier. CSCdt96745 H.245 negotiation fails on intercluster trunk for forwarded call.
Resolved Caveats Table 2 Cisco CallManager Release 3.0(10) Resolved Caveats (continued) DDTS Number Summary Explanation CSCdu04286 After conferencing, if only two parties A Cisco CallManager code change corrects are left in the conference, TAPI redirect this behavior. causes both parties to be dropped instead of just the one doing the redirect. CSCdu05420 Locations bandwidth takes more than 20 hours to free up. CSCdu05485 Sending out 3.
Resolved Caveats Table 2 Cisco CallManager Release 3.0(10) Resolved Caveats (continued) DDTS Number Summary Explanation CSCdu10146 A caller initiates a call to a low bandwidth (30 KB) location with codec G.729. The caller initiates a conference using a software conference bridge, and the codec changes to G.711. The called party in the low bandwidth location changes to G.711 and joins the conference even though not enough bandwidth exists.
Resolved Caveats Table 2 Cisco CallManager Release 3.0(10) Resolved Caveats (continued) DDTS Number Summary CSCdu68211 Explanation The default SdlTraceTypeFlags value is The default value SdlTraceTypeFlags inadequate for debugging needs. changed to 0x00004B15. This change only occurs on new installs. On upgrade installations, the previous setting for the "SDLTraceTypeFlags" service parameter remains at 0x00004B05. Customers who install Cisco CallManager 3.0(10) for the first time receive this bug fix.
Resolved Caveats Table 2 Cisco CallManager Release 3.0(10) Resolved Caveats (continued) DDTS Number Summary Explanation CSCdu18646 An unstable modem connection exists through WS-X6608 and WS-X6624 gateways. This version includes new loads that have been designed to provide V.34 connection speeds with a connection rate of 85 percent or higher. Speeds in the V.90 range are possible, but not guaranteed. CSCdu29527 Phones at remote site continue to reset when secondary is server down.
Resolved Caveats Resolved Caveats - Release 3.0(9) Table 3 lists and describes Caveats that were resolved in Cisco CallManager Release 3.0(9) Note If you have an account with Cisco.com (Cisco Connection Online), you can use the Bug Toolkit to find caveats of any severity for any release. To access the Bug Toolkit, log on to http://www.cisco.com/support/bugtools. Table 3 Cisco CallManager Release 3.
Resolved Caveats Table 3 Cisco CallManager Release 3.0(9) Resolved Caveats (continued) DDTS Number Summary Explanation CSCds03249 The label field on phone directory number page no longer exists. Label line setting for phone is inoperable. Customer has a requirement to change the display of the line buttons to show information other than the directory number.
Resolved Caveats Table 3 Cisco CallManager Release 3.0(9) Resolved Caveats (continued) DDTS Number Summary CSCds74363 Explanation User can delete route list even if it is in The code now checks DeviceNumPlanMap table to see whether the route list is associuse. ated with any route pattern. CSCds74374 An error occurs while deleting an active A code change interprets the error and gives route filter. it a clearer message.
Resolved Caveats Table 3 Cisco CallManager Release 3.0(9) Resolved Caveats (continued) DDTS Number Summary Explanation CSCdt11252 Call transfer fails and throws a platform A Cisco CallManager software exception. modification implements the NEVER_CONNECT option for the CTI enable consultation transfer call.
Resolved Caveats Table 3 Cisco CallManager Release 3.0(9) Resolved Caveats (continued) DDTS Number Summary Explanation CSCdt27696 The message content returned incorrectly when you delete a server. The return error message now states “some devices are using the server.” CSCdt29654 A call to an active phone may result in negative bandwidth. A Cisco CallManager code change corrects this behavior. CSCdt30922 User cannot delete Gatekeeper on the first attempt when Anonymous is set.
Resolved Caveats Table 3 Cisco CallManager Release 3.0(9) Resolved Caveats (continued) DDTS Number Summary Explanation CSCdt44128 6608 sends disconnect when it does not A Cisco CallManager service parameter receive an alerting fast enough. was extended to correct this behavior. CSCdt48748 When Windows 2000 Administrator account name is changed, i.e., to "callmngradmin,” the installation reports an error changing the admin password. After upgrading to Cisco CallManager 3.
Resolved Caveats Table 3 Cisco CallManager Release 3.0(9) Resolved Caveats (continued) DDTS Number Summary Explanation CSCdt57397 The file, ringlist.xml, is overwritten during upgrades, which causes the Cisco IP Phone 7960 to reset. A code change causes the ringlist to remain after upgrade. CSCdt58120 Cisco CallManager update should not ask if machine is publisher/subscriber A Cisco CallManager code change ensures that the software automatically detects the machine type.
Resolved Caveats Resolved Caveats - Release 3.0(8) Table 4 lists and describes caveats that were resolved in Cisco CallManager Release 3.0(8). Note If you have an account with Cisco.com (Cisco Connection Online), you can use the Bug Toolkit to find caveats of any severity for any release. To access the Bug Toolkit, log on to http://www.cisco.com/support/bugtools. Table 4 Cisco CallManager Release 3.
Resolved Caveats Table 4 Cisco CallManager Release 3.0(8) Resolved Caveats (continued) DDTS Number Summary Explanation CSCds13646 AVVID: SNMP agent is missing on The vendor’s SNMP Extension Agent Cisco CallManager. MIBII Host Branch provides the functionalities for browsing the MIB II tree through the SNMP Agent; therefore, it is not in the domain of the Cisco CallManager SNMP Extension Agent.
Resolved Caveats Table 4 Cisco CallManager Release 3.0(8) Resolved Caveats (continued) DDTS Number Summary Explanation CSCds72125 DisconnectedEvent is received with Cause=CtiResourcesNAvail. When an external call called a CTI route point, the call was redirected back and forth between a CTI port and an IP phone several times. A code change fixed this problem. CSCds74298 A call to a shared line results in unreleased bandwidth.
Resolved Caveats Table 4 Cisco CallManager Release 3.0(8) Resolved Caveats (continued) DDTS Number Summary Explanation CSCds91320 AVVID: PerfMon ccmActivePhones counter is incorrect. A Cisco CallManager code change allows the PerfMon counter to display correctly. CSCdt02726 Consult call fails throwing exception. A Cisco CallManager code change corrects this problem. CSCdt04309 Disable ring on a shared line does not work properly on blind transfer.
Resolved Caveats Table 4 Cisco CallManager Release 3.0(8) Resolved Caveats (continued) DDTS Number Summary Explanation CSCdt15151 A calling party transform mask returns an invalid digit. A Cisco CallManager code change checks and drops calling party Microsoft Internet Explorer if calling party transform mask returns invalid digit. CSCdt15834 Deleted shared lines do not auto register. A Cisco CallManager code change auto registers deleted lines.
Resolved Caveats Table 4 Cisco CallManager Release 3.0(8) Resolved Caveats (continued) DDTS Number Summary Explanation CSCdt19887 MTP resources reporting status=1, but Cisco CallManager will not jump to better resources. The Cisco CallManager software has been modified to handle error code 255 from the Cisco Catalyst 6000 - DSP Resource device when there is error in opening the receive channel due to out of resource (transcoder); either the DSP is dead, or no more DSP is available in the device.
Resolved Caveats Table 4 Cisco CallManager Release 3.0(8) Resolved Caveats (continued) DDTS Number Summary Explanation CSCdt21490 MTP resets on 23rd 729-711 transcoding(VAD enabled) When the CPU time is lower than a low watermark, the transcoder takes no new calls (and the calls will not be complete). All new calls will be rejected. The transcoder will not accept new calls until CPU idle time goes above a high watermark. CPU time is regained after some active calls go idle.
Resolved Caveats Table 4 Cisco CallManager Release 3.0(8) Resolved Caveats (continued) DDTS Number Summary Explanation CSCdt28640 Cisco IP Phone 7960 intermittently delays dialtone when going off-hook. The off-hook message was getting delayed only in certain scenarios. A Cisco CallManager code change resolved this caveat. CSCdt29217 Call Park code correction to avoid blocking of Call Park numbers. CSCdt31546 A Cisco CallManager code change fixed this caveat.
Resolved Caveats Resolved Caveats - Release 3.0(7) Table 5 lists and describes Caveats that were resolved in Cisco CallManager Release 3.0(7) Note If you have an account with Cisco.com (Cisco Connection Online), you can use the Bug Toolkit to find caveats of any severity for any release. To access the Bug Toolkit, log on to http://www.cisco.com/support/bugtools. . Table 5 Cisco CallManager Release 3.
Resolved Caveats Table 5 Cisco CallManager Release 3.0(7) Resolved Caveats (continued) DDTS Number Summary Explanation CSCds55086 Access violation occurs in svchost Microsoft has a fix, contact Microsoft during Win2K startup on client running support for details at the following URL: Cisco SoftPhone. http://support.microsoft.com/support/kb/ar ticles/q278/7/18.asp. CSCds58392 Putting a call on hold generates a new call with wrong data.
Resolved Caveats Table 5 Cisco CallManager Release 3.0(7) Resolved Caveats (continued) DDTS Number Summary Explanation CSCds81134 Release messages are missing from Cisco CallManager. Changes made to the translation pattern to amends this problem. CSCds82314 Cisco CallManager will not initialize if The ability to initialize quickly even if many translation patterns exist. hundreds (tested with 2000 translations) of translation patterns exist was added to the software.
Resolved Caveats Table 5 Cisco CallManager Release 3.0(7) Resolved Caveats (continued) DDTS Number Summary Explanation CSCds92026 No disconnect event occurs when disconnecting consult conference. CallManager.java was modified not to set setConferenceFeature during the initialization of the consult Conference call. CSCds92393 SDL router services are declared dead.
Resolved Caveats Resolved Caveats - Release 3.0(6) Table 6 lists and describes Caveats that were resolved in Cisco CallManager Release 3.0(6) Note If you have an account with Cisco.com (Cisco Connection Online), you can use the Bug Toolkit to find caveats of any severity for any release. To access the Bug Toolkit, log on to http://www.cisco.com/support/bugtools. . Table 6 Cisco CallManager Release 3.
Resolved Caveats Table 6 Cisco CallManager Release 3.0(6) Resolved Caveats (continued) DDTS Number Summary Explanation CSCdr74342 DC Directory gets suspended due to file The problem was due to the file system system error. backup utility locking the file using the win32 LockFile(). LockFile either allows a shared Read lock or an exclusive Read or Write lock. If a shared Read lock has been obtained by a process; no process (including the one that had first opened the file) can write to that file.
Resolved Caveats Table 6 Cisco CallManager Release 3.0(6) Resolved Caveats (continued) DDTS Number Summary Explanation CSCds53378 Cisco CallManager upgrade with locations prevents SW-based conference from working. The code for unlimited bandwidth in location for Cisco CallManager 3.0 does not currently work. Migration has been changed to remove the 0 bandwidth location records and set any devices location using it to NULL. This will, in effect, give that situation no bandwidth limitation.
Resolved Caveats Table 6 Cisco CallManager Release 3.0(6) Resolved Caveats (continued) DDTS Number Summary Explanation CSCds63460 BLIND TRANSFER: caller/calledid information becomes messed up on blind transfer. Cisco CallManager software has been modified to correctly display the calling, called party number, and name for the scenario of a call that was blind transferred to a line, which already had an active call (call-waiting scenario).
Resolved Caveats Table 6 Cisco CallManager Release 3.0(6) Resolved Caveats (continued) DDTS Number Summary Explanation CSCds66507 Cisco WebAttendant client will not install on Windows NT operating system. Windows operating systems version of regsvr32.exe could not load the .dll extensions containing the Cisco WebAttendant controls. Each Cisco WebAttendant DLL tries to start a multimedia timer when the DLL is loaded.
Resolved Caveats Table 6 Cisco CallManager Release 3.0(6) Resolved Caveats (continued) DDTS Number Summary Explanation CSCds69538 Conference is in bad state when When Cisco AutoAttendant is redirected to Cisco AutoAttendant redirects call back a second CTI port, a redirect signal is sent to its own ports to the Conference process inside of Cisco CallManager. The logic in this process was not expecting a conference resource to be an origination point for a redirection.
Resolved Caveats Table 6 Cisco CallManager Release 3.0(6) Resolved Caveats (continued) DDTS Number Summary Explanation CSCds77578 Cisco CallManager does not cut through after progress with DE30+ (overlap sending). At the overlap sending situation, the channel ID can be received in setup pack. CSCds79716 UserPrefs do not work after an upgrade from versions prior to Cisco CallManager 3.0(5a) to Cisco CallManager 3.0(5a).
Resolved Caveats Resolved Caveats - Release 3.0(5a) Table 7 lists and describes Caveats that were resolved in Cisco CallManager Release 3.0(5a). Note If you have an account with Cisco.com (Cisco Connection Online), you can use the Bug Toolkit to find caveats of any severity for any release. To access the Bug Toolkit, log on to http://www.cisco.com/support/bugtools. Table 7 Cisco CallManager Release 3.
Resolved Caveats Table 7 Cisco CallManager Release 3.0(5a) Resolved Caveats (continued) DDTS Number Summary Explanation CSCdr41614 When a DTMF digit is pressed when a phone is connected to a conference, the digit is dropped. DTMF digits are not propagated to members of a conference.
Resolved Caveats Table 7 Cisco CallManager Release 3.0(5a) Resolved Caveats (continued) DDTS Number Summary Explanation CSCdr51675 This problem occurs under any of the following conditions: When using the Cisco CallManager Control Center web page, the services for a server do not appear when it is selected. The screen displays "A connection to the server could not be established.
Resolved Caveats Table 7 Cisco CallManager Release 3.0(5a) Resolved Caveats (continued) DDTS Number Summary Explanation CSCdr78651 Ability to park call by directory number Modified park code allocation to use the is missing. same park code number when call park reversion occurred. This allows the parking party to repark the same call to the same park code in effect when call park reversion occurred. CSCdr80088 Metalink import error message occurs. Reinstallation fixed the problem.
Resolved Caveats Table 7 Cisco CallManager Release 3.0(5a) Resolved Caveats (continued) DDTS Number Summary Explanation CSCds19447 No information about Cisco AutoAttendant install exists in Cisco CallManager install documents. The AutoAttendant Administrative Guide documents the information. CSCds21377 The Cisco CallManager service was up but was not running. Looking at PerfMon statistics showed that the CPU utilization of Cisco CallManager was zero, but Cisco CallManager did show as running.
Resolved Caveats Table 7 Cisco CallManager Release 3.0(5a) Resolved Caveats (continued) DDTS Number Summary Explanation CSCds67376 Auto install on 7820/22 locks up on final reboot after upgrade. When performing upgrades on the MCS7820 or 7822, the server would lock up on the final reboot. This issue is resolved if Windows 2000 service pack 1 is installed prior to upgrading Cisco CallManager. The Cisco CallManager CD will now detect whether SP1 is installed and end the upgrade if it is not.
Open Caveats Open Caveats Open Caveats for Cisco CallManager Release 3.0(10) Table 8 describes possible unexpected behaviors by Cisco CallManager Release 3.0(10). Unless otherwise noted, these caveats apply to all Cisco CallManager 3.0 releases up to and including Cisco CallManager Release 3.0(10) Note If you have an account with Cisco.com (Cisco Connection Online), you can use the Bug Toolkit to find caveats of any severity for any release. To access the Bug Toolkit, log on to http://www.cisco.
Open Caveats Table 8 Open Caveats for Cisco CallManager Release 3.0(10) (continued) DDTS number Description CSCdr36331 Going from low bit rate to low bit rate, the wrong counter is sent from a transcoder. The problem occurs when the system is configured, so a transcoder is invoked to transcode between two low-bit-rate codecs (for example, from a G.723 to a G.729). Note Cisco CallManager Release 3.0 does not support the use of a transcoder to support low-bit-rate to low-bit-rate transcoding.
Open Caveats Table 8 Open Caveats for Cisco CallManager Release 3.0(10) (continued) DDTS number Description CSCdr39403 Database notification does not work in certain situations. Updates made from the Cisco CallManager administration page are registered but not reflected in the MIB tables until the SNMP data collector or Cisco CallManager (depending on the type of update) is restarted.
Open Caveats Table 8 Open Caveats for Cisco CallManager Release 3.0(10) (continued) DDTS number Description CSCdr39493 You cannot assign the same extension to a Cisco Catalyst 6000 24 Port FXS Analog Interface Module and a Cisco IP phone. Workaround: No workaround exists. For Cisco CallManager Release 3.0, only MGCP gateways (VG200s) allow FXS ports to share the same phone number with a Cisco IP phone. This release does not support shared-line capability for other analog gateways in this release.
Open Caveats Table 8 Open Caveats for Cisco CallManager Release 3.0(10) (continued) DDTS number Description CSCdr77184 Call park numbers do not recycle through configured range. Workaround: Go to Feature > Call Park, select a range, and click Update; or create a new range. CSCdr80075 A need exists for the Cisco CallManager to check the assignment of lines and speed-dial keys for errors.
Open Caveats Table 8 Open Caveats for Cisco CallManager Release 3.0(10) (continued) DDTS number Description CSCds09623 The scroll bar does not appear on Device/Phone list page. Workaround: The Administration web pages are designed for a minimum display resolution of 800 x 600. This release does not support lower resolutions. CSCds12355 Cisco CallManager reboot causes no-answer condition in random Cisco uOne in cluster.
Open Caveats Table 8 Open Caveats for Cisco CallManager Release 3.0(10) (continued) DDTS number Description CSCds42397 Terminal services do not function. Workaround: This is a Microsoft limitation. CSCds42397 Terminal Services are nonfunctional. Workaround: This is a Microsoft limitation. CSCds46274 Cisco IP Phone 7960 user on G.729 call hears hiss after digit during IVR prompt. Workaround: No workaround exists.
Open Caveats Table 8 Open Caveats for Cisco CallManager Release 3.0(10) (continued) DDTS number Description CSCds55942 AVVID: Call produces cumulative feedback when conferencing back to itself. Workaround: Avoid conferencing a call back on itself. CSCds59268 When Call Forward No Answer is configured on a line with partition, the calls forward to Call Forward No Answer.
Open Caveats Table 8 Open Caveats for Cisco CallManager Release 3.0(10) (continued) DDTS number Description CSCds80198 Call pickup does not pick up a call even when line is Call Forward All. Workaround: No workaround exists. CSCds84446 AVVID: Volume from Cisco Access Digital Trunk Gateway DT-24+ to Cisco uOne is too low to hear voice mail. Workaround: No workaround exists. CSCds88617 GWY_ERR_C80ERR_RESOURCEUNAVAILABLE is reported from Cisco Access Digital Trunk Gateway DT-24+.
Open Caveats Table 8 Open Caveats for Cisco CallManager Release 3.0(10) (continued) DDTS number Description CSCdt17567 Conference master drops from conference while adding 24th party into the conference. Workaround: No workaround exists. CSCdt20517 Calls placed on IP phones show translated No. Workaround: The problem does not occur when no translation is done, but if dial translations are required, no workaround exists.
Open Caveats Table 8 Open Caveats for Cisco CallManager Release 3.0(10) (continued) DDTS number Description CSCdt29275 Cisco CallManager 3.0(5a) upgrades reset enterprise parameter URLs to default. Workaround: After the upgrade, change the URLs to the values that existed prior to the upgrade. CSCdt30332 Cisco Messaging Interface stops after Cisco CallManager 3.0(7) upgrades. Workaround: This is not an error. A blank VoiceMailDN is an invalid configuration.
Open Caveats Table 8 Open Caveats for Cisco CallManager Release 3.0(10) (continued) DDTS number Description CSCdt40012 DE 30+ loses D Channel under stress. Workaround: No workaround exists. CSCdt40683 Cisco Messaging Interface partition must match route partition when configuring Cisco Messaging Interface.
Open Caveats Table 8 Open Caveats for Cisco CallManager Release 3.0(10) (continued) DDTS number Description CSCdt50317 Cisco CallManager 3.0(7) Call Detail Records do not nove from subscriber to sublisher. Workaround: No workaround exists. CSCdt52841 Cisco WebAttendant documentation calls for read access to the wausers share, but change access is required to open the database. Workaround: Allow change access to the wausers share. CSCdt53938 Upgrade does not put BINs in nondefault TFTPPATH.
Open Caveats Table 8 Open Caveats for Cisco CallManager Release 3.0(10) (continued) DDTS number Description CSCdt62208 Cisco IP Phone 7960 reports two missed calls if unanswered. Workaround: Mask the problem by increasing the CallManager T301 timer so that the ringout time is greater than the PSTN ringout time. CSCdt62292 Call from PSTN to an undefined directory number records 0 in CDR. Workaround: No workaround exists. CSCdt64163 User cannot delete partition from Cisco Callmanager.
Open Caveats Table 8 Open Caveats for Cisco CallManager Release 3.0(10) (continued) DDTS number Description CSCdt73926 CDR CallID is reset with Cisco CallManager restart. Workaround: If Cisco CallManager must be restarted, extract CDRs before restarting Cisco CallManager. Otherwise, relate records will need to be determined by examination of the time and date of the record. CSCdt76403 CDR records are incorrect when recording conference calls. Workaround: No workaround exists.
Open Caveats Table 8 Open Caveats for Cisco CallManager Release 3.0(10) (continued) DDTS number Description CSCdu06412 Cisco CallManager incorrectly interprets the disconnect cause. Workaround: Use the route group that chooses local gateway. CSCdu08950 Unchecking the run H.225 on every node still has location leaks. Workaround: No workaround exists. CSCdu10456 Transfer succeeds after first party drops. Workaround: No workaround exists.
Open Caveats Table 8 Open Caveats for Cisco CallManager Release 3.0(10) (continued) DDTS number Description CSCdu21141 A lineAnswer returns SUCCESS, but state does not change. Workaround:Use blind transfer or consult transfer instead of arbitrary transfer. CSCdu21447 Cisco CallManager subscriber does not refresh database upon network recovery. Workaround: Stop and start the Cisco CallManager service on the recovered Cisco CallManager.
Open Caveats Table 8 Open Caveats for Cisco CallManager Release 3.0(10) (continued) DDTS number Description CSCdu52827 Network time protocol service hangs. Workaround: Perform the following steps if you experience an issue with the Network time protocol service: Step 1 Right click My Network Places. Step 2 Click Properties. Step 3 Right click Local Area Connection. Step 4 Click Properties. Step 5 Choose Internet Protocol (TCP/IP). Step 6 Click Properties. Step 7 Click Advanced.
Documentation Updates Table 8 DDTS number Open Caveats for Cisco CallManager Release 3.0(10) (continued) Description CMTerminals -- Firmware CSCdr53488 Cisco IP Phone 7960 did not work after a Cisco CallManager was stopped and then restarted after about a 30 minute interval. Workaround: Using the **#** reset sequence on the phone brings it back into operation. CSCdr55189 Cisco IP Phone 7960 takes 7min to work if pvid of tele not equal to pvid of CM. Workaround: No workaround exists.
Documentation Updates New Service Parameters Table 9 contains new Cisco CallManager service parameters, with descriptions, that were not included in the Release 3.0(5) Cisco CallManager Administration Guide or the online help for the Cisco CallManager application. Table 9 Cisco CallManager Service Parameter Updates ParamName Values Description CcmPriorityClass Default: 0 CcmPriorityClass = 0: Cisco CallManager process runs in normal priority class.
Documentation Updates Table 9 Cisco CallManager Service Parameter Updates ParamName Values CTIRequestTimeo Default: 5 (seconds) ut Description Specifies timeout interval. Timer ensures responses to CTI requests are generated for situations where network or remote Cisco CallManager node problems prevent the normal processing of the CTI requests.
Documentation Updates Table 9 Cisco CallManager Service Parameter Updates ParamName Values Description IpTosCm2Cm Default: 3 Controls class of service of IP traffic and signals between Cisco CallManager to Cisco CallManager. Note The following list shows that the valid value for IpTosCm2Cm is between 0 and 7 and is represented as follows: 0 = routine 1 = priority 2 = immediate 3 = flash 4 = flashOver 5 = critical 6 = internet 7 = network Release Notes for Cisco CallManager Release 3.
Documentation Updates Table 9 Cisco CallManager Service Parameter Updates ParamName Values Description IpTosCm2Dvce Default: 3 Controls class of service of IP traffic and signals between Cisco CallManager to device. Controls class of service of IP traffic and signals between Cisco CallManager to Cisco CallManager.
Documentation Updates Table 9 Cisco CallManager Service Parameter Updates ParamName Values Description MaxCTI Connections Default: 400 Designates the maximum number of CTI connections. Cisco CallManager allows a maximum number of CTI connections. Typically, each CTI application (or instance of the application) has a single CTI connection to the Cisco CallManager; for example, each Softphone instance has a single CTI connection to the Cisco CallManager.
Documentation Updates Table 9 Cisco CallManager Service Parameter Updates ParamName Values NumberingPlanInf Default: 1 o ReorderRouteList Default: F StopRoutingOnOu Default: F tOfBandwidthFlag Description Gives some control over the ISDN Numbering Plan Information field on the Called Party Number. This control that is available for H.
Documentation Updates Table 9 Cisco CallManager Service Parameter Updates ParamName Values Description StopRoutingOnUn Default: F allocatedNumberF lag Specifies when set to true, that if a call being routed through a route list detects the associated “cause” during the release of the call, no re-routing to the next device in the route list is attempted and the call is released with the associated cause.
Documentation Updates Service Parameters Table 10 contains new Cisco CallManager service parameters, with descriptions, that were not included in the Release 3.0 Cisco CallManager Administration Guide or the online help for the Cisco CallManager application. Caution Table 10 Do not modify any defaults or settings of the following parameters without the assistance of the Cisco Technical Assistance Center (TAC). Cisco CallManager Service Parameters Not Included in Release 3.
Documentation Updates Table 11 CMI Service Parameters Not Included in Release 3.0 Documentation ParamName Description BackupCallManagerName This parameter defines the names of the Cisco CallManagers that are going to be used for the CMI backup. You can use either the name of a Cisco CallManager or its IP address. BaudRate Cisco CMI connects to the voice mail system via an ETA/TIA-232 connection. This parameter defines that connection.
Documentation Updates Table 11 CMI Service Parameters Not Included in Release 3.0 Documentation (continued) ParamName Description InputDnSignificantDigits This parameter is designed to accommodate the differences between voice mail mailbox numbers and DNs. If a Legacy voice mail system has mailbox numbers that are longer than the DNs on the system, this parameter can be used to strip the most significant digits. The numeric value of this parameter indicates how many digits should be used.
Documentation Updates Table 11 CMI Service Parameters Not Included in Release 3.0 Documentation (continued) ParamName Description Parity Cisco CMI connects to the voice mail system via an EIA/TIA-232 connection. This parameter defines that connection. Recommended default value: Even Note RouteFilter CMI requires this parameter is one of four required to register an intercept for the voice mail system with which CMI is going to work.
Documentation Updates Table 11 CMI Service Parameters Not Included in Release 3.0 Documentation (continued) ParamName Description SsapiKeepAliveInterval During normal operations, CMI will be attached to a Cisco CallManager. When this is the case, CMI sends a keepalive message to the Cisco CallManager at the rate specified by this numeric parameter.
Documentation Updates Table 11 CMI Service Parameters Not Included in Release 3.0 Documentation (continued) ParamName Description ValidateDns When CMI receives incoming lamp commands from the voice-mail system, it normally validates the DN against the NumPlan table. This is an attempt to verify that the DN matches an existing DN known to Cisco CallManager. If the DN is not found in NumPlan, an invalid DN message is sent to the voice mailbox.
Documentation Updates Running Show Tech To run show tech correctly, use this example to construct your command: show -f output.txt -v -w480 db The example given in the Show Command chapter of Configuring Remote Serviceability for Cisco CallManager 3.0 (page 3-2) lacks a space before “db.” Changes This section contains changes that have occurred since the original release of the Cisco CallManager Administration Guide Release 3.0. These changes do not currently appear in the Release 3.
Documentation Updates Cisco CallManager Service Parameters The following list contains the service parameters, which can be configured for the Cisco CallManager service type, that were omitted from the Release 3.
Documentation Updates • SdlTraceTypeFlags • SendingCompleteIndicator • ToneOnCallForward • TypeOfCalledNumberForH225Devices • VoiceMail Cisco TFTP Service Parameters The following list contains the service parameters, which can be configured for the Cisco TFTP service type, that were omitted from the Release 3.
Documentation Updates • DataBits • DialingPlan • InputDnSignificantDigits • KeepAliveDn • OutputDnFormat • OutputExternalFormat • Parity • RouteFilter • SsapKeepAliveInterval • StopBits • ValidateDns • VoiceMailParition Cisco IP Voice Media Streaming Service Parameters The following list contains the service parameters, which can be configured for the Cisco IP Voice Media Streaming service type, that were omitted from the Release 3.
Obtaining Documentation Errors This section contains any errors contained in the Cisco CallManager Administration Guide for Release 3.0 and/or the online help for the Cisco CallManager application. The upcoming release of the document and online help application will correct these errors. Incorrect Name of MwiSearchSpace Service Parameter The name of the Cisco Messaging Interface (CMI) service parameter appears incorrectly in the documentation and online help application.
Obtaining Documentation World Wide Web You can access the most current Cisco documentation on the World Wide Web at the following sites: • http://www.cisco.com • http://www-china.cisco.com • http://www-europe.cisco.com Documentation CD-ROM Cisco documentation and additional literature are available in a CD-ROM package, which ships with your product. The Documentation CD-ROM is updated monthly and may be more current than printed documentation.
Obtaining Technical Assistance Documentation Feedback If you are reading Cisco product documentation on the World Wide Web, you can submit technical comments electronically. Click Feedback in the toolbar and select Documentation. After you complete the form, click Submit to send it to Cisco. You can e-mail your comments to bug-doc@cisco.com.
Obtaining Technical Assistance Customers and partners can self-register on Cisco.com to obtain additional personalized information and services. Registered users can order products, check on the status of an order, access technical support, and view benefits specific to their relationships with Cisco. To access Cisco.com, go to the following website: http://www.cisco.
Obtaining Technical Assistance Contacting TAC by Telephone If you have a priority level 1 (P1) or priority level 2 (P2) problem, contact TAC by telephone and immediately open a case. To obtain a directory of toll-free numbers for your country, go to the following website: http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml P1 and P2 level problems are defined as follows: • P1—Your production network is down, causing a critical impact to business operations if service is not restored quickly.
