Cisco Systems 3.0(10) manual Resolved Caveats

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