CVP/VVB Invoke Subdialog 3rd Party VXML Document fails - connection refused

[terri.rose]

We are trying to invoke a 3rd party VXML document using the Invoke Subdialog node in CVP.  The URL executes successfully and a portion of the VXML document is received (actual size is 7k but only 2k received) in VVB but then a connection error is thrown:  VXMLDocumnet.loadbAndParse().aThread.run(): got vbe (VBEvent type) =error.badfetch: Connection refused (Connection refused); nested exception is:
java.net.ConnectException: Connection refused (Connection refused)

Has anyone successfully invoked a 3rd party VXML document in VVB 12.5 or any other version?

Additional information - after additional testing, we have determined it's the DOCTYPE declaration causing the Connection Refused.  What VVB changes are needed to allow this doc type?  

<!DOCTYPE vxml PUBLIC '-//W3C//DTD VOICEXML 2.1//EN' 'http://www.w3.org/TR/2007/REC-voicexml21-20070619/vxml.dtd'>

[bill.king1]

Is this the size issue you're mentioning? This is for an older version but perhaps something similar?

https://community.cisco.com/t5/collaboration-documents/subdialog-invoke-usage-to-invoke-a-direct-vxml-application-using/ta-p/3613290

[terri.rose]

This is good information but our problem is with the length of the VXML Document itself not the length of the URL and parameters being passed. The VXML document is 7k but the fetch is only returning 2k of the document.

[bill.king1]

I wonder if this defect is talking about your issue or more around audio files, but it might be worth looking into?

https://bst.cloudapps.cisco.com/bugsearch/bug/CSCus07896

[terri.rose]

No, we've been able to determine it's the DOCTYPE declaration which is referencing an internet based DTD and the VVB does not have internet access.  Anyone found any workarounds for this?

[ptindall]

Leave it out.  At the bare minimum, just use this --

<?xml version=\"1.0\" encoding=\"UTF-8\"?>
<vxml version=\"2.1\">
        ... etc ...
</vxml>

[terri.rose]

Unfortunately, this VXML is coming from an internal 3rd party platform, and the vendor is indicating a DOCTYPE should be supported by VVB. This is true but the VVB doesn't have internet access and we don't want to enable external access either. Is there a way for VVB to 'ignore' the DOCTYPE declaration?

[ptindall]

I'm sure you've already considered it but do you have the option to reference the DTD on the same server on which the VoiceXML is located?

[terri.rose]

Yes, we are asking the vendor about that but my thought would be if you can change the DOCTYPE why not simply remove it all together. My other thought would be if VVB could simply ignore the DOCTYPE but I've not found any information on that possibility.

[bill.king1]

I might not be following, but would any option be to have the VVB use an internet proxy to reach this document, if VVB doesn't have direct internet access? It appears that's an option with set speechserver httpsProxy host <hostname> for instance.

[terri.rose]

That is an option but requires an enterprise security exception which we would prefer not to do at this point.

[terri.rose · Accepted solution]

Solution provided by Cisco TAC.

It appears to be a permission issue when VVB accessing the entire path 'http://www.w3.org/TR/2007/REC-voicexml21-20070619/vxml.dtd' which you can check with third party.

Try this work around.

1. On CVP media server IIS path, create a folder path as shown below and create a vxml.dtd file.

                     >>   c:\inetpub\wwwroot\TR\2007\REC-voicexml21-20070619

                               >>   vxml.dtd

2. On VVB configure www.w3.org in host-to-ip entry to point to IIS.

                   admin: show vvb host-to-ip

                    IPAddress      HostName

                    # This file is managed by hosts_mgr.sh

                    127.0.0.1  localhost

                     xx.xx.xx.xx   www.w3.org

Command successful.

3. Copy the contents of vxml.dtd file from 'http://www.w3.org/TR/2007/REC-voicexml21-20070619/vxml.dtd' to the file in IIS.

So this way we fake www.w3.org some internal server from which VVB will get the file.