|
|
|
|
|
|
|
| Resolved Caveats |
|
Table 4 | Cisco CallManager Release 3.0(8) Resolved Caveats (continued) |
| ||
|
|
|
| |
DDTS Number | Summary | Explanation |
| |
|
|
|
| |
CSCdt21490 | MTP resets on 23rd | When the CPU time is lower than a low |
| |
|
| transcoding(VAD enabled) | watermark, the transcoder takes no new |
|
|
|
| calls (and the calls will not be complete). |
|
|
|
| All new calls will be rejected. The |
|
|
|
| transcoder will not accept new calls until |
|
|
|
| CPU idle time goes above a high |
|
|
|
| watermark. CPU time is regained after |
|
|
|
| some active calls go idle. A high watermark |
|
|
|
| is used to reopen the new channels after |
|
|
|
| entering into a rejection mode, which is |
|
|
|
| entered when a call is rejected by a low |
|
|
|
| watermark. After the change, #24 call or |
|
|
|
| more calls will be rejected but will not |
|
|
|
| cause the transcoder to reset. |
|
|
|
|
| |
CSCdt21581 | User experiences a fast busy when | A Cisco CallManager code change resolves |
| |
|
| transferring a conference. | this caveat. |
|
|
|
|
| |
CSCdt23132 | Bandwidth control with shared lines | A Cisco CallManager code change fixes |
| |
|
| results in only 1 line ringing. | this problem. |
|
|
|
|
| |
CSCdt25478 | Call forwarding on the same phone | A Cisco CallManager code change fixes |
| |
|
| inherits ring of forwarded lines. | this caveat. |
|
|
|
|
| |
CSCdt27176 | When user resets DT24 gateway, | A Cisco CallManager code change fixed |
| |
|
| Cisco CallManager crashes with | this caveat. |
|
|
| DrWatson. |
|
|
|
|
|
| |
CSCdt27572 | Inbound callers get reorder; B channel | A CcRejReq message coming into the B |
| |
|
| is out of service. | channel process (processpn9cuser) and not |
|
|
|
| being handled caused this bug. The B |
|
|
|
| channel hung in an uncertain state, but the |
|
|
|
| CO in the PSTN received it as available for |
|
|
|
| new calls. |
|
|
|
|
| |
CSCdt27581 | User cannot delete partitions. This is an | A Cisco CallManager code change fixed |
| |
|
| error but m_com_error was not valid. | this caveat. |
|
|
|
|
|
|
|
| Release Notes for Cisco CallManager Release 3.0(10) |
|
|
|
|
| ||
|
|
| 45 | |
|
|
|
