Resolved Caveats
Table 6 |
| Cisco CallManager Release 3.0(6) Resolved Caveats (continued) | ||||
|
|
|
| |||
DDTS Number | Summary | Explanation | ||||
|
|
|
| |||
CSCds69538 | Conference is in bad state when | When Cisco AutoAttendant is redirected to | ||||
|
|
| Cisco AutoAttendant redirects call back | a second CTI port, a redirect signal is sent | ||
|
|
| to its own ports | 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. | ||
|
|
|
| |||
CSCds70328 | Cisco WebAttendant timed out and | Cisco CallManager software was modified | ||||
|
|
| gave no reorder tone. | 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. | ||
|
|
|
| |||
CSCds72813 | CTI: Gigantica crashes when opening | Cisco CallManager is crashing when user | ||||
|
|
| provider with ctifw user. | passes a device name bigger than 15 | ||
|
|
|
| characters. The problem is happening as | ||
|
|
|
| user copies longer than | ||
|
|
|
| in CtiDeviceName variable, causing it to | ||
|
|
|
| have nonnull terminated string. Terminating | ||
|
|
|
| the string with Null corrected the problem. | ||
|
|
|
| |||
CSCds73688 | SdlMaxUnHandledExceptions=0 | The value was hard coded to 5 and not read | ||||
|
|
| results in StackWalk. | from database, and the code was not | ||
|
|
|
| checking for not equal to zero in 3 of the 16 | ||
|
|
|
| places. | ||
|
|
|
| |||
CSCds74266 | Cisco CallManager crashes and | The Cisco CallManager software has been | ||||
|
|
| restarts; then, it sits idle until manual | modified to rectify this problem. | ||
|
|
| restart. |
|
|
|
|
|
|
| |||
CSCds76640 | State of Logout and Go Offline buttons | This problem was solved by syncing up the | ||||
|
|
| does not change. | TCD server and the Cisco WebAttendant. | ||
|
|
|
|
|
|
|
|
| Release Notes for Cisco CallManager Release 3.0(10) |
|
|
| |
|
|
|
|
| ||
56 |
|
|
|
|
| |
|
|
|
| |||
