Resolved Caveats
60
Release Notes for CiscoCallManager Release 3.0(10)
78-13493-02
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.
•Thetarget 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 IPPhone 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 IPPhone should
have displayed the "Not Enough
Bandwidth" message by default.
CSCdr68109 Cisco CallManager service does not
displayin Windows 2000 services after
subscriber installation.
The publisher and subscriber
Cisco CallManager servers are installed.
All the Cisco CallManager services appear
inWindows 2000 services on the subscriber
after installation.
CSCdr75417 Backspacein Cisco IP Phone 7960 may
crash Cisco Call Manager. While attempting to make an outgoing call
from a Cisco IP Phone 7960, if the user
presses the "BackSpace <<" quickly
enough, it can intermittently cause a
Cisco CallManager restart.
Table7 Cisco CallManager Release 3.0(5a) Resolved Caveats (continued)
DDTS Number Summary Explanation