Collaboration Knowledge Base

Core IssueSome parameters in the ccndir.ini file are incorrect.ResolutionTo resolve this issue, perform these steps:From the Cisco Customer Response Applications (CRA) Administration web page, go to Tools > Plug-ins and click the Cisco CRA Editor hyp...

Core IssueThe Structured Query Language (SQL) server is not accessed with the proper authentication.ResolutionTo resolve this issue, perform these steps on the Customer Response Applications (CRA) historical reporting client computer:Go to Start > Pr...

Core IssueThe script is invalid or the language to which the script has been set was not installed successfully.ResolutionTo resolve this issue, perform these steps:Validate the script. Set the language at the route point to en_US and verify ...

Core IssueSynchronization between the Cisco Customer Response Applications (CRA) and the Historical Reports Database Server was not completed.ResolutionTo resolve this issue, perform these steps:Configure CRA with the Historical Reports Database Serv...

Core IssueThe application script associated with the Computer Telephony Integration (CTI) route point did not load correctly.ResolutionTo resolve this issue, perform these steps:Validate the application script in the Customer Response Applications (C...

Core IssueCisco CallManager, even after upgrade from version 3.3(2) to version 3.3(3), is displaying incorrect versions for the installed components. The display is as shown in the table below.Component Version Installation ID Cisco IP Manager Assist...

Core IssueWhile the VG248 is upgraded to version vgc-main-1-3-1ES8-2.tar and the router is reloaded, the router becomes stuck in diagnostic mode.The issue is caused by a corrupt software image being upgraded.ResolutionIn order to resolve the issue, p...

Core IssueAn error message appears after an operating system (OS) upgrade from 4.3a to 4.3aSR9 on the Cisco CallManager server. The error message reads:Potential critical Error encountered running cpSATARAID2.exe /s /f.  It returns a value of 2. Reso...

Core IssueThis is the topology:IP PHONE 1                     IP PHONE 2     |                               |     CCM SUB --------------CCM PUB |             CCM CLUSTER |------------------------------------ |  PSTN GW 1                         PSTN...

Core IssueMobilityManager 1.2, which worked prior to the upgrade, fails to register after an upgrade to Cisco CallManager 5.0.  The Shared Line and Outgoing CTI Ports shows the Out of Service error message. When you modify the Cisco CallManager versi...

Core IssueIf you select the Export Report tool in the Report Viewer on a Cisco Customer Response Applications (CRA) Historical Reports client computer on which the language is set to Simplified Chinese, the Export dialog box will not contain a defaul...

Core IssueA session ends when the user tries to install a Session Initiation Protocol (SIP) version 4 release through a TFTP server. After 10 seconds, the TFTP server prompts to upload the file again.The upgrade fails due to a change in the naming co...

ResolutionTo verify the connectivity between DGW and MPDS, perform these steps:Log in to DGW. Issue the telnet localhost <8070> command.Change context to data-access by issuing the dsdgw> context data-access command.Issue the dsdgw[data-access]> db-s...

ResolutionThe Cisco 7920 IP Phones support Layer 2 (L2) Enhanced Distributed Coordination Function (EDCF) such as Quality of Service (QoS) for downstream (toward the access point) traffic. In addition, the Cisco 7920 dynamically announces its presenc...

Core IssueThis issue occurs if an application does not receive a disconnect signal after a call and the application does not have an error handling mechanism to detect that the call has ended. This can happen because some applications are invalid.Res...