cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
1324
Views
0
Helpful
0
Comments
cdnadmin
Level 11
Level 11

Subject: RE: debug in Cisco Call Studio
Replied by: Janine Graves on 08-04-2012 11:44:20 AM
The Standalone Builder only does the equivalent of the  Studio 'Deploy' which is basically like a 'compile' command. And it puts the compiled application on the VXMLServer of your selection.

Then you have to tell VxmlServer to load it into memory. This is done in one of the following ways:
a) restart Cisco VXML Server service (windows services window).
b) Or log onto the VxmlServer and run one of the administrative scripts:
C:/Cisco/CVP/VxmlServer/applicatoins/appname/admin/deployApp.bat (if it's a new application) or updateApp.bat (if you've modified from Studio and recompiled).

Then if you have your gateway dialpeers configured (standalone) or dialpeers and ICM routing script configured (comprehensive mode), you'll be able to call in using a telephone.

If this proves too much, then you can test much of the application logic using the Studio Debugger. This bypasses the telephony, and won't retrieve audio files, but you can see the audio files that would display, you can simulate dtmf entry, you can test much of the application. From the Studio Navigator, right click on the app name, select Debug Call Studio Project.

Janine

Subject: RE: New Message from ERWAN TJIA in Customer Voice Portal (CVP) - CVP - All
Replied by: GEOFFREY THOMPSON on 08-04-2012 11:59:26 AM
The first thing to check, in Comprehensive mode, is the Error Log and the Call Server log for your Call Server. See if your GS,Server,V microapp is configured correctly. It will print out the ECC vars necessary to make the CVP VXML application run. Make sure these are what you should have.

Regards,
Geoff
This document was generated from CDN thread

Created by: ERWAN TJIA on 08-04-2012 01:07:27 AM
hi ,
 
I am trying to do chapter 10 of "CVP Getting Start Guide".   Script was validated ok and no error, from Logger also looks fine.
But when I called the 1888-1234  that supposed to trigger the script, it did not gave me anything nor error message.
 
- How to do debug from Call Studio in this case  ?
- any suggestion what to check in this case?
- i am trying to debug from CLI ,  but it keep saying "not a valid path"  ?

buildApp <project path> <deploy path> [-quiet <log file>] [-debug]
 
tks
 
Getting Started

Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community:

Quick Links