Cisco Cisco IPICS Release 2.1 Instructions De Sécurité Importantes

Because defect status continually changes, be aware that 

snapshot of the defects that were open at the time this report was compiled. For 
an updated view of open defects, access Bug Toolkit and follow the instructions 
as described in the 

. You can also use 

Bug Toolkit to view caveats that were opened in previous releases of Cisco IPICS 
and which may still be open.

Bug Toolkit requires that you have an account with Cisco.com. By using the 
Bug Toolkit, you can find caveats of any severity for any release. Bug Toolkit may 
also provide a more current listing than this document provides. To access the Bug 
Toolkit, log on to 

If the Cisco IPICS database becomes corrupted after an unexpected system shutdown, 
you may not be able to configure the SIP provider or use customized script prompts 
and spoken names. Corrupted database records may be removed by running the 2.0(2) 
SR1 installer or a script for release 2.1(1).

Under load conditions that exceed the Cisco IPICS specifications, the Cisco IPICS 
database may become unresponsive. In this situation, certain system operations, such 
as activating VTGs, do not succeed. To resolve this issue, restart the server.

Under load conditions that exceed the Cisco IPICS specifications, the Cisco IPICS 
application may become unresponsive. In this situation, certain system operations, 
such as activating VTGs, do not succeed. To resolve this issue, restart the server.