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
CSCds19447		No information about	The AutoAttendant Administrative Guide
		Cisco AutoAttendant install exists in	documents the information.
		Cisco CallManager install documents.
CSCds21377		The Cisco CallManager service was up	During standard installation, an error
		but was not running. Looking at	occurred making the processing of
		PerfMon statistics showed that the CPU	Cisco CallManager shut down, but the
		utilization of Cisco CallManager was	CCM.exe service did not clear itself from
		zero, but Cisco CallManager did show	memory.
		as running.
CSCds26356		MGCP cannot do a one-to-one port	Changes were made in Cisco CallManager
		mapping with an IP phone.	code to support the Service Parameter flag
			MatchingCgpnWithAttendantFlag, though,
			for a large site, using this flag is not an
			optimal solution for call completion rate.
			With 1500 FXO ports, call completion rate
			could be reduced by 4. Cisco recommends
			to spend the initial configuration effort to
			use Partition and Calling Search Space. A
			combination of these two methods might be
			the optimal solution.
CSCds36692		Having in excess of 200 translation	This has been fixed by increasing the
		patterns causes Cisco CallManager to	timeout from 10 to 20 minutes.
		take more than 10 minutes to initialize.
CSCds38023		Non-unique timer ID causes transfer	After long periods, there was a chance that
		and hold to stop working.	unique timer ID was no longer unique. This
			would cause various timers to fail. The
			problem was identified and fixed.
CSCds53566		Unable to unpause backup service in	Automated Install fixed this problem for
		MCS backup utility	Cisco CallManager 3.0(5a).

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