Cisco Cisco Customer Voice Portal 8.0(1)

I'm sorry, we are experiencing difficulties. Please
call back a later time.

•

Place the HelloWorld call from Exercise #1 (assumes you previously
performed Exercise #1 successfully).

Note: If the HelloWorld call goes through, the voice gateway,
VXML server, and Unified Communications Manager are all
working and the issue is with some aspect that is unique to the
customhelloworld implementation.

•

On the CVP server, from C:\Cisco\CVP\VXMLServer\admin, run
status.bat to verify that customhelloworld is running on the VXML
server. You can also see if there are active callers or sessions waiting
for the customhelloworld application.

•

If you are performing the TTS version of this exercise, be sure that
you put text into the TTX box.

•

If you created customhelloworld to play a text message, the TTS
server is a unique link in the customhelloworld exercise. (In the
prior exercise, the HelloWorld application does not require a TTS
server.) Access the TTS server and verify that it is up.

•

If you are performing the non-TTS version of the exercise, be sure
the link to the audio file is typed correctly in the URI box and the
name of the .wav file is spelled correctly.

•

Be sure the wave file you are trying to access (non-TTS version of
the customhelloworld exercise) has been copied to:
C:\Cisco\CVP\VXMLServer\Tomcat\webapps\CVP\audio.

•

Access the voice gateway configuration file and verify that it
properly points to the TTS server. Refer to 

 and to 

.

You left the original TTS response typed into the TTS box of the audio
element (as suggested). The application first attempts to locate and

You call the customhelloworld DN and instead
of the expected holdmusic.wav response, you
hear the TTS response you created earlier.

play the designated audio file. When it cannot do so, it attempts the
text response. Because it is playing the text response, you know that
customhelloworld is working. However, the URI you entered is
probably incorrect.

CVP Subdialog Return - Caller Input Error

The CVP Subdialog Return element requires a yes or no value for its Call Input parameter. In
the screen shot below, the user first left the Caller Input value blank. When the user tried to
"validate" the application, the user received error shown in "Call Studio Problems." The screen
shot shows the user then typed in yes to fulfill the requirement. When the user tries to validate
the application again, the error will no longer be displayed.

Getting Started with Cisco Unified Customer Voice Portal Release 8.0(0)