Cisco CallManager Release 3.0(10 Specification page 46

Table of Contents

Advertisement

Resolved Caveats
Table 4
Cisco CallManager Release 3.0(8) Resolved Caveats (continued)
DDTS Number Summary
CSCdt28640
Cisco IP Phone 7960 intermittently
delays dialtone when going off-hook.
CSCdt29217
Call Park code correction to avoid
blocking of Call Park numbers.
CSCdt31546
A DBL exception in MWI message may
crash the Cisco Callmanager.
CSCdt38000
Cisco IP Phone 7960 does not register
after cluster-wide outage.
CSCdt38916
CallingParty=Unknown Number does
not work with Cisco uOne
CSCdt39262
Cisco CallManager may allow more
calls than limited by Locations.
CSCdt39402
One-way audio exists with DT-24+
Load D003H300.
CSCdt62890
A deleted phone extension still exists in
SQL database.
Release Notes for Cisco CallManager Release 3.0(10)
46
Explanation
The off-hook message was getting delayed
only in certain scenarios. A
Cisco CallManager code change resolved
this caveat.
A Cisco CallManager code change fixed
this caveat.
A Cisco CallManager code change cor-
rected this problem.
A Cisco CallManager code change ensures
that, if registration is not acknowledged, the
phone will recover.
A Cisco CallManager code change checks
the calling party length field before calling
the related function.
The problem was that the bandwidth to be
consumed (24 kbps or 80 kbps) was an
"unsigned int" and it was being compared
for greater than a negative "int."
During the ARP cache timeout, removal of
a dynamic entry was causing the port count
to go negative. The port count prevents the
removal of an address that is being used by
several streams. A Cisco CallManager code
change prevents the port count variable
from going negative during ARP cache
timeout.
After you delete the phone, the extension no
longer appears in SQL database.
78-13493-02

Advertisement

Table of Contents
loading

This manual is also suitable for:

Callmanager release 3.0

Table of Contents