I have an issue with VXML session variables not getting written to the reporting database in CVP 4.0.
This is a CVP 4.0 system with vxml server and reporting server. Everything appears to be configured. Reporting and application reporting is enabled from the Operations console and the inclusive filter is set to include everything and has been saved and deployed to the vxml server. All the servers have been restarted. The only session variables that appear in the vxmlsessionvariable table are the ones that are passed as named value pairs from ICM in the ToExtVXML variables. Is there any additional configuration that needs to be done in Studio or VXML server to get the other session variables to show up in the reporting database?
I don?t know if this makes a difference or not, but the application in question was ported from CVP 3.1 into the 4.0 Studio and deployed and most of the session variables are created in custom elements.
This is quite urgent because the customer needs to be able to report on these session variables.
SIP traces provide key information in troubleshooting SIP Trunks, SIP
endpoints and other SIP related issues. Even though these traces are in
clear text, these texts can be gibberish unless you understand fully
what they mean. This document attempts to br...
Please find the attached HTML document, download and open it on your PC.
This provides an easy to use form where you simply answer a few
questions and it will render the proper jabber-config.xml file for you
to copy/paste. There is built in logic to verif...
CUCM Database Replication is an area in which Cisco customers and
partners have asked for more in-depth training in being able to properly
assess a replication problem and potentially resolve an issue without
involving TAC. This document discusses the bas...