Cisco Systems 3.0(10) manual Release Notes for Cisco CallManager Release

Resolved Caveats

Table 2	Cisco CallManager Release 3.0(10) Resolved Caveats (continued)
DDTS Number		Summary	Explanation
CSCdt94077		Device tables do not update correctly	Calls going out through a digital gateway
		after failover occurs.	were being dropped after one
			Cisco CallManager in a cluster fails in a
			certain way (links to other
			Cisco CallManagers in the cluster stay up,
			even though its devices fail over), and its
			phones and gateways have registered with
			the backup Cisco CallManager.
			A user running Cisco CallManager Release
			3.0(8) or earlier in a clustered environment
			more likely encounters this problem.
			A Cisco CallManager code change corrects
			this behavior.
CSCdt94179		Redirect fails, and subsequent redirect	A Cisco CallManager code change ensures
		gets no response.	that orphaned destinations get cleaned up
			properly during a redirect of the originator.
CSCdt95027		Cisco CallManager does not allow	Any device, which during registration sends
		simulated phones to register.	the MaxFramePacketSize as zero during
			registration, cannot register with the
			Cisco CallManager.The device needs to
			send the correct capabilities to be able to
			register.
CSCdt95612		When a user right-clicks on the backup	A Cisco CallManager code change corrects
		utility icon in the task tray, then clicks	this behavior.
		somewhere on the desktop, part of the
		popup menu remains on the screen.
CSCdt95934		After Cisco CallManager is upgraded,	To correct this caveat, the database layer
		the Cisco CallManager server IP	now resolves the host name and IP address
		address changes to the	better.
		Cisco CallManager DNS name.

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