Heads Up :
The post you are writing will appear in a public forum. Please ensure all content is appropriate for public consumption. Review the employee guidelines for the community here.
Is there any way to get additional trace from Audium Call Services as it makes in-line XML decisions? I have application logging at "Complete" and only see the exit state. I tried the undocumented Debug feature mentioned elsewhere and it produced the VXML trace files, but the XML decision operates in a different space.
I have about 25 different values of Session.MessageID to check - this is coming from a back-end system - and I am getting some unexpected behaviour. For example, "DE/17" works fine but "DE/07" and "DE/05" cannot be matched and exit out the default.
I'd rather not write a custom Java decision class.
Any assistance appreciated - as always.
Regards, Geoff
Subject: RE: Debugging XML Decision Elements? Replied by: null on 25-08-2005 06:28:03 PM Nothing like replying to one's own posts, eh?
A lunchtime discussion on this ensued - and someone suggested that "/0" looks like the end of a word to Audium and may be the cause of the problem.
I tried escaping the slash in the XML comparison thusly:
Subject: RE: Debugging XML Decision Elements? Replied by: Michael Bochynski on 25-08-2005 07:11:35 PM Hi Geoff,
We will look into this issue. It seems that â¿¿/0â¿¿ is treated as a special escape character in the Decision XML.
Can you confirm, that every data having â¿¿/0â¿¿ cannot e interpreted properly, while everything else is interpreted fine?
Note that we are working on the custom Debug element, which would allow you to print out the Session Data and Element data. This element might be useful for debug purposes. This element should be available by the end of next week, September 2nd in our Sample Java Code section at:
Subject: RE: Debugging XML Decision Elements? Replied by: null on 26-08-2005 02:47:11 PM Can you confirm, that every data having â¿¿/0â¿¿ cannot e interpreted properly, while everything else is interpreted fine?[/quote:a625661253] Thanks for your response, Michael. In fact, some cases with "/0" may work - most confusing. Specifically, "DE/03" does work but "DE/05" does not.
I do have a good workaround though, so I am pretty pleased with myself. 😉
I like the idea of the debug element and look forward to giving it a try.
Regards, Geoff
Subject: RE: Debugging XML Decision Elements? Replied by: Michael Bochynski on 26-08-2005 03:11:18 PM Hi Geoff,
Your findings are very interesting. We will look into it to see whether the values are escaped/encoded/parsed somewhere.
As soon as the Debug element will be ready, I will post the update here. Note that this will be a sample code, provided as-is with full source code.
Regards, Michael
Subject: RE: Debugging XML Decision Elements? Replied by: Michael Bochynski on 01-09-2005 06:29:36 PM Hi Geoff
We have just released a sample Debug element. It allows you to print out to console and/or log to a file Session and/or Element Data. The sample Debug element is available for download in our Sample Java code forum at:
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: