Cisco CallManager Release 3.0(10 Specification page 40

Resolved Caveats
Table 4 Cisco CallManager Release 3.0(8) Resolved Caveats (continued)
DDTS Number Summary
CSCds13646 AVVID: SNMP agent is missing on
Cisco CallManager. MIBII Host Branch
CSCds34122 A failure to delete or reset the MGCP
gateway exists in the find & list gateway
page.
CSCds50672 Call Forward All from a directory
number to the same directory number
causes high CPU usage.
CSCds53113 User hears a dual ringback tone when
calling PSTN using H.323 gateway.
CSCds57777 AVVID: PerfMon H.323 gateway is
reinstantiated at Cisco CallManager
reset of gateway.
CSCds65137 No option exists for Subscriber for
called and or calling party; i.e., number
type.
CSCds66475 Cisco CallManager does not allow a
Automated Install on top of a FAT32b
partition. This caveat is fixed on the
MCS 7825/7835/7835-1000.
CSCds67657 1GB virtual memory grab occurs on
Cisco CallManager with hot fix.
CSCds69496 External Call Forward All loop causes
high Cisco CallManager CPU usage.
Release Notes for Cisco CallManager Release 3.0(10)
40
Explanation
The vendor's SNMP Extension Agent
provides the functionalities for browsing
the MIB II tree through the SNMP Agent;
therefore, it is not in the domain of the
Cisco CallManager SNMP Extension
Agent.
The Cisco CallManager code change
handles MGCP gateway delete and reset
from Find&List gateway page.
Call Forward All can no longer be used to
call the same directory number.
Call control no longer directs the
originating device to play ringback on
alerting if call control has already cut
through media.
The H.323 PerfMon statistics are removed
when the H.225D stops.
A Cisco CallManager code changes adds
support for Subscriber Number option for
Calling/Called party IE number type in the
digital PRI gateway configuration page.
This issue only occurs if the C: drive is
changed to FAT32. The auto install will be
modified to install over a FAT32 partition
regardless of the specific drive associated to
that partition.
This fix causes the base virtual memory
footprint to be larger than in the past, but it
solves the memory losses seen in the past.
Setting the CallManager Service Parameter
MaxForwardsToDn to 0 disables the cause
of this problem.
78-13493-02