Filter
Top Products
61
Release Notes for Cisco CallManager Release 3.0(10)
78-13493-02
Resolved Caveats
CSCdr78651 Ability to park call by directory number
is missing.
Modified park code allocation to use the
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.
CSCdr80095 Large number of File Does Not Exist
messages appear in event viewer.
Automated install was changed to include
the following directory:
C:\WINNT\Help\iisHelp
CSCdr92982 The Cisco Messaging Interface trace
will not create trace files after
configuring TraceFile.
The Cisco Messaging Interface service has
to be stopped and started to create the new
file.
CSCdr93620 Databasemigration of Cisco uOne ports
from Cisco CallManager Release 2.4 to
Release 3.0 fails.
The administrator must remove the
VoiceMail DNs from NumPlan table when
migrating from 2.4 to 3.0 in order to fix this
problem.
CSCds09586 100% CPU utilization occurs on the
web server (inetinfo).
This problem occurred when trying to set
the Speed Dial on an administrator’s phone.
CSCds10242 Cisco IP Phone 7960 to NetMeeting
G.711 calls without MTP have poor
audio quality.
Calls from a Microsoft NetMeeting client to
a Cisco 7960 IP phone result in poor audio
quality heard on the Cisco IP Phone 7960
side of the conversation. If the 'i' button is
pressed twice while the call is active, the
RxSize shows up as 32, although it should
be 20. This problem is not observed on
Cisco IP PHone model 30 VIP or Cisco IP
Phone model 12 SP+ phones.
CSCds14106 Cisco CallManager 3.0(2d) stops
responding after starting; it will not
accept any connections.
Cisco CallManager may stop responding
and stop accepting connections after
starting up if a high number of route
patterns are configured (greater than 300).
Table 7 Cisco CallManager Release 3.0(5a) Resolved Caveats (continued)
DDTS Number Summary Explanation