on 01-25-2014 10:45 AM
David, Only compilers will recognize escape sequences. When passing data through the ExtVXML arrays its simply being added as a string to the submit tag in the VXML coming from VXML Server. The gateway isn't a fan of this and throws an error. There aren't any elegant ways of getting the apostrophe into ICM from an External Script that i know of... you would have to get creative. I've been here and in my case, we simply removed them and ended up with with "Toms Diner."David Wall:I know that Java can do string substitutions, but "Toms Diner" and "Tom s Diner" are not the same as "Tom's Diner". Interestingly, if I hard-code "Tom\'s Diner" into the value for the FromExtVXML0 variable, it won't validate. I would have expected the escape character to be recognized.
This issue causes the call to be dropped - so quite a severe issue.
Yes, you can use custom Java to workaround it - but the Cisco Call Studio application - knowing that an apostrophe is not a allowed character - should by default do this for you.
The issue is - an app can be written which works 99% of the time - but if something is returned from a backend API or you set a variable with an invalid character (i.e. an apostrophe) - when the call returns to ICM, the call is dropped and the ICM script isn't even aware - (it stays at the VXML Server node) - until this node will timeout.
I am surprised that this issue isn't been fixed - and I can confirm it occurs in 12.6.2
Gerry
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: