Table Of Contents
Release Notes for Cisco CallManager Release 3.0(8)
Contents
Introduction
System Requirements
Determining the Software Version
Related Documents
New and Changed Information
New Software Features in Release 3.0(8)
Strong Encryption
Global Call ID
New Software Features in Release 3.0(7)
Important Notes for Release 3.0(7)
Service Parameter Restart Conditions
Cisco IP Phone 7910 and Cisco IP Phone 7940 Compatibility Issue
New Software Features in Release 3.0(6)
Cisco WebAttendant
Tech Prefixes
Service Parameter
Important Notes for Release 3.0(6)
Cisco IP Phone 7910 and Cisco IP Phone 7940 Compatibility Issue
New Hardware and Software Features in Release 3.0(5a)
Support for New Cisco IP Phones
TAPI 2.1 and JTAPI 1.2 Service Providers
Multicluster Scalability and ITU-T H.323 Enhancements
Cisco IP Phone Services on Cisco Pixel-Based Display Phones
Corporate Directory Dialing from Cisco IP Phones
Additional MGCP Support for Cisco VoIP Gateways
Cisco VG200 FXO Hookflash Support
AMIS-A Support
User Interface Enhancements
Important Notes for Cisco CallManager Release 3.0(5a)
Computer Telephony Integration
BAT Reinstallation
IOS Version
Intercluster Trunk Configuration
Cisco CallManager Integration with Corporate LDAP Directories
Cisco IP Phone 7910 and Cisco IP Phone 7940 Compatibility Issue
Resolved Caveats
Resolved Caveats - Release 3.0(8)
Resolved Caveats - Release 3.0(7)
Resolved Caveats - Release 3.0(6)
Resolved Caveats - Release 3.0(5a)
Open Caveats
Open Caveats for Cisco CallManager Release 3.0(8)
Troubleshooting
Documentation Updates
New Service Parameters
Configuring the Microsoft Telnet Daemon for Bridged Telnet
Server Name Change
Running Show Tech
Changes
Default Value Changed for SdlTraceTotalNumFiles Service Parameter
Omissions
Cisco CallManager Service Parameters
Cisco TFTP Service Parameters
Cisco Messaging Interface Service Parameters
Cisco IP Voice Media Streaming Service Parameters
Cisco Enterprise Service Parameters
Errors
Incorrect Name of MwiSearchSpace Service Parameter
Incorrect Definition for HoldType and ToneOnHoldTime
Service and Support
Obtaining Documentation
World Wide Web
Documentation CD-ROM
Ordering Documentation
Obtaining Technical Assistance
Cisco.com
Technical Assistance Center
Documentation Feedback
Release Notes for Cisco CallManager Release 3.0(8)
February 22, 2001
These release notes describe the new features and caveats for Cisco CallManager Release 3.0(8). Use these release notes in conjunction with the Installing Cisco CallManager Release 3.0(8) document, located on Cisco Connection Online (CCO), and the Cisco Documentation CD-ROM. The Installing Cisco CallManager Release 3.0(8) document is also packaged with your CDs or convergence server.
The latest software upgrades and release notes for Cisco CallManager 3.0(8) are available on Cisco Connection Online (CCO) at
http://www.cisco.com/cgi-bin/tablebuild.pl/callmgr.
Contents
These release notes discuss the following topics:
•
Introduction
•System Requirements
•Determining the Software Version
•Related Documents
•New and Changed Information
•Resolved Caveats
•Open Caveats
•Troubleshooting
•Documentation Updates
•Service and Support
•Obtaining Documentation
•Obtaining Technical Assistance
Introduction
Cisco CallManager, a network business communication system, provides high-quality telephony over IP networks. Cisco CallManager enables the conversion of conventional, proprietary, circuit-switched PBXs to multiservice, open LAN systems.
System Requirements
Cisco CallManager Release 3.0 must be installed and configured on a Cisco Media Convergence Server.
When upgrading to Cisco CallManager Release 3.0(8) from CCO, you are prompted to install Service Pack 1 and then the hot fix.
Caution You must first install the Service Pack 1 and then the hot fix. Installing them in the improper order causes the installation to fail.
For system hardware component information and system requirements, refer to Installing Cisco CallManager Release 3.0(8).
Determining the Software Version
To determine the software version of Cisco CallManager 3.0(8), open Cisco CallManager Administration; then click Details on the main Cisco CallManager Administration page. The following information displays:
•Cisco CallManager System version
•Cisco CallManager Administration version
•Database information and database DLL versions
Related Documents
The following list shows related documents for Release 3.0(8) of Cisco CallManager:
•Cisco CallManager Administration Guide for Release 3.0(8)
•Cisco WebAttendant User Guide
•Cisco WebAttendant Quick Start Guide
•Cisco JTAPI Developer Guide
•Cisco TAPI Developer Guide
•Troubleshooting Guide for Cisco CallManager Release 3.0(8)
•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
•Software License Agreement
•Installing Cisco CallManager 3.0(8)
•Quick Start Guide for Cisco CallManager Release 3.0
New and Changed Information
New Software Features in Release 3.0(8)
The following sections contain new and changed software features in Cisco CallManager Release 3.0(8).
Strong Encryption
Cisco CallManager Release 3.0(8) contains low encryption (56-bit or less) in all of its components.
Access the Cryptographic Software link from the main CCO download location at http://www.cisco.com/cgi-bin/tablebuild.pl/callmgr for applications that contain 128-bit encryption, such as, TNDconnect.exe (Bridged Telnet application) and DC directory .dll extensions.
Note Versions preceding Cisco CallManager Release 3.0(8) included TNDconnect.exe (Bridged Telnet application) and DC Directory .dll extensions that contain strong encryption (128-bit).
Global Call ID
The TAPI Service Provider (TSP) version 3.0 that is packaged with Cisco CallManager 3.0 supports Global Call ID.
Applications use the Global Call ID to identify a specific call as it traverses various resources in the Cisco CallManager. For example, a Call Center application uses Global Call ID to track a call that comes into a CTI Route Point, gets redirected to a CTI Port, and terminates at an Agent's IP Phone.
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" section 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.
•Digital Port
•Ethernet Phone Port
•Analog Port
•MGCP Listen Port
•MGCP Keep-alive Port
•MessageWaitingOffDN
•MessageWaitingOnDN
•StatisticsEnabled
•MaxDaResponseTimeoutErrorCount
•MaxTotalNumberOfRegisteredCallingEntities
Note The Service Parameter restart conditions apply to all versions up to an including Cisco CallManager 3.0(7).
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.
Cisco WebAttendant
Cisco WebAttendant supports the traditional role of a manual attendant console. Associated with a Cisco IP Phone, the application allows the attendant to quickly accept and dispatch calls to enterprise users. An integrated directory service provides traditional busy lamp field (BLF) and direct station select (DSS) functions for any line in the system. The application is Web-enabled and, therefore, portable to Windows 98, NT, and 2000 platforms.
As one of its primary benefits over traditional attendant console systems, Cisco WebAttendant monitors the state of every line in the system to efficiently dispatch calls. The absence of a hardware-based line monitor device offers a much more affordable and distributable manual attendant solution than traditional consoles.
Note Each Cisco CallManager in a cluster can process as many as 2000 Cisco WebAttendant calls per hour.
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.
Step 6 Select GateKeeperSupportedPrefix from the Configured Service Parameters.
Step 7 Add the proper value; i.e., 1#, 2#, etc. Only one tech prefix is allowed.
Service Parameter
Cisco CallManager Release 3.0(6) supports a new service parameter.
MaxCTIConnections—This parameter sets the maximum number of simultaneous active CTI connections between an application and the Cisco CallManager. The default value is 400 connections.
Important Notes for Release 3.0(6)
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 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.
•Cisco IP Phone 7910—This is a single-line Cisco IP Phone with the following features:
–Two-line, 24-character display
–Four fixed function buttons (Line, Hold, Transfer, Settings)
–Six programmable buttons
–Hands-free dialing speaker
–Single 10 BaseT (RJ-45) connector
–Message waiting indicator
–Provision for either inline or local plug power
•Cisco IP Phone 7910-SW+—This is a single-line Cisco IP Phone with the following features:
–Two-line, 24-character display
–Four fixed function buttons (Line, Hold, Transfer, Settings)
–Six programmable buttons
–Hands-free dialing speaker
–Dual 10/100 BaseT (RJ-45) connectors into dual port 10/100 BaseT switch
–Message waiting indicator
–Provision for either inline or local plug power
•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
TAPI 2.1 and JTAPI 1.2 Service Providers
The Microsoft Telephony Application Programming Interface (TAPI) and Java Telephony API (JTAPI) service providers enable development of sophisticated, converged multimedia applications. These APIs support the following Cisco applications in this release:
•Cisco IP SoftPhone
•Cisco IP Contact Center
•Cisco IP Interactive Voice Response System
•Cisco IP Auto Attendant
•E-Services Application Engine
In addition, third-party software vendors may develop applications using these APIs. This release does not support Service Providers Interface redundancy.
Multicluster Scalability and ITU-T H.323 Enhancements
Cisco CallManager Release 3.0(5a) adds the following scalability and ITU-T H.323 enhancements for multicluster environment in which call admission control is provided by Cisco's H.323 gatekeeper, the Cisco Multimedia Conference Manager (MCM):
•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. Also, because the SA/DA name required a hexadecimal address, configuration at the Cisco MCM and in the Cisco CallManager database was error prone. Cisco CallManager Release 3.0(5a) allows individual gatekeeper-controlled Cisco CallManagers to be configured at the Cisco MCM and allows a Cisco CallManager host name or dotted decimal IP address to be used instead of a hexadecimal address.
•More efficient Cisco CallManager to H.323 Gatekeeper registration—Cisco CallManager can register to the Cisco MCM using full RRQ upon Cisco CallManager initialization. Subsequent RRQs are periodically sent to the gatekeeper as a keep-alive function. In Cisco CallManager Release 3.0(5a) the lightweight RRQ format of H.225 RAS specification is used to reduce periodic-processing burden on the Cisco MCM CPU.
•Admission Request (ARQ) enhancements—When an intercluster call is initiated, the gatekeeper-controlled Cisco CallManager in a cluster issues the E.164 address of the destination in its ARQ to the MCM. Also, the gatekeeper-controlled Cisco CallManager in the source cluster accepts the IP address of the destination device in the resulting Admission Confirm (ACF) message.
•Gatekeeper-controlled Cisco CallManagers, during the initial RRQ, send a full E.164 address range Cisco MCM—Cisco MCM will accept the registration now that it is aware of the full E.164 address range of the cluster associated with that gatekeeper-controlled Cisco CallManager. Future enhancements to the Cisco MCM software will include the ability for Cisco MCM to automatically add the address ranges to the Cisco MCM dial plan.
Cisco IP Phone Services on Cisco Pixel-Based Display Phones
Cisco IP Phone 7940 and Cisco IP Phone 7960 have an HTTP client with an XML parser. When a user presses the Services fixed-function button, the HTTP client will attach to a preconfigured (by the administrator) URL. This URL will display a menu of available HTML/XML services for the user. These services are normally located on an HTTP server separate from the Cisco CallManager or 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.
Note The eXtensible Markup Language (XML) Application Programming Interface (API) is available for end-user application development. The description of this API is documented in Cisco IP Phone Services Application Development Note, which is available for download from CCO at http://www.cisco.com/univercd/cc/td/doc/product/voice/sw_ap_to/ under the category "Third-Party Application Development Guides."
Assistance to resolve bugs in the API is available through TAC. Assistance for application development is not available through TAC. Applications development assistance will be made available in the near-term through a specifically tasked help desk. Until that help desk is available, application development support is not available for the XML API.
Corporate Directory Dialing from Cisco IP Phones
The Cisco IP Phone 7940 and Cisco IP Phone 7960 display a menu of directories when a user presses directories. When the user selects Corporate Directory from the menu, the phone presents the option of specifying characters to find the destination user's first name, last name, or directory number. The user may enter any number of characters in any of these fields, then press Search. An HTTP request goes to an HTML service, which queries the embedded Cisco CallManager directory. The HTML service then delivers, through XML tags, the complete listing of matched user entries to the phone's display. The user may then scroll to select the destination entry and press Dial to initiate the dial sequence to that destination.
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.0(5a) adds MGCP support for the following Cisco VoIP gateways:
•Cisco 2600 Series gateways with FXS and FXO analog interfaces
•Cisco 3600 Series gateways (362X, 364X, 366X) with FXS and FXO analog interfaces
Note At Cisco CallManager Release 3.0(5a), MGCP code support in the 36XX router/gateways was not complete. Once complete and tested, these gateways will be supported in an AVVID network.
Cisco VG200 FXO Hookflash Support
The added Cisco VG200 FXO hookflash support Symbol NetVision Phones, which are configured as H.323 client devices. The Cisco VG200 can be configured to provide hookflash feature support from H.323 NetVision phones through Cisco VG200 FXO ports attached to PBXs. The NetVision Phones issue H.245 messages through the Cisco CallManager to Cisco VG200 FXO gateways on initiation by the user of PBX functions. The Cisco VG200 gateway interprets the signals and translates them to an FXO hookflash followed by a PBX-specific feature code.
AMIS-A Support
Signaling within the Skinny Gateway Control Protocol client and Skinny Gateway stacks in Cisco CallManager has been extended to properly interpret and pass out-of-band equivalent signals for "A," "B," "C," and "D" DTMF signals. These additional signals can be passed from AMIS-A compliant messaging system 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.0(5a) makes the following enhancements to the Cisco CallManager Administration configuration pages:
•Cisco IP Phone Services Configuration—This new page enables administrators to add, modify, or delete Cisco IP Phone services to which users can subscribe to at their site. To access this page from the main Cisco CallManager Administration page, select Feature > Cisco IP Phone Services.
•Cisco uOne Port Wizard—The Cisco uOne Port Wizard enables administrators to quickly configure ports associated with a Cisco uOne messaging server to the Cisco CallManager database. To access the wizard from the main Cisco CallManager Administration page, select Device > Cisco uOne Port; then, click the Cisco uOne Port Wizard link.
•CTI Route Point Configuration—This new page enables administrators to add, modify, and delete CTI route points. A CTI route point is a virtual device that can receive multiple, simultaneous calls for the purpose of application-controlled redirection. Applications that use CTI route points include the Cisco IP Interactive Voice Response System. To access this page from the main Cisco CallManager Administration page, select Device > CTI Route Point.
•CTI Port Configuration—This new page enables administrators to add, modify, and delete a CTI port configuration. CTI ports are virtual devices that are used by software-based Cisco CallManager applications such as Cisco SoftPhone, Cisco AutoAttendant, and Cisco IP Interactive Voice Response (IVR). To access this page from the main Cisco CallManager Administration page, select Device > Phones; then, select CTI Ports.
•Gatekeeper Configuration—You can now access gatekeeper configuration as a separate configuration page where administrators can configure one gatekeeper, or Cisco MCM, per Cisco CallManager cluster. A gatekeeper device supports the H.225 RAS message set used for call admission control, bandwidth allocation, and dial pattern resolution. To access this page from the main Cisco CallManager Administration page, select Device > Gatekeeper.
•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. The MGCP gateway configuration no longer appears as a separate menu item under Device. To access gateway configuration pages from the main Cisco CallManager Administration pages, select Device > Add a New Device; then, select Gateway from the drop-down listbox menu.
Important Notes for Cisco CallManager Release 3.0(5a)
Computer Telephony Integration
Computer Telephony Integration serves as the base interface to Cisco CallManager for TAPI and JTAPI applications as well as direct CTI applications such as Cisco WebAttendant. Cisco CallManager 3.0(5a) allows you to control CTI application usage on a per-user basis. You can enable CTI application use for a particular user by browsing to entry in the User->Global Directory in the Cisco CallManager Administration Console and selecting the "Enable CTI Application Use" checkbox.
Note By default, CTI application use is disabled for all users.
In addition, Cisco CallManager 3.0(5a) also enforces a limit of 400 concurrent CTI connections per Cisco CallManager server. Each CTI application opens a single CTI connection to the Cisco CallManager on successful initialization. Alive CTI connection is required for the application to function.
Note A CTI connection is simply a TCP connection between the CTI application and the Cisco CallManager server and is distinct from a CTI port that is a virtual device.
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.
IOS Version
The Cisco CallManager Release 3.0(5a) was tested with IOS 12.1(3x)XI2.
Intercluster Trunk Configuration
An intercluster trunk, a virtual .H323 gateway, interlinks Cisco CallManagers in different clusters. Beginning with Cisco CallManager Release 3.0(4), intercluster trunks were configured differently. To ensure redundancy and proper failover operation, each cluster must configure an intercluster trunk to each Cisco CallManager in the remote cluster with which it shares a link.
For example, assume that you are configuring intercluster trunks among three Cisco CallManager clusters: Cluster-1, Cluster-2, and Cluster-3C:
•Cluster-1 has three Cisco CallManagers: CCM-A, CCM-B, and CCM-C.
•Cluster-2 has two Cisco CallManagers: CCM-D and CCM-E.
•Cluster-3 has two Cisco CallManagers: CCM-F and CCM-G.
In the preceding scenario, you must configure 14 intercluster trunks to ensure redundancy:
•Cluster-1 configures 4 intercluster trunks (to CCM-D and CCM-E in Cluster-2 and CCM-F and CCM-G in Cluster-3).
•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).
Note If you add another cluster to this example configuration and you still want to maintain the intercluster links, you must modify the configuration for each cluster to add the necessary links between the cluster to all of the Cisco CallManagers in the new cluster. You must also configure the new cluster with intercluster trunks to all of the Cisco CallManagers in the existing clusters.
Cisco CallManager Integration with Corporate LDAP Directories
Cisco CallManager integration with corporate LDAP directories, such as Microsoft Active Directory and Netscape Directory Services, is not available in Cisco CallManager Release 3.0(5a). The availability of this feature will be announced at a later date, pending completion of integration testing
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.
Resolved Caveats
Resolved Caveats - Release 3.0(8)
Table 2 lists and describes Caveats that were resolved in Cisco CallManager Release 3.0(8).
Table 1 Cisco CallManager Release 3.0(8) Resolved Caveats
DDTS Number
|
Summary
|
Explanation
|
CSCdr60534
|
The Cisco IP Phone 7960 allows Call Forward All to be set even when digits are not dialed.
|
Changes were made in CMI by way of CSCdt08716 to resolve the issue and not allow CMI to register with an empty DN pattern. If the CMI application doesn't have a valid Mailbox number, it will not start. The forwarding function works as expected after this and gives out a reorder after the timer expires and no digits have been dialed.
|
CSCds13646
|
AVVID: SNMP agent is missing on Cisco CallManager. MIBII Host Branch
|
The vendor's SNMP Extension Agent 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.
|
CSCds34122
|
A failure to delete or reset the MGCP gateway exists in the find&list gateway page.
|
The Cisco CallManager code change handles MGCP gateway delete and reset from Find&List gateway page.
|
CSCds43704
|
Call looping uses CPU and other resources in Cisco CallManager
|
A Cisco CallManager code change fixed this problem.
|
CSCds50672
|
Call Forward All from a directory number to the same directory number causes high CPU usage.
|
Call Forward All can no longer be used to call the same directory number.
|
CSCds53113
|
User hears a dual ringback tone when calling PSTN using H.323 gateway.
|
Call control no longer directs the originating device to play ringback on alerting if call control has already cut through media.
|
CSCds57777
|
AVVID: PerfMon H.323 gateway is reinstantiated at Cisco CallManager reset of gateway.
|
The H.323 PerfMon statistics are removed when the H.225D stops.
|
CSCds65137
|
No option exists for Subscriber for called and or calling party; i.e., number type.
|
A Cisco CallManager code changes adds support for Subscriber Number option for Calling/Called party IE number type in the digital PRI gateway configuration page.
|
CSCds66475
|
Cisco CallManager does not allow a Automated Install on top of a FAT32b partition. This caveat is fixed on the MCS 7825/7835/7835-1000.
|
This issue only occurs if the C: drive is changed to FAT32. The auto install will be modified to install over a FAT32 partition regardless of the specific drive associated to that partition.
|
CSCds67657
|
1GB virtual memory grab occurs on Cisco CallManager with hot fix.
|
This fix causes the base virtual memory footprint to be larger than in the past, but it solves the memory losses seen in the past.
|
CSCds69496
|
External Call Forward All loop causes high Cisco CallManager CPU usage.
|
Setting the CallManager Service Parameter MaxForwardsToDn to 0 disables the cause of this problem.
|
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.
|
Shared line checks the bandwidth for each device and only consumes for the device active.
|
CSCds82957
|
SQL database does not properly tell Cisco CallManager to start after upgrade.
|
The Cisco CallManager was coming up before the SQL Server. A code change a fixed this problem.
|
CSCds84419
|
AVVID: Null translation pattern prevents dialtone on Cisco IP Phone 7960.
|
This works as designed in the Cisco CallManager.
|
CSCds88597
|
Display issue exists during MeetMe and AdHoc conference calls.
|
The display change no longer shows the Conference number. The screen displays "To Conference" for MeetMe as well as AdHoc Conferences.
|
CSCds89614
|
Call Pickup stops working.
|
Cisco CallManager software has been modified to fix a call scenario that will break the Call Pickup feature. The call pick up table entry needs to be removed after the original destination party has had a Call Forward No Answer put into effect to a new destination and that new destination has a Call Forward setup to another destination.
|
CSCds89808
|
Cisco CallManager crashes when receiving ISDN setup with non-call-associated signaling.
|
Cisco CallManager software was modified to block the call because it does not support non-call-associated signaling on a D-channel.
|
CSCds91028
|
Cisco CallManager does not apply the calling party transform mask.
|
The code change allows a customer to configure a Caller ID mask on the gateway configuration web page, so the last redirecting or first redirecting numbers display in the "Calling Party" field of the ISDN primary setup message in the full E.164 format.
|
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 corrected this problem.
|
CSCdt04309
|
Disable ring on a shared line does not work properly on blind transfer.
|
The problem of keying on the wrong directory number was fixed.
|
CSCdt06347
|
When device is deleted, the forward intercept table is not updated.
|
The call-forwarding properties associated with this deleted device remain valid to Cisco CallManager even though the device no longer exists.
|
CSCdt07520
|
User receives error message when changing partition on phone line.
|
A Cisco CallManager code change corrected this problem.
|
CSCdt07581
|
Insert new user page does not update WA AutoDial name correctly
|
In the Cisco CallManager Release 3.1 User Preferences, the user manually configures the Auto Attendant name dialing and it will not be populated automatically.
|
CSCdt08275
|
Call forward does not work for the second time with IVR route point
|
A Cisco CallManager code change corrected this problem.
|
CSCdt08446
|
Gatekeeper Device pool change requires resetting the PC.
|
A Cisco CallManager code change corrected this problem.
|
CSCdt09642
|
Deleting a gateway gives error message.
|
When the deletion succeeds, no error message is given.
|
CSCdt11706
|
The wrong redirecting parameters exist for Call Forward No Answer.
|
A Cisco CallManager code change fixed this caveat.
|
CSCdt12383
|
Cisco CallManager may crash when making gatekeeper-controlled calls.
|
A Cisco CallManager code change corrected this problem.
|
CSCdt12794
|
Consult failed due to InvalidStateException.
|
A Cisco CallManager code change corrected this problem.
|
CSCdt13681
|
A directory number started returning busy to callers because too many calls had been forwarded to that number.
|
A Cisco CallManager code change corrected this problem.
|
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.
|
CSCdt18271
|
Phone displays "You have Voice Mail" when the mailbox is empty.
|
A previously unresolved caveat caused this problem.
|
CSCdt18312
|
Call Forward with IVR and Hunt Groups fails after 4 forwards.
|
The Cisco CallManager code change resets a variable to false when it receives a message, and the new destination number has an intercept table entry. By doing so the Cisco CallManager continues to forward the call after the CTI application redirects the call to a new destination.
|
CSCdt18313
|
Select devices button takes you to the wrong web page.
|
A Cisco CallManager code change fixed this caveat.
|
CSCdt18621
|
User cannot delete H.323 gateway without receiving error message.
|
The error message will not be given if the deletion is successful.
|
CSCdt18904
|
Users cannot insert gatekeepers.
|
A Cisco CallManager code change fixed this caveat.
|
CSCdt18911
|
When user adds a phone line, the web page freezes.
|
A Cisco CallManager code change fixed this caveat.
|
CSCdt19231
|
Double forwarding gives transfer exception but no dropped event.
|
A Cisco CallManager code change resets a variable to false when it receives a message, and the new destination number has an intercept table entry. By doing so, the Cisco CallManager continues to forward the call after the CTI application redirects the call to a new destination.
|
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 available in the device. The Cisco CallManager marks the device unavailable, so that the next call uses the next transcoder device. The Cisco Catalyst 6000 - DSP Resource device will wait until all the active calls existing in the device become idle; then, it will reset itself and reregister with the Cisco CallManager.
|
CSCdt20323
|
The 3660 router MGCP configuration fails with Cisco CallManager 3.0(6).
|
A Cisco CallManager code change fixed this caveat.
|
CSCdt20674
|
Manual DA restart causes Cisco CallManager restart.
|
The Cisco Access Digital Trunk Gateway DT - 24+ control process was stopping before a related thread that reads the udp messages coming in from the gateway had stopped. This udp read thread was then trying to access Cisco Access Digital Trunk Gateway DT - 24+ data members that no longer existed in memory, thus causing a crash of Cisco CallManager.
|
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. A high watermark is used to reopen the new channels after entering into a rejection mode, which is entered when a call is rejected by a low watermark. After the change, #24 call or more calls will be rejected but will not cause the transcoder to reset.
|
CSCdt21581
|
User experiences a fast busy when transferring a conference.
|
A Cisco CallManager code change resolved this caveat.
|
CSCdt23132
|
Bandwidth control with shared lines results in only 1 line ringing.
|
A Cisco CallManager code change fixed this problem.
|
CSCdt25478
|
Call forwarding on the same phone inherits ring of forwarded lines.
|
A Cisco CallManager code change fixed this caveat.
|
CSCdt27176
|
When user resets DT24 gateway, Cisco CallManager crashes with DrWatson.
|
A Cisco CallManager code change fixed this caveat.
|
CSCdt27572
|
Inbound callers get reorder; B channel is out of service.
|
A CcRejReq message coming into the B channel process (processpn9cuser) and not being handled caused this bug. The B channel hung in an uncertain state, but the CO in the PSTN received it as available for new calls.
|
CSCdt27581
|
User cannot delete partitions. This is an error but m_com_error was not valid.
|
A Cisco CallManager code change fixed this caveat.
|
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.
|
A Cisco CallManager code change fixed this caveat.
|
CSCdt31546
|
A DBL exception in MWI message may crash the Cisco Callmanager.
|
A Cisco CallManager code change corrected this problem.
|
CSCdt38000
|
Cisco IP Phone 7960 does not register after cluster-wide outage.
|
A Cisco CallManager code change insures that if registration is not acknowledged that the phone will recover.
|
CSCdt38916
|
CallingParty=Unknown Number does not work with Cisco uOne
|
A Cisco CallManager code change checks the calling party length field before calling the related function.
|
CSCdt39262
|
Cisco CallManager may allow more calls than limited by Locations.
|
The problem was that the bandwidth to be consumed (24kbps or 80kbps) was an "unsigned int" and it was being compared for greater than a negative "int."
|
CSCdt39402
|
Oneway audio exists with DT-24+ Load D003H300.
|
During the ARP cache timeout, removal of a dynamic entry was causing the port count to go negative. The port count prevents the removal of an address that is being used by several streams. A Cisco CallManager code change prevents the port count variable from going negative during ARP cache timeout.
|
Resolved Caveats - Release 3.0(7)
Table 2 lists and describes Caveats that were resolved in Cisco CallManager Release 3.0(7).
Table 2 Cisco CallManager Release 3.0(7) Resolved Caveats
DDTS Number
|
Summary
|
Explanation
|
CSCds11354
|
No ringback occurs on transfer from PSTN calls coming in on IOS gateway.
With Cisco CallManager 3.0(1) connecting to the PSTN via an H.323 gateway, if a call comes into a phone and it is blind transferred to another phone, the PSTN side will only receive dead air; ringback does not occur.
|
The Cisco CallManager software has been modified to send the H225UserInfo message to the IOS gateway with Q931 Signal IE, so the IOS gateway can play/stop ringback tone for the call that is being transferred to another party. This fix has to work with the fix for CSCds87266, which was opened against the IOS gateway. The fix for CSCds87266 may not be ready until the next major feature release. Therefore, even the Cisco CallManager can send the h.225 Suriname message to the IOS gateway. The problem cannot be verified until the IOS gateway is fixed.
|
CSCds28310
|
Users cannot dial to Cisco uOne using low-bandwidth codec.
|
Transcoder will now be involved allowing low-bandwidth calls from Cisco SoftPhone to access Cisco uOne.
|
CSCds34596
|
Can't Delete A Server - Error:
1576 UNDEFINED displays.
|
The database layer was modified to remove the Database Layer Service when the server is removed.
|
CSCds35388
|
AVVID: Installing Cisco CallManager Release 3.0 document incorrectly instructs the administrator to change the password for Cisco CallManagerAdmin and SQLSvc accounts.
|
Installing Cisco CallManager Release 3.0(5) document has been updated to reflect that you must set the same password for all the Cisco CallManager Admin accounts and the same password for all the SQLSvc accounts for each server in the cluster.
|
CSCds39670
|
Incorrect MsgWaitingLampMode is set in CTI LineGetInfoResp for route points.
|
Set the messageWaitingLampMode member variable to FALSE. Also print out the value of dwMessageWaitiingLampMode in CTIHandler.
|
CSCds41030
|
DB Admin does not limit the input for URLs on phone config page.
|
Limit the input length of "External Data Locations" fields for the Cisco IP Phone 7960 and Cisco IP Phone 7940, and the "URL too long" message will not appear.
|
CSCds53834
|
GateKeeper configuration page does not display.
|
This page does not display with Netscape Navigator.
|
CSCds55086
|
Access violation occurs in svchost during Win2K startup on client running Cisco SoftPhone.
|
Microsoft has a fix, contact Microsoft support for details at the following URL: http://support.microsoft.com/support/kb/articles/q278/7/18.asp.
|
CSCds58392
|
Putting a call on hold generates a new call with wrong data.
|
CallManager.java was modified so it does not set the LastHeldTerminalConn when it is not Consult call.
|
CSCds65594
|
Cisco CallManager does not accept a non-ISDN call progress information element when using the 4ESS protocol.
|
Resolved dropped message by message translation due to the presence of codeset 6 information elements in the SETUP message. MsgTrans shall not drop any ISDN message if locking shift information elements are received. It is up to the pn9* to decide whether the message can be discarded. Also added support of progress indicator for PRI 4ESS setup message.
|
CSCds73845
|
Wrong last redirected address in blind transfer where b is only po
|
CallManager.java was modified to create TransferManager with proper transferController.
|
CSCds74306
|
Transfers across locations do not release all bandwidth resources.
|
Bandwidth is now released after transfer.
|
CSCds76274
|
Bandwidth is not returned to pool after H.323 intercluster trunk call failure.
|
The code was changed to compensate for a failed call and return bandwidth as expected.
|
CSCds78107
|
A need exists for a new error message from CTI for directory login timeout.
|
In the code that queries the directory for user authentication, a case was added to distinguish a directory timeout due to high demand from a login failure. A new error code was also added, so the APIs can also distinguish the two cases and act accordingly.
|
CSCds78869
|
Cisco IP Phone 7910 sends cdp with POWER TLV as 6300 mw instead of 5040 mw.
|
Per hardware engineering, all Cisco IP Phones in the 7900 Family developed thus far have a maximum requirement of 6300 mwatts. This value is now reported via the appropriate TLV in the CDP response in loads P004P301 (Cisco IP Phone 7910) and P003P301 (Cisco IP Phone 7960 and Cisco IP Phone 7940).
|
CSCds81134
|
Release messages are missing from Cisco CallManager.
|
Changes were made to the translation pattern to amend this problem.
|
CSCds82314
|
Cisco CallManager will not initialize if many translation patterns exist.
|
The ability to initialize quickly even if hundreds (tested with 2000 translations) of translation patterns exist was added to the software.
|
CSCds85150
|
CTI: gateway call is not producing ringback event.
|
CTI call state notification is sent, so ringback will be heard.
|
CSCds85215
|
Application gets Talking event even though call is over.
|
CallManager.java was modified to process callClosedEvent, so that it does not send any getCallInfo request.
|
CSCds85283
|
Memory leak occurs in call waiting scenario
|
The Cisco CallManager software was changed to keep memory from growing in specific call waiting scenario.
|
CSCds87448
|
IP voice media streaming application uses 100% CPU.
|
The Cisco CallManager code was changed to recover from a random unhandled internal error causing high CPU usage.
|
CSCds87552
|
Blind transfer from voice mail locks up port.
|
Cisco CallManager software has been modified to reset the intercept entry's dnActive field even when it cannot find the active call entry for the ssParty when receiving the ssDataInd msg.
|
CSCds90217
|
CiscoAddrInServiceEv is not sent for softphone.
|
ProviderImpl and TerminalImpl were changed, so JTAPI opens the CTI Port when DeviceRegisteredEvent for a third-party observer as a result of first-party observers register the CTI Port.
|
CSCds90743
|
Cisco CallManager crashes when attempting to add 17 participants to conference bridge.
|
Cisco CallManager was fixed to prevent crashes caused by array boundary exceeded when the number of conference participants is more than 16.
|
CSCds91718
|
Need exists to include CTI Messages in default SDL trace setting.
|
The default database was changed to facilitate this problem.
|
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.
|
When stationD process receives the ccNotifyReq message and there is no CI associated with the StationCdpc process before we display the information in CcNotifyReq message, one more check needs to be added to make sure there is valid CI to route pattern association; otherwise it will crash the Cisco CallManager.
|
Resolved Caveats - Release 3.0(6)
Table 3 lists and describes Caveats that were resolved in Cisco CallManager Release 3.0(6).
Table 3 Cisco CallManager Release 3.0(6) Resolved Caveats
DDTS Number
|
Summary
|
Explanation
|
CSCdr22835
|
Users cannot change WS-X6608 port type once set without resetting card
|
Cisco CallManager software was changed to find the correct WS-X6608 port type.
|
CSCdr74342
|
DCD: DC Directory gets suspended due to FileSystem error
|
The problem was due to the file system 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. Thus, if a user attempted to update DCD while the backup utility held a lock on DCD's DB volumes, DCD was unable to write to disk and consequently got into an awkward state. DCD now obtains an exclusive Read/Write lock on startup on its DB volumes. This lock prevents any other process from even opening the file. Thus, DCD is guaranteed that no process can deny it (DCD) write access to its own files once it (DCD) successfully comes up.
|
CSCdr74342
|
DC Directory gets suspended due to file system error.
|
The problem was due to the file system 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. Thus, if a user attempted to update DCD while the backup utility held a lock on DCD's DB volumes, DCD was unable to write to disk and consequently got into an awkward state. DCD now obtains an exclusive Read/Write lock on startup on its DB volumes. This lock prevents any other process from even opening the file. Thus, DCD is guaranteed that no process can deny it (DCD) write access to its own files once it (DCD) successfully comes up.
|
CSCds18156
|
Symbol Phone create multiple H225D registered with Line Control
|
The code has been changed to allow only one H225D to register with LineControl.
|
CSCds20015
|
Cisco IP Phone 7960 P3 port does not forward for first 9 seconds after linkup.
|
A parameter was added to Settings/Network Configuration/Forwarding Delay YES/NO.
|
CSCds43712
|
PerfMon statistics appear to be unreliable.
|
The Cisco CallManager software has been modified so that the PerfMon statistics appear correctly.
|
CSCds43792
|
Sending Disconnect with cause equals an unallocated number.
|
The protocol violation on inbound call was fixed. According to Q.931 standard, Cisco CallManager shall send RELEASE COMPLETE instead of DISCONNECT when unassigned number is received in the SETUP message.
|
CSCds46180
|
Slow SDL timer Service using call load of 2.25 cps and IVR
|
Internal data structures that kept track of call information were not being cleaned up correctly which lead to some inefficiencies over time.
|
CSCds53378
|
AVVID: 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.
|
CSCds57574
|
WebAttendant will not install on Win98 client machine
|
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. Starting the timer was moved from the loading of the DLL to when the actual loading of the control by the web browser occurs. This allows the regsvr32.exe to load and register the DLL.
|
CSCds61655
|
GetCallInfo returns wrong info on call fwded to route point.
|
A changed was made previously to save information about the calling, called, and redirected parties during call setup, so this information can be returned in the lineGetCallInfo when the call is forwarded. These changes were made to the code that handles the stations but also needed to be made to the code that handles route points.
|
CSCds61871
|
No error message occurs on unauthorized CTI user via TSP.
|
The problem was corrected by using a timer to introduce a delay between sending the response and closing the pipe.
|
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). After the change, the calling, called party number, and name correctly display for both the active call and incoming call.
|
CSCds63489
|
Call waiting call is not idled on Call Forward No Answer.
|
A fix was made to CTI to allow the 3rd and subsequent calls to roll to voicemail or be answered instead of disconnecting or going to fast busy.
|
CSCds65046
|
Server logs out Cisco WebAttendant client when the client is idle for 2 minutes.
|
A race condition was causing TCD to corrupt its keepalive tracking registers for some logged-on clients. This would cause TCD to erroneously determine that the client was dead, closing the TCP connection to the client. Changes were made to prevent this multi threaded race condition from affecting the keep alive logic.
|
CSCds66353
|
Cisco CallManager tells MGCP gateway to use VAD when SilenceSuppression is set to False.
|
The Cisco CallManager software's code was modified to support SilenceSuppression accordingly.
|
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. Starting the timer was moved from the loading of the DLL to when the actual loading of the control by the web browser occurs. This allows the regsvr32.exe to load and register the DLL.
|
CSCds67120
|
CTI logs out TCDSRV and drops TCP connection.
|
The fix was made to process the heartbeat at normal priority.
|
CSCds67147
|
Illegal characters are accepted when setting user password.
|
There are no checks in place when users first enters their password, this is causing the problem since there is a check in place when their password gets validated.
|
CSCds67766
|
Install: SAenvProperties.ini is not updated after the install.
|
The silent portion of the install that Automated Install executes was not calling the code to set this up.
|
CSCds68278
|
CTI ports are disabled during upgrades.
|
The DCD upgrade process has been changed to preserve the existing value of the CTI Application Use Enabled global flag. Thus, if a user has set the value of the global flag to true, the value would still be set to true after an upgrade.
|
CSCds69538
|
Conference is in bad state when Cisco AutoAttendant redirects call back to its own ports
|
When Cisco AutoAttendant is redirected to a second CTI port, a redirect signal is sent 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. As a result, it never checked for that possibility and did not correctly delete the old information and add new information into its tables regarding the present configuration of the conference.
|
CSCds70328
|
Cisco WebAttendant timed out and gave no reorder tone.
|
Cisco CallManager software was modified to use the correct call reference identifier to build the CcRejInd message when the CtiNewCallAcceptTimer was received so that the CcRejInd message was sent to the correct process to clear the call with reorder tone.
|
CSCds72813
|
CTI: Gigantica crashes when opening provider with ctifw user.
|
Cisco CallManager is crashing when user passes a device name bigger than 15 characters. The problem is happening as user copies longer than 15-character names in CtiDeviceName variable, causing it to have nonnull terminated string. Terminating the string with Null corrected the problem.
|
CSCds73688
|
SdlMaxUnHandledExceptions=0 results in StackWalk.
|
The value was hard coded to 5 and not read from database, and the code was not checking for not equal to zero in 3 of the 16 places.
|
CSCds74266
|
Cisco CallManager crashes and restarts; then, it sits idle until manual restart.
|
The Cisco CallManager software has been modified to rectify this problem.
|
CSCds76640
|
State of Logout and Go Offline buttons does not change.
|
This problem was solved by syncing up the TCD server and the Cisco WebAttendant.
|
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).
|
A race condition between DCD's initialization and the execution of avvid_upgrade caused the problem. The avvid_upgrade script now waits 20 seconds for DCD to finish its initialization before continuing with the upgrade process.
|
CSCds79952
|
Cisco CallManager stackwalk for CM2 of Dallas Alpha
|
Buffer was increased to allow large display names on CTI and phone devices.
|
CSCds81073
|
PRIUser ringback does not perceive reorder tone with CallForward Incorrect.
|
Cisco CallManager software has been modified to process the CcInfoReq message in state:
call_received7 (ProcessPn9cuser) and call_delivered4 (ProcessPn9cnet and ProcessH225Cdpc), and if the cause code value in the CcInfoReq is temporary failure, send the Disconnect message to disconnect the call. By doing so, it prevents the caller from the gateway receiving the ringback tone for a long period of time even when the call was dismissed due to the error while accessing the voice mail (such as voice mail configuration error or hop count exceeded).
|
CSCds82156
|
Confusing screen occurs on auto upgrade when selecting publisher/subscriber is selected
|
The screen was changed to be read more clearly.
|
Resolved Caveats - Release 3.0(5a)
Table 4 lists and describes Caveats that were resolved in Cisco CallManager Release 3.0(5a).
Table 4 Cisco CallManager Release 3.0(5a) Resolved Caveats
DDTS Number
|
Summary
|
Explanation
|
CSCdp96950
|
CPU usage stays up to 100% with svchost.exe.
|
This was determined to be a Microsoft problem. Currently, a new version of tapisrv.dll fixes this problem.
|
CSCdr35751
|
This problem occurs when Call Forward All is cleared from the user preference pages for a DN that is shared by multiple phones (that is, a multiline).
|
When Call Forward All is cleared on a multiline, a reset is only sent down to one phone that shares the multiline, and the call forward lights are cleared on that phone only. The call forward is cleared for the specified DN, but the forward lights on all other phones will remain on, thus giving a false indication that the phone is still forwarded, when it really is not.
|
CSCdr40345
|
Errors are returned by the Cisco CallManager User Administration web pages.
|
These errors appear when the directory does not contain a complete listing of the devices in the Cisco CallManager database. This occurs when the directory is first configured with a large number of devices to import from the database to the directory.
|
CSCdr41614
|
DTMF digits are not propagated to members of a conference.
|
When a DTMF digit is pressed when a phone is connected to a conference, the digit is dropped.
For example, if a ringing phone is added to a conference, and the phone is subsequently not answered and forwards to voice mail, there is no way to remove that party from the conference, or to exit or shut down voice mail.
|
CSCdr42883
|
Memory leaks in the database occur as a result of normal operation of the system.
|
DLLHost.exe as the executable grows in memory size as changes are made to the database via services or Cisco CallManager Administration. If a long time elapses, the memory size will drop. However, if several services poll the database periodically, this may not occur.
|
CSCdr49680
|
When the Cisco Catalyst 6000 8 Port Voice T1 and Services Module is reset while conferences are in progress, the Cisco CallManager will not set up any more conferences.
|
This occurs when the device re-registers with the Cisco CallManager, and the callers have not yet hung up the phones.
|
CSCdr50642
|
After the initial installation, changing a server name to an IP address will cause phones not to boot. Auto-registering phones will not connect to Cisco CallManager.
|
The reason they do not connect is that the configuration file still contains the server name.
|
CSCdr51675
|
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."
|
This problem occurs under any of the following conditions:
•The server hosting the Cisco CallManager Administration web pages cannot resolve the name or IP address of the target server.
•The target server is offline.
•The target server no longer exists, but it is still configured in the Cisco CallManager Administration pages.
•The target server's name in DNS does not match the server's machine name.
|
CSCdr57242
|
OutofBandwidthText is not on by default.
|
A call from a Cisco IP Phone to another Cisco IP Phone gets a reorder tone intermittently. Nothing on the phone display indicates the reason. Further troubleshooting showed that the call was made between locations, and it was out of bandwidth. The Cisco IP Phone should have displayed the "Not Enough Bandwidth" message by default.
|
CSCdr68109
|
Cisco CallManager service does not display in Windows 2000 services after subscriber installation.
|
The publisher and subscriber Cisco CallManager servers are installed. All the Cisco CallManager services appear in Windows 2000 services on the subscriber after installation.
|
CSCdr75417
|
Backspace in Telecaster could crash Cisco Call Manager.
|
While attempting to make an outgoing call from a Cisco IP Phone 7960, if the user presses the "BackSpace <<" quick |
