Rajah,
This appears to be an issue with the way those two voice browsers are handling the URL's. It's possible to rearrange things such that the ; and = are no longer in the URL, but this begs the question: what else are those platforms going to get wrong? I'd let the respective vendors know what your problems are, as it's really their responsibility to get their code functioning properly, and in the meantime try a different platform. I use Voxeo's Prophecy <http://www.voxeo.com/prophecy/> quite a bit, and have found only minor incompatibilities with it (nothing on the level of what you're dealing with). It's free for 2-ports and an easy install. Sincerely, Randy Childers OpenMethods From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Rajah Kalipatnapu Sent: Wednesday, July 09, 2008 4:33 PM To: [email protected] Subject: [vtp-dev] VXI* VoiceXML browser,OpenVXML and Tomcat does UTF-8 in URL cause problem? I've created an ivr web app using OpenVXML studio. The process is smooth. I exported it as a webapp and deployed with Tomcat. I'm using vxml browsers VoiceGlue (open source) and VXI* VoiceXML demo versions to prototype and evaluate the solution for our application. The problem we are facint is observed with both the browsers. This is the problem. 1. When the call started the initial/root vxml is downloaded and parsed fine. 2. The next URL sent to Tomcat 3. Tomcat sends 404/402. 4. Call drops. Observations: 1. Actual URL - http://localhost:9090/mediaivrapp/-/next;jsessionid=B75CD6DCECB6A1202F1D 29155C23B5F7?cbb0fc79382a4f039e6f8eb5fef8b1cd=success.filled&ANI=7818712 22&DNIS=617428444 2. URL logged at Tomcat /mediaivrapp/-/next%3Bjsessionid%3DB75CD6DCECB6A1202F1D29155C23B5F7?cbb0 fc79382a4f039e6f8eb5fef8b1cd=success.filled&ANI=781871222&DNIS=617428444 The problem seems to be due to the fact that Tomcat does not support UTF-8 by default. For example VoiceGlue and i6.net voicexml browsers both sending the URL in the form shown in 2. As you see the ";' and "=" characters are converted to UTF-8 Ascii codes by the voice xml browser and this seems to be causing the Tomcat not to map it to the right resource and return 404. Where as if I manually treverse through the VXML using IE it works fine and IE sends the URL in ISO-8859-1 format and does not convert them to UTF-8. This is the peice of information, I found. "ISO-8859-1 to UTF-8. ISO-8859-1 is the default character encoding for servers and browsers according to the HTTP specification section 3.4.1." And it seems Tomcat is also by default using ISO-8859-1. I've modified Tomcat server.xml to add UTF-8 encoing in the Connector. But still it didn't work. This is blocking our validation of OPenVXML and VoiceGlue. I appreciate and help. Thanks in Advance, Rajah No virus found in this incoming message. Checked by AVG - http://www.avg.com Version: 8.0.138 / Virus Database: 270.4.7/1541 - Release Date: 7/8/2008 7:50 PM
_______________________________________________ vtp-dev mailing list [email protected] https://dev.eclipse.org/mailman/listinfo/vtp-dev
