37
Release Notes for Cisco CallManager Release 3.0(10)
78-13493-02
Resolved Caveats
CSCdt44128
6608 sends disconnect when it does not
receive an alerting fast enough.
A Cisco CallManager service parameter
was extended to correct this behavior.
CSCdt48748
When Windows 2000 Administrator
account name is changed, i.e., to
"callmngradmin,” the installation
reports an error changing the admin
password.
After upgrading to Cisco CallManager
3.0(9), the customer no longer experienced
this problem.
CSCdt49457
STI backup may fail with large
database.
A newly created backup prevents this
behavior.
CSCdt51159
Resetting h.225 device by any means
causes AnonymousDevice failure.
A Cisco CallManager code change corrects
this behavior.
CSCdt51281
ISDN layer3 stack on PRI-EURO
response to INFOR in state U4
A Cisco CallManager code change corrects
this behavior.
CSCdt52273
MeetMe conference button does not
reset T302 timer.
A new timer corrects this problem.
CSCdt52506
CDR database will not be restored.
When backing up Cisco CallManager
databases larger than 2 GB to a local or
network drive, the file is clipped while
being added to the TAR file.
The backup software was fixed to get rid of
a 2 GB limitation.
CSCdt53123
Cisco CallManager does not register
with gatekeeper until the
Cisco CallManager is stopped and
started.
A button now exists to reset the gateway.
CSCdt53834
Cisco Catalyst 6000 8 Port Voice E1/T1
and Services Module does not support
G711Alaw.
The code that caused this caveat only
checked for G711 muLaw. The code now
checks for G711ALaw.
CSCdt54279
Change of zone name in Gatekeeper
device requires the administrator to stop
and start the Cisco CallManager.
The code now changes the gatekeeper zone,
and the administrator uses the Reset
Gatekeeper button to reset gatekeeper.
Table 3
Cisco CallManager Release 3.0(9) Resolved Caveats (continued)
DDTS Number Summary
Explanation