Resolved Caveats
38
Release Notes for Cisco CallManager Release 3.0(10)
78-13493-02
CSCdt57397
The file, ringlist.xml, is overwritten
during upgrades, which causes the
Cisco IP Phone 7960 to reset.
A code change causes the ringlist to remain
after upgrade.
CSCdt58120
Cisco CallManager update should not
ask if machine is publisher/subscriber
A Cisco CallManager code change ensures
that the software automatically detects the
machine type.
CSCdt58373
100% CPU usage occurs when call is
disconnected manually after open and
or close line.
A Cisco CallManager code change corrects
this behavior.
CSCdt58667
CDR code does not handle exceptions
and needs more debugging.
A Cisco CallManager code change corrects
this behavior.
CSCdt58776
No disconnected event occurs after
adding and removing observers.
A Cisco CallManager code change corrects
this behavior.
CSCdt59083
RedirectingID is not correct when call
is redirected and then forwarded.
A Cisco CallManager code change corrects
this behavior.
CSCdt60194
No dial tone/lineOpen failed occurs
after TSP regression test.
A Cisco CallManager code change corrects
this behavior.
CSCdt62354
Cisco CallManager does not reregister
with gatekeeper after WAN failure
clears.
A code change corrects this behavior.
CSCdt66118
With null translation pattern exists, all
calls release without a tone.
A Cisco CallManager code change corrects
this behavior.
CSCdt69132
A need exists to add additional
debugging information for dead router
services.
A Cisco CallManager code change corrects
this behavior.
CSCdt81114
Fragmented skinny messages may crash
Cisco CallManager.
A network was causing packets to get
delayed and broken apart. The fragmented
messages were coming from only one
building.
CSCdt82472
Hitting line button on a multiline phone
fails in some scenarios.
A code change corrects this behavior.
Table 3
Cisco CallManager Release 3.0(9) Resolved Caveats (continued)
DDTS Number Summary
Explanation