Cisco Cisco Customer Voice Portal Downloads 릴리즈 노트
4
Release Notes for Cisco Customer Voice Portal, Release 3.0(0) Updated 6/24/05
CVP 3.0 Considerations
The ICM data sheet titled "Cisco Software Support Release Methodology for Cisco ICM and Cisco IPCC
Enterprise and Hosted Editions" describes the ES and SR processes. While this data sheet describes the
ICM processes, this information also applies to CVP 3.0. You can find this data sheet at:
Enterprise and Hosted Editions" describes the ES and SR processes. While this data sheet describes the
ICM processes, this information also applies to CVP 3.0. You can find this data sheet at:
http://ftp-sj.cisco.com/cisco/custcontact/icmpdf/Maintenance_Strategy_IPCC_and_ICM_5.12.pdf
Refer to the ICM data sheet for more information about Engineering Specials and Service Releases. The
location for CVP ES and SR updates is http://www.cisco.com/kobayashi/sw-center/contact_center/CVP/
location for CVP ES and SR updates is http://www.cisco.com/kobayashi/sw-center/contact_center/CVP/
Note
The hot fix process still applies to ISN release 2.1 and previous release. For hot fix information, refer to
the downloads page on the Cisco web site.
the downloads page on the Cisco web site.
Engineering Special For CVP 3.0
Currently there is an Engineering Special available for CVP 3.0. This Engineering Special is associated
with defect number CSCsa56023. For more information, use the Bug Tool Kit
(http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl)
with defect number CSCsa56023. For more information, use the Bug Tool Kit
(http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl)
to access this defect.
Getting Updates for CVP VoiceXML Studio
The CVP VoiceXML Studio product uses a different process for updating software. These updates are
obtained through a Studio utility. To get latest Studio updates, start Studio and select:
obtained through a Studio utility. To get latest Studio updates, start Studio and select:
Help->Software Updates->Latest updates
Studio will search the Eclipse site as well as the Cisco Web site for updates and display them to you.
Tomcat Server Considerations
When you select the CVP VoiceXML full installation option, the Tomcat server software is installed by
default. However, when you select the CVP VoiceXML Server only option the Tomcat server is not
installed. If you want to install the CVP VoiceXML Server with Tomcat, you must use the Custom
Installation option.
default. However, when you select the CVP VoiceXML Server only option the Tomcat server is not
installed. If you want to install the CVP VoiceXML Server with Tomcat, you must use the Custom
Installation option.
Instructions for setting up CVP VXML Server with JNDI Database Connections
If you are using MSSQL, the recommended driver is the i-net Opta XS driver on
http://www.inetsoftware.de. This is the most mature, commercially available JDBC driver out in the
market.
http://www.inetsoftware.de. This is the most mature, commercially available JDBC driver out in the
market.
If you are using MySQL, the tested driver is Connector/J 3.0 which can be found at
http://dev.mysql.com/downloads/connector/j/3.0.html
http://dev.mysql.com/downloads/connector/j/3.0.html
The driver will be a .jar file. Place his .jar file in the C:\Cisco\CVP\Tomcat 4.1\common\lib directory.
This is a directory in Tomcat's classpath.
This is a directory in Tomcat's classpath.
Tomcat Context:
You must now add a Tomcat Context for the database connection so that CVP VXML Server knows how
to communicate with your database. If you are connecting to more than one database, you will need to
create more than one <Resource> entry with its associated <ResourceParams> within the <Context> ...
</Context> tags, one <Resource> entry with <ResourceParams> for each database you wish to connect
with. To add the Tomcat Context, do the following:
You must now add a Tomcat Context for the database connection so that CVP VXML Server knows how
to communicate with your database. If you are connecting to more than one database, you will need to
create more than one <Resource> entry with its associated <ResourceParams> within the <Context> ...
</Context> tags, one <Resource> entry with <ResourceParams> for each database you wish to connect
with. To add the Tomcat Context, do the following: