|
|
|
|
|
|
|
|
|
|
|
| Resolved Caveats |
| ||
Table 3 | Cisco CallManager Release 3.0(9) Resolved Caveats (continued) | ||||||
|
|
|
|
| |||
| DDTS Number | Summary | Explanation | ||||
|
|
|
|
| |||
| CSCdt11252 | Call transfer fails and throws a platform | A Cisco CallManager software | ||||
|
|
| exception. | modification implements the | |||
|
|
|
| NEVER_CONNECT option for the CTI | |||
|
|
|
| enable consultation transfer call. With the | |||
|
|
|
| NEVER_CONNECT option, the | |||
|
|
|
| application (ICD) can choose not to | |||
|
|
|
| establish media path between the CTI route | |||
|
|
|
| port and the agent when it invokes the | |||
|
|
|
| consultation transfer between the original | |||
|
|
|
| caller and the agent so that the consultation | |||
|
|
|
| transfer can work successfully. This change | |||
|
|
|
| only impacts CTI enable consultation | |||
|
|
|
| transfer call, and it depends on the change | |||
|
|
|
| made in CTI, JTAPI, and other applications. | |||
|
|
|
|
| |||
| CSCdt12706 | CTI connection info is not cleaned up | An incorrect statements order caused the | ||||
|
|
| when an application closes a connection | problem; an attempt occurs to retrieve an | |||
|
|
|
| element from the table after that element is | |||
|
|
|
| already removed. The known problem in the | |||
|
|
|
| RW hash table implementation multiplies | |||
|
|
|
| the problem.[ ] operator has a @side effect; | |||
|
|
|
| an attempt to retrieve nonexisting element | |||
|
|
|
| from the table causes a new element | |||
|
|
|
| creation.The statements are not in the right | |||
|
|
|
| order to correct this problem. | |||
|
|
|
|
| |||
| CSCdt18455 | Conference does not work with two | The code now removes 'All' ports option for | ||||
|
|
| outgoing calls through VG200 gateway. | FXO ports. | |||
|
|
|
|
| |||
| CSCdt20323 | 3660 Router MGCP configuration fails | An update to the product capabilities table | ||||
|
|
| with Cisco CallManager 3.0(6). | fixes this problem. | |||
|
|
|
|
| |||
| CSCdt26019 | Upgrading to Cisco CallManager | A Cisco CallManager code change corrects | ||||
|
|
| 3.0(5a) from an earlier version results in | this behavior. | |||
|
|
| one Cisco IP Phone 7940 button |
|
|
|
|
|
|
| template. |
|
|
|
|
|
|
|
|
| |||
| CSCdt26442 | When a new user is added on | With the latest plug in schema files on | ||||
|
|
| Cisco CallManager 3.0(7) with | Cisco CallManager 3.0(9), the plug in | |||
|
|
| AD/NDS plugin, the user gets an error. | works. | |||
|
|
|
|
|
|
|
|
|
|
| Release Notes for Cisco CallManager Release 3.0(10) |
|
|
| |
|
|
|
| ||||
|
|
|
|
| 35 |
| |
|
|
|
|
| |||
