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
CSCdt75620		A need exists for TAPI dwCalledID to	A code change ensures that TAPI
		reflect original called party.	dwCalledID reflects the original called
			party.
CSCdt75990		Calls with compatible regions and	A code change resolves this behavior.
		capabilities fail.
CSCdt78337		If call park range overlaps at pattern,	If call park range overlapped an external
		Cisco CallManager router thread may	dial pattern, and you dialed one of the call
		stop.	park numbers, Cisco CallManager may
			have displayed a router thread stopped
			error.
			A code change corrects this behavior.
CSCdt80375		Cisco Access Digital Trunk Gateway	Rare circumstances can lead
		DT-24+ may not reregister after failure.	Cisco CallManager to perceive a
			Cisco Access Digital Trunk Gateway
			DT-24+ D-channel as still online when, in
			reality, it is down and has unregistered with
			the Cisco CallManager. This causes
			CallManager to bar the Cisco Access
			Digital Trunk GatewayDT-24+ from
			reregistering because it perceives the
			D-channel to be up.
			A Cisco CallManager code change corrects
			this behavior.
CSCdt82340		Cisco CallManager does not restart	Cisco CallManager software modification
		when experiencing race condition.	in the initilization procedure makes it exit
			abnormally when there is a problem
			(exception returned from DBL) with
			initializing the CDR thread.
CSCdt83029		When an extension has a call on hold	CTI now sends an event indicating that the
		and an active call, the held call does not	call on HOLD and an active call exist, and
		disconnect when each caller hangs up	the active call hangs up.
		on the call.
CSCdt83360		After Cisco CallManager is upgraded,	A code change extends the services URL
		some services do not appear.	maximum length to beyond 128 characters.
	Release Notes for Cisco CallManager Release 3.0(10)
24			78-13493-02