This document was generated from CDN thread
Created by: GEOFFREY THOMPSON on 09-06-2009 10:34:01 PM
G'day,
In CVP 3.0 I used to configure C:\Cisco\CVP\Tomcat 4.1\webapps\CVP\WEB-INF\web.xml
<servlet>
<servlet-name>Server</servlet-name>
<servlet-class>com.audium.server.controller.Controller</servlet-class>
<!-- Call Services Servlet-->
<init-param>
<zaram-name>Debug</zaram-name>
<zaram-value>on </zaram-value>
</init-param>
<load-on-startup>0</load-on-startup>
</servlet>
(in the above, put "param" for "zaram" - it won't let me post param)
When Tomcat/Call Services started it would write a warning
*** DEBUG LOG FILES WILL NOW BE PRODUCED ***
and each interaction would produce a file (with an extremely long file name) in the Tomcat logs directory that contained the complete VXML generated by Call Services and sent to the gateway. This was useful to debug complex issues with Say It Smart and custom Voice Elements.
I'm trying to do the same with CVP 7.0, and I don't see this working.
Does it work for any of you? Is there a different way of doing this now?
(EDIT: i was just checking this. An example of the name is 3F28D5E20A58E0AB8C2B0D03ACED297F.txt and it's actually in
C:\Cisco\CVP\Server\logs.)
Regards,
Geoff
Subject: RE: Low level debugging - making Call Services write all VXML in a trace fi
Replied by: Kamesh Chidambaram on 09-06-2009 10:49:26 PM
Hi Geoff,
I haven't tried this on Tomcat. But I have used 'debug voip application vxml inout' on the voice gateway to look at the vxml content and sometimes wireshark on the vxml server. It would be good to look at a log file though.
Kamesh
Subject: RE: Low level debugging - making Call Services write all VXML in a trace fi
Replied by: GEOFFREY THOMPSON on 09-06-2009 11:55:52 PM
Yeah, that was in my mind too. The person doing for whom this form of debugging was going to be useful is not that router savvy.
Regards,
Geoff
Subject: RE: Low level debugging - making Call Services write all VXML in a trace fi
Replied by: Janine Graves on 10-06-2009 12:29:25 AM
Geoff,
It's now called Debug Logging and it's done on an application
basis. No restarting Tomcat.
In Studio, go into the Project / Properties / General tab.
In the Loggers box, click on Add
Enter a Name: VxmlLogs (this will become a subdirectory of the
<appname><em class="moz-txt-slash">/logs/ folder on VxmlServer
Enter the class:
com.audium.logger.application.debug.ApplicationDebugLogger (case sensitive)
Select: Enforce Call Event Order
Then deploy and run the updateApp.bat script.
You'll get one log file
for each call to that application and it'll be in the VxmlServer
directory under applications/<appname><em class="moz-txt-slash">/logs/VxmlLogs/
Janine
Subject: RE: Low level debugging - making Call Services write all VXML in a trace fi
Replied by: GEOFFREY THOMPSON on 10-06-2009 02:09:19 AM
Holy mackeral. That's a bit complicated compared to what we used to do. I suppose some may say that restarting Tomcat was a huge downide but this debug was so verbose you could never use it in production.
But thank you for typing all that in. I suppose I could have found that info in the VXML Server Guide, eh?
Regards,
Geoff
Subject: RE: Low level debugging - making Call Services write all VXML in a trace fi
Replied by: Robert Atkins on 28-07-2009 09:02:40 PM
Janine,
Do you then need to remember to go back to the project's general properties and delete this logger before deploying the application to a production system? And then re-add it back when deploying to your test environment? (We worked that way in the 3.1 environment with it off in production and always on in test.) Kind of ugly.
Is there an easier way to accomplish this?
Thanks,
Bob Atkins
Subject: RE: Low level debugging - making Call Services write all VXML in a trace fi
Replied by: Ranjana Narayan on 29-07-2009 09:20:51 AM
Robert,
The best practice would be to to edit the General Properties of the application in the Studio to either add/delete the DebugLogger and then deploy the app.
An easier way in production environment would be edit the deployed application itself, the settings of the debuglogger is at <CVP_Home>/VXMLServer\applications\<app>\data\application\settings.xml, you should be able to edit it.
Add/Delete the below xml snippet under <logger> element of the file:
<logger_instance name="Debug" class="com.audium.logger.application.debug.ApplicationDebugLogger" enforce_call_event_order="false" />.
You will have to execute the updateapp.bat for the changes to take effect.
Hope this helps,
Ranjana Narayan.
