Cisco Cisco Customer Voice Portal 8.0(1) User Guide

C

HAPTER 

3:

 

A

DMINISTRATION

 

 

V

OICE

XML

 

S

ERVER 

U

SER 

G

UIDE 

 

 

 

FOR 

C

ISCO 

U

NIFIED 

C

USTOMER 

V

OICE 

P

ORTAL 

R

ELEASE 

4.0(1) 

 

 

 

 

 

49

o

 

 The voice browser can be configured to point to another URL 

for calls coming on the specific number. This can point to another machine running the 
VoiceXML Server or even just a web server with a single static VoiceXML document 
playing the suspended message. A separate file would be needed for each application. 
This is a manual process and requires another machine with at least a web server (it can 
be on the same machine which would allow the Java application server to be restarted but 
would not allow the machine itself to be restarted).  

A new application that is created in Unified CVP VoiceXML Studio and deployed to a machine 
on which the VoiceXML Server is running cannot begin accepting calls until the VoiceXML 
Server loads the new application. In order to load the application, the 

deployApp

 script found in 

the 

admin

 folder of the new application should be launched. Windows users should use the script 

named 

deployApp.bat

 and Unix users should use the script named 

deployApp.sh

.  

If multiple applications are created and need to be deployed together, the 

deployAllNewApps

 

script found in the 

admin

 directory of the VoiceXML Server will deploy all new applications 

together. Windows users should use the script named 

deployAllNewApps.bat

 and Unix users 

should use the script named 

deployAllNewApps.sh

. All existing voice applications are 

unaffected and calls can now be received for all new applications. 

Due to the fact that the VoiceXML Server automatically loads all available applications when the 
Java application server is started up, there is no need to run an administration script when new 
applications are deployed on the VoiceXML Server while the application server is not running. 

Note that previously-deployed CVP VXML Server 3.x applications can be directly copied to a 
Unified CVP VoiceXML Server 4.0 environment without being redeployed from Unified CVP 
VoiceXML Studio 4.0 first.  These applications will work just as they did under 3.x, but will not 
provide SNMP or Data Feed information unless the loggers corresponding to those features are 
enabled.  If those features are desired then the applications should first be imported into Unified 
CVP Studio 4.0 where the loggers can be configured, and then the application can be deployed. 
For more information about these loggers and how to configure them, please refer to the 
“Application Logging” section of Chapter 5: VoiceXML Server Log and to the VoiceXML Studio 
User Guide for Cisco Unified Customer Voice Portal. 

There are two separate methods for removing an application from the memory of Unified CVP 
VoiceXML Server while the Java application server is still running. Determining which method 
to use will depend on the operating system and the circumstances behind the application 
removal. 

The first method involves two steps. The first is to delete (or move) the folder holding the 
desired application from the VoiceXML Server 

applications

 folder. The second step involves 

launching the script 

flushAllOldApps.bat

 on Windows or 

flushAllOldApps.sh

 on Unix