DOCTYPE is optional, why UCCX still issues Error in logs?

Question

We have a vxml server pointed by UCCX voice browser. I tested a simple vxml app. then found this error in logs.
I believe in UCCX technic docs, it says the DOCTYPE is optional, why it still complains it?
129984: Feb 15 11:10:39.691 EST %MIVR-SS_VB-7-UNK:Task:28000000019 [Error] aa (line:2 column:57) Document root element "vxml", must match DOCTYPE root "null".
129985: Feb 15 11:10:39.691 EST %MIVR-SS_VB-7-UNK:Task:28000000019 [Error] aa (line:2 column:57) Document is invalid: no grammar found.
129984: Feb 15 11:10:39.691 EST %MIVR-SS_VB-7-UNK:Task:28000000019 [Error] aa (line:2 column:57) Document root element "vxml", must match DOCTYPE root "null".
129985: Feb 15 11:10:39.691 EST %MIVR-SS_VB-7-UNK:Task:28000000019 [Error] aa (line:2 column:57) Document is invalid: no grammar found.
Following is the vxml:
<?xml version="1.0" encoding="UTF-8"?>
<vxml xmlns="http://www.w3.org/2001/vxml" version="2.0">
     <form>
       <field name="choice">
                  <prompt>Would you like coffee, tea, milk, or nothing?</prompt>
       <grammar xml:lang="en-US" type="application/srgs+xml" version="1.0" mode="voice">
             <rule id="drinks" >
              <one-of>
                    <item>coffee</item>
                    <item>tea</item>
                    <item>milk</item>
                    <item>nothing</item>
              </one-of>
             </rule>
        </grammar>
       </field>
       <filled>
                  Just a second.
                  Your <value expr="choice"/> is ready.
       </filled>
      </form>
</vxml>

Answer 1

Hi,
that's really strange.
I use a static VXML with a similar structure - no DOCTYPE - and UCCX does not complain it at all.
Can you tell me the exact version of the UCCX (including the minor version).
Thanks.
G.
P.S.: If you have control over the VXML output, can you try inserting the locale to the header like this:
<?xml version="1.0" encoding="UTF-8"?>
http://www.w3.org/2001/vxml" xml:lang="cs-cz">
  etc etc
I recall having a problem with UCCX-Nuance integration if we did not include the lang attribute.