Cisco Systems 3.0(10) manual Summary Explanation

Resolved Caveats

Table 2	Cisco CallManager Release 3.0(10) Resolved Caveats (continued)
DDTS Number		Summary	Explanation
CSCdt42403		User loses a call after transferring	A Cisco CallManager code change corrects
		toward a busy line.	this behavior. This item duplicates
			CSCdt45632, CSCdt82239, and
			CSCdr58998.
CSCdt47805		High CPU usage during directory	This only occurred when 3-4 phones were
		searches from Cisco IP Phone 7960	set to simultaneously do a corporate
		occurs.	directory search with blank search criteria
			that the publisher CPU hits 95+% for 10-20
			seconds.
CSCdt46334		Bandwidth does not release to pool after	A Cisco CallManager code change corrects
		normal call clearing.	this behavior.
CSCdt49472		User cannot assign an all-numeric	A code change allows entry of numeric
		pattern to Gatekeeper-controlled H.225	patterns.
		device.
CSCdt51077		User cannot use hostname as	The software now allows a user to use
		Cisco CallManager server name when	hostname as Cisco CallManager server
		primary DNS suffix is set.	name when primary DNS suffix is set.
CSCdt59773		Cisco IP Phone 7960 is susceptible to a	This occurred when scrolling through
		ping attack and may crash and reboot.	various menus on the phone while it is
			under a ping attack. This no longer occurs.
CSCdt62462		Synchronous Data Link (SDL) router	A Cisco CallManager code change corrects
		service stopped.	this behavior.
CSCdt65935		CallForward SDL update does not work	A Cisco CallManager code change puts in
		(SsapiPtr->SsDbChangeFwdInfoReq).	an alarm to collect more information when
			the Cisco CallManager fails to update the
			local database tables when it receives
			change notification from database layer.
CSCdt66312		Message Waiting Indicator (MWI) stays	A newer version of Cisco Unity TSP
		off when message is left while SP is up,	appears to have made this caveat
		but line is closed.	unreproducible.

	Release Notes for Cisco CallManager Release 3.0(10)
22	78-13493-02