Cisco CallManager Release 3.0(10 Specification page 79

Table 8
DDTS number Description
CSCdu06412 Cisco CallManager incorrectly interprets the disconnect cause.
Workaround: Use the route group that chooses local gateway.
CSCdu08950 Unchecking the run H.225 on every node still has location leaks.
Workaround: No workaround exists.
CSCdu10456 Transfer succeeds after first party drops.
Workaround: No workaround exists.
CSCdu13985 Race condition exists when observer is removed at same time call is idled.
Workaround: No workaround exists.
CSCdu14950 Octel voice-mail outcall ports lock up.
Workaround: Reset gateway.
CSCdu17141 Call from callpark cannot be retrieved.
Workaround: No workaround exists.
CSCdu18827 A need exists for Cisco CallManager to support leading display character for Digital
Multiplex System (DMS) protocol.
Workaround: For the direction of IP phones to Nortel phones only, the display field
on the line configuration for phones can be set up with a leading space that will fix
the problem in one direction. For the other direction, currently no way exists to
remove the extra, initial character from the display.
CSCdu18892 When the publisher is down, call forward can be configured from the phone, which
should not be possible.
Workaround: No workaround exists.
CSCdu19175 MWI does not work when phone is off line.
Workaround: Have all the phones in one partition and have the Calling Search Space
(CSS) for the voice mailbox have this partition as the first selection in its selection
criteria.
CSCdu20075 Cisco WebAttendant fails to install on Cisco CallManager Release 3.0(9).
Workaround: Use a Cisco WebAttendant install from Callmanager 3.0(7).
78-13493-02
Open Caveats for Cisco CallManager Release 3.0(10) (continued)
Release Notes for Cisco CallManager Release 3.0(10)
Open Caveats
79