This document provides installation instructions for CVP11.5(1) ES8. It also contains a list of CVP issues resolved by this engineering special. Please review all sections in this document pertaining to installation before installing the product. Failure to install this engineering special as described may result in inconsistent CVP behavior.
This document contains these sections:
The Product
Alert Tool offers you the ability to set up one or more profiles that will
enable you to receive email notification of new Field Notices, Product Alerts
or End of Sale information for the products that you have selected.
The Product
Alert Tool is available at http://www.cisco.com/cgi-bin/Support/FieldNoticeTool/field-notice
This ES includes fix for defects CSCvd43429, CSCvc55365, CSCvc39129, CSCvc02798, CSCvb57724, CSCvd32043, CSCvc22558, CSCvc92728, CSCvb43729, CSCvc43805, CSCvc39129
Cisco Unified Customer Voice Portal 11.5
CVP11.5(1) ES8 is compatible with and should be installed on these CVP components:
Do not install this engineering special on any of the following components:
Follow the below steps in sequence to install this ES:
·
Update
the below properties present in C:\Cisco\CVP\conf
vxml.properties
o
VXML.ContextService.executorThreadPoolSize = 50
o
VXML.ContextService.httpMaxConnectionsPerRoute = 50
o
VXML.ContextService.statsLogInterval = 1800000
o
VXML.ContextService.getStatusInterval = 30000
oamp.properties
o omgr.contextServiceStatusInterval=30
o omgr.csStatusTimeout=180
To uninstall this patch, go to Control Panel. Select "Add or Remove Programs". Find the installed patch in the list and select "Remove".
Note: Patches have to be removed in the reverse order in which they were installed. For example, if you had installed patches 3, then 5, then 10 for a product, you will need to uninstall patches 10, 5 and 3 in that order to remove all patches for that product.
This section provides a list of significant CVP defects resolved by this engineering special. It contains these subsections:
Note: You can view more information on and track individual CVP defects using the Cisco Bug Toolkit located at: http://www.cisco.com/support/bugtools/Bug_root.html
This section lists caveats specifically resolved by CVP11.5(1) ES8.
Caveats in this section are ordered by CVP component, severity, and then
identifier.
Be sure to include ALL of the resolved caveats for the files you're delivering,
i.e. all of the caveats from the release notes of the previous ES which
included these files.
|
Identifier |
Severity |
Component |
Headline |
|
CSCvb43729 |
2 |
appsvr |
Context
Service POD ID Not passed in POD.ID ECC Variable |
|
CSCvc22558 |
3 |
appsvr |
CVP-CS
De-Registration & Registration Tasks should be Event based instead of
Fixed Timers |
|
CSCvd32043 |
6 |
appsvr |
Context
Service Serviceabilty enhancements |
|
CSCvc55365 |
3 |
ss_ged |
CVP
not filling in the user.cvp_server_info variable. |
|
CSCvb57724 |
2 |
ss_sip |
CVP
11.5 - Call Studio Script - DNIS is replaced by the ANI |
|
CSCvc92728 |
2 |
ss_vxml |
CVP
Get Speech microapp not working in 11.5 |
|
CSCvc02798 |
2 |
vxml_server |
Save
& Deploy of Context Service Connection Data to VXML Server Fails from
OAMP |
|
CSCvd43429 |
2 |
vxml_server |
CVP
v11.5 Call is disconnected after Capture Node |
|
CSCvc43805 |
3 |
vxml_server |
VXML
session count does not match with Licenses in Use |
|
CSCvc39129 |
6 |
vxml_server |
VXML
Server as TLS client |
Caveats are ordered by severity then defect number.
Be sure to include ALL of the resolved caveats for the files you're delivering,
i.e. all of the caveats from the release notes of the previous ES which
included these files.
Defect Number: CSCvb43729
Component: appsvr
Severity: 2
Headline: Context Service POD ID Not passed in POD.ID ECC Variable
Symptom: CVP
is not passing Context Service POD ID in POD.ID ECC Variable
Conditions: In 11.5 CVP is sending Context Service POD ID Information in
variable user.microapp.FromExtVXML[4]
i.e. Array size of '5' instead of POD.ID ECC Variable
Workaround: Delete the existing user.microapp.FromExtVXML
ECC Variable with array size of 4 and create another user.microapp.FromExtVXML
ECC Variable with array size of 6
Further Problem Description:
Defect Number: CSCvb57724
Component: ss_sip
Severity: 2
Headline: CVP 11.5 - Call Studio Script - DNIS is replaced by the ANI
Symptom:
When a call is sent from ICM Script to a CVP Call Studio Script, the DNIS (Orginal Called Number) field is populated with the ANI
(Calling Party number) 10.1.1.1.1475254621514.9.HelloWorld,09/30/2016
12:57:01.514,,start,newcall, 10.1.1.1.1475254621514.9.HelloWorld,09/30/2016
12:57:01.514,,start,ani,1001 10.1.1.1.1475254621514.9.HelloWorld,09/30/2016
12:57:01.514,,start,areacode,765 10.1.1.1.1475254621514.9.HelloWorld,09/30/2016
12:57:01.514,,start,exchange,744 10.1.1.1.1475254621514.9.HelloWorld,09/30/2016
12:57:01.514,,start,dnis,1001 //DNIS is 3001 for this call. ANI is 1001.
Conditions: CVP 11.5
Workaround:
Further Problem Description: Install CVP11.5.1_ES7 which has a fix for this
defect
https://software.cisco.com/download/special/release.html?config=d9e9155b48ab4dd05d4a624e5952c934
Defect Number: CSCvc02798
Component: vxml_server
Severity: 2
Headline: Save & Deploy of Context Service Connection Data to VXML Server Fails from OAMP
Symptom:
Save & Deploy of Context Service Connection Data to VXML Server Fails from
OAMP
Conditions: During DeRegistration/Registration of
CVP Context Service setup we keep noticing that the Save & Deploy Fails
from OAMP Server, It looks like the VXML Server in
corresponding CVP Servers are not responding properly but if we restart the CVP
Server then the Save & Deploy for another 2-3 attempts will be successful
and again starts Failing. Because of this issue the Context Service DeRegistration/Registration Automation Fails and also the
Context Service Call Flow is impacted.
Workaround: Restart CVP(VXML/Call)Server
Further Problem Description:
Defect Number: CSCvc92728
Component: ss_vxml
Severity: 2
Headline: CVP Get Speech microapp not working in 11.5
$$IGNORE
Symptom: Call flow fails and the VXML Page generated as an output of MicroApp contains empty variable.
Conditions: Call flow fails and the VXML Page generated as an
output of MicroApp contains empty variable.
Workaround: USER_MICROAPP_TOEXTVXML[1]:;VH_INTERACTION_ID
The ECC variable array has an empty value, there is no value between ':' and
';' because of which that empty entry is coming in the VXML which browser is
not liking. Workaround could be to modify the ECC variable and remove the ?;? before the VH_INTERACTION_ID variable in the ICM
script.
Further Problem
Description:
Defect Number: CSCvd43429
Component: vxml_server
Severity: 2
Headline: CVP v11.5 Call is disconnected after
Capture Node
Symptom: CVP v11.5 Call is disconnected after Capture Node
Conditions: IVR SS was moved to vxmlserver in 11.5 and
it handles microapps differently.
Workaround: No work around.
Further Problem Description: IVR SS was moved to vxmlserver in 11.5 and
it handles microapps differently. Bug alert verified
by escalation Engr Anjum. Anjum Jeelani (anjeelan)
Defect Number: CSCvc22558
Component: appsvr
Severity: 3
Headline: CVP-CS De-Registration & Registration
Tasks should be Event based instead of Fixed Timers
Symptom: CVP-CS De-Registration & Registration Tasks should be Event based
instead of Fixed Timers
Conditions: The Context Service De-Registration or Registration should be
deterministic i.e. Event Based instead of fixed timers. After De-Registration
the automation should not wait for few mins or have fixed timers before
starting Registration, Instead the Clients i.e. CVP in this case should enable
Register button only after the De-Registration cleanup has completed (i.e If state listener is triggered) We need to have Event
based mechanism in place for De-Registration & Registration Button to be
even enabled i.e. Based on the Events triggered from CS Cloud the Clients i.e.
CVP in this case should enable the Register/De-Register Buttons in the OAMP UI
accordingly.
Workaround: Introducing fixed Timers which can lead to inconsistency in Automation
Further Problem Description:
Defect Number: CSCvc43805
Component: vxml_server
Severity: 3
Headline: VXML session count does not match with
Licenses in Use
$$PREFCS
Symptom: VXML session count does not match with the Licenses in Use
Conditions: During load test
Workaround: NA
Further Problem
Description: One
or more of the following links will take you to an emergency patch called an
Engineering Special or ES. If you are not directly experiencing this problem,
we encourage you to select or wait for a formally tested fix in an upcoming
major, minor, or maintenance release. Installing any interim emergency patch or
ES on a production system poses a risk of instability due to the limited
testing it receives. If you believe you are currently experiencing this problem
and you cannot wait for a later release, please select the link for the ES
built for your system. To identify the base version for this ES, please remove
_ES?? from the version name listed below. That will give you the version of the
tested base release you may install a given ES over. Be sure to read the
release notes or Readme file before running the patch installer.
Defect Number: CSCvc55365
Component: ss_ged
Severity: 3
Headline: CVP not filling in the user.cvp_server_info
variable.
Symptom: CVP is not filling in the user.cvp_server_info
variable.
Conditions: CVP 11.5(1)
Workaround: None.
Further Problem Description: One
or more of the following links will take you to an emergency patch called an
Engineering Special or ES. If you are not directly experiencing this problem,
we encourage you to select or wait for a formally tested fix in an upcoming
major, minor, or maintenance release. Installing any interim emergency patch or
ES on a production system poses a risk of instability due to the limited
testing it receives. If you believe you are currently experiencing this problem
and you cannot wait for a later release, please select the link for the ES
built for your system. To identify the base version for this ES, please remove
_ES?? from the version name listed below. That will give you the version of the
tested base release you may install a given ES over. Be sure to read the
release notes or Readme file before running the patch installer.
Defect Number: CSCvc39129
Component: vxml_server
Severity: 6
Headline: VXML Server as TLS client
Symptom: When using the VXML Server as TLS client, trying to setup TLS session
from custom element code to remote web server, only TLS 1.0 is supported. The
documentation is not clear about this. We need a clear note providing this
information to avoid confusion.
Conditions: CVP 10.5 uses JDK 7 and JDK 7 does not support TLS 1.1 or TLS 1.2 for
client.
Workaround: There are some potential workarounds, but this is something customer
will need to manage from their custom element code.
http://superuser.com/questions/747377/enable-tls-1-1-and-1-2-for-clients-on-java-7
So there needs to be explicit code in the element to enable TLS 1.2. TLS 1.0 is
supported by default.
Further Problem
Description: One
or more of the following links will take you to an emergency patch called an
Engineering Special or ES. If you are not directly experiencing this problem,
we encourage you to select or wait for a formally tested fix in an upcoming
major, minor, or maintenance release. Installing any interim emergency patch or
ES on a production system poses a risk of instability due to the limited
testing it receives. If you believe you are currently experiencing this problem
and you cannot wait for a later release, please select the link for the ES
built for your system. To identify the base version for this ES, please remove
_ES?? from the version name listed below. That will give you the version of the
tested base release you may install a given ES over. Be sure to read the
release notes or Readme file before running the patch installer.
Defect Number: CSCvd32043
Component: appsvr
Severity: 6
Headline: Context Service Serviceabilty
enhancements
Symptom: Not sufficient data to debug any context Service failures
Conditions: When using context service functionality
Workaround:
Further Problem Description:
The following sections provide sources for obtaining documentation from Cisco Systems.
You can access the most current Cisco documentation on the World Wide Web
at the following sites:
Cisco documentation and additional literature are available in a CD-ROM
package, which ships with your product. The Documentation CD-ROM is updated
monthly and may be more current than printed documentation. The CD-ROM package
is available as a single unit or as an annual subscription.
Cisco documentation is available in the following ways:
If you are reading Cisco product documentation on the World Wide Web, you
can submit technical comments electronically. Click Feedback in the toolbar and
select Documentation. After you complete the form, click Submit to send it to
Cisco.
You can e-mail your comments to bug-doc@cisco.com.
To submit your comments by mail, use the response card behind the front
cover of your document, or write to the following address:
Attn Document Resource Connection
Cisco Systems, Inc.
170 West Tasman Drive
San Jose, CA 95134-9883
We appreciate your comments.
Cisco provides Cisco.com as 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 website.
Cisco.com is the foundation of a suite of interactive, networked services
that provides immediate, open access to Cisco information and resources at anytime, from anywhere in the world. This highly integrated
Internet application is a powerful, easy-to-use tool for doing business with
Cisco.
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. In addition, you can resolve technical
issues with online technical support, download and test software packages, and
order Cisco learning materials and merchandise. 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.
To access Cisco.com, go to: http://www.cisco.com
The Cisco TAC website 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 the TAC website: http://www.cisco.com/tac
P3 and P4 level problems are defined as follows:
In each of the above cases, use the Cisco TAC website to quickly find
answers to your questions.
To register for Cisco.com, go to the following website:
http://www.cisco.com/register/
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 website: http://www.cisco.com/tac/caseopen
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 website:
http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml
P1 and P2 level problems are defined as follows: