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

Open Caveats

		Table 8	Open Caveats for Cisco CallManager Release 3.0(10) (continued)
DDTS number		Description
CSCdt50317		Cisco CallManager 3.0(7) Call Detail Records do not nove from subscriber to
		sublisher.
		Workaround: No workaround exists.
CSCdt52841		Cisco WebAttendant documentation calls for read access to the wausers share, but
		change access is required to open the database.
		Workaround: Allow change access to the wausers share.
CSCdt53938		Upgrade does not put BINs in nondefault TFTPPATH.
		Workaround: Two known workarounds exist.
		1) Upgrade the primary TFTP server first
		2) Place the device loads on the primary TFTP server before upgrading any of the
		other clusters.
CSCdt54310		Call Detail Records are written incorrectly when digit manipulation is performed on
		Route List.
		Workaround: Perform digit manipulation on the Route Pattern. This may cause
		other ill effects, such as causing the Placed Calls directory on the Cisco IP phone to
		not include the correct number.
CSCdt57230		Cisco CallManager upgrade adds extra ProcessNode for the same
		Cisco CallManager.
		Workaround: After adding the machine to a domain, the customer must change the
		name of the server in the Cisco CallManager Admin web pages.
CSCdt57230		Cisco CallManager upgrade adds extra ProcessNode for the same
		Cisco CallManager.
		Workaround: No workaround exists.
CSCdt57270		Publisher and or subscriber servers have difficulty with different passwords.
		Workaround: Use the same administrator password for the publisher and all
		subscriber servers.
CSCdt62091		Directory number entries remain in database.
		Workaround: Assign the desired directory number to a phone; then, remove the
		directory number from the phone. The directory number record will be removed from
		the database.
	Release Notes for Cisco CallManager Release 3.0(10)
76			78-13493-02