Cisco Systems 3.0(10) manual Summary Explanation

			Resolved Caveats
Table 7	Cisco CallManager Release 3.0(5a) Resolved Caveats (continued)
DDTS Number		Summary	Explanation
CSCdr41614		DTMF digits are not propagated to	When a DTMF digit is pressed when a
		members of a conference.	phone is connected to a conference, the
			digit is dropped.
			For example, if a ringing phone is added to
			a conference, and the phone is subsequently
			not answered and forwards to voice mail,
			there is no way to remove that party from
			the conference, or to exit or shut down voice
			mail.
CSCdr42883		Memory leaks in the database occur as	DLLHost.exe as the executable grows in
		a result of normal operation of the	memory size as changes are made to the
		system.	database via services or Cisco CallManager
			Administration. If a long time elapses, the
			memory size will drop. However, if several
			services poll the database periodically, this
			may not occur.
CSCdr49680		When the Cisco Catalyst 6000 8 Port	This occurs when the device re-registers
		Voice T1 and Services Module is reset	with the Cisco CallManager, and the callers
		while conferences are in progress, the	have not yet hung up the phones.
		Cisco CallManager will not set up any
		more conferences.
CSCdr50642		After the initial installation, changing a	The reason they do not connect is that the
		server name to an IP address will cause	configuration file still contains the server
		phones not to boot. Auto-registering	name.
		phones will not connect to
		Cisco CallManager.

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