Cisco CallManager Release 3.0(10 Specification page 42

Resolved Caveats
Table 4 Cisco CallManager Release 3.0(8) Resolved Caveats (continued)
DDTS Number Summary
CSCds91320 AVVID: PerfMon ccmActivePhones
counter is incorrect.
CSCdt02726 Consult call fails throwing exception.
CSCdt04309 Disable ring on a shared line does not
work properly on blind transfer.
CSCdt06347 When device is deleted, the forward
intercept table is not updated.
CSCdt07520 User receives error message when
changing partition on phone line.
CSCdt07581 Insert new user page does not update
WA AutoDial name correctly
CSCdt08275 Call forward does not work for the
second time with IVR route point
CSCdt08446 Gatekeeper Device pool change
requires resetting the PC.
CSCdt09642 Deleting a gateway gives error message. When the deletion succeeds, no error
CSCdt11706 The wrong redirecting parameters exist
for Call Forward No Answer.
CSCdt12383 Cisco CallManager may crash when
making gatekeeper-controlled calls.
CSCdt12794 Consult failed due to
InvalidStateException.
CSCdt13681 A directory number started returning
busy to callers because too many calls
had been forwarded to that number.
Release Notes for Cisco CallManager Release 3.0(10)
42
Explanation
A Cisco CallManager code change allows
the PerfMon counter to display correctly.
A Cisco CallManager code change corrects
this problem.
The problem of keying on the wrong
directory number was fixed.
The call-forwarding properties associated
with this deleted device remain valid to
Cisco CallManager even though the device
no longer exists.
A Cisco CallManager code change cor-
rected this problem.
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.
A Cisco CallManager code change
corrected this problem.
A Cisco CallManager code change cor-
rected this problem.
message is given.
A Cisco CallManager code change fixed
this caveat.
A Cisco CallManager code change
corrected this problem.
A Cisco CallManager code change
corrected this problem.
A Cisco CallManager code change cor-
rected this problem.
78-13493-02