Resolved Caveats

 

Table 7

Cisco CallManager Release 3.0(5a) Resolved Caveats (continued)

 

 

 

 

 

DDTS Number

Summary

Explanation

 

 

 

 

 

CSCdr78651

Ability to park call by directory number

Modified park code allocation to use the

 

 

 

is missing.

same park code number when call park

 

 

 

 

reversion occurred. This allows the parking

 

 

 

 

party to repark the same call to the same

 

 

 

 

park code in effect when call park reversion

 

 

 

 

occurred.

 

 

 

 

 

CSCdr80088

Metalink import error message occurs.

Reinstallation fixed the problem.

 

 

 

 

 

CSCdr80095

Large number of File Does Not Exist

Automated install was changed to include

 

 

 

messages appear in event viewer.

the following directory:

 

 

 

 

C:\WINNT\Help\iisHelp

 

 

 

 

 

CSCdr92982

The Cisco Messaging Interface trace

The Cisco Messaging Interface service has

 

 

 

will not create trace files after

to be stopped and started to create the new

 

 

 

configuring TraceFile.

file.

 

 

 

 

 

CSCdr93620

Database migration of Cisco uOne ports

The administrator must remove the

 

 

 

from Cisco CallManager Release 2.4 to

VoiceMail DNs from NumPlan table when

 

 

 

Release 3.0 fails.

migrating from 2.4 to 3.0 in order to fix this

 

 

 

 

problem.

 

 

 

 

 

CSCds09586

100% CPU utilization occurs on the

This problem occurred when trying to set

 

 

 

web server (inetinfo).

the Speed Dial on an administrator’s phone.

 

 

 

 

 

CSCds10242

Cisco IP Phone 7960 to NetMeeting

Calls from a Microsoft NetMeeting client to

 

 

 

G.711 calls without MTP have poor

a Cisco 7960 IP phone result in poor audio

 

 

 

audio quality.

quality heard on the Cisco IP Phone 7960

 

 

 

 

side of the conversation. If the 'i' button is

 

 

 

 

pressed twice while the call is active, the

 

 

 

 

RxSize shows up as 32, although it should

 

 

 

 

be 20. This problem is not observed on

 

 

 

 

Cisco IP PHone model 30 VIP or Cisco IP

 

 

 

 

Phone model 12 SP+ phones.

 

 

 

 

 

CSCds14106

Cisco CallManager 3.0(2d) stops

Cisco CallManager may stop responding

 

 

 

responding after starting; it will not

and stop accepting connections after

 

 

 

accept any connections.

starting up if a high number of route

 

 

 

 

patterns are configured (greater than 300).

 

 

 

 

 

 

 

 

Release Notes for Cisco CallManager Release 3.0(10)

 

 

 

 

 

 

78-13493-02

 

 

61

 

 

 

Page 61
Image 61
Cisco Systems 3.0(10) manual Summary Explanation