Resolved Caveats
Resolved Caveats - Release 3.0(5a)
Table 7 lists and describes Caveats that were resolved in Cisco CallManager
Release 3.0(5a).
Note If you have an account with Cisco.com (Cisco Connection Online), you can use the Bug Toolkit to find caveats of any severity for any release.
To access the Bug Toolkit, log on to http://www.cisco.com/support/bugtools.
Table 7 | Cisco CallManager Release 3.0(5a) Resolved Caveats | ||
|
|
| |
DDTS Number | Summary | Explanation | |
|
|
| |
CSCdp96950 | CPU usage stays up to 100% with | This was determined to be a Microsoft | |
|
| svchost.exe. | problem. Currently, a new version of |
|
|
| tapisrv.dll fixes this problem. |
|
|
| |
CSCdr35751 | This problem occurs when Call Forward | When Call Forward All is cleared on a | |
|
| All is cleared from the user preference | multiline, a reset is only sent down to one |
|
| pages for a DN that is shared by | phone that shares the multiline, and the call |
|
| multiple phones (that is, a multiline). | forward lights are cleared on that phone |
|
|
| only. The call forward is cleared for the |
|
|
| specified DN, but the forward lights on all |
|
|
| other phones will remain on, thus giving a |
|
|
| false indication that the phone is still |
|
|
| forwarded, when it really is not. |
|
|
| |
CSCdr40345 | Errors are returned by the | These errors appear when the directory does | |
|
| Cisco CallManager User | not contain a complete listing of the devices |
|
| Administration web pages. | in the Cisco CallManager database. This |
|
|
| occurs when the directory is first configured |
|
|
| with a large number of devices to import |
|
|
| from the database to the directory. |
|
|
|
|
| Release Notes for Cisco CallManager Release 3.0(10) |
58 |