Cisco Support Community
Showing results for 
Search instead for 
Did you mean: 

Welcome to Cisco Support Community. We would love to have your feedback.

For an introduction to the new site, click here. And see here for current known issues.

New Member



For an IVR VXML app running in UCCE 8.x, what's the best way to debug the communication between VXML gateway and VXML server. I just want to analyse the communication as a whole from VXML server's perspective, i.e., http requests received by the VXML server and then the VXML pages returned for all pages returned for an application.

I saw some debug levels like

'debug http client cache' and

'debug http client error'

to be set on the voice gateway. Would that be sufficient or should I setup some debugging on my VXML app as well to see the VXML pages returned.


Everyone's tags (3)
New Member


Perhaps this may help you in your endeavor

Sent from Cisco Technical Support iPad App

New Member


Hi Jason,

Thanks for the link, but this didn't help me much. I actually want to analyze the http request URL received by VXML server and the VXML pages that the server responds.

I tried debug http client all and debug vxml, but didnt' find the right output.

I acutally want to analyze the complete VXML flow of communication from the VXML server's perspective, i.e., what http request it recieved and then what http response it returned.


New Member



Sorry that didnt help. Have you considered using the application debug loggers?

They log into the debugging directory and look like this (this is a partial request for brevity but you get the point). Outside of this you may just need a wireshark capture or something from the VXML server.

Here is a snippet of one of the logs from my lab:


--------- New Page Request ---------


Request Received on:  05/30/2012 22:31:27.371

------- HTTP Request Headers -------

Header Name = "cookie"  Header Value = "$Version=0; JSESSIONID=60060C760B1299364882B18D4CF6E512; $Path=/CVP"

Header Name = "content-type"  Header Value = "application/x-www-form-urlencoded"

Header Name = "user-agent"  Header Value = "Cisco-IOS-C3725/12.4"

Header Name = "connection"  Header Value = "close"

Header Name = "host"  Header Value = ""

Header Name = "accept"  Header Value = "text/vxml, text/x-vxml, application/vxml, application/x-vxml, application/voicexml, application/x-voicexml, text/plain, text/html, audio/basic, audio/wav, multipart/form-data, application/octet-stream"

------ Request HTTP Arguments ------

Parameter Name = "audium_vxml_root"  Parameter Value #0 = "true"

Parameter Name = "namelist"  Parameter Value #0 = ""

Parameter Name = "calling_into"  Parameter Value #0 = "RSM"

--------- VoiceXML Response --------

Response Returned on:  05/30/2012 22:31:27.433" version="2.1">
























Here is a reference from the User Guide for Cisco Unified CVP VXML Server and Cisco Unified CallStudio (page120 (line here:


The Application Debug Logger

At times when debugging an application it would be advantageous to see information concerning

the HTTP requests made by the voice browser and the corresponding HTTP responses of VXML

User Guide for Cisco Unified CVP VXML Server and Cisco Unified Call Studio Release 8.0(1)


Chapter 5: VXML Server Logging

Application Loggers

Server. The Debug Logger creates a single file per call that contains all HTTP requests and

responses that occurred within that call session. The log files are named

debug_logYYYY-MM-DD-HH-SESSIONID.txt where YYYY is the year, MM is the month, DD

is the day, and HH is the hour (in 24-hour time) that the file is created and SESSIONID is the

VXML Server session ID (for example,

debug_log2000-01-01-17- The session ID is

included in the filename to ensure uniqueness of the files.

The debug log contains:

• A timestamp of when each HTTP request was received from the voice browser as well as

when the response was sent back by VXML Server.

• All headers of the HTTP request.

• All arguments passed with the HTTP request, whether they be set via GET or POST.

• The entire VoiceXML page returned in the HTTP response.

• It is recommended to use the Debug Logger only when performing debugging and not in a

production environment as it incurs overhead on the system in creating and managing file

IO and replicating the HTTP response, which must be generated once for the voice browser

and once for each Debug Logger instance.

Note: The Debug Logger does not require the enforce call event order to be turned on,

however without it there could be situations where under load the HTTP requests and responses

are out of order or mixed together in the file.

CreatePlease to create content