Cisco CallManager Release 3.0(10 Specification page 56

Resolved Caveats
Table 6 Cisco CallManager Release 3.0(6) Resolved Caveats (continued)
DDTS Number Summary
CSCds69538 Conference is in bad state when
Cisco AutoAttendant redirects call back
to its own ports
CSCds70328 Cisco WebAttendant timed out and
gave no reorder tone.
CSCds72813 CTI: Gigantica crashes when opening
provider with ctifw user.
CSCds73688 SdlMaxUnHandledExceptions=0
results in StackWalk.
CSCds74266 Cisco CallManager crashes and
restarts; then, it sits idle until manual
restart.
CSCds76640 State of Logout and Go Offline buttons
does not change.
Release Notes for Cisco CallManager Release 3.0(10)
56
Explanation
When Cisco AutoAttendant is redirected to
a second CTI port, a redirect signal is sent
to the Conference process inside of
Cisco CallManager. The logic in this
process was not expecting a conference
resource to be an origination point for a
redirection. As a result, it never checked for
that possibility and did not correctly delete
the old information and add new
information into its tables regarding the
present configuration of the conference.
Cisco CallManager software was modified
to use the correct call reference identifier to
build the CcRejInd message when the
CtiNewCallAcceptTimer was received so
that the CcRejInd message was sent to the
correct process to clear the call with reorder
tone.
Cisco CallManager is crashing when user
passes a device name bigger than 15
characters. The problem is happening as
user copies longer than 15-character names
in CtiDeviceName variable, causing it to
have nonnull terminated string. Terminating
the string with Null corrected the problem.
The value was hard coded to 5 and not read
from database, and the code was not
checking for not equal to zero in 3 of the 16
places.
The Cisco CallManager software has been
modified to rectify this problem.
This problem was solved by syncing up the
TCD server and the Cisco WebAttendant.
78-13493-02