Cisco Systems 3.0(10) manual Summary Explanation

Resolved Caveats

Table 4	Cisco CallManager Release 3.0(8) Resolved Caveats (continued)
DDTS Number		Summary	Explanation
CSCdt28640		Cisco IP Phone 7960 intermittently	The off-hook message was getting delayed
		delays dialtone when going off-hook.	only in certain scenarios. A
			Cisco CallManager code change resolved
			this caveat.
CSCdt29217		Call Park code correction to avoid	A Cisco CallManager code change fixed
		blocking of Call Park numbers.	this caveat.
CSCdt31546		A DBL exception in MWI message may	A Cisco CallManager code change cor-
		crash the Cisco Callmanager.	rected this problem.
CSCdt38000		Cisco IP Phone 7960 does not register	A Cisco CallManager code change ensures
		after cluster-wide outage.	that, if registration is not acknowledged, the
			phone will recover.
CSCdt38916		CallingParty=Unknown Number does	A Cisco CallManager code change checks
		not work with Cisco uOne	the calling party length field before calling
			the related function.
CSCdt39262		Cisco CallManager may allow more	The problem was that the bandwidth to be
		calls than limited by Locations.	consumed (24 kbps or 80 kbps) was an
			“unsigned int” and it was being compared
			for greater than a negative “int.”
CSCdt39402		One-way audio exists with DT-24+	During the ARP cache timeout, removal of
		Load D003H300.	a dynamic entry was causing the port count
			to go negative. The port count prevents the
			removal of an address that is being used by
			several streams. A Cisco CallManager code
			change prevents the port count variable
			from going negative during ARP cache
			timeout.
CSCdt62890		A deleted phone extension still exists in	After you delete the phone, the extension no
		SQL database.	longer appears in SQL database.

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