49
Release Notes for Cisco CallManager Release 3.0(10)
78-13493-02
Resolved Caveats
CSCds81134 Release messages are missing from
Cisco CallManager.
Changes made to the translation pattern to
amends this problem.
CSCds82314 Cisco CallManager will not initialize if
many translation patterns exist.
The ability to initialize quickly even if
hundreds (tested with 2000 translations) of
translation patterns exist was added to the
software.
CSCds85150 CTI: gateway call is not producing
ringback event.
CTI call state notification is sent, so ring-
back will be heard.
CSCds85215 Application gets Talking event even
though call is over.
CallManager.java was modified to process
callClosedEvent, so that it does not send
any getCallInfo request.
CSCds85283 Memory leak occurs in call waiting
scenario
The Cisco CallManager software was
changed to keep memory from growing in
specific call waiting scenario.
CSCds87448 IP voice media streaming application
uses 100% CPU.
The Cisco CallManager code was changed
to recover from a random unhandled
internal error causing high CPU usage.
CSCds87552 Blind transfer from voice mail locks up
port.
Cisco CallManager software has been
modified to reset the intercept entry's
dnActive field even when it cannot find the
active call entry for the ssParty when
receiving the ssDataInd msg.
CSCds90217 CiscoAddrInServiceEv is not sent for
softphone.
ProviderImpl and TerminalImpl were
changed, so JTAPI opens the CTI Port when
DeviceRegisteredEvent for a third-party
observer as a result of first-party observers
register the CTI Port.
CSCds90743 Cisco CallManager crashes when
attempting to add 17 participants to
conference bridge.
Cisco CallManager was fixed to prevent
crashes caused by array boundary exceeded
when the number of conference participants
is more than 16.
CSCds91718 Need exists to include CTI Messages in
default SDL trace setting.
The default database was changed to
facilitate this problem.
Table 5 Cisco CallManager Release 3.0(7) Resolved Caveats (continued)
DDTS Number Summary Explanation