|
|
|
|
|
|
|
| Resolved Caveats |
|
Table 4 | Cisco CallManager Release 3.0(8) Resolved Caveats (continued) |
| ||
|
|
|
| |
DDTS Number | Summary | Explanation |
| |
|
|
|
| |
CSCds72125 | DisconnectedEvent is received with | When an external call called a CTI route |
| |
|
| Cause=CtiResourcesNAvail. | point, the call was redirected back and forth |
|
|
|
| between a CTI port and an IP phone several |
|
|
|
| times. A code change fixed this problem. |
|
|
|
|
| |
CSCds74298 | A call to a shared line results in | Shared line checks the bandwidth for each |
| |
|
| unreleased bandwidth. | device and only consumes for the device |
|
|
|
| active. |
|
|
|
|
| |
CSCds84419 | AVVID: Null translation pattern | This works as designed in the |
| |
|
| prevents dialtone on Cisco IP Phone | Cisco CallManager. |
|
|
| 7960. |
|
|
|
|
|
| |
CSCds88597 | Display issue exists during MeetMe and | The display change no longer shows the |
| |
|
| AdHoc conference calls. | Conference number. The screen displays |
|
|
|
| "To Conference" for MeetMe as well as |
|
|
|
| AdHoc Conferences. |
|
|
|
|
| |
CSCds89614 | Call Pickup stops working. | Cisco CallManager software modification |
| |
|
|
| fixes a call scenario that will break the Call |
|
|
|
| Pickup feature. The call pickup table entry |
|
|
|
| needs to be removed after the original |
|
|
|
| destination party has had a Call Forward No |
|
|
|
| Answer put into effect to a new destination |
|
|
|
| and that new destination has a Call Forward |
|
|
|
| setup to another destination. |
|
|
|
|
| |
CSCds89808 | Cisco CallManager crashes when | Cisco CallManager software was modified |
| |
|
| receiving ISDN setup with | to block the call because it does not support |
|
|
|
| ||
|
|
|
| |
|
|
|
| |
CSCds91028 | Cisco CallManager does not apply the | The code change allows a customer to |
| |
|
| calling party transform mask. | configure a Caller ID mask on the gateway |
|
|
|
| configuration web page, so the last |
|
|
|
| redirecting or first redirecting numbers |
|
|
|
| display in the “Calling Party” field of the |
|
|
|
| ISDN primary setup message in the full |
|
|
|
| E.164 format. |
|
|
|
|
|
|
|
| Release Notes for Cisco CallManager Release 3.0(10) |
|
|
|
|
| ||
|
|
| 41 | |
|
|
|
