I'm migrating some VXML applications from Avaya MPS to AEP. The VXML documents includes an xml namespace declaration for a JSP tag library which the MPS ignores but the AEP voice browser rejects. The error is reported as "unrecognized attribute xmlns:c". What is AEP voice browser doing different to MPS to determine the validity of namespaces and how can I prevent it rejecting them without having to re-code the applications?
For reference, this is the error including the first few lines of vxml:
@2013-01-07 19:45:06,170||FINE|VB|2705|Session=trtpoc-mpp1m-2013007184505-15|an error was encountered running this application|trtpoc-mpp1m####
@2013-01-07 19:45:06,170|PAVB_03001|ERROR|VB|2705|Session=trtpoc-mpp1m-2013007184505-15|Unable to load VoiceXML DTD. XML parsing error from DOM. System Id: /WeatherDemo/requests, in Line 1, at Column 286, Exception Message: unrecognized attribute - xmlns:c, File Content: <?xml version="1.0" encoding="UTF-8"?><vxml xmlns="http://www.w3.org/2001/vxml" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:c="ivrframeworktaglib" version="2.1" xsi:schemaLocation="http://www.w3.org/2001/vxml
http://www.w3.org/TR/2007/REC-voicexml21-20070619/vxml.xsd"><meta name="generator" content="JSP_BasicAskState_v6"/>
<var name="maxNoMatchPrompts" expr="3" />
<var name="maxNoInputPrompts" expr="3" />
<var name="maxErrors" expr="4" />
Thanks,
