|
|
|
|
|
|
|
| Resolved Caveats |
|
Table 6 | Cisco CallManager Release 3.0(6) Resolved Caveats (continued) |
| ||
|
|
|
| |
DDTS Number | Summary | Explanation |
| |
|
|
|
| |
CSCds53378 | Cisco CallManager upgrade with | The code for unlimited bandwidth in |
| |
|
| locations prevents | location for Cisco CallManager 3.0 does |
|
|
| conference from working. | not currently work. Migration has been |
|
|
|
| changed to remove the 0 bandwidth location |
|
|
|
| records and set any devices location using it |
|
|
|
| to NULL. This will, in effect, give that |
|
|
|
| situation no bandwidth limitation. |
|
|
|
|
| |
CSCds57574 | Cisco WebAttendant will not install on | Windows operating systems version of |
| |
|
| a Windows 98 client machine. | regsvr32.exe could not load the .dll |
|
|
|
| extensions containing the |
|
|
|
| Cisco WebAttendant controls. Each |
|
|
|
| Cisco WebAttendant DLL tries to start a |
|
|
|
| multimedia timer when the DLL is loaded. |
|
|
|
| Starting the timer was moved from the |
|
|
|
| loading of the DLL to when the actual |
|
|
|
| loading of the control by the web browser |
|
|
|
| occurs. This allows the regsvr32.exe to load |
|
|
|
| and register the DLL. |
|
|
|
|
| |
CSCds61655 | GetCallInfo returns wrong info on call | A changed was made previously to save |
| |
|
| fwded to route point. | information about the calling, called, and |
|
|
|
| redirected parties during call setup, so this |
|
|
|
| information can be returned in the |
|
|
|
| lineGetCallInfo when the call is forwarded. |
|
|
|
| These changes were made to the code that |
|
|
|
| handles the stations but also needed to be |
|
|
|
| made to the code that handles route points. |
|
|
|
|
| |
CSCds61871 | No error message occurs on | The problem was corrected by using a timer |
| |
|
| unauthorized CTI user via TSP. | to introduce a delay between sending the |
|
|
|
| response and closing the pipe. |
|
|
|
|
|
|
|
| Release Notes for Cisco CallManager Release 3.0(10) |
|
|
|
|
| ||
|
|
| 53 | |
|
|
|
