Not at all. Have you added the CVP VXML servers to the Ops Console device map as “stand-alone VXML”? If so, you may find this confusing down the track, and may wish to delete them and add them again as CVP VXML servers.

Regards,
Geoff

If you want the CVP Call Server on the same 'server' or system as the VXML Server, then you should uninstall all the Cisco software (and then delete the directories, reboot) and reinstall the CVP software.

Some of the things you'll have to do after installing the CVP software include (You should find this all well documented in the CVP Config and Admin Guide):

1) you'll need to use the Operations Console to 'configure' the Call Server, and the Vxml Server (s) .
2) You'll have to install different tcl files on the VXML gateway (there are different tcl file for standalone vs. comprehensive) and they are installed under the C:/Cisco/CVP/OpsConsole directory
3) Set up your VXML Gateway with Dial Peers for the ICM label used for CVP Routing Client (usually 8111111111),
4) Configure the ICM routing script to send the calls to your Studio application.


VxmlServer and Studio need the least reconfiguration when going from standalone to comprehensive.
In fact, other than the following 2 items, there's little else that I can think of which changes from Standalone to Comprehensive.
Studio differences:
(1) use CVP_Subdialog_Return to allow ICM to transfer calls instead of using the Studio Transfer element and
(2) use CVP_Subdialog_Return to tell ICM to release the call, instead of using a Studio Hangup element to release the call

Janine