Resolved Caveats
62
Release Notes for Cisco CallManager Release 3.0(10)
78-13493-02
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.
During standard installation, an error
occurred making the processing of
Cisco CallManager shut down, but the
CCM.exe service did not clear itself from
memory.
CSCds26356
MGCP cannot do a one-to-one port
mapping with an IP phone.
Changes were made in Cisco CallManager
code to support the Service Parameter flag
MatchingCgpnWithAttendantFlag, though,
for a large site, using this flag is not an
optimal solution for call completion rate.
With 1500 FXO ports, call completion rate
could be reduced by 4. Cisco recommends
to spend the initial configuration effort to
use Partition and Calling Search Space. A
combination of these two methods might be
the optimal solution.
CSCds36692
Having in excess of 200 translation
patterns causes Cisco CallManager to
take more than 10 minutes to initialize.
This has been fixed by increasing the
timeout from 10 to 20 minutes.
CSCds38023
Non-unique timer ID causes transfer
and hold to stop working.
After long periods, there was a chance that
unique timer ID was no longer unique. This
would cause various timers to fail. The
problem was identified and fixed.
CSCds53566
Unable to unpause backup service in
MCS backup utility
Automated Install fixed this problem for
Cisco CallManager 3.0(5a).
Table 7
Cisco CallManager Release 3.0(5a) Resolved Caveats (continued)
DDTS Number Summary
Explanation
