Resolved Caveats
24
Release Notes for Cisco CallManager Release 3.0(10)
78-13493-02
CSCdt75620
A need exists for TAPI dwCalledID to
reflect original called party.
A code change ensures that TAPI
dwCalledID reflects the original called
party.
CSCdt75990
Calls with compatible regions and
capabilities fail.
A code change resolves this behavior.
CSCdt78337
If call park range overlaps at pattern,
Cisco CallManager router thread may
stop.
If call park range overlapped an external
dial pattern, and you dialed one of the call
park numbers, Cisco CallManager may
have displayed a router thread stopped
error.
A code change corrects this behavior.
CSCdt80375
Cisco Access Digital Trunk Gateway
DT-24+ may not reregister after failure.
Rare circumstances can lead
Cisco CallManager to perceive a
Cisco Access Digital Trunk Gateway
DT-24+ D-channel as still online when, in
reality, it is down and has unregistered with
the Cisco CallManager. This causes
CallManager to bar the Cisco Access
Digital Trunk GatewayDT-24+ from
reregistering because it perceives the
D-channel to be up.
A Cisco CallManager code change corrects
this behavior.
CSCdt82340
Cisco CallManager does not restart
when experiencing race condition.
Cisco CallManager software modification
in the initilization procedure makes it exit
abnormally when there is a problem
(exception returned from DBL) with
initializing the CDR thread.
CSCdt83029
When an extension has a call on hold
and an active call, the held call does not
disconnect when each caller hangs up
on the call.
CTI now sends an event indicating that the
call on HOLD and an active call exist, and
the active call hangs up.
CSCdt83360
After Cisco CallManager is upgraded,
some services do not appear.
A code change extends the services URL
maximum length to beyond 128 characters.
Table 2
Cisco CallManager Release 3.0(10) Resolved Caveats (continued)
DDTS Number Summary
Explanation
