Open Caveats
|
|
| Table 8 | Open Caveats for Cisco CallManager Release 3.0(10) (continued) | ||
|
|
|
|
| ||
DDTS number | Description |
|
|
| ||
|
|
| ||||
CSCds42397 | Terminal services do not function. | |||||
|
|
| Workaround: This is a Microsoft limitation. | |||
|
|
| ||||
CSCds42397 | Terminal Services are nonfunctional. | |||||
|
|
| Workaround: This is a Microsoft limitation. | |||
|
|
| ||||
CSCds46274 | Cisco IP Phone 7960 user on G.729 call hears hiss after digit during IVR prompt. | |||||
|
|
| Workaround: No workaround exists. | |||
|
|
| ||||
CSCds48200 | Missing Disconnected, Established & TransferEnd in | |||||
|
|
| Workaround: Avoid the scenario in which one party of the call is doing consult | |||
|
|
| transfer and other party from the same call is performing consult conference. | |||
|
|
| ||||
CSCds48216 | Missing DisconnEv, EstablishedEv & ConferenceEnd if conference PNC transfer. | |||||
|
|
| Workaround: Avoid cases of starting as a consult transfer and invoking consult | |||
|
|
| conference without completing the transfer first or vice versa. If you start an | |||
|
|
| operation, finish it, and then perform next operation. | |||
|
|
| ||||
CSCds50413 | Missing Disconnected, Established & TransferEnd in conference transfer scenario. | |||||
|
|
| Workaround: No workaround exists. | |||
|
|
| ||||
CSCds50626 | STIBOOT caused an exception c0000006H in module MSVBVM50.DLL at 0137. | |||||
|
|
| Workaround: Do not remove the media during the installation. If the media is | |||
|
|
| removed, restart the install. | |||
|
|
| ||||
CSCds50763 | Spurious NewCall is created when a redirect is done following an unhold state. | |||||
|
|
| Workaround: No workaround exists for either Cisco IP Phone model 12 SP+ or | |||
|
|
| Cisco IP Phone model 30 VIP; however, this operations works on the Cisco IP Phone | |||
|
|
| 7900 family. |
|
|
|
|
|
| ||||
CSCds50786 | Users must create conference parent call before sending out conferenced events. | |||||
|
|
| Workaround: Microsoft will not fix this bug until Service Pack 3 of Windows 2000; | |||
|
|
| therefore, to work around this problem, you must configure the multiprocessor | |||
|
|
| machine to use only one of the processors on that machine. | |||
|
|
| ||||
CSCds55389 | Backup installation starts after the Cisco CallManager installation is exited. | |||||
|
|
| Workaround: This works as designed. Even if the install is exited, the backup utility | |||
|
|
| needs to be configured (or server chosen as target). | |||
|
|
|
|
| ||
|
| Release Notes for Cisco CallManager Release 3.0(10) | ||||
|
| |||||
70 |
|
|
|
|
| |
|
|
|
| |||