Resolved Caveats
Table 4 | Cisco CallManager Release 3.0(8) Resolved Caveats (continued) | ||
|
|
| |
DDTS Number | Summary | Explanation | |
|
|
| |
CSCdt19887 | MTP resources reporting status=1, but | The Cisco CallManager software has been | |
|
| Cisco CallManager will not jump to | modified to handle error code 255 from the |
|
| better resources. | Cisco Catalyst 6000 - DSP Resource device |
|
|
| when there is error in opening the receive |
|
|
| channel due to out of resource (transcoder); |
|
|
| either the DSP is dead, or no more DSP is |
|
|
| available in the device. The |
|
|
| Cisco CallManager marks the device |
|
|
| unavailable, so that the next call uses the |
|
|
| next transcoder device. The Cisco Catalyst |
|
|
| 6000 - DSP Resource device will wait until |
|
|
| all the active calls existing in the device |
|
|
| become idle; then, it resets itself and |
|
|
| reregisters with the Cisco CallManager. |
|
|
| |
CSCdt20674 | Manual DA restart causes | The Cisco Access Digital Trunk Gateway | |
|
| Cisco CallManager restart. | DT - 24+ control process was stopping |
|
|
| before a related thread that reads the udp |
|
|
| messages coming in from the gateway had |
|
|
| stopped. This udp read thread was then |
|
|
| trying to access Cisco Access Digital Trunk |
|
|
| Gateway DT - 24+ data members that no |
|
|
| longer existed in memory, thus causing a |
|
|
| crash of Cisco CallManager. |
|
|
|
|
| Release Notes for Cisco CallManager Release 3.0(10) |
44 |