This document provides installation instructions for CVP12.5(1) ES24. It also contains a list of CVP issues resolved by this engineering special. Review all installation information before installing the product. Failure to install this engineering special as described can result in inconsistent CVP behaviour.
This document contains these sections:
· About Cisco CVP (and CVP Engineering Specials)
· CVP Compatibility and Support Specifications
· CVP Engineering Special Installation Planning
· Obtaining Technical Assistance
This Engineering Special patch:
· Includes Defect Fixes
· Is a cumulative ES.
· CVP 12.5(1)
This section lists the CVP components on which you
can and cannot install this engineering special.
You can install CVP12.5(1) ES24 on these CVP components:
· Call Server
· OAMP
· Reporting Server
·
Remote Operation
NA
Pre-Installation Steps:
1. It is mandatory to install ES16 and ES23 before installing CVP12.5(1) ES24.
2. Before installing the patch, the audio files must be backed up from C:\Cisco\CVP\VXMLServer\Tomcat\webapps\CVP\audio folder.
3. Take backup of all custom files, if any. The custom
files are located in the lib folder of the application-specific directory in the VXML
server. For example, the files for HelloWorld custom application are located in the C:\Cisco\CVP\VXMLServer\Application\Helloworld\lib
folder.
Patching Unified CVP VXMLServer and CallServer:
1. Perform shutdown on CVP VXMLServer and CallServer.
2. Run the patch installer.
3. Reboot the machine.
NOTE 1: Please follow below steps to view the heartbeat messages in Call Server and VXML Server logs. These xml and property file changes are applicable only for defect CSCvy45122.
1. Append C:\cisco\cvp\conf\log4j.xml with below code:
<logger name="com.cisco.cvp.callserver" additivity="false">
<level value="debug" />
<appender-ref ref="Async" />
</logger>
2. Append C:\cisco\cvp\conf\log4j_vxml.xml with below code:
<logger name="com.cisco.cvp.callserver" additivity="false">
<level value="debug" />
<appender-ref ref="Async" />
</logger>
3. Restart Call Server and vxml server.
4. Append c:\cisco\cvp\conf\ivr.properties with below code:
IVR.ivrHeartbeatInterval = 30000
IVR.ivrVxmlCheckHeartbeat = true
IVR.ivrVxmlHeartbeatMaxAllowedToMiss = 3
5. Restart Call Server and vxml server.
NOTE 2: Default JavaScript engine configured is rhino. In case of script engine specific error, the JavaScript engine can be changed to nashorn, by adding below property to CVP_HOME\conf\vxml.properties file.
VXML.JsEngine = nashorn
restart VXML Server Service
Patching Unified OPSConsoleServer:
1. Shutdown Cisco CVP OPSConsoleServer service.
2. Run the patch installer.
3. Reboot the machine.
Patching Unified CVP Reporting Server:
1. Perform shutdown on CVP CallServer.
2. Run the patch installer.
3. Reboot the machine.
Post Installation Steps:
1. Ensure all services are up and running after the patch is installed.
2. Ensure the audio folder is created under C:\Cisco\CVP\VXMLServer\Tomcat\webapps\CVP
3. Restore the backed up audio files and custom files.
3. Find the installed patch in the list and select "Remove".
Call Studio Resolved Defects in CVP12.5(1) ES24
|
Identifier |
Headline |
|
CSCvy39652 |
DialogFlowParam Element Reset Parameter. |
|
CSCvy39125 |
Allow Substitutions for Intent Settings in DialogFllowParam Element |
|
CSCvw09507 |
CVP application with WSDL takes long time to load upon clicking decision editor. |
|
CSCvy53187 |
Decision element gives an error: "An error has occurred. See error log for more details. |
https://software.cisco.com/download/specialrelease/813a62ba262b8278db2712b0b17a0ee5
This section provides a list of significant CVP defects resolved by this engineering special.
Resolved Defects in CVP12.5(1) ES24
This section lists Defects specifically resolved by CVP12.5(1) ES24
|
Identifier |
Headline |
|
CSCvy45122 |
CVP 12.5: Call Server fails to respond to VXML NEWCALLEVENT request resulting in call failures |
|
CSCvu67527 |
CVP is changing SDP Origin/sess-version field for 180 Ringing and 200 OK |
|
CSCvx76118 |
Dialogflow Regionalization support |
|
CSCvu80401 |
CVP Graceful shutdown getting stuck on Partial State |
|
CSCvv69970 |
CVP server stops processing all calls after a server reboot |
|
CSCvw81416 |
DialogFlow, VXML Document is wrongly having prompt in the catch block for no-input |
|
CSCvw54682 |
Java null pointer exception is seen in VXML server logs when it could not find dfElem |
|
CSCvx14235 |
VXML applications failing after timeout randomly at Set Value node |
|
CSCvs62001 |
CVP log files are not getting retrieved via SPOG Log collection utlity |
|
CSCvt08503 |
ES11 install on CVP 11.6 does not allow Location edits |
|
CSCvt65315 |
CVP OAMP VXML Application Transfer Fails |
|
CSCvt72000 |
OAMP: Allow hostname for VXML server in VVB template management |
|
CSCvu06714 |
CVP PCS Survey and SMS and email survey after voice with WxM |
|
CSCvu22331 |
Limit ports usage per cvp server with smart license |
|
CSCvu65114 |
VXMLServer StandAlone REQICM label request was not honoring the PRIMARY/BACKUP configuration |
|
CSCvv62292 |
CVP OAMP GUI issues with sip server group and call server statistics after installing 12.5(1) ES10. |
|
CSCvt14449 |
Zombie Checker Update Request Causes Mid Session Refresh |
|
CSCvu96623 |
Form/Digit element re-prompts no-match n+1 times while configuration has only 'n' times. |
|
CSCvv43755 |
CVP v11.5 Calls Fail Due to channel does not exist Exception Error |
|
CSCvs04334 |
Migrate CVP OAMP from Struts 1.2.4 to Struts 2.x or alternate framework |
|
CSCvu96648 |
VXML GW throws semantic error for no-match scenario and drops the call. |
You can access current Cisco documentation on the Support pages at the following sites:
· https://www.cisco.com
· https://www-china.cisco.com
·
https://www-europe.cisco.com
To provide comments about this document, send an email message to the following address:
contactcenterproducts_docfeedback@cisco.com
We appreciate your comments.
Cisco.com is a starting point for all technical assistance. Customers and partners can obtain documentation, troubleshooting tips, and sample configurations from online tools. For Cisco.com registered users, additional troubleshooting tools are available from the TAC site.
Cisco.com provides a broad range of features and services to help customers and partners streamline business processes and improve productivity. Through Cisco.com, you can find information about Cisco and our networking solutions, services, and programs. You can also resolve technical issues with online technical support and download software packages. Valuable online skill assessment, training, and certification programs are also available.
Customers and partners can self-register on
Cisco.com to obtain additional personalized information and services.
Registered users can order products, check on the status of an order, access
technical support, and view benefits specific to their relationships with
Cisco.
The Cisco TAC site is available to all customers who
need technical assistance with a Cisco product or technology that is under
warranty or covered by a maintenance contract.
If you have a priority level 3 (P3) or priority level 4 (P4) problem, contact TAC by going to https://www.cisco.com/c/en/us/support/index.html.
P3 and P4 level problems are defined as follows:
· P3--Your network performance is degraded. Network functionality is noticeably impaired, but most business operations continue.
· P4--You need information or assistance on Cisco product capabilities, product installation, or basic product configuration.
In each of the above cases, use the Cisco TAC site to quickly find answers to your questions.
If you cannot resolve your technical issue by using
the TAC online resources, Cisco.com registered users can open a case online by
using the TAC Case Open tool at the following site: https://mycase.cloudapps.cisco.com/create/start/
If you have a priority level 1(P1) or priority level 2 (P2) problem, contact TAC by telephone and immediately open a case. To obtain a directory of toll-free numbers for your country, go to the following sites:
· Enterprise and Service Provider Products--https://www.cisco.com/c/en/us/support/web/tsd-cisco-worldwide-contacts.html
· Small Business Products--https://www.cisco.com/c/en/us/support/web/tsd-cisco-small-business-support-center-contacts.html
P1 and P2 level problems are defined as follows:
· P1--Your production network is down, causing a critical impact to business operations if service is not restored quickly. No workaround is available./li>
· P2--Your production network is severely degraded, affecting significant aspects of your business operations. No workaround is available.